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: BSOD Bug Check String keeps changing

09 Aug 2012   #1
Psyfa

Windows 7 Ultimate x64
 
 
BSOD Bug Check String keeps changing

Hi;
My PC has been running fine for the last couple of months, but the last 2 weeks I've had multiple BSOD's. I've taken it in to be fixed and it came back with the same problem!
I downloaded BlueScreenView and all the dump files have differing bug check codes. I updated my bios, graphics drivers and as many other drivers I could think of, but still no luck.

Any help is really appreciated!


My System SpecsSystem Spec
09 Aug 2012   #2
FredeGail

Microsoft Windows 7 Ultimate: x64 (SP1)
 
 

Hello Psyfa and welcome to Sevenforums.

BSOD Analyse

Daemon Tools

Daemon Tools can be a BSOD causer on some systems, I'd suggest you to uninstall it. Instead of Daemon Tools you could use MagicISO.

Code:
DAEMON Tools Lite	"c:\program files (x86)\daemon tools lite\dtlite.exe" -autorun	Andreas-PC\Andreas	HKU\S-1-5-21-3255088738-302951698-1628164408-1000\SOFTWARE\Microsoft\Windows\CurrentVersion\Run
Memory / 3rd party driver related

Looking at your bugcheck it's likely that a memory corruption event was triggered. Though a driver could be causing the memory to be borked, but we're usually suggesting a memory test before moving forward. Do a scan with Memtest86+. Memtest is a scanner that'll check your sticks for errors.

warning   Warning
Note that the below instructions may break your WARRANTY rules. If you're unsure check manuals, separated warranty papers, stickers on computer for secure permission.

To ensure that we'll know if it's the slots on the motherboard that's broken, or the sticks itself - we have a little procedure we'll recommend. Remove 1 stick, scan the other with Memtest in the current slot. After 7 passes, move the stick to another slot and scan, and so on and so forth until you've scanned all the sticks, and all the slots, one by one.

Memtest86+ - Advanced Memory Diagnostic Tool

Best Regards,
Frederik.
My System SpecsSystem Spec
10 Aug 2012   #3
Psyfa

Windows 7 Ultimate x64
 
 

Thanks Frederik;

I'll do that as soon as I can and get back to let you know what happens.
My System SpecsSystem Spec
10 Aug 2012   #4
FredeGail

Microsoft Windows 7 Ultimate: x64 (SP1)
 
 

You're welcome.

Take all the time you'll need.

Best Regards,
Frederik.
My System SpecsSystem Spec
13 Aug 2012   #5
Psyfa

Windows 7 Ultimate x64
 
 

Hi again;
Ok, I tested my ram using memtest and got no errors. I didn't follow the procedure you suggested, what I did was test the ram without removing a stick, to see if an error would pop up if both sticks were tested simultaneously . I ran 7 passes and the sticks both checked out clean.

Can I assume the ram is good even though I didn't follow the procedure?

Thanks again.
Regards;
Andreas
My System SpecsSystem Spec
13 Aug 2012   #6
FredeGail

Microsoft Windows 7 Ultimate: x64 (SP1)
 
 

Yes, you'll be fine.

Let's run Driver Verifier.
Quote:
Using Driver Verifier is an iffy proposition. Most times it'll crash and it'll tell you what the driver is. But sometimes it'll crash and won't tell you the driver. Other times it'll crash before you can log in to Windows. If you can't get to Safe Mode, then you'll have to resort to offline editing of the registry to disable Driver Verifier.

So, I'd suggest that you first backup your stuff and then make sure you've got access to another computer so you can contact us if problems arise.
Then make a System Restore point (so you can restore the system using the Vista/Win7 Startup Repair feature) - and create a System Repair Disc (Win7) if you don't have a full installation DVD.
You can do this by going to Start...All Programs...Maintenance...Create a System Repair Disc (don't forget to test the disc to make sure it works).

For Vista, you can download the repair discs from different websites. If unable to locate them, shoot me a PM and I'll point you to them.
For Win8, BSOD's are different - and we'll have to adjust how we do this with them.

Also, to ensure that you can recover, here's another couple of additional steps:
- Get to the Safe Mode menu (rapidly tap F8 just before the Windows splash screen comes up). Scroll down to and select "Disable automatic restart on System Failure"
- Get the RED information from this picture (in particular we will need the name of the file that the error occurred in):
Picture of a BSOD

Then, here's the procedure to run Driver Verifier:
- Go to Start and type in "verifier" (without the quotes) and press Enter
- Select "Create custom settings (for code developers)" and click "Next"
- Select "Select individual settings from a full list" and click "Next"
- Select everything EXCEPT FOR "IRP Logging", "Force Pending I/O Requests" and "Low Resource Simulation" and click "Next" ("Special Pool" may be able to be used depending on amount of RAM and errors being seen. In situations with small amounts of RAM, DO NOT select it),
- Select "Select driver names from a list" and click "Next"
Then select all drivers NOT provided by Microsoft and click "Next"
- Select "Finish" on the next page.

Reboot the system and wait for it to crash to the Blue Screen. Continue to use your system normally, and if you know what causes the crash, do that repeatedly. The objective here is to get the system to crash because Driver Verifier is stressing the drivers out. If it doesn't crash for you, then let it run for at least 36 hours of continuous operation (an estimate on my part).

Reboot into Windows (after the crash) and locate the memory dump file. If present, turn off Driver Verifier by going back in and selecting "Delete existing settings" on the first page. Then, zip up the memory dump file(s) and upload them with your next post. If no dump files were generated, post back for further suggestions.

If you can't get into Windows because it crashes too soon, try it in Safe Mode.
If you can't get into Safe Mode, try using System Restore from your installation DVD to set the system back to the previous restore point that you created.

If that doesn't work, post back and we'll have to see about fixing the registry entry off-line:
Code:
Delete these registry keys to stop Driver Verifier from loading (works in XP, Vista, Win7):
        HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\VerifyDrivers
        HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\VerifyDriverLevel
Best Regards,
Frederik.
My System SpecsSystem Spec
13 Aug 2012   #7
Psyfa

Windows 7 Ultimate x64
 
 

hello Frederik;
Thanks, I'll try that and let you know what happens
My System SpecsSystem Spec
14 Aug 2012   #8
Psyfa

Windows 7 Ultimate x64
 
 

Hi frederik,
OK, i think driver verifier worked, because I found the memory.dmp file. Only problem now is that it is 97MB when compressed. The original file is more than 500 MB.
I tried opening it with bluescreenview, but there is not much to see there,
so I attached a screeshot of the bluscreenview report.

I apologise if I'm making some rookie mistakes here , this is my first build.

Regards;
Andreas
My System SpecsSystem Spec
14 Aug 2012   #9
FredeGail

Microsoft Windows 7 Ultimate: x64 (SP1)
 
 

Quote   Quote: Originally Posted by Psyfa View Post
Hi frederik,
OK, i think driver verifier worked, because I found the memory.dmp file. Only problem now is that it is 97MB when compressed. The original file is more than 500 MB.
I tried opening it with bluescreenview, but there is not much to see there,
so I attached a screeshot of the bluscreenview report.

I apologise if I'm making some rookie mistakes here , this is my first build.

Regards;
Andreas
Hello Andreas!

There was definitely a verifier violation at this point. Do you have small memory dumps enabled? (to ensure
Quote:
To ensure minidumps are enabled:

* Press Start, in the Search Box type: "sysdm.cpl" (without the quotes), press Enter.

* Select the Advanced tab, click on Startup and Recovery Settings.
* Ensure that Automatically restart is unchecked.
* Under the Write Debugging Information headline select Small memory dump (256 kB) in the dropdown box.
* Ensure that the Small Dump Directory is listed as %systemroot%\Minidump.
* OK till you're out of the dialogue.
* Reboot if changes have been made.
Either way just let it crash once or twice more and see if the size has changed at all.

Thanks for your effort,
Frederik.
My System SpecsSystem Spec
15 Aug 2012   #10
Psyfa

Windows 7 Ultimate x64
 
 

Hi Frederik
I managed to get a useable dump file that points to ntoskrnl.exe+5b1fd. So far my PC has only crashed once and has been running for a while.
My dumpfile is attached, hope this helps!

Regards;
Andreas
My System SpecsSystem Spec
Reply

 BSOD Bug Check String keeps changing




Thread Tools



Similar help and support threads for2: BSOD Bug Check String keeps changing
Thread Forum
BSODs ntoskrnl.exe, many different Bug Check String. BSOD Help and Support
BSOD after changing already changing rams BSOD Help and Support
BSOD during Battlefield 3, changing bug check string BSOD Help and Support
Storing a string of characters under one key? General Discussion

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 08:50 AM.
Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App