Windows 7 BSOD

oregon

Active Member
Are any of you guys getting BSOD's with 7? I get it very often, and it seems to be linked to watching online video or using iTunes. Use of these things will usually, but not always, lead to a BSOD.

It says something along the lines of "Driver IRQL is less than or equal to" and it dumps the memory, then shuts down. I always get this same message and it happens pretty consistently while doing the above mentioned things.

I have tried reinstalling 7, from the old to the new version, but it still happens. Any idea what might be causing it? I think it is probably a memory problem, but I'm not sure how to check that.
 
The only problem I have with windows 7 is. It does a memory dump and then shuts down my computer. The beta did the same blasted thing. I am running the RC copy now. Not all the time tho, I mostly stay in my windows xp pro x64. Most stable os I have ever used.
 
I get a few random BSOD's from time to time.

IRQ error bsod's

did a mem check & reinstalled 7 seems pretty OK right now, have a few problems with CCC also (well I think it's that, get a few lock ups when first going into 3D mode. Causes some games to crash, others not..
 
Not had any BSOD here...I've had a few Windows Explorer is not responding but vista was Notorious for that too on my system, not happened as many times as it did on vista though.

other than that it's been solid.
 
The only problem I have with windows 7 is. It does a memory dump and then shuts down my computer. The beta did the same blasted thing. I am running the RC copy now. Not all the time tho, I mostly stay in my windows xp pro x64. Most stable os I have ever used.

Yeah, I'm pretty sure that's what mine is doing, and I also avoid 7 as much as possible. I really hope they fix this though.
 
My only problem was a screen freeze with colored grid of the last screen on my monitor. I re-installed windows - and noticed that my Malawarebytes application had a false positive and I deleted a file ( I think windows system file ). After re-installing Windows - and ignoring - rather than deleting the file in question - everything's been running fine
 
Back
Top