Two back-to-back BSoDs

PwnFrnzy

Hardware & Perfomance
Pro User
Local time
12:18 AM
Messages
500
Location
California, US
- x86 (32-bit) or x64 ?
x64
- the original installed OS on the system?
Yes.
- an OEM or full retail version?
OEM.
- What is the age of system (hardware)?
Almost 7 months.
- What is the age of OS installation
Same age as System/Hardware.

Earlier today I experienced two BSoD's back-to-back. I left my computer for a moment and dropped my Xbox controller, I think it bit my computer case when it fell, when I returned to my computer it was locked up and not responding to CTRL+ALT+DEL.
I restarted and at the login screen it locked up again. I'm wondering what happened to cause both BSoDs.
 

My Computer

Computer type
PC/Desktop
Computer Manufacturer/Model Number
Frankenstein PC
OS
Windows 7 Home Premium 64-bit SP1
CPU
Intel core i7 920 @ 2.67Ghz; Bloomfield 45nm Technology
Motherboard
Intel Corporation DX58SO (J1PR)
Memory
16GB Dual-Channel DDR3 @ 540MHz (7-7-7-19)
Graphics Card(s)
4095MB NVIDIA GeForce GTX 960 (EVGA)
Sound Card
N/A Integrated Audio
Monitor(s) Displays
Acer S231HLbid LED Monitor 23"
Screen Resolution
1920x1080 1080p 60Hz
Hard Drives
BOOT: 59GB ADATA SP900 (SSD)
STORAGE 1: 977GB Hitachi HDS721010CLA (SATA) @7200RPM;
STORAGE 2: 465GB Western Digital WDC WD5000AAKS-65YGA0 (SATA) @ 7200RPM;
PSU
EVGA SuperNOVA 750 G1 80+ Gold (120-G1-0750-XR)
Case
Cooler Master Elite Gaming Case Black 430
Cooling
Cooler Master Hyper 212 Heatsink. Front and rear 120mm fan
Keyboard
Rosewill RIKB-11003
Mouse
James Donkey 112S
Internet Speed
200/40
Antivirus
Avast! Antivirus Free
Browser
Cyberfox x64 / FireFox / PaleMoon x64; kept up-to-date
Other Info
Windows Installed on March 21, 2014
PwnFrnzy,

> Please read through...

"It's not a true crash, in the sense that the bluescreen was initiated only because the combination of video driver and video hardware was being unresponsive, and not because of any synchronous processing exception".

Since Vista, the "Timeout Detection and Recovery" (TDR) components of the OS video subsystem have been capable of doing some truly impressive things to try to recover from issues which would have caused earlier OSs like XP to crash.

As a last resort, the TDR subsystem sends the video driver a "please restart yourself now!" command and waits a few seconds.

If there's no response, the OS concludes that the video driver/hardware combo has truly collapsed in a heap, and it fires off that stop 0x116 BSOD.

If playing with video driver versions hasn't helped, make sure the box is not overheating.

Try removing a side panel and aiming a big mains fan straight at the motherboard and GPU.

Run it like that for a few hours or days - long enough to ascertain whether cooler temperatures make a difference.

If so, it might be as simple as dust buildup and subsequently inadequate cooling.

I would download cpu-z and gpu-z (both free) and keep an eye on the video temps Let us know if you need help

http://www.sevenforums.com/crash-lo...op-0x116-video_tdr_error-troubleshooting.html



> Your Avast may be a contributing cause of your BSOD'S.
Please remove and replace with Microsoft Security Essentials AT LEAST TO TEST.

http://files.avast.com/files/eng/aswclear5.exe

Microsoft Security Essentials - Free Antivirus for Windows
 

My Computer

Computer Manufacturer/Model Number
LAPTOP. HP Pavilion dv7-4010TX .
OS
Win 7 Ultimate 64-bit. SP1.
CPU
Intel i7 -720QM.[1.6GHz Turbo Boost 2.8GHz. 6MB Cache.]
Memory
8 DDR 3 RAM. 1066MHZ
Graphics Card(s)
ATI 1024 MB. DDR3. Radeon HD5650
Monitor(s) Displays
17.3" High Definition Brightview LCD. LED Backlit.
Screen Resolution
1600 x 900.
Hard Drives
640GB
Case
Laptop / notebook.
Mouse
Logitech Anywhere mouse. MX.
Internet Speed
ADSL [ but too slow ]
Back
Top