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 Crashes


  • Please log in to reply
3 replies to this topic

#1 jimmyjenkins

jimmyjenkins

  • Members
  • 3 posts
  • OFFLINE
  •  
  • Gender:Male
  • Local time:03:08 PM

Posted 01 September 2016 - 10:01 PM

i have a similar problem however the issue is not isolated to gaming, my computer could crash from having skype and youtube open

 

System Information (local)

Computer name: CHELL
Windows version: Windows 8.1 , 6.3, build: 9600
Windows dir: C:\Windows
Hardware: ASUSTeK COMPUTER INC., CROSSHAIR V FORMULA-Z
CPU: AuthenticAMD AMD FX™-9590 Eight-Core Processor AMD586, level: 21
8 logical processors, active mask: 255
RAM: 34252275712 bytes total


 

Crash Dump Analysis

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

On Sat 8/27/2016 11:03:36 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\082716-16203-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14E3A0)
Bugcheck code: 0xC000021A (0xFFFFC00017B2BA50, 0x0, 0x0, 0x0)
Error: STATUS_SYSTEM_PROCESS_TERMINATED
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This means that an error has occurred in a crucial user-mode subsystem.
There is a possibility this problem was caused by a virus or other malware.
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 8/27/2016 11:03:36 PM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0xC000021A (0xFFFFC00017B2BA50, 0x0, 0x0, 0x0)
Error: STATUS_SYSTEM_PROCESS_TERMINATED
Bug check description: This means that an error has occurred in a crucial user-mode subsystem.
There is a possibility this problem was caused by a virus or other malware.
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 8/20/2016 10:16:41 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\082016-13781-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14E3A0)
Bugcheck code: 0x133 (0x0, 0x501, 0x500, 0x0)
Error: DPC_WATCHDOG_VIOLATION
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL or above.
This appears to be a typical software driver bug and is not likely to be caused by a hardware 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 Mon 5/30/2016 5:06:06 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\053016-10468-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0xABA63)
Bugcheck code: 0x1000007E (0xFFFFFFFF80000003, 0xFFFFF80174D32A63, 0xFFFFD00021C5DCA8, 0xFFFFD00021C5D4B0)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a system thread generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
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 4/17/2016 2:08:28 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\041616-10171-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14E3A0)
Bugcheck code: 0x3B (0x80000003, 0xFFFFF800B58BDA63, 0xFFFFD000232167A0, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Fri 3/25/2016 2:12:06 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\032416-13562-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14E3A0)
Bugcheck code: 0xA (0xFFFFD0002210E0DD, 0x2, 0x1, 0xFFFFF802ACB3A213)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Mon 2/1/2016 4:41:59 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\020116-10343-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14E2A0)
Bugcheck code: 0x50 (0xFFFFF6FB40000800, 0x1, 0x0, 0x6)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that invalid system memory has been referenced.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
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 1/23/2016 8:14:07 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\012316-11531-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14E2A0)
Bugcheck code: 0x50 (0xFFFFFFFFFFFFFFF8, 0x0, 0xFFFFF801472A5173, 0x0)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that invalid system memory has been referenced.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Mon 12/28/2015 9:17:16 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\122815-11328-01.dmp
This was probably caused by the following module: dxgmms1.sys (dxgmms1+0x7B11)
Bugcheck code: 0x1E (0xFFFFFFFFC000001D, 0xFFFFF80196C15B11, 0xFFFFD0005018C3C0, 0xFFFFF8037C1B15B0)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32\drivers\dxgmms1.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: DirectX Graphics MMS
Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.



On Fri 12/25/2015 9:00:02 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\122515-12859-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14E8A0)
Bugcheck code: 0x1E (0xFFFFFFFF80000003, 0xFFFFF802582AF8A3, 0x0, 0xFFFFE000B7930A80)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



 

Conclusion

23 crash dumps have been found and analyzed. Only 10 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.
 

-thank you

oh also if the problem ends up being with the components i have no problem replacing them, i just want a functional computer 


Edited by jimmyjenkins, 01 September 2016 - 10:05 PM.


BC AdBot (Login to Remove)

 


#2 dominickceja

dominickceja

  • Members
  • 4 posts
  • OFFLINE
  •  
  • Local time:12:38 AM

Posted 03 September 2016 - 04:13 AM

You should get your PC repaired.



#3 jimmyjenkins

jimmyjenkins
  • Topic Starter

  • Members
  • 3 posts
  • OFFLINE
  •  
  • Gender:Male
  • Local time:03:08 PM

Posted 03 September 2016 - 05:02 PM

You should get your PC repaired.

10/10 :thumbup2:  :thumbup2:

thanks guy



#4 hamluis

hamluis

    Moderator


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

Posted 11 December 2016 - 11:28 AM

If you have not resolved this situation yet, please do the following.

 

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

 

Louis






0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users