- Jun 5, 2017
- 3
- 0
- 4,510
Hey there, so i recently installed a x2 8gb kit in my cpu, and its worked flawlessly for the past two weeks but starting last night i've gotten about 4 BSOD. I'm not sure how to figure out what exactly is causing the problem but i did DL whocrashed and ran it, here are the results. I would seriously appreciate any information/help/direction that you folks could give me. Thanks!
Crash dumps are enabled on your computer.
Crash dump directories:
C:\Windows
C:\Windows\Minidump
On Sun 9/20/2020 7:22:11 PM your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\092020-5281-01.dmp
This was probably caused by the following module: hardware.sys (hardware)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFB563F7EDC2B7, 0xFFFF878C806A65F0, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
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.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: hardware.sys .
Google query: hardware.sys SYSTEM_SERVICE_EXCEPTION
On Sun 9/20/2020 7:22:11 PM your computer crashed or a problem was reported
crash dump file: C:\Windows\MEMORY.DMP
This was probably caused by the following module: hardware.sys (hardware)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFB563F7EDC2B7, 0xFFFF878C806A65F0, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
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.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: hardware.sys .
Google query: hardware.sys SYSTEM_SERVICE_EXCEPTION
On Sun 9/20/2020 12:32:59 PM your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\092020-4812-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1C2990)
Bugcheck code: 0x18 (0x0, 0xFFFFAC08B56611B0, 0x2, 0xFFFFF8054566B3FF)
Error: REFERENCE_BY_POINTER
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 the reference count of an object is illegal for the current state of the object.
This bug check belongs to the crash dump test that you have performed with WhoCrashed or other software. It means that a crash dump file was properly written out.
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 9/20/2020 12:15:09 PM your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\092020-4906-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1C2990)
Bugcheck code: 0x1A (0x41201, 0xFFFFFCAE0423AA00, 0x81000082BEF6D867, 0xFFFFD703F6CBF320)
Error: MEMORY_MANAGEMENT
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 severe memory management error occurred.
This might be a case of memory corruption. This may be because of a hardware issue such as faulty RAM, overheating (thermal issue) or because of a buggy driver. 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 9/19/2020 5:12:42 PM your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\091920-5296-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1C2990)
Bugcheck code: 0x50 (0xFFFFF86D052A0E20, 0x10, 0xFFFFF86D052A0E20, 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 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 9/19/2020 4:17:06 PM your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\091920-6984-01.dmp
This was probably caused by the following module: nvlddmkm.sys (0xFFFFF8047263E2B2)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF8047263E2B2, 0xFFFF9282E3308358, 0xFFFF9282E3307BA0)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_edab19158bdd0d0a\nvlddmkm.sys
product: NVIDIA Windows Kernel Mode Driver, Version 451.67
company: NVIDIA Corporation
description: NVIDIA Windows Kernel Mode Driver, Version 451.67
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.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: nvlddmkm.sys (NVIDIA Windows Kernel Mode Driver, Version 451.67 , NVIDIA Corporation).
Google query: nvlddmkm.sys NVIDIA Corporation SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
Crash dumps are enabled on your computer.
Crash dump directories:
C:\Windows
C:\Windows\Minidump
On Sun 9/20/2020 7:22:11 PM your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\092020-5281-01.dmp
This was probably caused by the following module: hardware.sys (hardware)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFB563F7EDC2B7, 0xFFFF878C806A65F0, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
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.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: hardware.sys .
Google query: hardware.sys SYSTEM_SERVICE_EXCEPTION
On Sun 9/20/2020 7:22:11 PM your computer crashed or a problem was reported
crash dump file: C:\Windows\MEMORY.DMP
This was probably caused by the following module: hardware.sys (hardware)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFB563F7EDC2B7, 0xFFFF878C806A65F0, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
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.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: hardware.sys .
Google query: hardware.sys SYSTEM_SERVICE_EXCEPTION
On Sun 9/20/2020 12:32:59 PM your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\092020-4812-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1C2990)
Bugcheck code: 0x18 (0x0, 0xFFFFAC08B56611B0, 0x2, 0xFFFFF8054566B3FF)
Error: REFERENCE_BY_POINTER
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 the reference count of an object is illegal for the current state of the object.
This bug check belongs to the crash dump test that you have performed with WhoCrashed or other software. It means that a crash dump file was properly written out.
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 9/20/2020 12:15:09 PM your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\092020-4906-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1C2990)
Bugcheck code: 0x1A (0x41201, 0xFFFFFCAE0423AA00, 0x81000082BEF6D867, 0xFFFFD703F6CBF320)
Error: MEMORY_MANAGEMENT
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 severe memory management error occurred.
This might be a case of memory corruption. This may be because of a hardware issue such as faulty RAM, overheating (thermal issue) or because of a buggy driver. 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 9/19/2020 5:12:42 PM your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\091920-5296-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1C2990)
Bugcheck code: 0x50 (0xFFFFF86D052A0E20, 0x10, 0xFFFFF86D052A0E20, 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 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 9/19/2020 4:17:06 PM your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\091920-6984-01.dmp
This was probably caused by the following module: nvlddmkm.sys (0xFFFFF8047263E2B2)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF8047263E2B2, 0xFFFF9282E3308358, 0xFFFF9282E3307BA0)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_edab19158bdd0d0a\nvlddmkm.sys
product: NVIDIA Windows Kernel Mode Driver, Version 451.67
company: NVIDIA Corporation
description: NVIDIA Windows Kernel Mode Driver, Version 451.67
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.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: nvlddmkm.sys (NVIDIA Windows Kernel Mode Driver, Version 451.67 , NVIDIA Corporation).
Google query: nvlddmkm.sys NVIDIA Corporation SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
WhoCrashed and BlueScreenView only give brief summary info with on real detail or ability to dig into unfortunately.
Facebook
Twitter
Instagram