BSOD 5x a Day

Can anyone check this out not sure whats causing it memory managemnet errors attached are the logs its been happening alot lately.

Thanks very much

Lets start here. These were Related to SNTUSB64.SYS Sentinel System USB Driver from SafeNet, Inc. Yours is from 2008 literally years before win 7 came out. Remove and replace with Microsoft Security Essentials


Symantec is a frequent cause of BSOD's. I would remove and replace it with Microsoft Security Essentials AT LEAST TO TEST


http://us.norton.com/support/kb/web_...080710133834EN

Microsoft Security Essentials - Free Antivirus for Windows

Thank you for your response.

I removed Sentinel System USB Driver updated it to 5/20/2011 vers 7.5.7.0

Removed Norton Installed Microsoft Security Essentials

mystic1111 said:

Thank you for your response.

I removed Sentinel System USB Driver updated it to 5/20/2011 vers 7.5.7.0

Removed Norton Installed Microsoft Security Essentials

Let us know how you are doing and if you still crash upload them to us

Ken

Will do so far this morning no BSOD !!

Ken
Just got another BSOD attached are the latest files. Thanks so much for helping me with this.

mystic1111 said:

Ken
Just got another BSOD attached are the latest files. Thanks so much for helping me with this.

Now we are getting somewhere.




These crashes were caused by memory corruption/exception (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 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.

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.

Old drivers needing updating

Code:

Sentinel64.sys    6/2/2008 1:14:55 AM    fffff880`07304000    fffff880`0732a000    0x00026000    0x48438fdf                            
Sahdad64.sys    10/27/2008 10:56:11 PM    fffff880`01b97000    fffff880`01ba2000    0x0000b000    0x49068d5b                            
Saibad64.sys    10/27/2008 10:56:15 PM    fffff880`01b8e000    fffff880`01b97000    0x00009000    0x49068d5f                            
SaibVdAd64.sys    10/27/2008 10:56:20 PM    fffff880`0442f000    fffff880`04439000    0x0000a000    0x49068d64                            
mcdbus.sys    2/24/2009 5:34:07 AM    fffff880`0ff82000    fffff880`0ffbe880    0x0003c880    0x49a3cd1f                            
ASMMAP64.sys    7/2/2009 4:13:26 AM    fffff880`02ad5000    fffff880`02add000    0x00008000    0x4a4c7a36

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

i let the mem test run over night here is the results not sure what all this means but dont look good.

mystic1111 said:

i let the mem test run over night here is the results not sure what all this means but dont look good.

Points either to the memory or the mobo slot it is in. Try one stick at a time and with a known good try each mobo slot to determine which.