Jump to content


 


Register a free account to unlock additional features at BleepingComputer.com
Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.


Click here to Register a free account now! or read our Welcome Guide to learn how to use this site.

Photo

Random Hard Hang Crash (no BSOD)


  • Please log in to reply
12 replies to this topic

#1 JamesKirk

JamesKirk

  • Members
  • 7 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Dallas, Texas
  • Local time:12:01 AM

Posted 07 August 2014 - 04:33 PM

Hello and thank you for taking the time to read my post. Any help you can offer is appreciated.

 

The problem :

At random times while the computer is running different programs under heavy loads only, the computer will hard hang to black screen with no BSOD.

 

Windows Kernel event ID 41 error "The system has rebooted without cleanly shutting down first" 

BugcheckCode 278
BugcheckParameter1 0xfffffa8006cbf010
BugcheckParameter2 0xfffff8800fe727a0
BugcheckParameter3 0xffffffffc000009a
BugcheckParameter4 0x4
SleepInProgress false
PowerButtonTimestamp 0

 

Caps Lock key is unresponsive.

My problem is similar to this post :

http://www.bleepingcomputer.com/forums/t/532681/random-complete-freezes-on-high-end-machine/

 

 
I have used these programs and I am happy to list results:
Wise Registry Cleaner
Event Viewer
MiniToolBox by Farbar (with ImgBurn)
Speccy

 

I ran MemTest86+ on both of my RAM sticks. Both had no errors.

 

PSU is OCZ Z Series 850W that is less than 1 year old.

 

 

By heavy load, I mean gaming with netflix playing on second monitor or running photoshop and gaming simultaneously.

 

By random, I mean a time span of 36 hours to 20 minutes.

 

I expect my problem to be with the PSU, but I welcome any alternatives you may suggest. If you do expect the culprit to be the PSU, do you know of any way to definitely identify the problem without testing the PSU with a multimeter while under heavy load?

 

Thank you

James Kirk.

 

 

 

 



BC AdBot (Login to Remove)

 


#2 sflatechguy

sflatechguy

  • BC Advisor
  • 2,244 posts
  • OFFLINE
  •  
  • Gender:Male
  • Local time:01:01 AM

Posted 07 August 2014 - 05:14 PM

The 41 bugcheck code is pretty generic -- it simply means the computer shut down unexpectedly. If there is a minidump file (C:\Windows|Minidump), you might want to examine it to see if there are any other error messages that might point to something more concrete. You can use Blue Screen Viewer or Debugging Tools for Windows to do that, then post the log here.

The most recent Event Viewer logs from the last time the computer hung up would also be useful.

 

I would recommend uninstalling the registry cleaner. They have a history of causing more problems than they solve.

http://www.bleepingcomputer.com/forums/t/373006/registry-cleaners/

http://answers.microsoft.com/en-us/windows/forum/windows_7-performance/recommended-registry-cleaners/871eb3a9-3b97-4113-a257-6a43795f2175



#3 JamesKirk

JamesKirk
  • Topic Starter

  • Members
  • 7 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Dallas, Texas
  • Local time:12:01 AM

Posted 08 August 2014 - 12:00 PM

The 41 bugcheck code is pretty generic -- it simply means the computer shut down unexpectedly. If there is a minidump file (C:\Windows|Minidump), you might want to examine it to see if there are any other error messages that might point to something more concrete. You can use Blue Screen Viewer or Debugging Tools for Windows to do that, then post the log here.

The most recent Event Viewer logs from the last time the computer hung up would also be useful.

 

I would recommend uninstalling the registry cleaner. They have a history of causing more problems than they solve.

http://www.bleepingcomputer.com/forums/t/373006/registry-cleaners/

http://answers.microsoft.com/en-us/windows/forum/windows_7-performance/recommended-registry-cleaners/871eb3a9-3b97-4113-a257-6a43795f2175

 

 

Thank you for your help!

 

Here is the info requested.

 

I deleted the RegCleaner and ran Blue Screen Viewer.

 

I have 12 minidump files. 11 look to be the same problem with DirectX Graphics Kernel. The oldest file has hal.dll+12a3b listed as the expected problem, but this happened 7 months ago and only happened once.

 

Data from Blue Screen Viewer:

 

==================================================
Dump File         : 080614-10748-01.dmp
Crash Time        : 8/6/2014 10:55:54 PM
Bug Check String  : 
Bug Check Code    : 0x00000116
Parameter 1       : fffffa80`0b217010
Parameter 2       : fffff880`0f5c993c
Parameter 3       : 00000000`00000000
Parameter 4       : 00000000`00000002
Caused By Driver  : dxgkrnl.sys
Caused By Address : dxgkrnl.sys+5d140
File Description  : DirectX Graphics Kernel
Product Name      : Microsoft® Windows® Operating System
Company           : Microsoft Corporation
File Version      : 6.1.7601.18228 (win7sp1_gdr.130731-2222)
Processor         : x64
Crash Address     : ntoskrnl.exe+75bc0
Stack Address 1   : 
Stack Address 2   : 
Stack Address 3   : 
Computer Name     : 
Full Path         : C:\Windows\Minidump\080614-10748-01.dmp
Processors Count  : 8
Major Version     : 15
Minor Version     : 7601
Dump File Size    : 568,064
Dump File Time    : 8/6/2014 10:56:25 PM
==================================================
 
