Very frequent BSODs

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.

RAM - Test with Memtest86+



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.

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

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.

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

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

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.

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.

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.

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

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.