Printable View
Has there ever been a difinitive answer to these BSOD crashes?
I had them a lot before. Then I bought a new mobo, hard disk, graphics card (practically rebuilt system) and have started getting them again.
Windows was completely reinstalled on a new Hard Disk.
It's driving me nuts. Could it be the RAM? surely its not a CPU problem, or even a PSU problem.
I've seen it be a lot of things, but it usually comes down to RAM - run a RAM checker on the machine and see what happens.
thought it ment that the system had run out of mem and has had to close used to see it alot when i had 512mb of ram with x64
if it did do that it would use the page file, not just die lol
its usually a ram error, run memtest or put your system to stock
I have had these with bad drivers or graphics cards and faulty graphics cards as well.
Errors like this are caused by anything that windows dosn't agree with, and therefore could quite literally be caused by anything. That said, it will usually be either a driver or hardware setting that is to blame. Some are les obvious than others (i.e. a driver installed by an iteration of ZoneAlarm caused BSOD's for a lot of people), some are just fantastically gob smacking (Windows sometimes quite literally makes a balls up of pre-install and subsequently installs the wrong HAL configuration for your system, which is a certain candidate for BSOD's).
To be quite honest, you can't be helped. You will have to go through a process of elimination.
Along with the brief 1-liner on the bugcheck should be a STOP code and maybe a filename which give a bit more information to work on.
Also, if you check in the Event Viewer and look in the System event log you should find a record along the lines of "Windows has recovered from a bugcheck" and have the details recorded in there.
My only personal experience with IRQL_NOT_LESS_THAN_OR_EQUAL bugchecks has been display drivers (typically nVidia), and upgrading (or sometimes regressing) them has fixed the problem.
I would be more inclined to think it a driver problem than a hardware issue.
i'd reset all the irqs on your bios - do a full flash/restore to defaults - see if that sorts it