Multiple BSODs that only started recently

kartik_11

Prominent
Jul 2, 2017
19
0
510
Windows version: Windows 10 , 10.0, build: 16299
Motherboard : B350 TOMAHAWK (MS-7A34)
CPU: AMD Ryzen 5 1600 Six-Core Processor AMD586, level: 23
12 logical processors, active mask: 4095
RAM: Ripjaws V 16 GB DDR4 @3200MHz
GPU : Asus turbo 1060 6 gb

I recently started getting BSODs randomly. I'm not an expert at BSODs but all of them have been related to network modules. The latest one however was dxg.sys. Can someone please help me fix this?

I ran WhoCrashed and this is the result. It however doesnt include the one with dxg.sys.

Crash Dump Analysis
--------------------------------------------------------------------------------

Crash dumps are enabled on your computer.

Crash dump directories:
C:\WINDOWS
C:\WINDOWS\Minidump

On Tue 26-06-2018 20:53:39 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\MEMORY.DMP
This was probably caused by the following module: ntkrnlmp.exe (nt!RtlRaiseStatus+0x6C9)
Bugcheck code: 0x1E (0xFFFFFFFF80000003, 0xFFFFF8018BAC35DC, 0x0, 0x7FFFFFFFFFFFFFFC)
Error: KMODE_EXCEPTION_NOT_HANDLED
Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
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.
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 25-06-2018 23:57:15 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\062518-52640-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x175820)
Bugcheck code: 0xA (0xFFFFFFFFFFFFFFF8, 0x2, 0x0, 0xFFFFF801D8A47379)
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 is a software bug.
This bug check belongs to the crash dump test that you have performed with WhoCrashed or other software. It means that a crash dump file was properly written out.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



The following dump files were found but could not be read. These files may be corrupt:
C:\WINDOWS\Minidump\062618-50890-01.dmp

 
Looks like an old OS build. Current is in the 17xxx. I would go into safe mode with networking, from an elevated command prompt run "sfc /scannow" and "DISM /Online /Cleanup-Image /CheckHealth" if SFC fails. While there, you can also run a "chkdsk /x" to check the hard drive for errors. You will need to restart to run the check disk. Then run updates and try to get Windows 10 1803. I would also recommend to create a restore point before running updates, and you may want to do them incrementally. As in 1607 > 1703 > 1709 > 1803, with restore points in between.
 
So i updated the drivers last night as scout_03 said and so far i haven't got any BSODs (fingers crossed). I think maybe it was just a drivers thing. Anyway thanks to all of you guys for helping.
 

Latest posts