==================================================
Dump File         : 080414-10592-01.dmp
Crash Time        : 8/4/2014 5:20:07 PM
Bug Check String  : 
Bug Check Code    : 0x00000116
Parameter 1       : fffffa80`0d3214e0
Parameter 2       : fffff880`0fe787a0
Parameter 3       : ffffffff`c000009a
Parameter 4       : 00000000`00000004
Caused By Driver  : dxgkrnl.sys
Caused By Address : dxgkrnl.sys+5d140
File Description  : DirectX Graphics Kernel
Product Name      : Microsoft® Windows® Operating System
Company           : Microsoft Corporation
File Version      : 6.1.7601.18228 (win7sp1_gdr.130731-2222)
Processor         : x64
Crash Address     : ntoskrnl.exe+75bc0
Stack Address 1   : 
Stack Address 2   : 
Stack Address 3   : 
Computer Name     : 
Full Path         : C:\Windows\Minidump\080414-10592-01.dmp
Processors Count  : 8
Major Version     : 15
Minor Version     : 7601
Dump File Size    : 711,152
Dump File Time    : 8/4/2014 5:21:32 PM
==================================================
 
==================================================
Dump File         : 080114-10873-01.dmp
Crash Time        : 8/1/2014 2:02:18 PM
Bug Check String  : 
Bug Check Code    : 0x00000116
Parameter 1       : fffffa80`0c045010
Parameter 2       : fffff880`0fe827a0
Parameter 3       : ffffffff`c000009a
Parameter 4       : 00000000`00000004
Caused By Driver  : dxgkrnl.sys
Caused By Address : dxgkrnl.sys+5d140
File Description  : DirectX Graphics Kernel
Product Name      : Microsoft® Windows® Operating System
Company           : Microsoft Corporation
File Version      : 6.1.7601.18228 (win7sp1_gdr.130731-2222)
Processor         : x64
Crash Address     : ntoskrnl.exe+75bc0
Stack Address 1   : 
Stack Address 2   : 
Stack Address 3   : 
Computer Name     : 
Full Path         : C:\Windows\Minidump\080114-10873-01.dmp
Processors Count  : 8
Major Version     : 15
Minor Version     : 7601
Dump File Size    : 753,720
Dump File Time    : 8/1/2014 2:03:23 PM
==================================================
 
==================================================
Dump File         : 072914-11606-01.dmp
Crash Time        : 7/29/2014 2:07:28 PM
Bug Check String  : 
Bug Check Code    : 0x00000116
Parameter 1       : fffffa80`0b7b3010
Parameter 2       : fffff880`0fe6f7a0
Parameter 3       : ffffffff`c000009a
Parameter 4       : 00000000`00000004
Caused By Driver  : dxgkrnl.sys
Caused By Address : dxgkrnl.sys+5d140
File Description  : DirectX Graphics Kernel
Product Name      : Microsoft® Windows® Operating System
Company           : Microsoft Corporation
File Version      : 6.1.7601.18228 (win7sp1_gdr.130731-2222)
Processor         : x64
Crash Address     : ntoskrnl.exe+75bc0
Stack Address 1   : 
Stack Address 2   : 
Stack Address 3   : 
Computer Name     : 
Full Path         : C:\Windows\Minidump\072914-11606-01.dmp
Processors Count  : 8
Major Version     : 15
Minor Version     : 7601
Dump File Size    : 577,632
Dump File Time    : 7/29/2014 2:08:03 PM
==================================================
 
==================================================
Dump File         : 010414-11169-01.dmp
Crash Time        : 1/4/2014 5:30:51 PM
Bug Check String  : 
Bug Check Code    : 0x00000124
Parameter 1       : 00000000`00000000
Parameter 2       : fffffa80`0910e028
Parameter 3       : 00000000`b2000000
Parameter 4       : 00000000`00070150
Caused By Driver  : hal.dll
Caused By Address : hal.dll+12a3b
File Description  : Hardware Abstraction Layer DLL
Product Name      : Microsoft® Windows® Operating System
Company           : Microsoft Corporation
File Version      : 6.1.7601.17514 (win7sp1_rtm.101119-1850)
Processor         : x64
Crash Address     : ntoskrnl.exe+75bc0
Stack Address 1   : 
Stack Address 2   : 
Stack Address 3   : 
Computer Name     : 
Full Path         : C:\Windows\Minidump\010414-11169-01.dmp
Processors Count  : 8
Major Version     : 15
Minor Version     : 7601
Dump File Size    : 296,160
Dump File Time    : 1/4/2014 5:31:31 PM
==================================================
 
 
 
