ok so id upgraded my motherboard and it has been amazing since ive had it about a week yesterday i was cleaning my room in depth so had my pc plugged in the tv it was running gta 5 at 4k and very high settings and it was very smooth. and i moved the pc back yesterday my bro was gaming gta 5 at 1080p its was smooth and then crashed no curser movement sound from amp was just zzzzzzzz and i could do nothing Ctrl + Alt + Delete did nothing i had to push the power button to switch it off and its constantly been crashing after a small amount of time i.e. after all services are loaded , then it stopped having the issue i saw this and played witcher 3 wildhunt and it was smooth for a couple of hours say 2-3 hrs then i turned it off and left i came back and turned her on and she loaded and then instantly frose i then restarted via the power button and tried again this time i got into windows and installed malwarebytes and scanned deleted the virus's it found and then tried to check my email it crashed i was sick of it and was going to reinstall windows , so i got my usb with windows 10 and plugged it in started the install and it kept freezing after the starting windows end section of the installation. eventually it got past it i was like is that the cursar it was i was going to add a password and then it frose i honestly have no clue what is wrong
my Pc is randomly crashing its driving me mad
- Thread starter amd4lif3
- Start date
Solution
rowdymoody
Honorable
- Jan 16, 2013
- 918
- 0
- 11,360
Almost sounds like you might be having hard drive problems.
Go to this pc, right click your hard drive, properties, tools, under error checking click check. See if it passes.
Go to this pc, right click your hard drive, properties, tools, under error checking click check. See if it passes.
im getting it booting into windows now but it does randomly freeze and blue screen each time with a different error message i dont believe it is a hard drive issue since when its works it works fast and stable but when it crashes its just really really frustrating
I once had a graphics card where the fan stopped working, it did exactly what you've described. Took some time to figure it out because after restarting everything would be fine then it's would crash again. Now this may not be what's happening to you, but it does have similarities to a GPU problem.
just doing all the windows updates , my theory is that my last OS got trashed hard as the hard drive had to be changed as in the type from MGR to GPT , though i was still getting issues and then alot of changes in the bios means its ran for over 10 mins now sooo happy if it works
my airflow is great and all components are cool via speccy and bios lol airflow is verry good have two intaking 140mm's , then a 120mm cpu fan and exhaust 120mm then the gpu has two fans its the Asus direct CU ii 4gb graphics card , and the psu takes its own air 120mm 880w psu overkill i know, i am using a i5 2500 and the motherboard is the Asus p8 h61m pro it has two pci slots i have the gpu in the bottem pci slot so its cooler away from the cpu
- Feb 18, 2010
- 30,566
- 321
- 107,640
use this and report what it found http://www.resplendence.com/whocrashed the other thing do you have any led on the board that lit except the board led itself and you have video onboard remove gpu and try the onboard to see if it will bsod .
What temperature is your system running at? On GPU Tweak, assuming you installed it, what is your gpu running at. I've had issues with the thick paste used on the Direct CUII coolers, with my R9 290X running way too hot. I replaced the paste and fixed the problem.
i'll run that test thank you, and system temps are around 38 degrees some parts lower some higher no temps are high and my gpu has been running fine for a long time ive had this card running 4k gta 5 smooth just yesterday lol literally
--------------------------------------------------------------------------------
Welcome to WhoCrashed (HOME EDITION) v 5.50
--------------------------------------------------------------------------------
This program checks for drivers which have been crashing your computer. If your computer has displayed a blue (or black) screen of death, suddenly rebooted or shut down then this program will help you find the root cause and possibly a solution.
Whenever a computer suddenly reboots without displaying any notice or blue (or black) screen of death, the first thing that is often thought about is a hardware failure. In reality, on Windows most crashes are caused by malfunctioning device drivers and kernel modules. In case of a kernel error, many computers do not show a blue screen unless they are configured for this. Instead these systems suddenly reboot without any notice.
This program will analyze your crash dumps with the single click of a button. It will tell you what drivers are likely to be responsible for crashing your computer. It will report a conclusion which offers suggestions on how to proceed in any situation while the analysis report will display internet links which will help you further troubleshoot any detected problems.
To obtain technical support visit www.resplendence.com/support
Click here to check if you have the latest version or if an update is available.
Just click the Analyze button for a comprehensible report ...
--------------------------------------------------------------------------------
Home Edition Notice
--------------------------------------------------------------------------------
This version of WhoCrashed is free for use at home only. If you would like to use this software at work or in a commercial environment you should get the professional edition of WhoCrashed which allows you to perform more thorough and detailed analysis. It also offers a range of additional features such as remote analysis on remote directories and remote computers on the network.
Click here for more information on the professional edition.
Click here to buy the the professional edition of WhoCrashed.
--------------------------------------------------------------------------------
System Information (local)
--------------------------------------------------------------------------------
computer name: DESKTOP-15S4HQR
windows version: Windows 10 , 10.0, build: 10240
windows dir: C:\Windows
Hardware: ASUSTeK COMPUTER INC., P8H61-M PRO
CPU: GenuineIntel Intel(R) Core(TM) i5-2500 CPU @ 3.30GHz Intel586, level: 6
4 logical processors, active mask: 15
RAM: 8553115648 total
--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Thu 13/08/2015 23:49:51 GMT your computer crashed
crash dump file: C:\Windows\Minidump\081415-29359-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14CC20)
Bugcheck code: 0x1E (0xFFFFFFFFC0000095, 0xFFFFF802E808BE31, 0x2, 0xFFFFE000DB2E6130)
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.
On Thu 13/08/2015 23:49:51 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: fltmgr.sys (FLTMGR!FltDecodeParameters+0x191A)
Bugcheck code: 0x1E (0xFFFFFFFFC0000095, 0xFFFFF802E808BE31, 0x2, 0xFFFFE000DB2E6130)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32\drivers\fltmgr.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Microsoft Filesystem Filter Manager
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 Thu 13/08/2015 23:11:43 GMT your computer crashed
crash dump file: C:\Windows\Minidump\081415-14906-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14CC20)
Bugcheck code: 0x3B (0xC0000095, 0xFFFFF803FB0F7E31, 0xFFFFD000214D86A0, 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 Thu 13/08/2015 23:10:24 GMT your computer crashed
crash dump file: C:\Windows\Minidump\081415-21046-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14CC20)
Bugcheck code: 0x157 (0xFFFFE000B00C45C0, 0x2, 0x2, 0x0)
Error: CUSTOM_ERROR
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
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 13/08/2015 23:06:37 GMT your computer crashed
crash dump file: C:\Windows\Minidump\081415-22500-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14CC20)
Bugcheck code: 0x7F (0x8, 0xFFFFF8039B248E70, 0xFFFFB000B38EA660, 0xFFFFF80399AA082B)
Error: UNEXPECTED_KERNEL_MODE_TRAP
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 the Intel CPU generated a trap and the kernel failed to catch this trap.
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 13/08/2015 22:52:44 GMT your computer crashed
crash dump file: C:\Windows\Minidump\081315-22125-01.dmp
This was probably caused by the following module: hal.dll (hal+0x3587F)
Bugcheck code: 0x124 (0x0, 0xFFFFE0008E88A028, 0xBE000000, 0x800400)
Error: WHEA_UNCORRECTABLE_ERROR
file path: C:\Windows\system32\hal.dll
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Hardware Abstraction Layer DLL
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 be caused by a thermal issue.
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 Thu 13/08/2015 22:42:28 GMT your computer crashed
crash dump file: C:\Windows\Minidump\081315-28390-01.dmp
This was probably caused by the following module: Unknown ()
Bugcheck code: 0x0 (0x0, 0x0, 0x0, 0x0)
Error: CUSTOM_ERROR
A third party driver was identified as the probable root cause of this system error.
Google query: CUSTOM_ERROR
--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------
7 crash dumps have been found and analyzed.
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.
Welcome to WhoCrashed (HOME EDITION) v 5.50
--------------------------------------------------------------------------------
This program checks for drivers which have been crashing your computer. If your computer has displayed a blue (or black) screen of death, suddenly rebooted or shut down then this program will help you find the root cause and possibly a solution.
Whenever a computer suddenly reboots without displaying any notice or blue (or black) screen of death, the first thing that is often thought about is a hardware failure. In reality, on Windows most crashes are caused by malfunctioning device drivers and kernel modules. In case of a kernel error, many computers do not show a blue screen unless they are configured for this. Instead these systems suddenly reboot without any notice.
This program will analyze your crash dumps with the single click of a button. It will tell you what drivers are likely to be responsible for crashing your computer. It will report a conclusion which offers suggestions on how to proceed in any situation while the analysis report will display internet links which will help you further troubleshoot any detected problems.
To obtain technical support visit www.resplendence.com/support
Click here to check if you have the latest version or if an update is available.
Just click the Analyze button for a comprehensible report ...
--------------------------------------------------------------------------------
Home Edition Notice
--------------------------------------------------------------------------------
This version of WhoCrashed is free for use at home only. If you would like to use this software at work or in a commercial environment you should get the professional edition of WhoCrashed which allows you to perform more thorough and detailed analysis. It also offers a range of additional features such as remote analysis on remote directories and remote computers on the network.
Click here for more information on the professional edition.
Click here to buy the the professional edition of WhoCrashed.
--------------------------------------------------------------------------------
System Information (local)
--------------------------------------------------------------------------------
computer name: DESKTOP-15S4HQR
windows version: Windows 10 , 10.0, build: 10240
windows dir: C:\Windows
Hardware: ASUSTeK COMPUTER INC., P8H61-M PRO
CPU: GenuineIntel Intel(R) Core(TM) i5-2500 CPU @ 3.30GHz Intel586, level: 6
4 logical processors, active mask: 15
RAM: 8553115648 total
--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Thu 13/08/2015 23:49:51 GMT your computer crashed
crash dump file: C:\Windows\Minidump\081415-29359-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14CC20)
Bugcheck code: 0x1E (0xFFFFFFFFC0000095, 0xFFFFF802E808BE31, 0x2, 0xFFFFE000DB2E6130)
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.
On Thu 13/08/2015 23:49:51 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: fltmgr.sys (FLTMGR!FltDecodeParameters+0x191A)
Bugcheck code: 0x1E (0xFFFFFFFFC0000095, 0xFFFFF802E808BE31, 0x2, 0xFFFFE000DB2E6130)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32\drivers\fltmgr.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Microsoft Filesystem Filter Manager
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 Thu 13/08/2015 23:11:43 GMT your computer crashed
crash dump file: C:\Windows\Minidump\081415-14906-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14CC20)
Bugcheck code: 0x3B (0xC0000095, 0xFFFFF803FB0F7E31, 0xFFFFD000214D86A0, 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 Thu 13/08/2015 23:10:24 GMT your computer crashed
crash dump file: C:\Windows\Minidump\081415-21046-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14CC20)
Bugcheck code: 0x157 (0xFFFFE000B00C45C0, 0x2, 0x2, 0x0)
Error: CUSTOM_ERROR
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
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 13/08/2015 23:06:37 GMT your computer crashed
crash dump file: C:\Windows\Minidump\081415-22500-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14CC20)
Bugcheck code: 0x7F (0x8, 0xFFFFF8039B248E70, 0xFFFFB000B38EA660, 0xFFFFF80399AA082B)
Error: UNEXPECTED_KERNEL_MODE_TRAP
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 the Intel CPU generated a trap and the kernel failed to catch this trap.
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 13/08/2015 22:52:44 GMT your computer crashed
crash dump file: C:\Windows\Minidump\081315-22125-01.dmp
This was probably caused by the following module: hal.dll (hal+0x3587F)
Bugcheck code: 0x124 (0x0, 0xFFFFE0008E88A028, 0xBE000000, 0x800400)
Error: WHEA_UNCORRECTABLE_ERROR
file path: C:\Windows\system32\hal.dll
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Hardware Abstraction Layer DLL
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 be caused by a thermal issue.
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 Thu 13/08/2015 22:42:28 GMT your computer crashed
crash dump file: C:\Windows\Minidump\081315-28390-01.dmp
This was probably caused by the following module: Unknown ()
Bugcheck code: 0x0 (0x0, 0x0, 0x0, 0x0)
Error: CUSTOM_ERROR
A third party driver was identified as the probable root cause of this system error.
Google query: CUSTOM_ERROR
--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------
7 crash dumps have been found and analyzed.
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.
ok progress i believed it crashed but then i waited and a balloon came in the corner sstating nvidia driver just failed on me maybe this is why it blue screened before blue screens usually occur when drivers are wierd and win 10 had alot of driver issues on start im just going to check the gpu in device manager
ok so print screened it this time
so will type it and try reinstalling drivers :
Display driver has stopped responding and has recovered
Display driver NVIDIA Windows Kernal Mode Driver, Version 353.54 stopped responding and has successfully recovered
and then the game has crashed by now
so will type it and try reinstalling drivers :
Display driver has stopped responding and has recovered
Display driver NVIDIA Windows Kernal Mode Driver, Version 353.54 stopped responding and has successfully recovered
and then the game has crashed by now
TRENDING THREADS
-
News Windows 11 will reportedly display a watermark if your PC does not support AI requirements- Started by Admin
- Replies: 19
-
-
-
Discussion What's your favourite video game you've been playing?- Started by amdfangirl
- Replies: 3K
Facebook
Twitter
Instagram