PC Error: BSOD (Now With Error Code!!)

Ok, you all know my roommate's PC that we keep having trouble with. Anyway this time it crashed she was able to write down the entire error code. Can anyone make heads or tails of this or know what it means?


Google (so far) isn't too much help. Everything on her PC is up-to-date. Currect service pack for Windows 7, plenty of disk space, all drivers are up-to-date for everything, etc.

I'm just stumped. We finally have a lead though, so if anyone can offer some insight, please share!

I googled it, because that's all I CAN do. Took me right back here! :)

check hd status with linux boot cd
run memtest from flash drive
rotate ram channels/slots and sticks regardless of memtest results
examine motherboard for blown capacitors / liquid damage
etc.

If you have the microsoft development software it will tell you exactly the problem from the minidump that computer creates when it crashes. Windows DDK and use the WinDBG program. move the Windows memory dump to your desktop so that you can access it then press CTRL D to load the dump. Post the result if you don't understand it. The problem is probably a driver issue.

0x01E generally denotes that your vcore is too low



0x0A = unstable RAM/IMC, increase QPI first, if that doesn't work increase vcore

0x1E = increase vcore

0x3B = increase vcore

0x3D = increase vcore

0xD1 = QPI/VTT, increase/decrease as necessary, can also be unstable Ram, raise Ram voltage

0x9C = QPI/VTT most likely, but increasing vcore has helped in some instances

0x50 = RAM timings/Frequency or uncore multi unstable, increase RAM voltage or adjust QPI/VTT, or lower uncore if you're higher than 2x

0x109 = Not enough or too Much memory voltage

0x116 = Low IOH (N voltage, GPU issue (most common when running multi-GPU/overclocking GPU)

0x7E = Corrupted OS file, possibly from overclocking. Run sfc /scannow and chkdsk /r

0x24 = suggests an HDD error but could be IO vCore when overclocking

also could try rolling back to CD drivers if you're using something newer

Cut and paste directly from MSDN:

Bug Check 0x1E: KMODE_EXCEPTION_NOT_HANDLED

The KMODE_EXCEPTION_NOT_HANDLED bug check has a value of 0x0000001E. This indicates that a kernel-mode program generated an exception which the error handler did not catch.
Important Info If You Have Received a STOP Code

If you received a blue screen error, or stop code, the computer has shut down abruptly to protect itself from data loss. A hardware device, its driver, or related software might have caused this error. If your copy of Windows came with your computer, call the manufacturer of your computer. If you purchased Windows separately from your computer, Microsoft provides support. To find contact info for Microsoft or your computer manufacturer, Contact Support.

If you have experience with computers and want to try to recover from this error, follow the steps provided in the Microsoft article Resolving STOP (Blue Screen) Errors in Windows.

These actions might prevent an error like this from happening again:

-Download and install updates and device drivers for your computer from Windows Update.
-Scan your computer for computer viruses.
-Check your hard disk for errors.


Here's the url to the entire page if you need it:
http://msdn.microsoft.com/en-us/library/windows/hardware/ff557408%28v=vs.85%29.aspx

Probably a bad stick of Ram, or one that is going bad potentially. Especially if you have seen this error multiple times.

I'm thinking it has to do with processor not getting power it needs. If i remember correctly I had a Kernel error when I had a bad overclock.