Solved Very frequent BSODs

xDeathSwitchx · Apr 10, 2012

- Win 7 Ultimate 64 bit
- the original OS was Win 7 Home 64 bit
- Full Retail

- System is about 4 years old but I upgraded the PSU and Graphics card a year ago
6 months ago HP replaced the motherboard
- I installed Win 7 Ultimate a few months ago.

A bit about my computer specs:
Win 7 Ultimate x64
Nvidia GTS 450
750w PSU
AMD Athlon II quad-core processor

Time stamps may be incorrect. Ever sense I got my computer back from HP the time clock never stayed right. I tested the CMOS battery and it appears to be brand new and installed correctly.

I had to run the Windows_NT6_BSOD application in safe mode if that matters. I'm posting this from my brothers PC because mine fails to say on for 15 mins.

There is nothing I am really doing that BSOD will appear. I can turn my computer on and let it idle and it wall BSOD. I have managed to copy down the following error codes.

0x00000024 - ntsf.sys
0x0000001e - eamonm.sys
0x00000019 - BAD_POOL_HEADER
0x0000003B - SYSTEM_SERVICE_EXCEPTION

Thank you for your help

JMH · Apr 10, 2012

These crashes were caused by memory corruption/exception (Cx05) probably a driver.
Please run these two tests to verify your memory and find which driver is causing the problem.

* If you are overclocking anything reset to default before running these tests.
In other words STOP!!!

* If you have Raid update its Driver.

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

Any errors are indicative of a memory problem.

If a known good stick fails in a motherboard slot it is probably the slot.

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

Driver verifier

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

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 "Special Pool", "Force Pending I/O Requests" and "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.

Reboot into Windows (after the crash) and turn off Driver Verifier by going back in and selecting "Delete existing settings" on the first page, then locate and zip up the memory dump file and upload it with your next post.

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.

xDeathSwitchx · Apr 10, 2012

Thank you for the help. I'll do this and then post back here with the results

zigzag3143 · Apr 10, 2012

Many, many, old drivers from as far back as 2005. Your problem stems from a memory issue probably caused by one of them.

Please update the below. Also update your ESET as it is named in one of the crashes

Code:

MarvinBus64.sys    9/23/2005 5:17:03 PM                                
emScan64.sys    6/21/2007 8:51:28 PM        
emFilter64.sys    6/21/2007 8:51:31 PM         
emDevice64.sys    6/21/2007 8:51:44 PM                                
emAudio64.sys    8/31/2007 5:15:32 PM        
Tpkd.sys    5/21/2009 5:36:18 PM                                            
nvstor64.sys    6/22/2009 6:23:37 PM        
nvsmu.sys    6/29/2009 3:36:37 AM

How To Find Drivers:

