Welcome to Windows 7 Forums. Our forum is dedicated to helping you find support and solutions for any problems regarding your Windows 7 PC be it Dell, HP, Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.

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

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

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.

Quote:

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

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

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.

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.

Quote:

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

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

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?

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.

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

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.

BSOD playing games in generalHello,
My first post so forgive me for any mistakes and please let me know how to correct them.
BSOD occurs whenever I play any games on my PC. Mostly I play the Age of Mythology but I've checked and BSOD occurs even when I play any other game. Please help me with what to do.

BSOD Help and Support

BSOD playing games in general, problem related to nvlddmkm.sysHello, I've been recently having problems and they are all apparently connected to nvlddmkm.sys and I don't know how to fix this, I've looked into this a lot and I'm not able to find any solutions. I have a NVIDIA GeForce 610M and I tried using the latest version as well (currently I have a version...

BSOD Help and Support

Frequent BSOD error in general- not while playing games only.Hi,
I am having BSOD error frequently. I am not able to give the error log but uploading the zip file containing such things. I am not an expert at this and hence requesting you to help me recover from this error. My PC configuration is as under:
i5-2500k|Asus P8Z77 V-LE|Corsair GS 600 | Corsair...

BSOD Help and Support

BSOD mainly when starting games, but also while multitaskingI hope I am posting this correctly.
I thought I knew about computers until I started to read some of the SF DIAG Tool v4 logs... and then I realized I am in way over my head.
My sincerest gratitude to anyone who can help me.
I get the BSOD mainly when starting games, such as Eve Online or...

BSOD Help and Support

BSOD playing Games (General)I'm getting random BSOD playing games. The video card was part of a system that was working without issues previously. I would not rule out that the video card is the issue however.
I'm getting various bluescreen issues, but one such is related to dxgmms1.sys
Computer:
MB: ASUS P8Z68-V...