Solved Random BSOD Problem. 0x000000D1, 0x0000001E

[Ngrungebb91]

Just thought of something after checking you system specs again.... Are you OC-ing on that board? If you are, or could be.. You'd be surprised, some people don't even know they are... Please set back to default to test. Also, to be sure check your timings on the ram. I've seen systems crash because f bad ram timings and/or voltages whilst they passed Memtest.

Also, make sure you post back on what you do and don't do as you follw our advise, just so we know what has been done, please.

Yeah i'm overclocking my CPU and RAM (Not RAM Frequency though... RAM is at stock 1600mhz) I know my CPU is fine, because even with the old ram it never gave me problems. I think the RAM QPI is at 1.45+v. Ram Voltage is 1.65V and the timings are 8-8-8-20. the stock timings should be 8-8-8-24. Would all of this really effect it?? I'd rather have my system overclocked because my CPU voltage is at 1.27V @ 4Ghz, i achieved such a low voltage bahaha.

 

[Maguscreed]

Well it would certainly explain why I'm having trouble nailing down a cause through the debugger.

 

[Ngrungebb91]

Well it would certainly explain why I'm having trouble nailing down a cause through the debugger.

Well, what could i do here then?? Reset the timings?? or should i bump up the QPI Voltage..?? cause i know when you have too low of a QPI Voltage it gives blue screens.. but i dont know what kind of STOP's they are. They could be 0x124 for all i know hahah.

BTW. Haven't had a BSOD since last night. They do come randomly though... i've been playing a game for 2 hours now haha.

 

[MvdB]

Hoping you are experienced enough to know what to do when OCing... I would jot down all current oc settings and go back to safe defaults everywhere to prove if that is a stable system. If so proven, next step is small OC steps, one at a time, to prove continued stable running.

But, to sum it up, your typeS of dump variety is mostly memory, OC ing and only sometimes mobo, bios, cpu.

 

[Ngrungebb91]

Hoping you are experienced enough to know what to do when OCing... I would jot down all current oc settings and go back to safe defaults everywhere to prove if that is a stable system. If so proven, next step is small OC steps, one at a time, to prove continued stable running.

But, to sum it up, your typeS of dump variety is mostly memory, OC ing and only sometimes mobo, bios, cpu.

Hmmm... Alright.. ill do that, would you want some bios screenshots to see what you think about my OC settings? Maybe both of you could take a look at it? I based my bios settings off of an i7 guide. So I know i'm not damaging anything because i have low voltages. I mean.. I think the QPI RAM voltage might be too low.. because if its lower than what it should be, it gives BSOD's

 

[Ngrungebb91]

Update... I got a 0x000000FC BSOD (One of the ones you both have looked at) When it restarted.. My network driver gave me errors and my internet icon had an unplugged status.. So it wouldnt let me troubleshoot it, so i had to uninstall my network driver and reinstall it VIA Asus Motherboard disk.. now i'm back online.. Heres a screenshot at device manager when it was not working. Uh... This might prove the Teefer2 theory for all the blue screens also. Even though my network is now running, I still see those Teefer2 errors in device manager.



Update #2. So i uninstalled my current version of endpoint and i got my dad to download me the new version of SEP. I installed it and no more errors in device manager. Now to test for blue screens. Will keep the thread updated.

 

[MvdB]

Was this Teefer problem there during the last few days? Or did it just pop up yesterday/today?
It's a good thing it is fixed, I only wonder what it was exactly as I would have expected this to be shown in the dumps more clearly. Please post back your final results (hoping it does not BSOD anymore) in the coming days. If you did not change any OC settings, only the Teefer thing, we'll study your dumps again to learn why we did not see that in the first place.

 

[Maguscreed]

Actually I only noticed teefer because it was failing to unload during the creation of the dump.
That sometimes signifies it's the actual faulting app, even though the debugger will often point to a windows system file during it.
This is just something I picked up after doing a lot of debugging for this site.

Using minidumps is a little hit and miss, but it's better than just wild guessing, the full dump files allow for better trace backs, but they are way to large to deal with easily in these circumstances.

 

[MvdB]

Actually I only noticed teefer because it was failing to unload during the creation of the dump.
That sometimes signifies it's the actual faulting app, even though the debugger will often point to a windows system file during it.
This is just something I picked up after doing a lot of debugging for this site.

Using minidumps is a little hit and miss, but it's better than just wild guessing, the full dump files allow for better trace backs, but they are way to large to deal with easily in these circumstances.

Saw that too, but only on the last one, other recent ones (after ram replacement) showed no problems unloading teefer + correct teefer versions. If it was only one dump we wouldn't have more to go on but these multiple dumps that did not consistently show the same unload probs.. that's strange.
Which is why I ask the extra question on how long the OP has has device driver excl marks on Teefer in Devices...
Would you have seen Teefer as a problem in the third to last dump?

 

[Maguscreed]

Well I stopped going over the dumps when I was told the machine had be clocked.
It just introduces too many possibilities. I can't comment on the entirety of the dumps.
I don't use a auto dump file scanner, I actually view them personally in the debugger console myself.

 

[MvdB]

Well I stopped going over the dumps when I was told the machine had be clocked.
It just introduces too many possibilities. I can't comment on the entirety of the dumps.
I don't use a auto dump file scanner, I actually view them personally in the debugger console myself.

So do I... takes some time though

 

[Ngrungebb91]

Was this Teefer problem there during the last few days? Or did it just pop up yesterday/today?It's a good thing it is fixed, I only wonder what it was exactly as I would have expected this to be shown in the dumps more clearly. Please post back your final results (hoping it does not BSOD anymore) in the coming days. If you did not change any OC settings, only the Teefer thing, we'll study your dumps again to learn why we did not see that in the first place.

I honestly dont know how long this teefer problem has been going on. To me, it seems like it was a major problem since it messed up my network drivers as i posted earlier hahah. Thank god thats over now. I am still overclocking, do my clocks look stable to you? No blue screens in the last 11 hours since i reinstalled the SEP.

 

[MvdB]

They look stable, but to be honest, that is near to impossible to say from a distance, without having your setup at hand. The best way to get to a stable configuration is to have the patience to try ONLY one thing at a time and test, test, test. Then, only if confirmed stable, try the next change....

 

[Ngrungebb91]

They look stable, but to be honest, that is near to impossible to say from a distance, without having your setup at hand. The best way to get to a stable configuration is to have the patience to try ONLY one thing at a time and test, test, test. Then, only if confirmed stable, try the next change....

Ahh okay, yeah i understand. Well if i get anymore BSOD's ill put everything back to stock and post the STOP code so we can try to figure it out. Thanks for everything haha.

 

[Ngrungebb91]

Alright its been a few days and 0 i repeat 0 blue screens have occured (hope i didnt jynx it lmao) So i'm going to mark as solved. Thanks for all of your help!

 

[MvdB]

My pleasure!