BSOD
in IT Support ·
Here are the BSOD codes I pulled from WhoCrashed..
System Information (local)
--------------------------------------------------------------------------------
computer name: LUX-PC
windows version: Windows 7 Service Pack 1, 6.1, build: 7601
windows dir: C:\Windows
Hardware: ASRock, 970 Pro3 R2.0
CPU: AuthenticAMD AMD FX(tm)-6300 Six-Core Processor AMD586, level: 21
6 logical processors, active mask: 63
RAM: 4249604096 total
--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
Your computer crashed on Tuesday, September 30, 2014, at 6:28:27 PM
crash dump file: C:\Windows\Minidump\093014-26052-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0x50 (0xFFFFF8001303DE88, 0x0, 0xFFFFF80002EC4E9F, 0x2)
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 looks like a typical software driver bug rather than a hardware issue.
The crash happened within the Windows kernel. It’s possible another unidentified driver is causing the trouble.
Your computer crashed on Tuesday, September 30, 2014, at 6:28:27 PM
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: win32k.sys (win32k!EngRestoreFloatingPointState+0xDA15)
Bugcheck code: 0x50 (0xFFFFF8001303DE88, 0x0, 0xFFFFF80002EC4E9F, 0x2)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\win32k.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Multi-User Win32 driver bug
Bug check description: This indicates that invalid system memory has been referenced.
This seems to be a standard software driver bug and likely isn't a hardware problem.
The crash occurred in a standard Microsoft module. There might be an issue with your system configuration, or possibly another driver we haven't caught yet.
Your computer crashed on Tuesday, September 30, 2014, at 6:26:39 PM
crash dump file: C:\Windows\Minidump\093014-25849-01.dmp
This was probably caused by the following module: tcpip.sys (tcpip+0x23975)
Bugcheck code: 0x1E (0x0, 0x0, 0x0, 0x0)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32\drivers\tcpip.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: TCP/IP Driver
Bug check description: This indicates that a kernel-mode program generated an exception that the error handler didn't catch.
This appears to be a typical software driver bug and shouldn't be a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration could be off, or it could be another unidentified driver.
Your computer crashed on Tuesday, September 30, 2014, at 6:22:59 PM
crash dump file: C:\Windows\Minidump\093014-24102-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0xA (0x38, 0x2, 0x0, 0xFFFFF80002EE3567)
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.
It looks like a standard software driver bug rather than anything involving your hardware.
The crash happened within the Windows kernel. It’s possible some other unidentified driver is causing the trouble here.
Your computer crashed on Tuesday, September 30, 2014, at 5:47:20 PM GMT
crash dump file: C:\Windows\Minidump\093014-19702-01.dmp
This was likely triggered by this module: Unknown ()
Bugcheck code: 0x0 (0x0, 0x0, 0x0, 0x0)
Error: CUSTOM_ERROR
It seems like a third-party driver is the most likely culprit for this system error.
Google query : CUSTOM_ERROR
Your computer crashed on Tuesday, September 30, 2014, at 5:14:54 PM GMT
crash dump file: C:\Windows\Minidump\093014-27346-01.dmp
This was likely triggered by this module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0x101 (0x21, 0x0, 0xFFFFF88001FBB180, 0x5)
Error: CLOCK_WATCHDOG_TIMEOUT
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This means a secondary processor in a multi-processor setup didn't receive its expected clock interrupt within the set timeframe.
This looks like a typical software driver bug and probably isn't a hardware issue, though it could potentially be related to overheating.
The crash occurred in the Windows kernel. There might be another driver involved that we can't pinpoint just yet.
Your computer crashed on Tuesday, September 30, 2014, at 4:39:19 PM GMT
crash dump file: C:\Windows\Minidump\093014-21465-01.dmp
This was likely triggered by this module: usbport.sys (USBPORT+0x2D27C)
Bugcheck code: 0xA (0xFFFFF80000BACB90, 0x2, 0x1, 0xFFFFF80002E8F4A1)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\usbport.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: USB 1.1 & 2.0 Port Driver
Bug check description: This suggests that Microsoft Windows or a kernel-mode driver tried to access paged memory while at DISPATCH_LEVEL or higher.
This appears to be a common software driver bug and is unlikely to be a hardware problem.
The crash happened in a standard Microsoft module. Your system settings might be off, or perhaps another driver on your machine is causing the issue without being identified yet.
System Information (local)
--------------------------------------------------------------------------------
computer name: LUX-PC
windows version: Windows 7 Service Pack 1, 6.1, build: 7601
windows dir: C:\Windows
Hardware: ASRock, 970 Pro3 R2.0
CPU: AuthenticAMD AMD FX(tm)-6300 Six-Core Processor AMD586, level: 21
6 logical processors, active mask: 63
RAM: 4249604096 total
--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
Your computer crashed on Tuesday, September 30, 2014, at 6:28:27 PM
crash dump file: C:\Windows\Minidump\093014-26052-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0x50 (0xFFFFF8001303DE88, 0x0, 0xFFFFF80002EC4E9F, 0x2)
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 looks like a typical software driver bug rather than a hardware issue.
The crash happened within the Windows kernel. It’s possible another unidentified driver is causing the trouble.
Your computer crashed on Tuesday, September 30, 2014, at 6:28:27 PM
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: win32k.sys (win32k!EngRestoreFloatingPointState+0xDA15)
Bugcheck code: 0x50 (0xFFFFF8001303DE88, 0x0, 0xFFFFF80002EC4E9F, 0x2)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\win32k.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Multi-User Win32 driver bug
Bug check description: This indicates that invalid system memory has been referenced.
This seems to be a standard software driver bug and likely isn't a hardware problem.
The crash occurred in a standard Microsoft module. There might be an issue with your system configuration, or possibly another driver we haven't caught yet.
Your computer crashed on Tuesday, September 30, 2014, at 6:26:39 PM
crash dump file: C:\Windows\Minidump\093014-25849-01.dmp
This was probably caused by the following module: tcpip.sys (tcpip+0x23975)
Bugcheck code: 0x1E (0x0, 0x0, 0x0, 0x0)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32\drivers\tcpip.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: TCP/IP Driver
Bug check description: This indicates that a kernel-mode program generated an exception that the error handler didn't catch.
This appears to be a typical software driver bug and shouldn't be a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration could be off, or it could be another unidentified driver.
Your computer crashed on Tuesday, September 30, 2014, at 6:22:59 PM
crash dump file: C:\Windows\Minidump\093014-24102-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0xA (0x38, 0x2, 0x0, 0xFFFFF80002EE3567)
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.
It looks like a standard software driver bug rather than anything involving your hardware.
The crash happened within the Windows kernel. It’s possible some other unidentified driver is causing the trouble here.
Your computer crashed on Tuesday, September 30, 2014, at 5:47:20 PM GMT
crash dump file: C:\Windows\Minidump\093014-19702-01.dmp
This was likely triggered by this module: Unknown ()
Bugcheck code: 0x0 (0x0, 0x0, 0x0, 0x0)
Error: CUSTOM_ERROR
It seems like a third-party driver is the most likely culprit for this system error.
Google query : CUSTOM_ERROR
Your computer crashed on Tuesday, September 30, 2014, at 5:14:54 PM GMT
crash dump file: C:\Windows\Minidump\093014-27346-01.dmp
This was likely triggered by this module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0x101 (0x21, 0x0, 0xFFFFF88001FBB180, 0x5)
Error: CLOCK_WATCHDOG_TIMEOUT
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This means a secondary processor in a multi-processor setup didn't receive its expected clock interrupt within the set timeframe.
This looks like a typical software driver bug and probably isn't a hardware issue, though it could potentially be related to overheating.
The crash occurred in the Windows kernel. There might be another driver involved that we can't pinpoint just yet.
Your computer crashed on Tuesday, September 30, 2014, at 4:39:19 PM GMT
crash dump file: C:\Windows\Minidump\093014-21465-01.dmp
This was likely triggered by this module: usbport.sys (USBPORT+0x2D27C)
Bugcheck code: 0xA (0xFFFFF80000BACB90, 0x2, 0x1, 0xFFFFF80002E8F4A1)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\usbport.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: USB 1.1 & 2.0 Port Driver
Bug check description: This suggests that Microsoft Windows or a kernel-mode driver tried to access paged memory while at DISPATCH_LEVEL or higher.
This appears to be a common software driver bug and is unlikely to be a hardware problem.
The crash happened in a standard Microsoft module. Your system settings might be off, or perhaps another driver on your machine is causing the issue without being identified yet.