Starcraft 2 BSOD reboot error

[Namish]

Hello Sevenforums!
I am a recent BSOD survivor because of these forms and your helpful member Writhziden. I have been BSOD free since my last post on this thread (http://www.sevenforums.com/crashes-...-bsods-irql_not_less_or_equal-0x0000000a.html) Until recently.

The last 2 days I have had a few different BSOD crashes. Unfortunately I was not expecting them and had my settings reboot after a BSOD. Because of this I was unable to catch the error codes.

I have attached the Grab all report below. Thank you all in advance for your time and for being such a great BSOD troubleshooting tool.

Sincerely,
Kyle

 

[x BlueRobot]

BugCheck 124, {0, fffffa80061ef8f8, 0, 0}

Probably caused by : AuthenticAMD

Stop 0x124 is a BSOD which is a hardware only related cause, and therefore it will be necessary to run some stress tests, however, from the other BSOD you have had, it commonly points to a graphics card driver or the Video RAM of your graphics card.

[COLOR="red"]BugCheck 10E[/COLOR], {1f, fffff8a00c1f4460, 0, 3d022}

Probably caused by : [COLOR="Red"]dxgmms1.sys[/COLOR] ( dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForSubmission+148 )

Usual causes:  Video driver, Video memory

Test the graphics card RAM and stability:

• http://www.sevenforums.com/tutorials/160729-nvidia-amd-video-card-test-occt.html

:warn:Read all the steps within the hardware test tutorials very carefully, as stress tests is designed run components to their maximum capacity, in order to point out failing or faulty hardware components.
You can you use this program to monitor the temperature during the stress test:

• CPUID HwMonitor

 

[Namish]

x BlueRobot,

Thanks for the quick reply. I ran OCCT a few times and had to abort the test each time after my GPU hit 81 degrees. It did however notice that my graphics card drivers were pretty badly out of date. I'm going to try and see if I can get it to BSOD again with the new drivers. Should most video cards be able to complete the OCCT stress test?

Kyle

 

[Namish]

x BlueRobot,
Well the drivers didn't help. I crashed again hard and could not boot into windows for about an hour. Got multiple blue screens. Here's the new grab.

Kyle

 

[x BlueRobot]

[COLOR="Red"]BugCheck 10E[/COLOR], {1f, fffff8a00c1f4460, 0, 3d022}

Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForSubmission+148 )

Usual causes:  Video driver, Video memory

What were the results of the OCCT test? A graphics card which isn't faulty should always pass regardless of the make or model.

NVIDIA GeForce GTX 260:

c:\windows\system32\drivers\nvlddmkm.sys (9.18.13.697, 12.82 MB (13,443,944 bytes), [COLOR="Red"]10/10/2012[/COLOR] 10:22 PM)

The graphics driver is updated which is good, did you install the Beta driver?

The other BSOD pointed to Stop 0x7E, and here is the usual causes of the crash:

Usual causes:  Insufficient disk space, [COLOR="red"]Device driver[/COLOR], [COLOR="Red"]Video card[/COLOR], BIOS, Breakpoint with no debugger attached, Hardware incompatibility, Faulty system service, Memory, 3rd party remote control

 

[Namish]

X BlueRobot,

I attached a zip of all the OCCT documentation. I have only ran the GPU:OCCT test because the the GPU:MEMTEST button is greyed out and I cannot select it. Here is a link to the Nvidia drivers I installed:

NVIDIA DRIVERS 306.97WHQL

 

[x BlueRobot]

X BlueRobot,

I attached a zip of all the OCCT documentation. I have only ran the GPU:OCCT test because the the GPU:MEMTEST button is greyed out and I cannot select it. Here is a link to the Nvidia drivers I installed:

NVIDIA DRIVERS 306.97WHQL

Good work with updating the graphics card driver, and I couldn't see any errors from the results you posted.

Do you have latest DirectX runtime installed?

Any more crashes?

 

[Namish]

Before running OCCT I installed the DirectX runtime via this link: Download DirectX End-User Runtime from Official Microsoft Download Center

My previous crash report happened after the DirectX and drivers update. I have not tried to crash it again since the multiple BSODS. I still have to abort the OCCT each time I try because it reaches 81 degrees. Should I keep trying to crash it and send up the Grabs?

 

[x BlueRobot]

No, not all graphics cards are able to support the Video RAM test, so it's completely normal if your graphics card isn't able to run the RAM test.

Any more crashes recently?

 

[Namish]

X BlueRobot,
Yes I am still crashing. It is much more frequent now and not just while on a video game. The last one was a IRQL_NOT_LESS_OR_EQUAL BSOD. This has me a bit concerned as this one happened many times while trying to fix the issues in my last troubleshoot a few months back.


Kyle

 

[x BlueRobot]

[COLOR="red"]BugCheck A[/COLOR], {fffff0800ad189c0, 2, 0, fffff80002a98ef2}

Probably caused by : [COLOR="Red"]memory_corruption[/COLOR]

Usual causes:  Kernel mode driver, System Service, BIOS, Windows, Virus scanner, Backup tool, compatibility

memory_corruption doesn't necessary mean that a RAM module is faulty, it can also point to a object which corrupted the RAM at the time of the crash, for instance a corrupted driver or program. Paging files and the CPU caches can also be causes.

Follow these steps -

Test for any corrupted drivers, by running Driver Verifier for least 24 hours, stop the test if a BSOD occurs before this time frame. Driver Verifier will place stress on the drivers within your system, which will cause corrupted drivers to crash and hopefully be pinpointed.

• http://www.sevenforums.com/tutorials/101379-driver-verifier-enable-disable.html

