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

System Problems


  • Please log in to reply
1 reply to this topic

#1 Sean-G

Sean-G

  • Members
  • 1 posts
  • OFFLINE
  •  
  • Local time:05:02 AM

Posted 09 December 2016 - 05:29 PM

Mod Edit:  Split from  https://www.bleepingcomputer.com/forums/t/526476/pc-shuts-off-crashes-during-gaming - Hamluis.

 

Have you tried running prime 95 to test the ram and the cpu? Do you have any over clocks on any hardware? Have you tried resetting the cmos to the default values in the bios?

 

Can you please run who crashed:

 

We need to analyze your operating system's crash dump files to further diagnose what could possibly be crashing your computer system.

Please download Who Crashed? and save it to your desktop.

Double click whocrashedSetup.exe and choose Run

On Windows Vista, 7, 8 and 8.1 machines, when User Account Control asks if you wish to install this program, say YES to install the program on your computer.

Program can also be installed by right click and choosing Run As An Administrator.

On the next screen choose Next and accept the agreement.

Install the program in it's default location C:\Program Files\WhoCrashed (If your primary drive is different from C:, choose your primary drive.)

Choose Next and allow program to create a Start Menu Folder called WhoCrashed and click Next.

Allow program to create desktop icon and click Next.

Now Click Install.

Once the program is installed on your computer system, look for the WhoCrashed icon.png desktop Icon and double click it.

Accept the User Account Control request and the program will open on your screen and should look something like this.

whocrashed.png

Next, Click the Analyze button. analyze.png

An Information Window should appear on your screen prompting you to scroll down your screen.

If a report was generated we would like to have a look at this report.

To do this, click File analyze.png and then choose Export.

Save as WhoCrashedOutput.htm to your desktop.

Open WhoCrashedOutput.htm and copy and paste all of the contents from System Information (local) and Crash Dump Analysis and the Conclusion into your next reply.

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

On Fri 12/9/2016 1:25:20 PM your computer crashed
crash dump file: C:\Windows\Minidump\120916-51230-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x4B297C) 
Bugcheck code: 0x124 (0x0, 0xFFFFFA80084C3038, 0x0, 0x0)
Error: WHEA_UNCORRECTABLE_ERROR
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that a fatal hardware error has occurred. This bug check uses the error data that is provided by the Windows Hardware Error Architecture (WHEA). 
This is likely to be caused by a hardware problem problem. This problem might also be caused because of overheating (thermal issue). 
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time. 



On Thu 12/8/2016 10:34:21 AM your computer crashed
crash dump file: C:\Windows\Minidump\120816-48063-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x4B297C) 
Bugcheck code: 0x124 (0x0, 0xFFFFFA800833E738, 0x0, 0x0)
Error: WHEA_UNCORRECTABLE_ERROR
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that a fatal hardware error has occurred. This bug check uses the error data that is provided by the Windows Hardware Error Architecture (WHEA). 
This is likely to be caused by a hardware problem problem. This problem might also be caused because of overheating (thermal issue). 
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time. 



On Wed 12/7/2016 2:16:34 PM your computer crashed
crash dump file: C:\Windows\Minidump\120716-42432-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x4B297C) 
Bugcheck code: 0x124 (0x0, 0xFFFFFA80085034F8, 0x0, 0x0)
Error: WHEA_UNCORRECTABLE_ERROR
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that a fatal hardware error has occurred. This bug check uses the error data that is provided by the Windows Hardware Error Architecture (WHEA). 
This is likely to be caused by a hardware problem problem. This problem might also be caused because of overheating (thermal issue). 
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time. 



On Sun 12/4/2016 12:13:08 PM your computer crashed
crash dump file: C:\Windows\Minidump\120416-47611-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x4B297C) 
Bugcheck code: 0x124 (0x0, 0xFFFFFA80083D9038, 0x0, 0x0)
Error: WHEA_UNCORRECTABLE_ERROR
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that a fatal hardware error has occurred. This bug check uses the error data that is provided by the Windows Hardware Error Architecture (WHEA). 
This is likely to be caused by a hardware problem problem. This problem might also be caused because of overheating (thermal issue). 
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time. 



On Sat 12/3/2016 8:41:45 PM your computer crashed
crash dump file: C:\Windows\Minidump\120316-46269-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x4B297C) 
Bugcheck code: 0x124 (0x0, 0xFFFFFA800838E038, 0x0, 0x0)
Error: WHEA_UNCORRECTABLE_ERROR
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that a fatal hardware error has occurred. This bug check uses the error data that is provided by the Windows Hardware Error Architecture (WHEA). 
This is likely to be caused by a hardware problem problem. This problem might also be caused because of overheating (thermal issue). 
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time. 



 

Conclusion

37 crash dumps have been found and analyzed. Only 5 are included in this report. No offending third party drivers have been found. Connsider using WhoCrashed Professional which offers more detailed analysis using symbol resolution. Also configuring your system to produce a full memory dump may help you. 


Read the topic general suggestions for troubleshooting system crashes for more information. 

Note that it's not always possible to state with certainty whether a reported driver is responsible for crashing your system or that the root cause is in another module. Nonetheless it's suggested you look for updates for the products that these drivers belong to and regularly visit Windows update or enable automatic updates for Windows. In case a piece of malfunctioning hardware is causing trouble, a search with Google on the bug check errors together with the model name and brand of your computer may help you investigate this further. 
 


Edited by hamluis, 11 December 2016 - 11:22 AM.


BC AdBot (Login to Remove)

 


#2 hamluis

hamluis

    Moderator


  • Moderator
  • 55,867 posts
  • ONLINE
  •  
  • Gender:Male
  • Location:Killeen, TX
  • Local time:08:02 AM

Posted 11 December 2016 - 11:24 AM

How to receive help diagnosing Blue Screens and Windows crashes - http://www.bleepingcomputer.com/forums/topic176011.html

 

Moved from Computer Gaming to Crashes/BSODs.

 

Louis






0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users