Sporadic BSOD while browsing internet or gaming

[SpoonyGundam]

BSODs have been happening pretty randomly for over a year with this computer. Sometimes they'll happen several times a month, and sometimes it takes months before another one happens. I just had three in the last week while either browsing or gaming. That's never happened before, so I'd really like to try and fix whatever's causing this.

 

[koolkat77]

Welcome

You msinfo file is corrupted. Please upload your msinfo32.nfo file. To get this:

• Click on the Start rb:
• Type msinfo32 into the Search programs and files box
• When it opens, go to File, Save
• Save as msinfo32.nfo and save in a place you will remember
• Let it finish the process of gathering and saving the system info
• Right click the .nfo file, click send to compressed (zipped) folder
• Upload the .zip file here.

1. STOP 0x0000001E: KMODE_EXCEPTION_NOT_HANDLED
   
   Usual causes: Device driver, hardware, System service, compatibility, Remote control programs, memory, BIOS​
2. STOP 0x000000D1: DRIVER_IRQL_NOT_LESS_OR_EQUAL
   
   Usual causes: Device driver​
3. STOP 0x0000001A: MEMORY_MANAGEMENT
   
   Usual causes: Device driver, memory, kernel​

Your dumps do not give a probable cause but just blaming windows files, so we'll start with enabling verifier

Verifier puts extreme stress on the drivers, bad ones will cause BSOD. If we change all those drivers we hope for no more BSODs, If you get no BSODs, then its not a driver and we look to hardware. With verifier on your computer may be a little laggy, but actually..its just doing its work.

Driver Verifier

I'd suggest that you first backup your data 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/Windows 7 Startup Repair feature).

In Windows 7 you can make a Startup Repair disk by going to Start....All Programs...Maintenance...Create a System Repair Disc - with Windows Vista you'll have to use your installation disk or the "Repair your computer" option at the top of the Safe Mode menu .

Then, here's the procedure:
- Go to Start and type in verifier 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 Low Resource Simulation and click Next
- 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).

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.
Driver Verifier - Enable and Disable

Information
Driver Verifier runs in the background, "testing" drivers for bugs. If it finds one, a Blue Screen of Death (BSOD) will result; the corresponding dump file will hopefully show the faulty driver.

Driver Verifier monitors kernel-mode drivers and graphics drivers to detect illegal function calls or actions that might corrupt the system. It can subject the drivers to a variety of stresses and tests to find improper behavior.

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.

 

[SpoonyGundam]

Ah, whoops. Sorry about the corrupt msinfo32.

I ran Driver Verifier and it BSODed immediately, so I guess that's a promising start?

Thank you for the help!

 

[koolkat77]

The msinfo file is still corrupted

Upload the text version:
Please upload your msinfo32.nfo file. To get this: Start Menu -> Type msinfo32 into the Search programs and files box -> When it opens, go to File, Save -> Save as msinfo32.nfo and save in a place you will remember -> Let it finish the process of gathering and saving the system info -> Right click the .nfo file, click send to compressed (zipped) folder -> Upload the .zip file here.

 

[koolkat77]

Driver verifier did find one thing.
Daemon Tools, please uninstall it with revo uninstallers advanced mode
Revo Uninstaller Free

2: kd> lmvm dtsoftbus01
start             end                 module name
fffff880`040b3000 fffff880`040f6000   dtsoftbus01 T (no symbols)           
    Loaded symbol image file: dtsoftbus01.sys
    Image path: \SystemRoot\system32\DRIVERS\dtsoftbus01.sys
    Image name: [COLOR="red"]dtsoftbus01.sys[/COLOR]
    Timestamp:        [COLOR="Red"]Thu Jan 13 14:27:08 2011 (4D2EB75C)[/COLOR]
    CheckSum:         00045141
    ImageSize:        00043000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

 

[SpoonyGundam]

I'm not sure what's going on with my msinfo32.nfo file. I'm making sure to let it finish every time.

Daemon Tools is pretty unexpected. I uninstalled it like you said. Should I run Driver Verifier again to see if it catches anything else?

 

[koolkat77]

It's not working. We'll try again later.

