BSODING playing games

[DemoNSesshY]

- x86 (32-bit) or x64 ? - the original installed OS on the system? - an OEM or full retail version? - OEM = came pre-installed on system - Full Retail = you purchased it from retailer - What is the age of system (hardware)? - What is the age of OS installation (have you re-installed the OS?)

Windows 7 X86

Original installed - Windows 7 professional

Retail version

Age 4-5 Years

OS install date - 3 months ago

 

[zigzag3143]

- x86 (32-bit) or x64 ? - the original installed OS on the system? - an OEM or full retail version? - OEM = came pre-installed on system - Full Retail = you purchased it from retailer - What is the age of system (hardware)? - What is the age of OS installation (have you re-installed the OS?)

Windows 7 X86

Original installed - Windows 7 professional

Retail version

Age 4-5 Years

OS install date - 3 months ago

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.

 

[DemoNSesshY]

Uhh what is a BIOs bug

 

[zigzag3143]

Uhh what is a BIOs bug

A bios bug can be a mistake in programming, or many other things. Thats why bios updates come out (to fix errors in previous versions)