BSOD with SLI both playing games and general multitasking on Win 7

Ichimaru · May 3, 2012

Hello,

I'd be so grateful if you could solve this problem. I've just installed a second 560ti in SLI and get constant BSOD both playing games and multitasking.

· OS - Vista/ Windows 7 ? Windows 7
· x86 (32-bit) or x64 ? x64
· What was original installed OS on system? Windows 7
· Is the OS an OEM version (came pre-installed on system) or full retail version (YOU purchased it from retailer)? I purchased from a retailer
· Age of system (hardware) Some less than 3 days old and some about 8 months old
· Age of OS installation - have you re-installed the OS? No, around 8 months old

· CPU - AMD Phenom II 955 3.2GHz
· Video Card - Nvidia 560ti SLI
· MotherBoard - Sabertooth 990FX
· Power Supply - brand & wattage - Corsair HX850 850 watt PSU

· System Manufacturer Custom built
· Exact model number (if laptop, check label on bottom)

zigzag3143 · May 3, 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 a 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.

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

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"
NOTE: You can use Low Resource Simulation if you'd like.
From my limited experimentation it makes the BSOD's come faster.
- 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.

If you are using win 8 add these
- Concurrency Stress Test
- DDI compliance checking

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.

Thanks to JCGriff2 & Usasma.

Sysnative Forums

Driver Reference Table

Click to expand...

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

Driver Verifier

Using Driver Verifier (Windows Drivers)

Ichimaru · May 3, 2012

Thanks a lot for finding close to the cause, seeing as this could take a while and I have to get up for work I will run memtest tomorrow and also Driver Verifier and report any problems to this thread.

Again thanks a lot.

Ichimaru · May 4, 2012

I am currently running memtest86 at home, it'll be running for 9 hours-ish. I am testing with both sticks in their normal slots to see if any errors occur, if they do I'll try one on it's own and that should single out the problem, providing it is a memory fault.

Ichimaru · May 4, 2012

zigzag3143 said:
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 a 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.

Click to expand...

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.

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

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"
NOTE: You can use Low Resource Simulation if you'd like.
From my limited experimentation it makes the BSOD's come faster.
- 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.

If you are using win 8 add these
- Concurrency Stress Test
- DDI compliance checking

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.

Thanks to JCGriff2 & Usasma.

Sysnative Forums

Driver Reference Table

Click to expand...

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

Driver Verifier

Using Driver Verifier (Windows Drivers)