Memory:

• http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html

Run Memtest86+ for least 7-8 passes, and preferrly overnight as it can take a while to fully complete.

Test each RAM stick individually, if an error is found then move the same RAM stick into the next DIMM slot and test again, if errors are found for the same RAM stick in every available slot then you have a faulty RAM module. On the other hand, if no errors are found in the next slot or the other slots for the same RAM module, then you have a faulty DIMM slot.

Test each RAM stick and every motherboard DIMM slot available.

Remove the graphics card too, just to make sure the Video RAM of the card is not causing any problems; only follow this step if your motherboard has a onboard graphics chip or you have an alternative card.

 

[Namish]

X BlueRobot,

I managed to crash the computer while running Driver Verifier. Here's the Grab all. It seems like the computer will crash after about 10 minutes of anything graphically heavy. It never seems to happen right after a boot-up.

Kyle

 

[x BlueRobot]

[COLOR="red"]BugCheck A[/COLOR], {fffff0800ad189c0, 2, 0, fffff80002a98ef2}

Probably caused by : [COLOR="Red"]memory_corruption[/COLOR]

Usual causes:  Kernel mode driver, System Service, BIOS, Windows, Virus scanner, Backup tool, compatibility

The latest .dmp file I could find was dated to yesterday, and is the same crash as listed above.

Have you completed the memory test with MemTest86+?

Have you looked for BIOS updates for your motherboard?

American Megatrends Inc. 1610, [COLOR="Red"]7/14/2009[/COLOR]

 

[Namish]

X BlueRobot,

I haven't been able to run Memtest yet because I am working 12 hour night shifts right now and have been dreading it horribly. A few months back I seem to remember Memtest as being the worst part of the trouble shooting requiring a boot disk, a computer disassemble and a solid night per stick of ram. I am almost considering buying a few newer sticks of ram and seeing if they solve the problem then just taking them back before dealing with Memtest again lol

I will work on updating my motherboard drivers and bios tomorrow and let you know if I can crash it. If I can I will devote my entire weekend to Memtest.

Also will driver verifier document something new in Grab All or does it make a separate log somewhere I need to attach?

Thanks,
Kyle

 

[x BlueRobot]

It was create a another .dmp file, if it does find any corrupted or misbehaving drivers.

 

[Namish]

X BlueRobot,

I finished up with Memtest86. I have three sticks of ram and 4 slots. The video card was removed. I did 8 passes of stick 1 in slot 1, 8 passes of stick 2 in slot 2, and 30 passes of stick 3 in slot 3. No errors on any of them. I assume I do not need to test the 4th slot since only the first 3 are being used correct?

I also figured out the bios updater for my mother board and should have the newest version. I have crashed once since doing all this and attached the Grab All

I'm beginning to suspect my motherboard being faulty again. I think the manufacturer just refurbished it without replacing it and it's going bad again. This is pretty much exactly how the other trouble shoot went a while back. Your thoughts?

Thanks,
Kyle

 

[x BlueRobot]

[COLOR="Red"]BugCheck A[/COLOR], {fffff0800ad189c0, 2, 0, fffff80002a98ef2}

Probably caused by : memory_corruption

Usual causes:  Kernel mode driver, System Service, BIOS, Windows, Virus scanner, Backup tool, compatibility

The latest crash (listed above) was dated as 3rd December, is this the latest dump saved?

Has Driver Verifier found anything yet?

Test the CPU and Power Supply with OCCT:

• http://www.sevenforums.com/tutorials/160729-nvidia-amd-video-card-test-occt.html

 

[Arc]

Also, try to roll back the driver to the earlier one ....

• Download and install Driver Fusion.
• Reboot the computer in Advanced Boot Options, safe mode. Search Driver Fusion in your start menu, and remove all components of your nVidia display driver.
• Boot normally now. Go to Drivers - Download NVIDIA Drivers, Drivers > Beta and Legacy; search there with your cards particulars for GeForce 306.23 Driver, dated 13.9.2012 and install it.

Can you check your RAM utilization during gaming, using a desktop gadget?

 

[Namish]

x BlueRobot / Arc,

I ran 10 minutes of the OCCT CPU stress test and it finished without a problem. I can run more if need be. The power supply test ended twice with a few errors (below) and I attached all the graphs/charts:

Error #1 -
"The exception Illegal Instruction
An attempt was made to execute an illegal instruction.
(0xc000001d) occured in the application at location 0x67ab082e.

Click on OK to terminate the program"

Error #2 -
"The instruction at 0x659a20f7 referenced memory at 0x00000c8. The memory could not be written.

Click on OK to terminate the program"

I deleted and updated my graphics drivers using Arc's instructions without much issue. I was however unable to delete a few of the files using Driver Fusion. I attached a few pictures of the files I could not remove.

You asked if this was the latest dump file. I don't really know how to tell if it saved the dump file or not. My last two crashes ended with an error saying “Display driver stopped responding and has recovered” and a memory error or just a BSOD/reboot. I don't know if they caused a dump file or not.

While trying to find a ram monitoring gadget I crashed. My screen blinked black, came back with the colors destroyed, then I got:
"Display driver stopped responding and has recovered
Display driver NVIDIA Windows Kernel Mode Driver, Version 306.23 stopped responding and has successfully recovered"
A few seconds later I crashed into BSOD:
"The video memory manager has encountered an unexpected fatal error
0x0000010E"

I will add the Grab All in the next post down.

Thanks again guys,
Kyle

 

[Namish]

Here's the Grab All from the previous post. Happened at approximately about 1530 hours on 12/08/12.