|21 Apr 2012||#1|
| || |
Computer Stops responding for minutes at a time then BSOD
Win 7 Home Premium x64. Three users logged in. The computer will all of a sudden stop responding for minutes at a time. Everything stops Keyboard, mouse, sidebar clocks, etc. Will then get short bursts of activity. If I am lucky to get it to shutdown, it will BSOD while shutting down.
Sometimes this happens on wake from sleep and sometimes when watching videos (youtube), playing Minecraft.
I have attached 2 of the most recent files in minidump
|My System Specs|
|21 Apr 2012||#2|
| || |
1-iastor.sys Caused of one of the crashes and other old drivers needing updating
V0060EVX.SYS 8/7/2006 3:48:41 AM V0060USB.SYS 8/7/2006 5:07:30 AM V0060Vid.sys 8/25/2006 3:51:55 AM moufiltr.sys 12/25/2006 10:27:18 PM lmimirr.sys 4/10/2007 6:32:45 PM nipbcfk.sys 7/10/2007 9:07:45 PM RaInfo.sys 1/4/2008 2:57:14 PM nidimk.dll 6/13/2008 12:29:46 PM LMIRfsDriver.sys 7/14/2008 12:26:56 PM iaStor.sys 7/20/2008 8:29:34 PM e1y60x64.sys 8/18/2008 5:45:05 PM nipalk.sys 5/26/2009 6:54:23 PM niorbk.dll 6/14/2009 4:14:57 PM NiViPxiK.sys 6/21/2009 2:56:20 PM NiViPxiKl.sys 6/21/2009 2:56:26 PM
- 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.
- - Driver manufacturer links are on this page: Drivers and Downloads
"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
|My System Specs|
|Similar help and support threads for2: Computer Stops responding for minutes at a time then BSOD|
|BSOD after about 50 minutes of idle time||BSOD Help and Support|
|Outlook 2010 stops and says it needs to reboot or stops responding||Browsers & Mail|
|BSOD after about 40 minutes of run time.||BSOD Help and Support|
|PC stops responding, no BSOD||BSOD Help and Support|
|BSOD several minutes after boot, every time.||BSOD Help and Support|
|Computer stops responding but doesn't freeze or crash||BSOD Help and Support|
|BSOD within minutes of cold boot every time||BSOD Help and Support|