BSOD playing Starcraft 2, error 0x00000034

[DevilPanda]

I have been having random BSOD for a very long time, it seems to mostly happen when playing Starcraft 2, although it does occasionally happen doing other things as well. I have tried updating all my drivers, doing a memtest and all that stuff but nothing has helped. The crash address is mostly ntoskrn.exe+7cc80 in Blue Screen View but every thing else seems to vary.

System Specs
-Windows 7 Home Premium
-64 bit
-Full Retail
-Intallation about 8 months old
-Hardware is around 1.5 years old

CPU: Intel i7950
GPU: Geforce GTX 460
Mobo: Asus Sabretooth X58
Mem: 6GB patriot
HDD: 1 tb Seagate Barracuda
SSD: 60GB OCZ (OS installed on this)

 

[zigzag3143]

These were all related to a memory exception but before we can address this you need to fix this;

You have a driver from 2005 that is a HUGE cause of BSOD's in win 7 called RTCORE64.SYS, it is the msi afterburner driver (used in overclocking). It needs at least to be updated and if it cant it needs to be removed. I would update to the newest. Yours is from 2005

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

 

[DevilPanda]

Thanks for the quick response. Apperently RTCORE64.SYS is also the driver for EVGA precision so I uninstalled that and now hope that that will help with the issue.

 

[zigzag3143]

Thanks for the quick response. Apperently RTCORE64.SYS is also the driver for EVGA precision so I uninstalled that and now hope that that will help with the issue.

May not be the cause but certainly will help

 

[DevilPanda]

Yea, it blue screened again while playing minecraft after I uninstalled it.
Edit: Included the dmp file (I think its the right one)

 

[zigzag3143]

Yea, it blue screened again while playing minecraft after I uninstalled it.
Edit: Included the dmp file (I think its the right one)

As I indicated before RTCORE probably wasnt (isnt) the problem. Your problem is called a memory exception


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 (DRT)

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

Driver Verifier

Using Driver Verifier (Windows Drivers)

 

[DevilPanda]

Finally got time to run the memory test last night, 7 passes and no errors, so if i continue to get blue screens I will probably back up all my stuff and run driver verifier when i get time this weekend.

Thank you so much for the help

 

[zigzag3143]

Finally got time to run the memory test last night, 7 passes and no errors, so if i continue to get blue screens I will probably back up all my stuff and run driver verifier when i get time this weekend.

Thank you so much for the help

Good job on memtest and good luck

 

[DevilPanda]

Thanks!

 

[zigzag3143]

Thanks!

My pleasure.

 

[DevilPanda]

Ran driver verifier over the weekend and eventually got a BSOD. This is the .dmp file from that crash while verifier was running.

 

[zigzag3143]

Ran driver verifier over the weekend and eventually got a BSOD. This is the .dmp file from that crash while verifier was running.

Still points to memory corruption and doesnt name a driver. Sometimes verifier can be an "iffy" proposition. Sometimes it gives a false positive, sometimes it doesnt catch a mis behaving driver.

It creates an artificial environment so sometimes it actually seems to fix the problem it is looking for.

I suggest you keep running it.

 

[DevilPanda]

I will just keep Verifier running for the next while. Also should I post the .dmp file when a blue screen occurs? Or should I just keep it running it until it seems to stop.

Also thanks for your great help!

 

[zigzag3143]

I will just keep Verifier running for the next while. Also should I post the .dmp file when a blue screen occurs? Or should I just keep it running it until it seems to stop.

Also thanks for your great help!

Yep I would keep running verifier and if it doesnt yield results soon we can have it check all the drivers. That may slow you down a bit.

My pleasure just hope we can fix this.

 

[DevilPanda]

So, today I ran it with all drivers, and it blue screened almost immediately after log in twice in a row. I had to go into safe mode to disable it.

Also for some strange reason there was only 1 dmp file from today that I could find, even though there were 2 blue screens.

 

[zigzag3143]

So, today I ran it with all drivers, and it blue screened almost immediately after log in twice in a row. I had to go into safe mode to disable it.

Also for some strange reason there was only 1 dmp file from today that I could find, even though there were 2 blue screens.

Related to LGVirHid.sys GamePanel Virtual Hid Device Driver from Logitech Inc. It is causing HIDCLASS.SYS to crash. Yours is from 2009 and should be updated or renoved

 

[DevilPanda]

I completely uninstalled my logitech gaming software that used that driver, ill probably just run without it for while and see if the blue screens stop, and if they do ill try to find some other software that will work.

I know I have said this alot, but thanks alot for your help

 

[DevilPanda]

I got a blue screen again after I uninstalled my Logitech software. According the the blue screen that came up, and bluescreenview it was caused by a graphics driver, nvlddmkm.sys, but my graphics drivers are up to date so I really don't know what to do now...

This is the dmp file if you want a look.

 

[writhziden]

Re-install or install the latest drivers for your display card. Your current drivers may be corrupted and/or outdated. Use the following method to re-install the drivers.

1. Download the drivers you want for your display card(s)
2. Click Start Menu
3. Click Control Panel
4. Click Uninstall a program
5. For NVIDIA:
   • Uninstall the NVIDIA Graphics Driver (this should uninstall all NVIDIA software and drivers)
   • Restart your computer
   • Make sure NVIDIA 3D Vision Driver, NVIDIA 3D Vision Video Player, NVIDIA HD Audio Driver, and NVIDIA PhysX System Software are not still listed under Uninstall a program through Control Panel
   • If any remain of the above, uninstall one at a time
   • If asked to restart after uninstalling any of the above, do so, and continue uninstalling any remaining NVIDIA items until all are removed
6. Restart your computer after uninstalling drivers for all display cards
7. Install the driver you selected for the display cards once Windows starts

 

[DevilPanda]

I re installed the drivers, it blue screened again (I had verifier running again), according to blue screen view it was caused by ntoskrnl.exe but I really dont know whats goin on.

This is the dmp file if anyone wants it.