Daemon Tools is a known cause for BSoDs. If you search our forum specially the Crashes & Debugging section you'll find out.

For now let verifier be disabled just observe your computer for more crashes and come and update this thread if you have more.

 

[SpoonyGundam]

Alright, I'll let it run normally. The timestamp on dtsoftbus01.sys is shortly before the first BSOD on this computer, so it seems like that was probably the issue.

Thanks again for the help!

 

[SpoonyGundam]

My computer just crashed again!

 

[koolkat77]

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
STOP 0x000000C2: BAD_POOL_CALLER  
Usual causes:  Device driver, ?Memory
BugCheck C2, {7, 109b, 5110301, fffff8a00f2d4f00}
Probably caused by : Ntfs.sys ( Ntfs!NtfsCommonCreate+257b )
Followup: MachineOwner
---------

Post a screenshot with crystal disk info:

• CrystalDiskInfo - Software - Crystal Dew World
• http://www.sevenforums.com/tutorials/9733-screenshots-files-upload-post-seven-forums.html

Run Disk Check on your hard disk for file system errors and bad sectors on it:

• http://www.sevenforums.com/tutorials/433-disk-check.html

Hard drive test both short and long with:

• SeaTools for Windows

Also the DOS version of:

• SeaTools for DOS

Take memtest. Run for 8 passes and test each stick in a know good slot for an additional 6 passes.

• http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html
• Guide to using Memtest86+ - Geeks to Go Forums

The goal is to test all the RAM sticks and all the motherboard slots.

Check your motherboard manual to ensure the RAM sticks are in the recommended motherboard slots. Some motherboards have very specific slots required for the number of RAM sticks installed.

If you get errors, stop the test and continue with the next step.

1. Remove all but one stick of RAM from your computer (this will be RAM stick #1), and run Memtest86 again, for 7 passes.
Be sure to note the RAM stick, use a piece of tape with a number, and note the motherboard slot.
If this stick passes the test then go to step #3.

2. If RAM stick #1 has errors, repeat the test with RAM stick #2 in the same motherboard slot.
If RAM stick #2 passes, this indicates that RAM stick #1 may be bad. If you want to be absolutely sure, re-test RAM stick #1 in another known good slot.
If RAM stick #2 has errors, this indicates another possible bad RAM stick, a possible motherboard slot failure or inadequate settings.
3. Test the next stick of RAM (stick #2) in the next motherboard slot.
If this RAM stick has errors repeat step #2 using a known good stick if possible, or another stick.
If this RAM stick has no errors and both sticks failed in slot#1, test RAM stick #1 in this slot.
4. If you find a stick that passes the test, test it in all the other motherboard slots.

If Part 2 testing shows errors, and all tests in Part 3 show errors, you will need to test the RAM sticks in another computer and/or test other RAM in your computer to identify the problem.

In this way, you can identify whether it is a bad stick of RAM, a bad motherboard, or incompatibility between the sticks.

 

[SpoonyGundam]

I've done everything so far except the long test with SeaTools. No errors found for the hard drive or memory.

I got another BSOD a few minutes ago, though.

 

[koolkat77]

Will take a look at them as soon as I can.
When did you last perform a clean install on this computer? What's the age of all its hardware?

 

[SpoonyGundam]

It's about two years old.

 

[koolkat77]

That's quite long and no wonder your msinfo won't upload. I'd suggest you to consider a reinstall of windows start afresh and tell us if the blue screen problems persist. Remember to back up all the stuff in C drive.

• http://www.sevenforums.com/tutorials/1649-clean-install-windows-7-a.html
• http://www.sevenforums.com/tutorials/219487-clean-reinstall-factory-oem-windows-7-a.html
• http://www.sevenforums.com/tutorials/31402-clean-install-upgrade-windows-7-version.html

Recommended antivirus program for Windows 7 based on stability compared to others:-

• Microsoft Security Essentials - Free Antivirus for Windows
• Malwarebytes - The Free version
• http://www.sevenforums.com/system-security/206705-good-free-system-security-combination.html

Let us know your decision. Good luck.

 

[koolkat77]

Any updates?