BSOD after installing/uninstalling MSI products, stop code 0x0000003b

[kunzy]

Hey folks,

Been a while since I have logged in here.

But I would like some input on fixing this BSOD. It comes about once a day. Random apps just start crashing (IE) and within a few seconds, the computer BSODs. I saw that it can be due to some bad MSI software.

My tech level isn't horrible, I understand a fair bit about windows and computers.

The .zip file is attached as outlined in the instructions. I appreciate any input and help offered.

Computer is win 7 pro x64 bit sp1 MSDNAA obtained
AMD Phenom II X4 955 Black Edition Deneb 3.2GHz Socket AM3
MSI 870A-G54 mobo
GeForce GTS 450 (Fermi)G.SKILL Ripjaws Series 4GB (2 x 2GB) 240-Pin DDR3 SDRAM DDR3 1600


Thanks again,
Kunzy

 

[JMH]

kunzy,
These crashes were caused by memory corruption.
Run these two tests to verify your memory and find which driver is causing the problem.

1-Memtest.

*Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder or another ISO burning program. Memtest86+ - Advanced Memory Diagnostic Tool

*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.

http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html


2-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" (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 "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.

http://www.sevenforums.com/tutorials/101379-driver-verifier-enable-disable.html


3 - Run a SFC as well please.
http://www.sevenforums.com/tutorials/1538-sfc-scannow-command-system-file-checker.html

4.- Please also remove AVG for testing & replace with MSE.
Download tools and utilities | AVG Worldwide

Microsoft Security Essentials - Free Antivirus for Windows

 

[kunzy]

Ohk, got ahead of you with the memtest.
Memtest 86+ 4.00 has successfully passed up through test #8 with no issues. Ran chkdsk to check for data corruption from the BSODs and it came back clean. I have backups set every sunday so I have a full system image ready to go for backup.

I have a laptop available for backup use as well.

I'll get started with step 2 and get back to you.



Thanks for the input thus far.

 

[kunzy]

ok, step 2 has caused stop code C9, won't boot normally. Would you like me to upload an updated .zip file with the reports?


EDIT:
Disabled the driver verifier to resume normal windows operation.

Will run sfc when I am able to resume normal bootup.

EDIT X2:
Running sfc in safe mode makes more sense to me, will do that as opposed to normal boot...


EDIT X3:
Just remembered a little tid-bit. All was well before the MSI live updater and MSI control center. Live updated was fine (though a little buggy) but the control center never ran. Upon initialization, it had errors loading the driver and eventually crashed out. I uninstalled the 2 programs, but is it possible the control center left it's buggy driver in windows?? Is there a program that you recommend to delete drivers like that? Can I do it with the verify tool?


EDIT X4:
sfc returned clean, no issues found

 

[JMH]

!. Would you like me to upload an updated .zip file with the reports?

2. Just remembered a little tid-bit. All was well before the MSI live updater and MSI control center. Live updated was fine (though a little buggy) but the control center never ran. Upon initialization, it had errors loading the driver and eventually crashed out. I uninstalled the 2 programs, but is it possible the control center left it's buggy driver in windows?? Is there a program that you recommend to delete drivers like that? Can I do it with the verify tool?

1. Yes please...

2. MSI Control Center. Description, Utility for PC overclocking, overvotage and power saving.
If you are overclocking return to default.

FYI. Phyxion.net - Driver Sweeper

Also COMPLETELY remove AVG & replace it with MSE for testing.... as stated in my Post 2.

 

[kunzy]

ok, AVG has been uninstalled and replaced with MSE.

Did trial in error on the driver verification. It was the dtsoftbus01.sys from DT Soft Ltd. I assume this is the Daemon tools program I am using for my virtual drives. I enabled only that one and it generated the blue screen that kept windows from fully booting earlier (stop code C9). Should I re-run verification with all selected but microsoft and d-tools driver?

No overclocking options have been set. Running stock since it was built.

EDIT:
I have had D-tools installed since the OS was installed. The only change to that program that I have made in the past week was a change to the skin used for the widget.

 

[kunzy]

Well, I don't have time to sit and tinker with it, too much homework.

I ended up backing up my homework and personal files and re-imaging to a backup about 2 weeks ago. Everything seems to be up and stable so far.

I appreciate the help and will deffinately have to remember some of the tricks to windows 7 you showed me.


Cheers,

Kunzy