BSOD plaing Starcraft2, error 0x00000101

[Apnea]

I keep getting a BSOD while playing starcraft. It doesn't happen very frequently but around once a day maybe twice if I play a lot.

the full error is :
The computer has rebooted from a bugcheck. The bugcheck was: 0x00000101 (0x0000000000000019, 0x0000000000000000, 0xfffff88003765180, 0x0000000000000002). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 120211-23524-01.

I really don't know much about this or how to fix it. I put together the computer myself the specs are: Asus P8P67-M PRO, 3.40 gigahertz Intel Core i7-2600K, NVIDIA GeForce GTX 560 Ti and 16 gigs of ddr3 ram.

 

[zigzag3143]

I keep getting a BSOD while playing starcraft. It doesn't happen very frequently but around once a day maybe twice if I play a lot.

the full error is :
The computer has rebooted from a bugcheck. The bugcheck was: 0x00000101 (0x0000000000000019, 0x0000000000000000, 0xfffff88003765180, 0x0000000000000002). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 120211-23524-01.

I really don't know much about this or how to fix it. I put together the computer myself the specs are: Asus P8P67-M PRO, 3.40 gigahertz Intel Core i7-2600K, NVIDIA GeForce GTX 560 Ti and 16 gigs of ddr3 ram.

Best advice that I've seen about this error (from here: http://www.sevenforums.com/crashes-...lock-interrupt-bsod-101-error.html#post356791 )

What you're looking for will be in one of the following categories:

a) BIOS bug
b) a driver whose activity is causing the target processor to lock up
c) a hardware defect (temperature, voltage, dust, RFI, outright borkedness...)

So, check the drivers
Then check the inside of the case (temperature, voltage, dust, etc).
Then run some hardware stress tests

Try this free video stress test: FurMark: VGA Stress Test, Graphics Card and GPU Stability Test, Burn-in Test, OpenGL Benchmark and GPU Temperature | oZone3D.Net
Try this free stress test: Free Software - GIMPS

Prime95 Setup:
- extract the contents of the zip file to a location of your choice
- double click on the executable file
- select "Just stress testing"
- select the "Blend" test. If you've already run MemTest overnight you may want to run the "Small FFTs" test instead.
- "Number of torture test threads to run" should equal the number of CPU's times 2 (if you're using hyperthreading).
The easiest way to figure this out is to go to Task Manager...Performance tab - and see the number of boxes under CPU Usage History
Then run the test for 6 to 24 hours - or until you get errors (whichever comes first).
The Test selection box and the stress.txt file describes what components that the program stresses.

Then try replacing parts.
Then look up the versions of your BIOS to see what changes were done.[/QUOTE]

 

[Apnea]

How do I check for Bios and driver errors?

 

[zigzag3143]

How do I check for Bios and driver errors?

You update BIOS (but be sure to have a backup) and driver verifier to find any problematic drivers.

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

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.