Hi,
for over a month now I've been getting a lot of BSODs and random shutdowns / freezes that require hard reset.
The only thing I've done is that I installed a "new" GPU ( a Gigabyte GT 730 1GB GDDR5 @1006Mhz, but it's still better then my old integrated one lol ). It was happening even before installing the GPU so I don't think that's what's causing the BSODs.
I've tried sfc /scannow and Dism /Online /Cleanup-Image /RestoreHealth but sfc didn't find anything and neither did Dism ( well at least it didn't tell me it found anything, here's the dism log just in case )
According to "WhoCrashed ( Home Edition )" it seems like there might be something wrong with "ntoskrnl.exe". Check the report below.
My specs:
Windows 10 x64
AMD A8 6600k; 4.2 GHz
Gigabyte GT 730 OC Edition; 1GB GDDR5 @1006 MHz
8GB of DDR3 RAM, 1866 MHz
WhoCrashed report:
Any ideas, please? Thanks!
PS: I've seen this thread but I don't think it's the GPU since I just got a new one and it's still happening.
for over a month now I've been getting a lot of BSODs and random shutdowns / freezes that require hard reset.
The only thing I've done is that I installed a "new" GPU ( a Gigabyte GT 730 1GB GDDR5 @1006Mhz, but it's still better then my old integrated one lol ). It was happening even before installing the GPU so I don't think that's what's causing the BSODs.
I've tried sfc /scannow and Dism /Online /Cleanup-Image /RestoreHealth but sfc didn't find anything and neither did Dism ( well at least it didn't tell me it found anything, here's the dism log just in case )
According to "WhoCrashed ( Home Edition )" it seems like there might be something wrong with "ntoskrnl.exe". Check the report below.
My specs:
Windows 10 x64
AMD A8 6600k; 4.2 GHz
Gigabyte GT 730 OC Edition; 1GB GDDR5 @1006 MHz
8GB of DDR3 RAM, 1866 MHz
WhoCrashed report:
On Mon 13/03/2017 18:10:32 your computer crashed
crash dump file: C:\WINDOWS\Minidump\031317-21578-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14A6F0)
Bugcheck code: 0xA (0xD9, 0x2, 0x0, 0xFFFFF8012A8E005C)
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 12/03/2017 15:44:00 your computer crashed
crash dump file: C:\WINDOWS\Minidump\031217-27375-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14A6F0)
Bugcheck code: 0xA (0x34, 0x2, 0x0, 0xFFFFF80382CD0D89)
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 12/03/2017 10:55:34 your computer crashed
crash dump file: C:\WINDOWS\Minidump\031217-34421-01.dmp
This was probably caused by the following module: ntfs.sys (NTFS+0xAEE64)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF80389CAEE64, 0x0, 0x168)
Error: KMODE_EXCEPTION_NOT_HANDLED
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 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 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 05/03/2017 22:23:48 your computer crashed
crash dump file: C:\WINDOWS\Minidump\030517-28015-01.dmp
This was probably caused by the following module: win32kbase.sys (0xFFFFF6940B206883)
Bugcheck code: 0x50 (0xFFFF890F86B8B0E8, 0x2, 0xFFFFF6940B206883, 0x2)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\WINDOWS\system32\win32kbase.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Base Win32k Kernel 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.
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 05/03/2017 19:04:35 your computer crashed
crash dump file: C:\WINDOWS\Minidump\030517-28640-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14A6F0)
Bugcheck code: 0xA (0x18, 0x2, 0x0, 0xFFFFF802D293CD1F)
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.
crash dump file: C:\WINDOWS\Minidump\031317-21578-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14A6F0)
Bugcheck code: 0xA (0xD9, 0x2, 0x0, 0xFFFFF8012A8E005C)
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 12/03/2017 15:44:00 your computer crashed
crash dump file: C:\WINDOWS\Minidump\031217-27375-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14A6F0)
Bugcheck code: 0xA (0x34, 0x2, 0x0, 0xFFFFF80382CD0D89)
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 12/03/2017 10:55:34 your computer crashed
crash dump file: C:\WINDOWS\Minidump\031217-34421-01.dmp
This was probably caused by the following module: ntfs.sys (NTFS+0xAEE64)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF80389CAEE64, 0x0, 0x168)
Error: KMODE_EXCEPTION_NOT_HANDLED
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 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 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 05/03/2017 22:23:48 your computer crashed
crash dump file: C:\WINDOWS\Minidump\030517-28015-01.dmp
This was probably caused by the following module: win32kbase.sys (0xFFFFF6940B206883)
Bugcheck code: 0x50 (0xFFFF890F86B8B0E8, 0x2, 0xFFFFF6940B206883, 0x2)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\WINDOWS\system32\win32kbase.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Base Win32k Kernel 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.
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 05/03/2017 19:04:35 your computer crashed
crash dump file: C:\WINDOWS\Minidump\030517-28640-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14A6F0)
Bugcheck code: 0xA (0x18, 0x2, 0x0, 0xFFFFF802D293CD1F)
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.
Any ideas, please? Thanks!
PS: I've seen this thread but I don't think it's the GPU since I just got a new one and it's still happening.
Facebook
Twitter
Instagram