So I get random BSOD throughout the day. But the time when I know the computer will crash is when I extract a certain folder. I don't know if its for all large folders, but it always crashed when I extract this folder. Its a css (counter strike source) addon textures for Gmod. Whenever I attempt to extract (copy) it into anywhere, then my computer crashed with a BSOD.
But it also crashed for any random reason, sometimes 5 mins in for doing nothing. Sometimes I could do alot of tasks at once and it finally crashes.
I replaced my video card with still crashed, and I ran a memtest on my ram and it passed. I ran a gpu stress test and passed without crashing. I replaced the hard drive and still crashed.
But here is the report from WhoCrashed, alot of the errors are from Realtek 8136/8168/8169 PCI/PCIe Adapters. I suspected it to be my realtek network driver, so I updated it and still received BSOD. I also updated my only other realtek driver which is my audio driver and it still crashed after the update. Please help, I already brought it to a computer repair shop and they did absolutely nothing.
--------------------------------------------------------------------------------
System Information (local)
--------------------------------------------------------------------------------
computer name: ROWOW-PC
windows version: Windows 7 Service Pack 1, 6.1, build: 7601
windows dir: C:\Windows
Hardware: ASRock, 970 Performance
CPU: AuthenticAMD AMD FX(tm)-9590 Eight-Core Processor AMD586, level: 21
8 logical processors, active mask: 255
RAM: 4264603648 total
--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Tue 3/10/2015 12:57:05 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\030915-45131-01.dmp
This was probably caused by the following module: rt64win7.sys (Rt64win7+0x29C8)
Bugcheck code: 0x1E (0x0, 0x0, 0x0, 0x0)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32\drivers\rt64win7.sys
product: Realtek 8136/8168/8169 PCI/PCIe Adapters
company: Realtek
description: Realtek 8136/8168/8169 NDIS 6.20 64-bit Driver
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.
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: rt64win7.sys (Realtek 8136/8168/8169 NDIS 6.20 64-bit Driver , Realtek ).
Google query: Realtek KMODE_EXCEPTION_NOT_HANDLED
On Tue 3/10/2015 12:57:05 AM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheck+0x0)
Bugcheck code: 0x1E (0x0, 0x0, 0x0, 0x0)
Error: KMODE_EXCEPTION_NOT_HANDLED
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 Sun 3/8/2015 10:46:30 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\030815-29874-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x74EC0)
Bugcheck code: 0xA (0xFFFFF88042F458C0, 0x2, 0x1, 0xFFFFF8000368380F)
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 Sun 3/8/2015 9:11:54 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\030815-31481-01.dmp
This was probably caused by the following module: hal.dll (0xFFFFF80003C0D502)
Bugcheck code: 0xA (0x8, 0x2, 0x0, 0xFFFFF80003C0D502)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\hal.dll
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Hardware Abstraction Layer DLL
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 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 Sun 3/8/2015 2:36:35 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\030815-36707-01.dmp
This was probably caused by the following module: rt64win7.sys (Rt64win7+0x29C8)
Bugcheck code: 0x1E (0x0, 0x0, 0x0, 0x0)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32\drivers\rt64win7.sys
product: Realtek 8136/8168/8169 PCI/PCIe Adapters
company: Realtek
description: Realtek 8136/8168/8169 NDIS 6.20 64-bit Driver
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.
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: rt64win7.sys (Realtek 8136/8168/8169 NDIS 6.20 64-bit Driver , Realtek ).
Google query: Realtek KMODE_EXCEPTION_NOT_HANDLED
On Sat 3/7/2015 5:17:00 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\030715-31527-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x74EC0)
Bugcheck code: 0xA (0x0, 0xD, 0x1, 0xFFFFF80003E1CCE0)
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 Sat 3/7/2015 5:09:32 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\030715-30045-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x74EC0)
Bugcheck code: 0x1E (0xFFFFFFFFC000001D, 0xFFFFF80003C87562, 0x0, 0x1EB00)
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 Sat 3/7/2015 4:58:37 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\030715-32214-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x74E90)
Bugcheck code: 0x1E (0x0, 0x0, 0x0, 0x0)
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 Sat 3/7/2015 4:06:03 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\030715-36083-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x74EC0)
Bugcheck code: 0xD1 (0x0, 0xD, 0x1, 0xFFFFFA8004B0B1B0)
Error: DRIVER_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 a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
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 3/7/2015 3:20:16 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\030715-66097-01.dmp
This was probably caused by the following module: rt64win7.sys (Rt64win7+0x29C8)
Bugcheck code: 0x1E (0x0, 0x0, 0x0, 0x0)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32\drivers\rt64win7.sys
product: Realtek 8136/8168/8169 PCI/PCIe Adapters
company: Realtek
description: Realtek 8136/8168/8169 NDIS 6.20 64-bit Driver
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.
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: rt64win7.sys (Realtek 8136/8168/8169 NDIS 6.20 64-bit Driver , Realtek ).
Google query: Realtek KMODE_EXCEPTION_NOT_HANDLED
But it also crashed for any random reason, sometimes 5 mins in for doing nothing. Sometimes I could do alot of tasks at once and it finally crashes.
I replaced my video card with still crashed, and I ran a memtest on my ram and it passed. I ran a gpu stress test and passed without crashing. I replaced the hard drive and still crashed.
But here is the report from WhoCrashed, alot of the errors are from Realtek 8136/8168/8169 PCI/PCIe Adapters. I suspected it to be my realtek network driver, so I updated it and still received BSOD. I also updated my only other realtek driver which is my audio driver and it still crashed after the update. Please help, I already brought it to a computer repair shop and they did absolutely nothing.
--------------------------------------------------------------------------------
System Information (local)
--------------------------------------------------------------------------------
computer name: ROWOW-PC
windows version: Windows 7 Service Pack 1, 6.1, build: 7601
windows dir: C:\Windows
Hardware: ASRock, 970 Performance
CPU: AuthenticAMD AMD FX(tm)-9590 Eight-Core Processor AMD586, level: 21
8 logical processors, active mask: 255
RAM: 4264603648 total
--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Tue 3/10/2015 12:57:05 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\030915-45131-01.dmp
This was probably caused by the following module: rt64win7.sys (Rt64win7+0x29C8)
Bugcheck code: 0x1E (0x0, 0x0, 0x0, 0x0)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32\drivers\rt64win7.sys
product: Realtek 8136/8168/8169 PCI/PCIe Adapters
company: Realtek
description: Realtek 8136/8168/8169 NDIS 6.20 64-bit Driver
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.
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: rt64win7.sys (Realtek 8136/8168/8169 NDIS 6.20 64-bit Driver , Realtek ).
Google query: Realtek KMODE_EXCEPTION_NOT_HANDLED
On Tue 3/10/2015 12:57:05 AM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheck+0x0)
Bugcheck code: 0x1E (0x0, 0x0, 0x0, 0x0)
Error: KMODE_EXCEPTION_NOT_HANDLED
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 Sun 3/8/2015 10:46:30 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\030815-29874-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x74EC0)
Bugcheck code: 0xA (0xFFFFF88042F458C0, 0x2, 0x1, 0xFFFFF8000368380F)
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 Sun 3/8/2015 9:11:54 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\030815-31481-01.dmp
This was probably caused by the following module: hal.dll (0xFFFFF80003C0D502)
Bugcheck code: 0xA (0x8, 0x2, 0x0, 0xFFFFF80003C0D502)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\hal.dll
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Hardware Abstraction Layer DLL
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 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 Sun 3/8/2015 2:36:35 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\030815-36707-01.dmp
This was probably caused by the following module: rt64win7.sys (Rt64win7+0x29C8)
Bugcheck code: 0x1E (0x0, 0x0, 0x0, 0x0)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32\drivers\rt64win7.sys
product: Realtek 8136/8168/8169 PCI/PCIe Adapters
company: Realtek
description: Realtek 8136/8168/8169 NDIS 6.20 64-bit Driver
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.
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: rt64win7.sys (Realtek 8136/8168/8169 NDIS 6.20 64-bit Driver , Realtek ).
Google query: Realtek KMODE_EXCEPTION_NOT_HANDLED
On Sat 3/7/2015 5:17:00 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\030715-31527-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x74EC0)
Bugcheck code: 0xA (0x0, 0xD, 0x1, 0xFFFFF80003E1CCE0)
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 Sat 3/7/2015 5:09:32 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\030715-30045-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x74EC0)
Bugcheck code: 0x1E (0xFFFFFFFFC000001D, 0xFFFFF80003C87562, 0x0, 0x1EB00)
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 Sat 3/7/2015 4:58:37 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\030715-32214-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x74E90)
Bugcheck code: 0x1E (0x0, 0x0, 0x0, 0x0)
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 Sat 3/7/2015 4:06:03 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\030715-36083-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x74EC0)
Bugcheck code: 0xD1 (0x0, 0xD, 0x1, 0xFFFFFA8004B0B1B0)
Error: DRIVER_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 a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
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 3/7/2015 3:20:16 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\030715-66097-01.dmp
This was probably caused by the following module: rt64win7.sys (Rt64win7+0x29C8)
Bugcheck code: 0x1E (0x0, 0x0, 0x0, 0x0)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32\drivers\rt64win7.sys
product: Realtek 8136/8168/8169 PCI/PCIe Adapters
company: Realtek
description: Realtek 8136/8168/8169 NDIS 6.20 64-bit Driver
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.
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: rt64win7.sys (Realtek 8136/8168/8169 NDIS 6.20 64-bit Driver , Realtek ).
Google query: Realtek KMODE_EXCEPTION_NOT_HANDLED
Facebook
Twitter
Instagram