In the attached file I have attached the latest dump file of the crash (I forced it like you stated, did this by enabling SLI and playing a game. Got about 1 minute in and BS'd. This also happens whilst general multi-tasking) and an image file of my computer running 9 hours of memtest86 and getting 5 passes and 0 errors. However, notice how the RAM settings are at 666MHz and the DDR setting at 1333? When mine is suppose to be 1600Mhz, is this normal?

Thanks.

zigzag3143 · May 4, 2012

Not driver verified and related to your video driver.

Ichimaru · May 4, 2012

zigzag3143 said:
Not driver verified and related to your video driver.

Are you saying the dump file isn't correct?

Or that it's not driver verified and that's the problem is related to my video driver? If so, do you know what the driver is that's causing the issue?

Thanks a lot!

zigzag3143 · May 5, 2012

Ichimaru said:
zigzag3143 said:

Not driver verified and related to your video driver.

Click to expand...

Are you saying the dump file isn't correct?

Or that it's not driver verified and that's the problem is related to my video driver? If so, do you know what the driver is that's causing the issue?

Thanks a lot!

Sorry. Either verifier was not enabled or the drivers being verified didnt include the video driver.

Yes the problem is related to the video driver and it is specifically named. That doesnt mean it cant be the card, power, heat, etc.

we need more DMP files to spot trends and having then verified would help.

Ichimaru · May 5, 2012

zigzag3143 said:
Ichimaru said:

zigzag3143 said:

Not driver verified and related to your video driver.

Click to expand...

Are you saying the dump file isn't correct?

Or that it's not driver verified and that's the problem is related to my video driver? If so, do you know what the driver is that's causing the issue?

Thanks a lot!

Click to expand...

Sorry. Either verifier was not enabled or the drivers being verified didnt include the video driver.

Yes the problem is related to the video driver and it is specifically named. That doesnt mean it cant be the card, power, heat, etc.

we need more DMP files to spot trends and having then verified would help.

Oh I see, well during reboot my computer did blue screen and I had to restore, do you think it restored before I modified driver verifier? And when I get the blue screen it always blames it on the file called nvlddmkm.sys

Thanks.

Ichimaru · May 5, 2012

I've zipped up 4 DMP files, hopefully this time it shows the correct information. I followed the DV guide step-by-step. My computer didn't let me boot into windows I had to System Restore, I kept tapping f8 for more options but all that came up was my MOBO options for booting into my HDD or optical. I chose to System Restore, and forced the crash like I said in my last post. I then turned off DV by deleting existing settings, I then zipped up 4 DMP files and these include 3 from yesterday and 1 from the one I did just now.

Thanks for your time.

zigzag3143 · May 5, 2012

Ichimaru said:
I've zipped up 4 DMP files, hopefully this time it shows the correct information. I followed the DV guide step-by-step. My computer didn't let me boot into windows I had to System Restore, I kept tapping f8 for more options but all that came up was my MOBO options for booting into my HDD or optical. I chose to System Restore, and forced the crash like I said in my last post. I then turned off DV by deleting existing settings, I then zipped up 4 DMP files and these include 3 from yesterday and 1 from the one I did just now.

Thanks for your time.

My pleasure.

It does indeed "appear" to blame the video driver each time, but it has two different error codes meaning either the video driver crashed in 2 different ways, or something else is making the video driver crash.

Unfortunately verifier doesnt seem to be enabled on all 4 of these. Can you type erifier /query and note if it says it is verifying the nvidia drivers?

It should not return "no drivers are being verified".

Other things that can be causing/contributing

1-sptd.sys
Please remove any CD visualization programs such as Daemon Tools and Alcohol 120%.

They use a driver, found in your dmp, called sptd.sys, that is notorious for causing BSODs.

Use this SPTD uninstaller DuplexSecure - Downloads DuplexSecure - FAQ

when you're done you can use this Freeware:

MagicISO Virtual CD/DVD-ROM (MagicDisc) in its place

Using MagicISO to create ISO image files

2-Old drivers

Code:

wacommousefilter.sys    2/16/2007 2:12:17 PM                       
netr28ux.sys    8/15/2007 10:50:03 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 Reference Table

Ichimaru · May 6, 2012

zigzag3143 said:
Ichimaru said:

I've zipped up 4 DMP files, hopefully this time it shows the correct information. I followed the DV guide step-by-step. My computer didn't let me boot into windows I had to System Restore, I kept tapping f8 for more options but all that came up was my MOBO options for booting into my HDD or optical. I chose to System Restore, and forced the crash like I said in my last post. I then turned off DV by deleting existing settings, I then zipped up 4 DMP files and these include 3 from yesterday and 1 from the one I did just now.

Thanks for your time.

Click to expand...

My pleasure.

It does indeed "appear" to blame the video driver each time, but it has two different error codes meaning either the video driver crashed in 2 different ways, or something else is making the video driver crash.

Unfortunately verifier doesnt seem to be enabled on all 4 of these. Can you type erifier /query and note if it says it is verifying the nvidia drivers?

It should not return "no drivers are being verified".

Other things that can be causing/contributing

1-sptd.sys
Please remove any CD visualization programs such as Daemon Tools and Alcohol 120%.

They use a driver, found in your dmp, called sptd.sys, that is notorious for causing BSODs.

Use this SPTD uninstaller DuplexSecure - Downloads DuplexSecure - FAQ

when you're done you can use this Freeware:

MagicISO Virtual CD/DVD-ROM (MagicDisc) in its place

Using MagicISO to create ISO image files

2-Old drivers

Code:

wacommousefilter.sys 2/16/2007 2:12:17 PM netr28ux.sys 8/15/2007 10:50:03 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 Reference Table

I typed verifier /query in cmd and it did indeed return that no drivers are being verified.

Also I've uninstalled all burning/ image mounting software and the same crash and BS errors still occur.

Thanks.

zigzag3143 · May 6, 2012

I didnt think it was enabled. Please re-read the instructions and enable it. If you have BSOD's upload the the DMP's

Ichimaru · May 6, 2012

zigzag3143 said:
I didnt think it was enabled. Please re-read the instructions and enable it. If you have BSOD's upload the the DMP's

Ah, obviously it needs to be verified for you to see in the DMP file. But the only reason they're not verified atm is because I've deleted by current settings on DV because that's what the instructions state:

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

But like I said, after enabling it I can't boot Windows. It just blue screens and I can't get into safe mode because f8 just brings up boot options for my mobo (I could change the hotkey?). So I end up using the Repair System disc I created but it can't repair Windows and I have to system restore which means I restore the system to a point in time before DV was enabled.

Thanks.

EDIT: This has been solved, with this board you have to be extremely accurate in pressing f8 otherwise the mobo boot options appear. I'll try DV again.

~Latest: Went through all of the step-by-step instructions which are not hard at all. Restarted my computer for the changes to take effect I then tried to boot windows and crashed at the logo screen, I then booted in safe mode which worked. BUT I can't enable SLI because the NVIDIA control panel isn't there in safe mode and that is the only thing that makes me BS. AND when I was in safe mode I typed verifier /query in cmd again and it should be enabled right? But it returned that no drivers were being verified. In my eyes from that there is no way round finding out what driver it is now? Unless there's another way. I'm really considering a clean install of Windows 7.

writhziden · May 14, 2012

Until you remove Daemon Tools and/or alcohol 120%, you will continue to get crashes on startup with Verifier running. Both of these are known to causes crashes with Verifier enabled.

Do you still need help tracking down the culprit?

BSOD with SLI both playing games and general multitasking on Win 7

New member

My Computer My Computer

At a glance

New member

My Computer My Computer

At a glance

New member

My Computer My Computer

At a glance

New member

My Computer My Computer

At a glance

New member

My Computer My Computer

At a glance

New member

My Computer My Computer

At a glance

New member

My Computer My Computer

At a glance

New member

My Computer My Computer

At a glance

New member

My Computer My Computer

At a glance

New member

My Computer My Computer

At a glance

New member

My Computer My Computer

At a glance

New member

My Computer My Computer

At a glance

New member

My Computer My Computer

At a glance

New member

My Computer My Computer

At a glance

Closed by request.

My Computer My Computer

At a glance

Similar threads

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer