Hey, so basically my problem is that I get bluescreens very often. I had one today, but computer actually froze in the bluescreen and doesn't show up in logs.
System build from WhoCrashed:
Everything at stock, heating that can be seen through programs like HWIDmonitor are ruled out for either problem.
Some logs from WhoCrashed:
Some of these blue screens I have never seen, and I actually looked at the timestamp on one and it happened when I was shutting down my computer. I have ran Memtest86+, sfc /scannow but nothing there. I have switched my power supply.
As for the other problem, computer freezing, it only happens when I'm using very high amounts of GPU & CPU power. Like playing CS:GO with uncapped FPS, resulting in 70-99% GPU usage. Does not happen instantly, after 10 mins or so. Heat is ruled out unless there is a bad sensor.
System build from WhoCrashed:
computer name: RAVENHEIM
windows version: Windows 8.1 , 6.2, build: 9200
windows dir: C:\Windows
Hardware: ASRock, Z97 Pro3
CPU: GenuineIntel Intel(R) Core(TM) i7-4790K CPU @ 4.00GHz Intel586, level: 6
8 logical processors, active mask: 255
RAM: 8538402816 total
windows version: Windows 8.1 , 6.2, build: 9200
windows dir: C:\Windows
Hardware: ASRock, Z97 Pro3
CPU: GenuineIntel Intel(R) Core(TM) i7-4790K CPU @ 4.00GHz Intel586, level: 6
8 logical processors, active mask: 255
RAM: 8538402816 total
Some logs from WhoCrashed:
On Sun 28.9.2014 22:19:07 GMT your computer crashed
crash dump file: C:\Windows\Minidump\092914-6250-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x153CA0)
Bugcheck code: 0xA0 (0x107, 0xA, 0xFFFFE00108F53D10, 0x0)
Error: INTERNAL_POWER_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 the power policy manager experienced a fatal error.
This problem might be caused by a 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 28.9.2014 17:47:22 GMT your computer crashed
crash dump file: C:\Windows\Minidump\092814-20062-01.dmp
This was probably caused by the following module: win32k.sys (win32k+0xE6500)
Bugcheck code: 0xFC (0xFFFFF9600019C500, 0xD920000114126021, 0xFFFFD00021B7F3B0, 0x2)
Error: ATTEMPTED_EXECUTE_OF_NOEXECUTE_MEMORY
file path: C:\Windows\system32\win32k.sys
product: Microsoft® Windows® -käyttöjärjestelmä
company: Microsoft Corporation
description: Monikäyttäjä Win32-ohjain
Bug check description: This indicates that an attempt was made to execute non-executable memory.
This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules. There is a possibility this problem was caused by a virus or other malware.
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 26.9.2014 12:06:38 GMT your computer crashed
crash dump file: C:\Windows\Minidump\092614-9578-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x153CA0)
Bugcheck code: 0x35 (0xFFFFE000E6877810, 0x0, 0x0, 0x0)
Error: NO_MORE_IRP_STACK_LOCATIONS
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 occurs when the IoCallDriver packet has no more stack locations remaining.
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 22.9.2014 7:47:28 GMT your computer crashed
crash dump file: C:\Windows\Minidump\092214-9265-01.dmp
This was probably caused by the following module: portcls.sys (0xFFFFF80135872DD9)
Bugcheck code: 0x50 (0xFFFFE001AE5C6008, 0x0, 0xFFFFF80135872DD9, 0x0)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\drivers\portcls.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Port Class (Class Driver for Port/Miniport Devices)
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 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 Sat 20.9.2014 21:16:19 GMT your computer crashed
crash dump file: C:\Windows\Minidump\092114-10937-01.dmp
This was probably caused by the following module: hal.dll (hal+0x37213)
Bugcheck code: 0x124 (0x0, 0xFFFFE001759FC028, 0xBF800000, 0x124)
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.
This happened when I tried to remove adaptive CPU voltage and ended up not putting in a voltage amount
On Wed 27.8.2014 21:21:31 GMT your computer crashed
crash dump file: C:\Windows\Minidump\082814-13515-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x153FA0)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF8024A90BD75, 0xFFFFD0013F853B90, 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 Tue 26.8.2014 4:03:39 GMT your computer crashed
crash dump file: C:\Windows\Minidump\082614-9250-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x153FA0)
Bugcheck code: 0xAB (0x1, 0x5070, 0x0, 0x6)
Error: SESSION_HAS_VALID_POOL_ON_EXIT
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 session unload occurred while a session driver still held memory.
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 Tue 26.8.2014 3:12:20 GMT your computer crashed
crash dump file: C:\Windows\Minidump\082614-5671-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x153FA0)
Bugcheck code: 0xEF (0xFFFFE001BAAC4900, 0x0, 0x0, 0x0)
Error: CRITICAL_PROCESS_DIED
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 critical system process died.
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 Tue 26.8.2014 3:08:56 GMT your computer crashed
crash dump file: C:\Windows\Minidump\082614-17796-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x153FA0)
Bugcheck code: 0xA (0xFFFFFA8006620048, 0x2, 0x1, 0xFFFFF803DC738596)
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 25.8.2014 11:41:25 GMT your computer crashed
crash dump file: C:\Windows\Minidump\082514-16640-01.dmp
This was probably caused by the following module: wdf01000.sys (Wdf01000+0x109C)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF8010625F09C, 0x0, 0xFFFFFFFFFFFFFFFF)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32\drivers\wdf01000.sys
product: Microsoft® Windows® -käyttöjärjestelmä
company: Microsoft Corporation
description: Suorituksenaikainen ydintilaohjainkehys
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.
Download to all these dumps: http://puu.sh/bSnbf.rar
Bluescreens on Bluescreenview: http://puu.sh/bSnwb.png
crash dump file: C:\Windows\Minidump\092914-6250-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x153CA0)
Bugcheck code: 0xA0 (0x107, 0xA, 0xFFFFE00108F53D10, 0x0)
Error: INTERNAL_POWER_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 the power policy manager experienced a fatal error.
This problem might be caused by a 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 28.9.2014 17:47:22 GMT your computer crashed
crash dump file: C:\Windows\Minidump\092814-20062-01.dmp
This was probably caused by the following module: win32k.sys (win32k+0xE6500)
Bugcheck code: 0xFC (0xFFFFF9600019C500, 0xD920000114126021, 0xFFFFD00021B7F3B0, 0x2)
Error: ATTEMPTED_EXECUTE_OF_NOEXECUTE_MEMORY
file path: C:\Windows\system32\win32k.sys
product: Microsoft® Windows® -käyttöjärjestelmä
company: Microsoft Corporation
description: Monikäyttäjä Win32-ohjain
Bug check description: This indicates that an attempt was made to execute non-executable memory.
This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules. There is a possibility this problem was caused by a virus or other malware.
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 26.9.2014 12:06:38 GMT your computer crashed
crash dump file: C:\Windows\Minidump\092614-9578-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x153CA0)
Bugcheck code: 0x35 (0xFFFFE000E6877810, 0x0, 0x0, 0x0)
Error: NO_MORE_IRP_STACK_LOCATIONS
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 occurs when the IoCallDriver packet has no more stack locations remaining.
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 22.9.2014 7:47:28 GMT your computer crashed
crash dump file: C:\Windows\Minidump\092214-9265-01.dmp
This was probably caused by the following module: portcls.sys (0xFFFFF80135872DD9)
Bugcheck code: 0x50 (0xFFFFE001AE5C6008, 0x0, 0xFFFFF80135872DD9, 0x0)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\drivers\portcls.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Port Class (Class Driver for Port/Miniport Devices)
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 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 Sat 20.9.2014 21:16:19 GMT your computer crashed
crash dump file: C:\Windows\Minidump\092114-10937-01.dmp
This was probably caused by the following module: hal.dll (hal+0x37213)
Bugcheck code: 0x124 (0x0, 0xFFFFE001759FC028, 0xBF800000, 0x124)
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.
This happened when I tried to remove adaptive CPU voltage and ended up not putting in a voltage amount
On Wed 27.8.2014 21:21:31 GMT your computer crashed
crash dump file: C:\Windows\Minidump\082814-13515-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x153FA0)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF8024A90BD75, 0xFFFFD0013F853B90, 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 Tue 26.8.2014 4:03:39 GMT your computer crashed
crash dump file: C:\Windows\Minidump\082614-9250-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x153FA0)
Bugcheck code: 0xAB (0x1, 0x5070, 0x0, 0x6)
Error: SESSION_HAS_VALID_POOL_ON_EXIT
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 session unload occurred while a session driver still held memory.
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 Tue 26.8.2014 3:12:20 GMT your computer crashed
crash dump file: C:\Windows\Minidump\082614-5671-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x153FA0)
Bugcheck code: 0xEF (0xFFFFE001BAAC4900, 0x0, 0x0, 0x0)
Error: CRITICAL_PROCESS_DIED
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 critical system process died.
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 Tue 26.8.2014 3:08:56 GMT your computer crashed
crash dump file: C:\Windows\Minidump\082614-17796-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x153FA0)
Bugcheck code: 0xA (0xFFFFFA8006620048, 0x2, 0x1, 0xFFFFF803DC738596)
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 25.8.2014 11:41:25 GMT your computer crashed
crash dump file: C:\Windows\Minidump\082514-16640-01.dmp
This was probably caused by the following module: wdf01000.sys (Wdf01000+0x109C)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF8010625F09C, 0x0, 0xFFFFFFFFFFFFFFFF)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32\drivers\wdf01000.sys
product: Microsoft® Windows® -käyttöjärjestelmä
company: Microsoft Corporation
description: Suorituksenaikainen ydintilaohjainkehys
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.
Download to all these dumps: http://puu.sh/bSnbf.rar
Bluescreens on Bluescreenview: http://puu.sh/bSnwb.png
Some of these blue screens I have never seen, and I actually looked at the timestamp on one and it happened when I was shutting down my computer. I have ran Memtest86+, sfc /scannow but nothing there. I have switched my power supply.
As for the other problem, computer freezing, it only happens when I'm using very high amounts of GPU & CPU power. Like playing CS:GO with uncapped FPS, resulting in 70-99% GPU usage. Does not happen instantly, after 10 mins or so. Heat is ruled out unless there is a bad sensor.
Facebook
Twitter
Instagram