Windows 7: Random BSOD Problem. 0x000000D1, 0x0000001E

Hello, for the past month or so.. I've been getting random BSOD's around 2-3 times a day.. mostly containing 0x000000D1 and 0x0000001E. I recently changed my ram from a 4GB GSKILL set to a 10GB Corsair Dominator set because of a 0x124 BSOD that the Gskill gave me.. it was defective.. Now I have been reading alot into these BSOD's and i have tried the following...

• Doing a "clean" installation on the Nvidia Graphics driver
• Scanning MalwareBytes.. (found 1, deleted.. but BSOD's still continue)
• Antivirus Scan (found nothing)
• Sfc/ Scannow scan
• Memtest86 (6 passes, found no errors)
• SPTD Driver Removal

My two last resorts if no one can find a solution would be to do a bios flash to a new version (I dont know how it would effect BSOD's though.. OR simply reinstall windows..



Here are the BSOD reports.. Someone please help me here.

It seems... at least from the couple of dumps I looked at (you have a massive number of them)
that norton has gone retarded on you.
Uninstalling/reinstalling may fix the issue.
If you are running mbam in active mode. You'll need to pick between norton or mbam if they run at the same time one is always going to wind up crashing the other.

Anyhow you can also see here, as you're having a similiar issue with Teefer2.sys locking.
Teefer2.sys BSOD | Symantec Connect Community

Ive had this antivirus since i started the build of the computer. No BSOD back then (a year ago) and I only enabled Malwarebytes just for one scan. Thanks for the link. Ill look into that! I'm kinda confused on how to solve this with the SEP problem... I might just uninstall/reinstall it. Can you or anyone else find any issues in my dump files?

I wasn't suggesting you get rid of it, my experience with norton users is they are all too loyal to ever consider dumping it even if, ...and this has actually happened, it renders the computer completely unusable, ..so no I wasn't suggesting you get rid of it.

Just for good measure you can always run this just to check for errors too. It's simple and doesn't take much time.
SFC /SCANNOW Command - System File Checker

What is interesting is that, among your many dumps with nearly just as many error codes, there is also a stop 124.
Most other codes are unclear as to the reason. They could point to drivers or BIOS/Hardware. 124 is normally much clearer: hardware. And if some hardware, like memory is off, it would explain the many different codes you got.

Your .dmp file shows a stop error of 0x124 which is a general hardware error .

A "stop 0x124" is fundamentally different to many other types of bluescreens because it stems from a hardware complaint.

Stop 0x124 minidumps contain very little practical information, and it is therefore necessary to approach the problem as a case of hardware in an unknown state of distress.

You can read more on this error and what to try here... Stop 0x124 - what it means and what to try Stop 0x124 - what it means and what to try

I would start some hw checking, beginning with the most probable one: memory
Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder or another ISO burning program.

Boot from the CD, and leave it running for at least 5 or 6 passes.

Just remember, any time Memtest reports errors, it can be either bad RAM or a bad motherboard slot.

Test the sticks individually, and if you find a good one, test it in all slots.

RAM - Test with Memtest86+

Ahhh okay, gotcha hahah. Running it now.... andd. No Errors found.

Hmm really?? Is this dump report recent? I just did a memtest this morning. Left it for 6 passes and no errors. I did the same thing last night too. no errors.. Could there still be a memory issue? I've done so much research on all of these blue screens and still nothing will help.

Well, regretfully memtest86 doesn't provide 100% clarity but lets trust it for now. next would be CPU:
Try this free stress test: Free Software - GIMPS

The dump was one in july 26th... seems recent enough, or have you changed HW since then?

Okay, ill go do the CPU test.. and yeah.. i have. On the 29th, i took out the defective GSkill Memory and installed the Corsair set.. so, that dump report mustve been about the bad memory.

ps... your memtest time, I know you are in another time zone... which is why I don't understand. You did a memtest this morning?? It is earlier there that here. Memtest 6 passes takes approx 6-8 hours on a fast machine.... You sure you didn't only do the first 6 steps in the first pass? It is a common mistake, please don't feel insulted by my question.