Hey guys im having a problem with my pc everytime i boot the pc first time after a proper shutdown i will certainly get a BSOD after an hour of boot then it will reboot on its own and no BSOD occur after that. This has been going on for weeks now and it is really frustating for me.It even occurs in Safe Mode.
Here are my PC specs :
-Asus Prime H310M-K R2.0
-NVIDIA GeForce GTX 1060
-Intel Core i5-8400
-8GB of DDR4 memory(2400MHz)
*Nothing is overclocked
Here are the error codes i get from WhoCrashed
On Thu 3/14/2019 10:08:16 PM your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\031419-6578-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1B35E0)
Bugcheck code: 0x50 (0xFFFFFFFFFEFFFFFF, 0x0, 0xFFFFF8027F4C2E29, 0x2)
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 3/14/2019 10:08:16 PM your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\MEMORY.DMP
This was probably caused by the following module: win32kfull.sys (win32kfull!NtUserMsgWaitForMultipleObjectsEx+0x7C6)
Bugcheck code: 0x50 (0xFFFFFFFFFEFFFFFF, 0x0, 0xFFFFF8027F4C2E29, 0x2)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\WINDOWS\system32\win32kfull.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Full/Desktop 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 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 3/14/2019 3:31:33 PM your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\031419-7406-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1B35E0)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80006A30C98, 0xFFFF8F055B906AF0, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
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 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 the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Wed 3/13/2019 8:58:47 PM your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\031319-7250-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1B35E0)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF802128F4F80, 0xFFFFB708116F5C20, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
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 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 the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Wed 3/13/2019 4:14:15 PM your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\031319-7671-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1B35E0)
Bugcheck code: 0x1A (0x41201, 0xFFFFBABFFE118648, 0x8400000215C12005, 0xFFFFA708AB4554A0)
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. This may be because of a hardware issue such as faulty RAM, overheating (thermal issue) or because of a buggy driver. This problem might also be caused because of overheating (thermal issue).
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 3/13/2019 3:11:33 PM your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\031319-61687-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1BBAF6)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF8065446CAF6, 0xFFFF8F0951490218, 0xFFFF8F095148FA60)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
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 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 the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
**Things i have done to try and get rid of BSOD
-Ran Windows Memory Diagnostics(No errors found)
-Ran Driver Verifier Manager (BSOD in an instant with error pointing to a driver called netr28ux.sys)
-Ran CHKDSK several times (No error)
-Tried checking errors for all the storage drives(No error)
-Clean reinstall of Windows 10
I will soon run the Driver Verifier Manager and post the results here.
Here are my PC specs :
-Asus Prime H310M-K R2.0
-NVIDIA GeForce GTX 1060
-Intel Core i5-8400
-8GB of DDR4 memory(2400MHz)
*Nothing is overclocked
Here are the error codes i get from WhoCrashed
On Thu 3/14/2019 10:08:16 PM your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\031419-6578-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1B35E0)
Bugcheck code: 0x50 (0xFFFFFFFFFEFFFFFF, 0x0, 0xFFFFF8027F4C2E29, 0x2)
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 3/14/2019 10:08:16 PM your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\MEMORY.DMP
This was probably caused by the following module: win32kfull.sys (win32kfull!NtUserMsgWaitForMultipleObjectsEx+0x7C6)
Bugcheck code: 0x50 (0xFFFFFFFFFEFFFFFF, 0x0, 0xFFFFF8027F4C2E29, 0x2)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\WINDOWS\system32\win32kfull.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Full/Desktop 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 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 3/14/2019 3:31:33 PM your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\031419-7406-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1B35E0)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80006A30C98, 0xFFFF8F055B906AF0, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
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 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 the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Wed 3/13/2019 8:58:47 PM your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\031319-7250-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1B35E0)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF802128F4F80, 0xFFFFB708116F5C20, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
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 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 the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Wed 3/13/2019 4:14:15 PM your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\031319-7671-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1B35E0)
Bugcheck code: 0x1A (0x41201, 0xFFFFBABFFE118648, 0x8400000215C12005, 0xFFFFA708AB4554A0)
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. This may be because of a hardware issue such as faulty RAM, overheating (thermal issue) or because of a buggy driver. This problem might also be caused because of overheating (thermal issue).
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 3/13/2019 3:11:33 PM your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\031319-61687-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1BBAF6)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF8065446CAF6, 0xFFFF8F0951490218, 0xFFFF8F095148FA60)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
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 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 the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
**Things i have done to try and get rid of BSOD
-Ran Windows Memory Diagnostics(No errors found)
-Ran Driver Verifier Manager (BSOD in an instant with error pointing to a driver called netr28ux.sys)
-Ran CHKDSK several times (No error)
-Tried checking errors for all the storage drives(No error)
-Clean reinstall of Windows 10
I will soon run the Driver Verifier Manager and post the results here.
Facebook
Twitter
Instagram