I have had this homebuilt system for about three months now:
fx-8350 vischera
2x hd7970 3gb crossfire
16gb gskill ddr3 1600 RAM
gigabyte 990fxa-ud3
asus eyefinity display
All of this was working fine until about a week or so ago when I started getting random BSOD. They almost exclusively happen during graphically intensive games. (dx11)
I analyzed them in WhoCrashed and it seemed to point at memory issues. I ran Memtest and it picked up an unidentified error. I have since returned these sticks and put in 8gb of corsair vengeance.
The blue screens continued, this time pointing to ATI's notorious atikmdag.sys bug.
So, from there i uninstalled CCC and used driver sweeper in safe mode. This seemed to help each time and with each different version of CCC. Just for good measure, I also re-installed the mobo drivers and the sound drivers. This helped for about a day until new random blue screens started happening in addition to atikmdag.sys.
My next step was to seriously downgrade. In addition to the 8GB of corsair vengeance, I took one of the GPUs out, went back to 1920x1080, and added new cooling options.
This helped the longest. A whole two days with no blue screens.
Alas the problem has returned. So it is time to swallow my pride and ask for help. Below are the most frequent WhoCrased reports.
On Wed 7/31/2013 6:54:38 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\073113-30529-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75C00)
Bugcheck code: 0x1A (0x403, 0xFFFFF680001ECBB8, 0x88600002113C280D, 0xFFFFF680001CCBB8)
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 Wed 7/31/2013 6:54:38 PM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: dxgmms1.sys (dxgmms1!VidMmInterface+0x24A8B)
Bugcheck code: 0x1A (0x403, 0xFFFFF680001ECBB8, 0x88600002113C280D, 0xFFFFF680001CCBB8)
Error: MEMORY_MANAGEMENT
file path: C:\Windows\system32\drivers\dxgmms1.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: DirectX Graphics MMS
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 Wed 7/31/2013 6:19:51 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\073113-27487-01.dmp
This was probably caused by the following module: dxgkrnl.sys (dxgkrnl+0x378A0)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF880042AE8A0, 0xFFFFF88007EF50E8, 0xFFFFF88007EF4940)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\drivers\dxgkrnl.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: DirectX Graphics Kernel
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.
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 Wed 7/31/2013 12:25:41 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\073013-32822-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75C00)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF800039A4F7E, 0x0, 0xFFFFFFFFFFFFFFFF)
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 Tue 7/30/2013 8:43:42 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\073013-34991-01.dmp
This was probably caused by the following module: atikmdag.sys (atikmdag+0xA0809)
Bugcheck code: 0x50 (0xFFFFFFFF800017D8, 0x1, 0xFFFFF88005629860, 0x5)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\drivers\atikmdag.sys
product: ATI Radeon Family
company: Advanced Micro Devices, Inc.
description: ATI Radeon Kernel Mode Driver
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.
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: atikmdag.sys (ATI Radeon Kernel Mode Driver, Advanced Micro Devices, Inc.).
Google query: Advanced Micro Devices, Inc. PAGE_FAULT_IN_NONPAGED_AREA
On Tue 7/30/2013 8:14:02 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\073013-35022-01.dmp
This was probably caused by the following module: Unknown ()
Bugcheck code: 0x0 (0x0, 0x0, 0x0, 0x0)
Error: CUSTOM_ERROR
A third party driver was identified as the probable root cause of this system error.
Google query: CUSTOM_ERROR
On Tue 7/30/2013 4:16:27 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\073013-33836-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75C00)
Bugcheck code: 0x1A (0x403, 0xFFFFF6800006F1A0, 0x9220000078FCC847, 0xFFFFF6800002F1A0)
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 Tue 7/30/2013 4:29:44 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\073013-35505-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75C00)
Bugcheck code: 0x50 (0xFFFFFB7E76000028, 0x0, 0xFFFFF800036493AA, 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 Mon 7/29/2013 3:59:13 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\072913-38828-01.dmp
This was probably caused by the following module: atikmpag.sys (atikmpag+0x2CC1C)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF88004465C1C, 0x0, 0x200)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32\drivers\atikmpag.sys
product: AMD driver
company: Advanced Micro Devices, Inc.
description: AMD multi-vendor Miniport 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: atikmpag.sys (AMD multi-vendor Miniport Driver, Advanced Micro Devices, Inc.).
Google query: Advanced Micro Devices, Inc. KMODE_EXCEPTION_NOT_HANDLED
On Sun 7/28/2013 6:07:15 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\072813-35084-01.dmp
This was probably caused by the following module: ntfs.sys (Ntfs+0x4688)
Bugcheck code: 0x24 (0x1904FB, 0xFFFFF8800718C918, 0xFFFFF8800718C170, 0xFFFFF880012F1317)
Error: NTFS_FILE_SYSTEM
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 a problem occurred in the NTFS file system.
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 7/26/2013 6:30:19 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\072613-34991-01.dmp
This was probably caused by the following module: atikmdag.sys (atikmdag+0x23C5C)
Bugcheck code: 0xA0000001 (0x5, 0x0, 0x0, 0x0)
Error: CUSTOM_ERROR
file path: C:\Windows\system32\drivers\atikmdag.sys
product: ATI Radeon Family
company: Advanced Micro Devices, Inc.
description: ATI Radeon Kernel Mode Driver
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: atikmdag.sys (ATI Radeon Kernel Mode Driver, Advanced Micro Devices, Inc.).
Google query: Advanced Micro Devices, Inc. CUSTOM_ERROR
On Fri 7/26/2013 5:12:13 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\072613-31356-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75C00)
Bugcheck code: 0x4E (0x99, 0x137218, 0x0, 0x137318)
Error: PFN_LIST_CORRUPT
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 page frame number (PFN) list is corrupted.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. 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 Fri 7/26/2013 12:51:45 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\072513-36769-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75C00)
Bugcheck code: 0xC2 (0x7, 0x109B, 0x1A80000, 0xFFFFFA80071F7C10)
Error: BAD_POOL_CALLER
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 current thread is making a bad pool request.
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 7/24/2013 1:37:43 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\072413-32994-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75C00)
Bugcheck code: 0x50 (0xFFFFFFB7E20055C0, 0x0, 0xFFFFF800036BBB3A, 0x5)
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 Wed 7/24/2013 1:01:47 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\072413-32120-01.dmp
This was probably caused by the following module: usbport.sys (USBPORT+0x2D27D)
Bugcheck code: 0xFE (0x6, 0xFFFFFA800AF0B2D0, 0x43787254, 0x0)
Error: BUGCODE_USB_DRIVER
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 indicates that an error has occurred in a Universal Serial Bus (USB) driver.
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.
fx-8350 vischera
2x hd7970 3gb crossfire
16gb gskill ddr3 1600 RAM
gigabyte 990fxa-ud3
asus eyefinity display
All of this was working fine until about a week or so ago when I started getting random BSOD. They almost exclusively happen during graphically intensive games. (dx11)
I analyzed them in WhoCrashed and it seemed to point at memory issues. I ran Memtest and it picked up an unidentified error. I have since returned these sticks and put in 8gb of corsair vengeance.
The blue screens continued, this time pointing to ATI's notorious atikmdag.sys bug.
So, from there i uninstalled CCC and used driver sweeper in safe mode. This seemed to help each time and with each different version of CCC. Just for good measure, I also re-installed the mobo drivers and the sound drivers. This helped for about a day until new random blue screens started happening in addition to atikmdag.sys.
My next step was to seriously downgrade. In addition to the 8GB of corsair vengeance, I took one of the GPUs out, went back to 1920x1080, and added new cooling options.
This helped the longest. A whole two days with no blue screens.
Alas the problem has returned. So it is time to swallow my pride and ask for help. Below are the most frequent WhoCrased reports.
On Wed 7/31/2013 6:54:38 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\073113-30529-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75C00)
Bugcheck code: 0x1A (0x403, 0xFFFFF680001ECBB8, 0x88600002113C280D, 0xFFFFF680001CCBB8)
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 Wed 7/31/2013 6:54:38 PM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: dxgmms1.sys (dxgmms1!VidMmInterface+0x24A8B)
Bugcheck code: 0x1A (0x403, 0xFFFFF680001ECBB8, 0x88600002113C280D, 0xFFFFF680001CCBB8)
Error: MEMORY_MANAGEMENT
file path: C:\Windows\system32\drivers\dxgmms1.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: DirectX Graphics MMS
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 Wed 7/31/2013 6:19:51 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\073113-27487-01.dmp
This was probably caused by the following module: dxgkrnl.sys (dxgkrnl+0x378A0)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF880042AE8A0, 0xFFFFF88007EF50E8, 0xFFFFF88007EF4940)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\drivers\dxgkrnl.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: DirectX Graphics Kernel
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.
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 Wed 7/31/2013 12:25:41 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\073013-32822-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75C00)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF800039A4F7E, 0x0, 0xFFFFFFFFFFFFFFFF)
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 Tue 7/30/2013 8:43:42 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\073013-34991-01.dmp
This was probably caused by the following module: atikmdag.sys (atikmdag+0xA0809)
Bugcheck code: 0x50 (0xFFFFFFFF800017D8, 0x1, 0xFFFFF88005629860, 0x5)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\drivers\atikmdag.sys
product: ATI Radeon Family
company: Advanced Micro Devices, Inc.
description: ATI Radeon Kernel Mode Driver
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.
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: atikmdag.sys (ATI Radeon Kernel Mode Driver, Advanced Micro Devices, Inc.).
Google query: Advanced Micro Devices, Inc. PAGE_FAULT_IN_NONPAGED_AREA
On Tue 7/30/2013 8:14:02 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\073013-35022-01.dmp
This was probably caused by the following module: Unknown ()
Bugcheck code: 0x0 (0x0, 0x0, 0x0, 0x0)
Error: CUSTOM_ERROR
A third party driver was identified as the probable root cause of this system error.
Google query: CUSTOM_ERROR
On Tue 7/30/2013 4:16:27 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\073013-33836-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75C00)
Bugcheck code: 0x1A (0x403, 0xFFFFF6800006F1A0, 0x9220000078FCC847, 0xFFFFF6800002F1A0)
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 Tue 7/30/2013 4:29:44 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\073013-35505-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75C00)
Bugcheck code: 0x50 (0xFFFFFB7E76000028, 0x0, 0xFFFFF800036493AA, 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 Mon 7/29/2013 3:59:13 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\072913-38828-01.dmp
This was probably caused by the following module: atikmpag.sys (atikmpag+0x2CC1C)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF88004465C1C, 0x0, 0x200)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32\drivers\atikmpag.sys
product: AMD driver
company: Advanced Micro Devices, Inc.
description: AMD multi-vendor Miniport 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: atikmpag.sys (AMD multi-vendor Miniport Driver, Advanced Micro Devices, Inc.).
Google query: Advanced Micro Devices, Inc. KMODE_EXCEPTION_NOT_HANDLED
On Sun 7/28/2013 6:07:15 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\072813-35084-01.dmp
This was probably caused by the following module: ntfs.sys (Ntfs+0x4688)
Bugcheck code: 0x24 (0x1904FB, 0xFFFFF8800718C918, 0xFFFFF8800718C170, 0xFFFFF880012F1317)
Error: NTFS_FILE_SYSTEM
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 a problem occurred in the NTFS file system.
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 7/26/2013 6:30:19 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\072613-34991-01.dmp
This was probably caused by the following module: atikmdag.sys (atikmdag+0x23C5C)
Bugcheck code: 0xA0000001 (0x5, 0x0, 0x0, 0x0)
Error: CUSTOM_ERROR
file path: C:\Windows\system32\drivers\atikmdag.sys
product: ATI Radeon Family
company: Advanced Micro Devices, Inc.
description: ATI Radeon Kernel Mode Driver
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: atikmdag.sys (ATI Radeon Kernel Mode Driver, Advanced Micro Devices, Inc.).
Google query: Advanced Micro Devices, Inc. CUSTOM_ERROR
On Fri 7/26/2013 5:12:13 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\072613-31356-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75C00)
Bugcheck code: 0x4E (0x99, 0x137218, 0x0, 0x137318)
Error: PFN_LIST_CORRUPT
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 page frame number (PFN) list is corrupted.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. 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 Fri 7/26/2013 12:51:45 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\072513-36769-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75C00)
Bugcheck code: 0xC2 (0x7, 0x109B, 0x1A80000, 0xFFFFFA80071F7C10)
Error: BAD_POOL_CALLER
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 current thread is making a bad pool request.
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 7/24/2013 1:37:43 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\072413-32994-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75C00)
Bugcheck code: 0x50 (0xFFFFFFB7E20055C0, 0x0, 0xFFFFF800036BBB3A, 0x5)
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 Wed 7/24/2013 1:01:47 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\072413-32120-01.dmp
This was probably caused by the following module: usbport.sys (USBPORT+0x2D27D)
Bugcheck code: 0xFE (0x6, 0xFFFFFA800AF0B2D0, 0x43787254, 0x0)
Error: BUGCODE_USB_DRIVER
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 indicates that an error has occurred in a Universal Serial Bus (USB) driver.
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.
Facebook
Twitter
Instagram