I reinstalled Windows 7 after I changed out my PSU for a Corsair 750W. My old one was a Rocketfish. I'm running an Asus Sabertooth Z77, an Intel i7-3770S, with 16GB of Corsair Vengeance DDR3. I have an nVidia GTX 770 running as well. I ran Whocrashed and here were the results:
Any ideas why this keeps happening? As I said, fresh install. Thanks.
On Thu 4/17/2014 9:08:05 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\041714-19562-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0x1A (0x5100, 0xFFFFF6FC50001358, 0x1, 0xA4D000034E60E963)
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. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
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 4/17/2014 9:08:05 PM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ntfs.sys (Ntfs+0xAF59C)
Bugcheck code: 0x1A (0x5100, 0xFFFFF6FC50001358, 0x1, 0xA4D000034E60E963)
Error: MEMORY_MANAGEMENT
file path: C:\Windows\system32\drivers\ntfs.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT File System Driver
Bug check description: This indicates that a severe memory management error occurred.
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.
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 4/17/2014 5:54:08 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\041714-16879-01.dmp
This was probably caused by the following module: ndis.sys (ndis+0x5CF8)
Bugcheck code: 0xD1 (0xB8863D8, 0x2, 0x1, 0xFFFFF88001621CF8)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\ndis.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NDIS 6.20 driver
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 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 4/17/2014 1:52:45 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\041714-19125-01.dmp
This was probably caused by the following module: fltmgr.sys (fltmgr+0x244D)
Bugcheck code: 0x3B (0xC000001D, 0xFFFFF8800126944D, 0xFFFFF88008FAE360, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
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 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 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 4/17/2014 1:50:33 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\041714-17565-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0xA (0xFFFFF880033F635C, 0xD, 0x0, 0xFFFFF80002AE1149)
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 Thu 4/17/2014 1:08:18 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\041714-21637-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0x50 (0xFFFFFFFFFFFFFFFF, 0x8, 0xFFFFFFFFFFFFFFFF, 0x0)
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 Thu 4/17/2014 12:16:57 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\041714-21309-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0x50 (0xFFFFF3001CA1EE10, 0x1, 0xFFFFF80002D5B64A, 0x7)
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 Thu 4/17/2014 10:34:58 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\041714-21372-01.dmp
This was probably caused by the following module: spldr.sys (spldr+0xE20)
Bugcheck code: 0xFC (0xFFFFF880017D9E20, 0x8000000004056963, 0xFFFFF8800AB6B310, 0x0)
Error: ATTEMPTED_EXECUTE_OF_NOEXECUTE_MEMORY
file path: C:\Windows\system32\drivers\spldr.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: loader for security processor
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 Thu 4/17/2014 2:11:42 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\041614-22027-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFFA800E582E28, 0x1, 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 Wed 4/16/2014 2:53:51 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\041614-20670-01.dmp
This was probably caused by the following module: ndis.sys (ndis+0x76CB)
Bugcheck code: 0xD1 (0xFFFFF300100AA3E8, 0x2, 0x1, 0xFFFFF880016AB6CB)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\ndis.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NDIS 6.20 driver
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 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.
crash dump file: C:\Windows\Minidump\041714-19562-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0x1A (0x5100, 0xFFFFF6FC50001358, 0x1, 0xA4D000034E60E963)
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. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
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 4/17/2014 9:08:05 PM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ntfs.sys (Ntfs+0xAF59C)
Bugcheck code: 0x1A (0x5100, 0xFFFFF6FC50001358, 0x1, 0xA4D000034E60E963)
Error: MEMORY_MANAGEMENT
file path: C:\Windows\system32\drivers\ntfs.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT File System Driver
Bug check description: This indicates that a severe memory management error occurred.
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.
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 4/17/2014 5:54:08 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\041714-16879-01.dmp
This was probably caused by the following module: ndis.sys (ndis+0x5CF8)
Bugcheck code: 0xD1 (0xB8863D8, 0x2, 0x1, 0xFFFFF88001621CF8)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\ndis.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NDIS 6.20 driver
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 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 4/17/2014 1:52:45 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\041714-19125-01.dmp
This was probably caused by the following module: fltmgr.sys (fltmgr+0x244D)
Bugcheck code: 0x3B (0xC000001D, 0xFFFFF8800126944D, 0xFFFFF88008FAE360, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
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 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 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 4/17/2014 1:50:33 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\041714-17565-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0xA (0xFFFFF880033F635C, 0xD, 0x0, 0xFFFFF80002AE1149)
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 Thu 4/17/2014 1:08:18 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\041714-21637-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0x50 (0xFFFFFFFFFFFFFFFF, 0x8, 0xFFFFFFFFFFFFFFFF, 0x0)
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 Thu 4/17/2014 12:16:57 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\041714-21309-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0x50 (0xFFFFF3001CA1EE10, 0x1, 0xFFFFF80002D5B64A, 0x7)
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 Thu 4/17/2014 10:34:58 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\041714-21372-01.dmp
This was probably caused by the following module: spldr.sys (spldr+0xE20)
Bugcheck code: 0xFC (0xFFFFF880017D9E20, 0x8000000004056963, 0xFFFFF8800AB6B310, 0x0)
Error: ATTEMPTED_EXECUTE_OF_NOEXECUTE_MEMORY
file path: C:\Windows\system32\drivers\spldr.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: loader for security processor
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 Thu 4/17/2014 2:11:42 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\041614-22027-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFFA800E582E28, 0x1, 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 Wed 4/16/2014 2:53:51 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\041614-20670-01.dmp
This was probably caused by the following module: ndis.sys (ndis+0x76CB)
Bugcheck code: 0xD1 (0xFFFFF300100AA3E8, 0x2, 0x1, 0xFFFFF880016AB6CB)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\ndis.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NDIS 6.20 driver
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 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.
Any ideas why this keeps happening? As I said, fresh install. Thanks.
Facebook
Twitter
Instagram