I attempted to update DirextX but I already have the latest version 11.1 for Win7. Do you recommend I uninstall DirectX and re-install?
Edit : My GeForce driver is 340.52 released on July 29th. As of 8/8/2014 it is up to date.

Edited by JamesKirk, 08 August 2014 - 12:08 PM.


#4 dc3

dc3

    Bleeping Treehugger


  • Members
  • 30,714 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Sierra Foothills of Northern Ca.
  • Local time:10:01 PM

Posted 08 August 2014 - 12:43 PM

Please post the Speccy snapshot.


Family and loved ones will always be a priority in my daily life.  You never know when one will leave you.

 

 

 

 


#5 sflatechguy

sflatechguy

  • BC Advisor
  • 2,244 posts
  • OFFLINE
  •  
  • Gender:Male
  • Local time:01:01 AM

Posted 08 August 2014 - 12:54 PM

I would recommend running sfc /scannow from a command prompt. Those dxgkernel error codes are likely being caused by the video driver, so you'll want to update that.
You should also go into Device Manager and make sure there isn't a yellow warning icon on your video card.

#6 JamesKirk

JamesKirk
  • Topic Starter

  • Members
  • 7 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Dallas, Texas
  • Local time:12:01 AM

Posted 08 August 2014 - 01:51 PM

Please post the Speccy snapshot.

 

http://speccy.piriform.com/results/ccv7dZFSVlws2ZDBxc1owBN



#7 JamesKirk

JamesKirk
  • Topic Starter

  • Members
  • 7 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Dallas, Texas
  • Local time:12:01 AM

Posted 08 August 2014 - 02:17 PM

I would recommend running sfc /scannow from a command prompt. Those dxgkernel error codes are likely being caused by the video driver, so you'll want to update that.
You should also go into Device Manager and make sure there isn't a yellow warning icon on your video card.

pJy52Az.jpg

 

nEulFZC.jpg



#8 sflatechguy

sflatechguy

  • BC Advisor
  • 2,244 posts
  • OFFLINE
  •  
  • Gender:Male
  • Local time:01:01 AM

Posted 08 August 2014 - 02:31 PM

Just reread your earlier post about the driver. At this point, my money is on the video card itself. That would explain the hardware abstraction layer (hal.dll) error.
Try using a different video card, or the built-in video monitor port, and see if the issue persists.

#9 dc3

dc3

    Bleeping Treehugger


  • Members
  • 30,714 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Sierra Foothills of Northern Ca.
  • Local time:10:01 PM

Posted 08 August 2014 - 02:44 PM

Your motherboard has onboard graphics and the CPU has integrated graphics.  So you can disconnect the dedicated card and see if the problem persists.


Family and loved ones will always be a priority in my daily life.  You never know when one will leave you.

 

 

 

 


#10 JamesKirk

JamesKirk
  • Topic Starter

  • Members
  • 7 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Dallas, Texas
  • Local time:12:01 AM

Posted 08 August 2014 - 03:45 PM

I changed to the onboard graphics. All seems well but I did not test the system for long. I loaded a game that often triggers the crash and attempted to play. My usual 150 FPS (Frames Per Second) was now only 9 FPS and the game in my opinion was unplayable even on the lowest settings.

 

The crash seems to happen when a heavy demand is placed on the the GPU. When the system is under normal load (internet browsing only) I have had no crashes.



#11 sflatechguy

sflatechguy

  • BC Advisor
  • 2,244 posts
  • OFFLINE
  •  
  • Gender:Male
  • Local time:01:01 AM

Posted 08 August 2014 - 03:50 PM

If you can borrow a faster graphics card that your system can support, or find one cheap, swap it out for the current video card. You've just pinpointed the problem -- your current video card can't handle the processing load being placed on it. And 9 frames per second won't cut it. ;-)

#12 JamesKirk

JamesKirk
  • Topic Starter

  • Members
  • 7 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Dallas, Texas
  • Local time:12:01 AM

Posted 09 August 2014 - 11:16 AM

I uninstalled all programs relating to the GPU then re-installed. Everything has worked perfectly for more than 18 hours. I will update here again if the problem returns. 

 

My thanks to everyone that posted here.

 

James Kirk.



#13 dc3

dc3

    Bleeping Treehugger


  • Members
  • 30,714 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Sierra Foothills of Northern Ca.
  • Local time:10:01 PM

Posted 09 August 2014 - 11:27 AM

Glad to hear it has been resolved. :thumbup2:


Family and loved ones will always be a priority in my daily life.  You never know when one will leave you.

 

 

 

 





0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users