• Some users have recently had their accounts hijacked. It seems that the now defunct EVGA forums might have compromised your password there and seems many are using the same PW here. We would suggest you UPDATE YOUR PASSWORD and TURN ON 2FA for your account here to further secure it. None of the compromised accounts had 2FA turned on.
    Once you have enabled 2FA, your account will be updated soon to show a badge, letting other members know that you use 2FA to protect your account. This should be beneficial for everyone that uses FSFT.

Can i get some help deciphering some BSOD's?

C

chockomonkey

[H]F Junkie
2FA
Joined
Oct 11, 2003
Messages
8,454
Trying to troubleshoot the cause of random crashes on my buddy's computer.

He's had varying stop codes, 0x3b a few times, 0x7f a couple times, and a 0x7e. Probably a couple others he didn't tell me about.

I tried to figure out the mini dump debugging, and got as far as loading up the dmp files in dumpchk... however it was telling me that i don't have the proper symbols, and i can't seem to find the answer to this problem on google.

Anyway, the dump files are here, if you have some spare time to burn helping me out:

Code: 
http://files.scottyshideout.com//files/1/dumpfiles/041811-14508-01.dmp
http://files.scottyshideout.com//files/1/dumpfiles/041811-16442-01.dmp
http://files.scottyshideout.com//files/1/dumpfiles/041611-15225-01.dmp
http://files.scottyshideout.com//files/1/dumpfiles/041511-31184-01.dmp
http://files.scottyshideout.com//files/1/dumpfiles/041811-14726-01.dmp
http://files.scottyshideout.com//files/1/dumpfiles/060710-35724-01.dmp

The ones i did open, even though it told me the symbols were incorrect, pointed to ntoskrnl.exe as the cause.

Thanks
 
^^ i hadn't thought of checking there for stop messages... AumHa.org, it turns out, has quite an extensive guide. It's a shame that shit never comes up in google, i spent a lot of time searching these stop codes to no avail.

NOTE: Many users search this site for the word minidump which often accompanies these Stop Message errors. The fact that a memory minidump occurred tells you nothing except what you already know — that there was an error. It is the name of the error condition and its 8-digit number that help you determine the actual error condition.
Click to expand...

Is this correct? I knew the stop code and following conditions were valuable, but my googling showed plenty of threads where ppl were picking apart dmp files and figuring shit out by that process.
 
chockomonkey said:
Is this correct? I knew the stop code and following conditions were valuable, but my googling showed plenty of threads where ppl were picking apart dmp files and figuring shit out by that process.
Click to expand...

In my experience, that's been the case for me: The dump files don't help. It may for others who are more technically inclined or possibly anal but in my personal experience, the age-old method of "trial and error" works well.
 
ooooh, I get to post this twice today.


The OverClockers BSOD code list

0x101 = increase vcore
0x124 = increase/decrease vcore or QPI/VTT...have to test to see which one it is
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 (NB) voltage, GPU issue (most common when running multi-GPU/overclocking GPU)
0x7E = Corrupted OS file, possibly from overclocking. Run sfc /scannow and chkdsk /r
 
You must log in or register to reply here.
Back
Top