Multiple BSOD every day - Various Error Codes

[busler]

I have been having multiple BSODs every day recently. It started about 6 months ago (only a few BSODs a week), but has been getting worse. As described in the posting instructions here is some system spec info:
- System Manufacturer/Model: Dell/Studio XPS 8000
- Operating System: Windows Home Premium x64
- the original installed OS on the system? Yes.
- an OEM or full retail version? OEM
- What is the age of system (hardware)? ~2 years old
- What is the age of OS installation (have you re-installed the OS?) ~2 years old
- CPU: Core i5 750 @2.67 GHz 2.66 GHz
- RAM: 6 GB
- Graphics Card: GeForce GT220
- AntiVirus: Microsoft Security Essentials



I have also attached the requested information listed on the posting instructions by jcgriff2. Please let me know if you need any additional information. Any help would be much appreciated.


Thanks!

 

[zigzag3143]

I have been having multiple BSODs every day recently. It started about 6 months ago (only a few BSODs a week), but has been getting worse. As described in the posting instructions here is some system spec info:
- System Manufacturer/Model: Dell/Studio XPS 8000
- Operating System: Windows Home Premium x64
- the original installed OS on the system? Yes.
- an OEM or full retail version? OEM
- What is the age of system (hardware)? ~2 years old
- What is the age of OS installation (have you re-installed the OS?) ~2 years old
- CPU: Core i5 750 @2.67 GHz 2.66 GHz
- RAM: 6 GB
- Graphics Card: GeForce GT220
- AntiVirus: Microsoft Security Essentials



I have also attached the requested information listed on the posting instructions by jcgriff2. Please let me know if you need any additional information. Any help would be much appreciated.


Thanks!

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


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.

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



2-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 (an estimate on my part).

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.

If that doesn't work, post back and we'll have to see about fixing the registry entry off-line:

Delete these registry keys to stop Driver Verifier from loading (works in XP, Vista, Win7):
        HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\VerifyDrivers
        HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\VerifyDriverLevel

Using Driver Verifier to identify issues with Windows drivers for advanced users


ALSO

Please run the update readiness tool and then update to SP-1


Ensure you install the correct 64 or 32 bit option for your system)
Download the System Update Readiness Tool (64bit)
Download the System Update Readiness Tool (32bit)


Now update to SP-1

Learn how to install Windows 7 Service Pack 1 (SP1)

 

[busler]

Thanks for your quick reply. I took some time to try your suggestions. Memory testing did not show any problems. I ended up reinstalling the video driver to see if this solved the issue. The reliability monitor indicated this may have been the problem. So far, so good! The computer has been running for about a day and we have not had any BSOD. I will definitely add any additional comments if I still have any problems. Thanks again!

 

[zigzag3143]

Thanks for your quick reply. I took some time to try your suggestions. Memory testing did not show any problems. I ended up reinstalling the video driver to see if this solved the issue. The reliability monitor indicated this may have been the problem. So far, so good! The computer has been running for about a day and we have not had any BSOD. I will definitely add any additional comments if I still have any problems. Thanks again!

My pleasure & good luck