- search Google for the name of the driver
- compare the Google results with what's installed on your system to figure out which device/program it belongs to
- visit the web site of the manufacturer of the hardware/program to get the latest drivers (DON'T use Windows Update or the Update driver function of Device Manager).
- if there are difficulties in locating them, post back with questions and someone will try and help you locate the appropriate program.

Click to expand...

- - The most common drivers are listed on this page: Driver Reference Driver Reference
- - Driver manufacturer links are on this page: Drivers and Downloads

EDIT::::

One more thing of note. You have dtsoftbus01.sys (Virtual Bus Driver from DT Soft Ltd) installed and it is often the source of trouble. I would remove it as well

xDeathSwitchx · Apr 10, 2012

The only two drivers I don't know how to update or what to do with is
dump_nvstor64.sys
nvstor64.sys

The drivers and downloads page gives me the following message:

driver created to provide disk access during crash dump file generation
Windows Update or 3rd party driver manufacturer, depending on the source driver

But I'm gonna try to update the rest of them right now

zigzag3143 · Apr 10, 2012

xDeathSwitchx said:
The only two drivers I don't know how to update or what to do with is
dump_nvstor64.sys
nvstor64.sys

The drivers and downloads page gives me the following message:

driver created to provide disk access during crash dump file generation
Windows Update or 3rd party driver manufacturer, depending on the source driver

But I'm gonna try to update the rest of them right now

My fault. Sorry about that. Was so busy editing my post to add another driver I missed it. Forget about the dump_nvstor64.sys. The nvstor64.sys you should do.

xDeathSwitchx · Apr 10, 2012

zigzag3143 said:
EDIT::::

One more thing of note. You have dtsoftbus01.sys ([/B]Virtual Bus Driver from DT Soft Ltd) installed and it is often the source of trouble. I would remove it as well

Okay, should I just run the normal Daemon Tools uninstaller or use a different unistaller program to remove it?

zigzag3143 said:
My fault. Sorry about that. Was so busy editing my post to add another driver I missed it. Forget about the dump_nvstor64.sys. The nvstor64.sys you should do.

I'm having a hard time finding nvstor64.sys update. But I'll see if it updates when I update my graphics card drivers.

xDeathSwitchx · Apr 10, 2012

So far I uninstalled DAEMON Tools and updated all the drivers. I had one BSOD before I updated nvstor64.sys and it was
0x0000003B - SYSTEM_SERVICE_EXCEPTION

But a lot less than before, hopefully I should be good now. I'll run memtest overnight and report with the results. But thank you for all your help again.

zigzag3143 · Apr 10, 2012

xDeathSwitchx said:
So far I uninstalled DAEMON Tools and updated all the drivers. I had one BSOD before I updated nvstor64.sys and it was
0x0000003B - SYSTEM_SERVICE_EXCEPTION

But a lot less than before, hopefully I should be good now. I'll run memtest overnight and report with the results. But thank you for all your help again.

Nvstor64.sys is your storage controller driver. Try re-installing it

xDeathSwitchx · Apr 11, 2012

Okay quick review here. I updated all the drivers listed. I tried to update ESET but it appears to be up to date. After re-installing Nvstor64.sys I got an immediate BSOD when logging into windows after the restart with the error code of 0x00000024. Here's the recent dump files.

zigzag3143 · Apr 11, 2012

xDeathSwitchx said:

Okay quick review here. I updated all the drivers listed. I tried to update ESET but it appears to be up to date. After re-installing Nvstor64.sys I got an immediate BSOD when logging into windows after the restart with the error code of 0x00000024. Here's the recent dump files.

Click to expand...

Well something is amiss.

Eset is still from 2010 and mine says 2012 so I dont think yours is updated. ESET was the process running at the time of the crash.

These drivers still are the same date as before.

Code:

[COLOR=Red]eamonm.sys 12/9/2010 1:29:20 AM ehdrv.sys 12/9/2010 1:29:58 AM [/COLOR] emAudio64.sys 8/31/2007 5:15:32 PM emDevice64.sys 6/21/2007 8:51:44 PM emFilter64.sys 6/21/2007 8:51:31 PM emScan64.sys 6/21/2007 8:51:28 PM [COLOR=Red]MarvinBus64.sys 9/23/2005 5:17:03 PM [/COLOR] [I]nvstor64.sys 6/22/2009 6:23:37 PM [/I]

xDeathSwitchx · Apr 11, 2012

zigzag3143 said:
Well something is amiss.

Eset is still from 2010 and mine says 2012 so I dont think yours is updated. ESET was the process running at the time of the crash.

These drivers still are the same date as before.

Code:

[COLOR=Red]eamonm.sys 12/9/2010 1:29:20 AM ehdrv.sys 12/9/2010 1:29:58 AM [/COLOR] emAudio64.sys 8/31/2007 5:15:32 PM emDevice64.sys 6/21/2007 8:51:44 PM emFilter64.sys 6/21/2007 8:51:31 PM emScan64.sys 6/21/2007 8:51:28 PM [COLOR=Red]MarvinBus64.sys 9/23/2005 5:17:03 PM [/COLOR] [I]nvstor64.sys 6/22/2009 6:23:37 PM [/I]

[/B]

Alright I'm going to break it down here

emAudio64.sys
emDevice64.sys
emFilter64.sys
emScan64.sys
MarvinBus64.sys

They are all Pinnacle Dazzle Instant DVD Recorder DVC Video Device drivers. I use my Dazzle DVC 100 as a webcam but I don't use the instant DVD recorder program so I just uninstalled that and the only one remaining is MarvinBus64.sys. So I'm assuming that is the driver that actually captures the video.

eamonm.sys
ehdrv.sys

Are ESET Nod 32. So I can try to uninstall and re-install and see if that helps.

nvstor64.sys

And this is being a real pain to fix. I uninstalled, restarted. Re-installed, restarted. Then that's when I got the BSOD after logging in.

JMH · Apr 11, 2012

IF you plan on uninstalling Eset do it via...
http://download.eset.com/special/ESETUninstaller.exe

Suggest you install MSE in its place.
Microsoft Security Essentials - Free Antivirus for Windows

xDeathSwitchx · Apr 11, 2012

JMH said:
IF you plan on uninstalling Eset do it via...
http://download.eset.com/special/ESETUninstaller.exe

Suggest you install MSE in its place.
Microsoft Security Essentials - Free Antivirus for Windows

I uninstalled it. Already had MSE

I also installed Avast and Comodo Firewall. I think I should be good with virus protection.

Code:

eamonm.sys    12/9/2010 1:29:20 AM         
ehdrv.sys    12/9/2010 1:29:58 AM            
emAudio64.sys    8/31/2007 5:15:32 PM       
emDevice64.sys    6/21/2007 8:51:44 PM                               
emFilter64.sys    6/21/2007 8:51:31 PM       
emScan64.sys    6/21/2007 8:51:28 PM

None on them listed above are on my computer anymore.

I uploaded a html file from DriverView giving all the details about the two remaining.
MarvinBus64.sys
nvstor64.sys

I cannot seem to update them for the life of me. I honestly think that I'm out of luck with MarvinBus64.sys. It's a SD Capture card driver so I don't think Pinnacle provides support for it anymore. So I may just have to uninstall it and invest in an actual webcam.

But for nvstor64.sys I really don't know why it wont update. I re-installed it and updated my graphics card drivers.

writhziden · Apr 11, 2012

You already had MSE installed? Now you have MSE and avast! installed together?

Your crashes are likely the cause of your security software performing the computer act of yelling at each other. Before further security violence ensues (blue screen crashes), I recommend that you remove avast! and only run MSE. You can try MSE with the Comodo Firewall software, but it may be more stable running with just the Windows firewall.

For better, stable protection, take a look at http://www.sevenforums.com/system-security/206705-good-free-system-security-combination.html

Clarification: When two realtime security programs (programs that are running and protecting the system as it runs) accomplish the same tasks, they will cause conflicts. The system files are accessed at the same time by both security programs and this can result in blue screen crashes. It used to be that some security software would actually flag other security software as malicious and a threat, and that would also cause crashes. The false positives with other antivirus software is now less prevalent, but still possible. Either way, it is best to only have one realtime protection program and one firewall protection program at a time. Standalone scanners like Malwarebytes (the non-trial version/non-pro version) and Superantispyware are okay to have on the system because they only access files during a full/quick scan of the system.

JMH · Apr 11, 2012

xDeathSwitchx said:
JMH said:

IF you plan on uninstalling Eset do it via...
http://download.eset.com/special/ESETUninstaller.exe

Suggest you install MSE in its place.
Microsoft Security Essentials - Free Antivirus for Windows

Click to expand...

I uninstalled it. Already had MSE I also installed Avast and Comodo Firewall. I think I should be good with virus protection.

It is NOT a good idea to have two Anti Virus programs running on your Operating System at the same time.
Conflicting programs slow your computer & may create crashes, freezes etc
More is NOT best.

Would suggest you remove Avast via
http://files.avast.com/files/eng/aswclear5.exe

xDeathSwitchx · Apr 11, 2012

I never realized MSE was a real-time. I thought it was a standalone scanner. Yikes. But that goes to show how much I actually used it. I'll uninstall avast.

zigzag3143 · Apr 11, 2012

xDeathSwitchx said:
I never realized MSE was a real-time. I thought it was a standalone scanner. Yikes. But that goes to show how much I actually used it. I'll uninstall avast.

Strictly from a BSOD perspective MSE causes the fewest, and it is a good, free, lightweight malware app. It is built into Win 8 BTW.

xDeathSwitchx · Apr 12, 2012

I uninstalled MarvinBus64.sys. Re-installed nvstor64.sys, for the 2nd time. I'll see if I get anymore BSOD. Also I ran memtest and it passed 7 times. As for antivirus I have MSE and Comodo Firewall running. If I don't get a BSOD in the next 24 hours we may have my problem solved

But I'm not gonna get my hopes up to quick now

JMH · Apr 12, 2012

If satisfied please mark your thread solved.
Good luck!

Should you get any more BSOD's submit them please.

Solved Very frequent BSODs

New member

My Computer

Banned

My Computer

New member

My Computer

New member

My Computer

New member

My Computer

New member

My Computer

New member

My Computer

New member

My Computer

New member

My Computer

New member

My Computer

New member

My Computer

New member

My Computer

Banned

My Computer

New member

My Computer

Closed by request.

My Computer

Banned

My Computer

New member

My Computer

New member

My Computer

New member

My Computer

Banned

My Computer