• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

Blue screen errors

Maximilian

Maximilian

Lifer
Ok, ive tried almost everything, which leads me to believe this is a hardware fault. I havent got parts to switch in/out to test though.

Ive been getting random blue screens every day for about a week now, some days it happens once, others itll happen more often, random suggests PSU problem, but its a seasonic S12 500w! it shouldnt be doing that. I havent got one to switch out with, so what i need is some way of determining what caused the bluescreens.

Theyve varied between DRIVER IRQL NOT LESS OR EQUAL, to BAD POOL CALLER and STOP AT -big random number-

Steps ive taken:
1. Removed overclock
2. Reinstalled mobo drvers
3. Reinstalled cpu drivers
4. Reinstalled graphics card drivers
5. Reinstalled audigy 2 ZS drivers
6. Got angry and hit keyboard
7. Removed all USB deviced except the mouse, keyboard is PS2.

I have about 10 memory dump files but i have no idea how to view them, and even if i did i wouldnt know what to do. Can anyone help with this please? Rigs in sig. Its the main one.
 


The guys that analyze the dumps here at MS have a rule of thumb (but not hard-set law) that they use:

more than 3 types of stop codes on the same box is almost always a hardware failure.

If you are seeing this and have also been overclocking this might not be good 🙁


Try underclocking (yea I know it sucks) for a while and disconnecting any hardware that you absolutely don't need. See if the Stops clear up, then add back hardware, then clock back to normal. Might help isolate what hardware or if you have possibly blown a cpu.

Memory diagnostics would also be a very good idea at this point.
 
Thanks dude ill get right on it. Im gonna put this box in another room and leave it running memtest and underclock the cpu too. Ill use my dual cpu for now.

See if it is the cpu, is that how a damaged cpu would behave? Ive never dealt with it before.
 
Originally posted by: Soviet
Thanks dude ill get right on it. Im gonna put this box in another room and leave it running memtest and underclock the cpu too. Ill use my dual cpu for now.

See if it is the cpu, is that how a damaged cpu would behave? Ive never dealt with it before.
Click to expand...

There is no rhyme or reason to how a damaged CPU behaves. Most often you get just complete failures to Post or boot. Sometimes you get really severe stability issues (bluescreens etc). Spontaneous reboots with no bluescreen etc etc.

The most insideous CPU damage results in bitflips... single bit of data getting flipped from 0 to 1 or vice versa.. could be in a register, could be a parameter in a function is supposed to get one thing but a biflip makes it get another. These usually manifest as bluescreens and typically the driver getting blamed in the crash wasn't really at fault.

Bitflips are common in overclocking because you end up making the tolerances for edge detection so tight that a tiny voltage deviation that would otherwise be harmless now causes a failure.
 
You must log in or register to reply here.

TRENDING THREADS

Back
Top