I keep getting blue screens while playing diablo 3, and I have no idea why.
This issue has been happening for months, and im kind of fed up now with it. I reinstalled everything thinking it would fix the issue but it does not. Please Help!
Minidumps are attached from my last two crashes.
I am running Windows 7 64x with a Radeon 5770 and a SSD
I used this program called Who Crashed to see the crash report and here is what it says:
Crash Dump Analysis
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Sun 3/2/2014 5:25:30 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\030214-19905-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7EFC0)
Bugcheck code: 0x50 (0xFFFFF8A04B7E66F0, 0x0, 0xFFFFF8800125B0A2, 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 which cannot be identified at this time.
On Sun 3/2/2014 5:17:33 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\030214-24897-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7EFC0)
Bugcheck code: 0x19 (0x3, 0xFFFFFA801161CC20, 0xFFFFFA801161CC20, 0xFFFFFA800F61CC20)
Error: BAD_POOL_HEADER
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 pool header is corrupt.
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 which cannot be identified at this time.
On Sat 7/6/2013 2:19:17 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\070613-22120-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7EFC0)
Bugcheck code: 0xA (0xFFFFFA81263B563B, 0x2, 0x0, 0xFFFFF80002EA1759)
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 which cannot be identified at this time.
This issue has been happening for months, and im kind of fed up now with it. I reinstalled everything thinking it would fix the issue but it does not. Please Help!
Minidumps are attached from my last two crashes.
I am running Windows 7 64x with a Radeon 5770 and a SSD
I used this program called Who Crashed to see the crash report and here is what it says:
Crash Dump Analysis
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Sun 3/2/2014 5:25:30 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\030214-19905-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7EFC0)
Bugcheck code: 0x50 (0xFFFFF8A04B7E66F0, 0x0, 0xFFFFF8800125B0A2, 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 which cannot be identified at this time.
On Sun 3/2/2014 5:17:33 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\030214-24897-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7EFC0)
Bugcheck code: 0x19 (0x3, 0xFFFFFA801161CC20, 0xFFFFFA801161CC20, 0xFFFFFA800F61CC20)
Error: BAD_POOL_HEADER
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 pool header is corrupt.
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 which cannot be identified at this time.
On Sat 7/6/2013 2:19:17 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\070613-22120-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7EFC0)
Bugcheck code: 0xA (0xFFFFFA81263B563B, 0x2, 0x0, 0xFFFFF80002EA1759)
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 which cannot be identified at this time.