Windows 7 Forums
Welcome to Windows 7 Forums. Our forum is dedicated to helping you find support and solutions for any problems regarding your Windows 7 PC be it Dell, HP, Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.


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


08 Aug 2011   #1

Windows 7 Home Premium 64bit
 
 
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.

My System SpecsSystem Spec
.

08 Aug 2011   #2

Microsoft Community Contributor Award Recipient

Windows 7 x64
 
 

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
My System SpecsSystem Spec
08 Aug 2011   #3

Windows 7 Home Premium 64bit
 
 

Quote   Quote: Originally Posted by Maguscreed View Post
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?
My System SpecsSystem Spec
.


08 Aug 2011   #4

Microsoft Community Contributor Award Recipient

Windows 7 x64
 
 

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
My System SpecsSystem Spec
08 Aug 2011   #5

Windows 7 64b Ultimate
 
 

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+
My System SpecsSystem Spec
08 Aug 2011   #6

Windows 7 Home Premium 64bit
 
 

Quote   Quote: Originally Posted by Maguscreed View Post
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
Ahhh okay, gotcha hahah. Running it now.... andd. No Errors found.
My System SpecsSystem Spec
08 Aug 2011   #7

Windows 7 Home Premium 64bit
 
 

Quote   Quote: Originally Posted by MvdB View Post
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+
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.
My System SpecsSystem Spec
08 Aug 2011   #8

Windows 7 64b Ultimate
 
 

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
Quote:
Prime95 Setup:
- extract the contents of the zip file to a location of your choice
- double click on the executable file
- select "Just stress testing"
- select the "Blend" test. If you've already run MemTest overnight you may want to run the "Small FFTs" test instead.
- "Number of torture test threads to run" should equal the number of CPU's times 2 (if you're using hyperthreading).
The easiest way to figure this out is to go to Task Manager...Performance tab - and see the number of boxes under CPU Usage History
Then run the test for 6 to 24 hours - or until you get errors (whichever comes first).
The Test selection box and the stress.txt file describes what components that the program stresses.

The dump was one in july 26th... seems recent enough, or have you changed HW since then?
My System SpecsSystem Spec
08 Aug 2011   #9

Windows 7 Home Premium 64bit
 
 

Quote   Quote: Originally Posted by MvdB View Post
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
Quote:
Prime95 Setup:
- extract the contents of the zip file to a location of your choice
- double click on the executable file
- select "Just stress testing"
- select the "Blend" test. If you've already run MemTest overnight you may want to run the "Small FFTs" test instead.
- "Number of torture test threads to run" should equal the number of CPU's times 2 (if you're using hyperthreading).
The easiest way to figure this out is to go to Task Manager...Performance tab - and see the number of boxes under CPU Usage History
Then run the test for 6 to 24 hours - or until you get errors (whichever comes first).
The Test selection box and the stress.txt file describes what components that the program stresses.
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.
My System SpecsSystem Spec
08 Aug 2011   #10

Windows 7 64b Ultimate
 
 

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.
My System SpecsSystem Spec
Reply

 Random BSOD Problem. 0x000000D1, 0x0000001E




Thread Tools



Similar help and support threads for2: Random BSOD Problem. 0x000000D1, 0x0000001E
Thread Forum
BSOD appearing at random, error 0x000000d1 - storport.sys BSOD Help and Support
BSOD seemingly at random, error 0x000000d1 BSOD Help and Support
Solved BSOD - 0x0000001e - 0x000000d1 BSOD Help and Support
BSOD Error 0x000000d1 & 0x0000003B -Crashes Random BSOD Help and Support
BSOD Random. error 0x000000d1 BSOD Help and Support
BSOD (initially playing BF3) error 0x0000001E and 0x000000D1 BSOD Help and Support
Solved Random BSOD, error 0x000000d1 DRIVER_IRQL... BSOD Help and Support

Our Sites

Site Links

About Us

Find Us

Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd

All times are GMT -5. The time now is 06:57 AM.
Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App
  

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33