Occasional BSOD usually after sleep mode

https://www.bleepingcomputer.com/forums/t/706825/occasional-bsod-usually-after-sleep-mode/

 

Bleeping Computer

 

Hi. . .

You've had 18 BSODs since 30 August 2019 - just under 2 months now.

I firmly believe the cause to be a faulty hard drive.  I'm just not sure which drive is the problem though. Windows and Windbg won't tell us that. We're lucky it even told us about the disk.

BSOD kernel memory dumps were invented to assist software programmers/coders in debugging their code; not for the purpose of identifying failing hardware - with the exception of one piece of hardware - hard drives. Windows is capable of detecting I/O errors and therefore can detect a failing hard drive.

Several of your BSODs contain this "Probably caused by:" statement - 

Probably caused by : hardware_disk

Others included this failure bucket ID -

FAILURE_BUCKET_ID:  X64_0xF4_csrss.exe_BUGCHECK_CRITICAL_PROCESS_8585060_IMAGE_hardware_disk

I can't highlight inside a codebox here, but as you read the line you'll notice an "F4" (referring to bugcgeck 0xf4) plus at the end - "hardware_disk"

Your BSOD bugchecks (STOP errors) include -

0xf4 - Critical Object Termination - a process (an app or program) suddenly, without warning or prompting, simply died (terminated). This is well known to me as an indicator of a faulty hard drive

0x7a - Kernel Data Inpage Error -  indicates that the requested page of kernel data from the paging file could not be read into memory -- again, Windows is telling us that the hard drive had a problem here while trying to read data from it and loading it into RAM

The system reports in the zip file that you provided (thank you, by the way) indicate that you have 2 hard drives. One SSD and one HDD.

SSD = Samsung SSD 850 PRO 256 GB ATA Device
HDD = 500 GB WDC WD5002AALX-00J37A0 ATA Device

First thing to do is to check for a firmware update for your SSD. Outdated firmware can cause the SSD to fail.

Samsung firmware - https://www.samsung.com/semiconductor/minisite/ssd/download/tools/

If you do find a firmware update, update it and test the system for a few days and see if the BSODs continue.

If so, or if no firmware update, run SeaTools for DOS, LONG test - on BOTH drives.

SeaTools for DOS - https://www.sysnative.com/forums/threads/hard-drive-hdd-diagnostics-sea-tools-for-dos-ssd-test.4072/

This version of SeaTools runs under DOS OS, so Windows does not load, so there will definitely be no BSODs during these tests.

Check for the firmware update; run the SeaTools tests on both drives. One of them is failing.

Regards. . .

jcgriff2

Just updated from 7 to 10 and getting 0x109 BSODs - asacpi.sys -- sptd.sys

Just updated from Windows 7 to Windows 10 and getting 0x109 BSODs - asacpi.sys -- sptd.sys



Sysnative - https://www.sysnative.com/forums/threads/just-updated-from-7-to-10-and-getting-random-0x00000109-blue-screens.29659/#post-275558



_________________________________________________________________



asacpi.sys (and also asio.sys s/b updated and/or removed as well)

Hi. . .

All 4 dumps were nearly identical with bugcheck 0x109 - CRITICAL_STRUCTURE_CORRUPTION

This bugcheck appears when when the kernel detects that critical kernel code or
data have been corrupted.

There are generally three causes for a corruption:
1) A driver has inadvertently or deliberately modified critical kernel code
or data. See Windows Hardware Dev Center
2) A developer attempted to set a normal kernel breakpoint using a kernel
debugger ..... THIS DOES NOT APPLY HERE TO YOU
3) A hardware corruption occurred, e.g. failing RAM holding kernel code or data is either bad or some other underlying hardware failure occurred that affects RAMs ability to properly hold kernel code - like extreme heat; PSU failure; motherboard, etc... - any piece of hardware that could affect RAM.

#1 seems to be a possibility to me given an Asus Utility driver that I found in your loaded [into RAM] driver listing in all 4 dumps that wreaked absolute havoc during the later days of Vista/early days of Windows 7. Windows 8 and 8.1 were not immune, either. However, I have not seen much negative activity regarding this driver and Windows 10. But if ever there was a driver to attempt to modify critical kernel code, it would be this Asus ATK0110 driver.

I used to see this driver (a 2004 version) wreaking mass havoc in Vista and Windows 7 systems years ago (literally hundreds of people per day sought BSOD help and the cause turned out to be asacpi.sys - even though it was never, ever mentioned in a dump - my theory is that because it is a boot driver, something else set it off long after boot-up), but all has been quiet since 2008-2009 as many have updated it, I guess. But now I see a 2012 version of the Asus driver in your now-Windows 10 system and cannot help but wonder if it is involved in your BSODs, especially since you did not report BSODs while the system was running Windows 7.

The driver belongs to Asus - it is some form of an Asus Utility driver - it is known as "ATK0110" -

Code:

ASACPI.sys   Thu Nov  1   21:54:34   2012 (509327DA)

Find an update for it - Driver Reference Table (DRT) | ASACPI.sys

Regards. . .

jcgriff2


BSOD DUMP SUMMARY

Code:

Built by: 18362.1.amd64fre.19h1_release.190318-1202
Debug session time: Thu Oct 17 20:44:29.085 2019 (UTC - 4:00)
System Uptime: 0 days 0:17:10.803
BugCheck 109, {a39fc9e52c18d6f6, b3b6d66b7e9b0b43, ffff8a8c8f9ae530, 1c}
Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )
BUGCHECK_STR:  0x109
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 18362.1.amd64fre.19h1_release.190318-1202
Debug session time: Thu Oct 17 18:17:54.330 2019 (UTC - 4:00)
System Uptime: 0 days 0:32:02.048
BugCheck 109, {a39ff35929d027a7, b3b6ffdf7c525bf4, ffff940993ad6970, 1c}
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )
BUGCHECK_STR:  0x109
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 18362.1.amd64fre.19h1_release.190318-1202
Debug session time: Thu Oct 17 18:38:28.493 2019 (UTC - 4:00)
System Uptime: 0 days 0:19:23.212
BugCheck 109, {a39fe367bff9e59a, b3b6efee127c19b7, ffffa40f304e1970, 1c}
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )
BUGCHECK_STR:  0x109
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 18362.1.amd64fre.19h1_release.190318-1202
Debug session time: Thu Oct 17 14:19:41.836 2019 (UTC - 4:00)
System Uptime: 0 days 0:29:56.552
BugCheck 109, {a39ff35e00d2b5d2, b3b6ffe45355edff, ffffb4056e4ce7b0, 1c}
Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )
BUGCHECK_STR:  0x109
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``

Just updated from 7 to 10 and getting random 0x00000109 blue screens

https://www.bleepingcomputer.com/forums/t/706220/just-updated-from-7-to-10-and-getting-random-0x00000109-blue-screens/

Hi. . .

All 4 dumps were nearly identical with bugcheck 0x109 - CRITICAL_STRUCTURE_CORRUPTION

This bugcheck appears when when the kernel detects that critical kernel code or

data have been corrupted.

There are generally three causes for a corruption:

1) A driver has inadvertently or deliberately modified critical kernel code

 or data. See http://www.microsoft.com/whdc/driver/kernel/64bitPatching.mspx

2) A developer attempted to set a normal kernel breakpoint using a kernel

 debugger ..... THIS DOES NOT APPLY HERE TO YOU

3) A hardware corruption occurred, e.g. failing RAM holding kernel code or data is either bad or some other underlying hardware failure occurred that affects RAMs ability to properly hold kernel code - like extreme heat; PSU failure; motherboard, etc... - any piece of hardware that could affect RAM.

#1 seems to be a possibility to me given an Asus Utility driver that I found in your loaded [into RAM] driver listing in all 4 dumps that wreaked absolute havoc during the later days of Vista/early days of Windows 7. Windows 8 and 8.1 were not immune, either. However, I have not seen much negative activity regarding this driver and Windows 10.  But if ever there was a driver to attempt to modify critical kernel code, it would be this Asus ATK0110 driver.

I used to see this driver (a 2004 version) wreaking mass havoc in Vista and Windows 7 systems years ago (literally hundreds of people per day sought BSOD help and the cause turned out to be asacpi.sys - even though it was never, ever mentioned in a dump - my theory is that because it is a boot driver, something else set it off long after boot-up), but all has been quiet since 2008-2009 as many have updated it, I guess. But now I see a 2012 version of the Asus driver in your now-Windows 10 system and cannot help but wonder if it is involved in your BSODs, especially since you did not report BSODs while the system was running Windows 7. 

The driver belongs to Asus - it is some form of an Asus Utility driver -

ASACPI.sys   Thu Nov  1   21:54:34   2012 (509327DA)

Find an update for it - https://www.sysnative.com/drivers/driver.php?id=ASACPI.sys

Regards. . .

jcgriff2

BSOD DUMP SUMMARY

Built by: 18362.1.amd64fre.19h1_release.190318-1202
Debug session time: Thu Oct 17 20:44:29.085 2019 (UTC - 4:00)
System Uptime: 0 days 0:17:10.803
BugCheck 109, {a39fc9e52c18d6f6, b3b6d66b7e9b0b43, ffff8a8c8f9ae530, 1c}
Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )
BUGCHECK_STR:  0x109
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 18362.1.amd64fre.19h1_release.190318-1202
Debug session time: Thu Oct 17 18:17:54.330 2019 (UTC - 4:00)
System Uptime: 0 days 0:32:02.048
BugCheck 109, {a39ff35929d027a7, b3b6ffdf7c525bf4, ffff940993ad6970, 1c}
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )
BUGCHECK_STR:  0x109
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 18362.1.amd64fre.19h1_release.190318-1202
Debug session time: Thu Oct 17 18:38:28.493 2019 (UTC - 4:00)
System Uptime: 0 days 0:19:23.212
BugCheck 109, {a39fe367bff9e59a, b3b6efee127c19b7, ffffa40f304e1970, 1c}
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )
BUGCHECK_STR:  0x109
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 18362.1.amd64fre.19h1_release.190318-1202
Debug session time: Thu Oct 17 14:19:41.836 2019 (UTC - 4:00)
System Uptime: 0 days 0:29:56.552
BugCheck 109, {a39ff35e00d2b5d2, b3b6ffe45355edff, ffffb4056e4ce7b0, 1c}
Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )
BUGCHECK_STR:  0x109
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
  

 

Windows 10 BSOD

https://forums.tomshardware.com/threads/bsod-while-in-games.3533249/#post-21344600

Hi. . .

I processed your 5 mini kernel dumps.

There were 3 different bugchecks; no 3rd party driver was named; "Unknown_Image" and "Unknown_Module" were littered throughout the dumps (in place of driver names). All of these items are indicative of unknown hardware failure being the cause.

The bugchecks and listed causes:

Code:

BugCheck 1E, {ffffffffc0000005, 0, 8, 0}
Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
BugCheck A, {10, 2, 1, fffff8064b0c20a4}
Probably caused by : USBPORT.SYS ( USBPORT!USBPORT_Core_iMapTransfer+45e )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
BugCheck A, {ffff848889c21d5d, 2, 1, fffff80543cbcca0}
Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
BugCheck 7F, {8, ffff96011174ff90, 0, fffff800306c6617}
Probably caused by : memory_corruption
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
BugCheck A, {30, 5, 0, fffff80245402b65}
Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``

Also, "NT" (the Windows Kernel) could not be found in most of the dumps.

Code:

***** Debugger could not find nt in module list,
module list might be corrupt

The fact that "Unknown_Module" was listed in the place of driver names tells me that memory corruption occurred.

Basically, for an app or driver to run, it must be loaded into RAM from the hard drive. When it is no longer needed, the object is unloaded from RAM to make room for other objects that need RAM to run.

Something appears to be affecting your RAM. It could be that RAM itself is bad or it could be an underlying piece of hardware like the PSU, motherboard, excessive heat (is your system internally clean?), etc... that is affecting RAMs ability to properly hold kernel code.

Run hardware diagnostics -

• RAM - memtest86+ - run 1 stick at a time; alternate the slots - https://www.sysnative.com/forums/hardware-tutorials/3909-test-ram-memtest86.html
• HDD - SeaTools for DOS, LONG test - https://www.sysnative.com/forums/hardware-tutorials/4072-hard-drive-hdd-diagnostics-sea-tools-dos-ssd-test.html

Regards. . .

jcgriff2

SUMMARY

Code:

Loading Dump File [C:\Users\PalmDesert\_jcgriff2_\dbug\__Kernel__\100919-6406-01.dmp]
*** WARNING: Unable to verify timestamp for Unknown_Module_00000000`00000000
Debug session time: Wed Oct  9 10:37:25.056 2019 (UTC - 4:00)
System Uptime: 0 days 0:16:46.822
*** WARNING: Unable to verify timestamp for Unknown_Module_00000000`00000000
*** WARNING: Unable to verify timestamp for Unknown_Module_00000000`00000000
Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )
DEFAULT_BUCKET_ID:  CORRUPT_MODULELIST_0x1E
BUGCHECK_STR:  0x1E
FAILURE_BUCKET_ID:  CORRUPT_MODULELIST_0x1E
Bugcheck code 0000001E
Arguments ffffffff`c0000005 00000000`00000000 00000000`00000008 00000000`00000000
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\PalmDesert\_jcgriff2_\dbug\__Kernel__\100719-6265-01.dmp]
Built by: 18362.1.amd64fre.19h1_release.190318-1202
Debug session time: Mon Oct  7 15:05:09.957 2019 (UTC - 4:00)
System Uptime: 0 days 0:31:10.723
Probably caused by : USBPORT.SYS ( USBPORT!USBPORT_Core_iMapTransfer+45e )
DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
BUGCHECK_STR:  AV
PROCESS_NAME:  destiny2.exe
FAILURE_BUCKET_ID:  AV_USBPORT!USBPORT_Core_iMapTransfer
Bugcheck code 0000000A
Arguments 00000000`00000010 00000000`00000002 00000000`00000001 fffff806`4b0c20a4
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\PalmDesert\_jcgriff2_\dbug\__Kernel__\100719-5515-01.dmp]
*** WARNING: Unable to verify timestamp for Unknown_Module_00000000`00000000
Debug session time: Mon Oct  7 12:48:10.080 2019 (UTC - 4:00)
System Uptime: 0 days 0:46:48.845
*** WARNING: Unable to verify timestamp for Unknown_Module_00000000`00000000
*** WARNING: Unable to verify timestamp for Unknown_Module_00000000`00000000
Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )
DEFAULT_BUCKET_ID:  CORRUPT_MODULELIST_AV
BUGCHECK_STR:  AV
FAILURE_BUCKET_ID:  CORRUPT_MODULELIST_AV
Bugcheck code 0000000A
Arguments ffff8488`89c21d5d 00000000`00000002 00000000`00000001 fffff805`43cbcca0
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\PalmDesert\_jcgriff2_\dbug\__Kernel__\100719-5437-01.dmp]
Built by: 18362.1.amd64fre.19h1_release.190318-1202
Debug session time: Mon Oct  7 12:00:50.286 2019 (UTC - 4:00)
System Uptime: 0 days 1:02:31.051
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : memory_corruption
BUGCHECK_STR:  0x7f_8
DEFAULT_BUCKET_ID:  CODE_CORRUPTION
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  MEMORY_CORRUPTION_STRIDE
Bugcheck code 0000007F
Arguments 00000000`00000008 ffff9601`1174ff90 00000000`00000000 fffff800`306c6617
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\PalmDesert\_jcgriff2_\dbug\__Kernel__\100719-5453-01.dmp]
*** WARNING: Unable to verify timestamp for Unknown_Module_2b75d79f`aebb2302
*** ERROR: Module load completed but symbols could not be loaded for Unknown_Module_2b75d79f`aebb2302
Debug session time: Mon Oct  7 10:39:32.454 2019 (UTC - 4:00)
System Uptime: 2 days 5:13:06.651
*** WARNING: Unable to verify timestamp for Unknown_Module_2b75d79f`aebb2302
*** ERROR: Module load completed but symbols could not be loaded for Unknown_Module_2b75d79f`aebb2302
Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )
DEFAULT_BUCKET_ID:  CORRUPT_MODULELIST_AV
BUGCHECK_STR:  AV
FAILURE_BUCKET_ID:  CORRUPT_MODULELIST_AV
Bugcheck code 0000000A
Arguments 00000000`00000030 00000000`00000005 00000000`00000000 fffff802`45402b65
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``

Last edited: Thursday at 4:36 PM

J. C. Griffith - Microsoft WI MVP Profile Page

BSOD while in games

https://forums.tomshardware.com/threads/bsod-while-in-games.3533249/#post-21345647

BSOD while in games



Memory Corruption



unknown_module

Problem with battleye >< (Never happen to me but after I formatted my laptop)

Battle-eye anti-cheat driver 

BEDaisy.sys  Thu Mar 21 02:57:59 2019 (5C936027)

https://www.sysnative.com/drivers/driver.php?id=BEDaisy.sys 

https://www.bleepingcomputer.com/forums/t/705235/installed-new-parts-and-now-everytime-i-fix-an-issue-3-more-pop-up/?p=4878671

Installed new parts and now everytime I fix an issue 3 more pop up

Bugcheck 0xef - critical process died

Test HDD and SSD

WINDOWS 7 - Numerous BSODs

TSF - https://www.techsupportforum.com/forums/f299/win7-crashing-before-i-can-use-sysnativefilecollectionapp-1235666-2.html#post7749486

Code:

BugCheck A, {fffff80002ba68a0, 2, 0, fffff80002881142}
Probably caused by : amdxhc31.sys ( amdxhc31+25cd0 )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
BugCheck C1, {fffff98019702f10, fffff980197020e8, 4740f8, 32}
Probably caused by : amdhub31.sys ( amdhub31+141e2 )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
BugCheck C1, {fffff98013da6e80, fffff98013da6268, f94188, 32}
Probably caused by : amdhub31.sys ( amdhub31+141d7 )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
BugCheck C1, {fffff9801bc66f50, fffff9801bc66428, b140b8, 32}
Probably caused by : amdhub31.sys ( amdhub31+42ad )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
BugCheck C1, {fffff9803b936e80, fffff9803b936228, 734188, 32}
Probably caused by : amdhub31.sys ( amdhub31+141d7 )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
BugCheck C1, {fffff9801bb74fc0, fffff9801bb74268, 134040, 23}
Probably caused by : FLxHCIc.sys ( FLxHCIc+18cd5 )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
BugCheck C1, {fffff980185daf10, fffff980185da168, 3b40f8, 23}
Probably caused by : amdhub31.sys ( amdhub31+141e2 )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
BugCheck C1, {fffff98017e2af30, fffff98017e2a028, 6940d8, 23}
Probably caused by : amdxhc31.sys ( amdxhc31+25cde )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
BugCheck C1, {fffff980180b2f10, fffff980180b2368, b740f8, 23}
Probably caused by : amdhub31.sys ( amdhub31+141e2 )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
BugCheck C1, {fffff9801c490fc0, fffff9801c4903e8, 6b4040, 32}
Probably caused by : amdxhc31.sys ( amdxhc31+25025 )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
BugCheck C1, {fffff9801c90cf50, fffff9801c90c268, 1d40b8, 23}
Probably caused by : amdhub31.sys ( amdhub31+42ad )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
BugCheck C1, {fffff98054592f50, fffff98054592128, 940b8, 23}
Probably caused by : amdhub31.sys ( amdhub31+42ad )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
BugCheck C1, {fffff98025ac8e80, fffff98025ac8268, cf4188, 23}
Probably caused by : amdhub31.sys ( amdhub31+141d7 )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
BugCheck C1, {fffff98026026fc0, fffff98026026ea8, a14040, 32}
Probably caused by : amdxhc31.sys ( amdxhc31+25025 )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
BugCheck A, {fffff80002b998a0, 2, 0, fffff80002874142}
Probably caused by : amdxhc31.sys ( amdxhc31+25cd0 )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
BugCheck C1, {fffff98063700f50, fffff98063700128, 3140b8, 23}
Probably caused by : amdhub31.sys ( amdhub31+416d )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
BugCheck C1, {fffff98040fecf10, fffff98040fec268, 3740f8, 23}
Probably caused by : amdhub31.sys ( amdhub31+1366a )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
BugCheck C1, {fffff980461eafc0, fffff980461ea168, e14040, 23}
Probably caused by : amdxhc31.sys ( amdxhc31+23c39 )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
BugCheck 1A, {5100, fffff6fc5006f030, 3a, 20}
Probably caused by : memory_corruption ( nt!MiFlushTbAsNeeded+309 )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
BugCheck C1, {fffff98046082e80, fffff98046082af0, e14188, 23}
Probably caused by : amdhub31.sys ( amdhub31+1365f )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
BugCheck C4, {e3, fffff88003630501, 7fefd7905f0, 0}
Probably caused by : cmdguard.sys ( cmdguard+8501 )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
BugCheck C4, {e3, fffff88003662501, 7fefcf505f0, 0}
Probably caused by : cmdguard.sys ( cmdguard+8501 )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
BugCheck C4, {e3, fffff88001808501, 7fefd9d05f0, 0}
Probably caused by : cmdguard.sys ( cmdguard+8501 )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
BugCheck C4, {e3, fffff880046f5501, 7fefdcc05f0, 0}
Probably caused by : cmdguard.sys ( cmdguard+8501 )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
BugCheck C1, {fffff9805f41efc0, fffff9805f41e228, 694040, 23}
Probably caused by : amdxhc31.sys ( amdxhc31+23c39 )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
BugCheck 1000007E, {ffffffffc0000005, fffff88007017e26, fffff88002571808, fffff88002571070}
Probably caused by : athurx.sys ( athurx+8e26 )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
BugCheck 1000007E, {ffffffffc0000005, fffff88004a16e26, fffff8800bac6808, fffff8800bac6070}
Probably caused by : athurx.sys ( athurx+8e26 )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
BugCheck 50, {fffff8000000fb0f, 8, fffff8000000fb0f, 0}
Probably caused by : athurx.sys ( athurx+9f3bb )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
BugCheck 1000007E, {ffffffffc0000005, fffff88007016e26, fffff88002586808, fffff88002586070}
Probably caused by : athurx.sys ( athurx+8e26 )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``

CONCLUSION: 29 dumps; 6 different bugchecks; 5 different 3rd party drivers named as "probable cause" - 3 possible hardware related bugchecks (0xa, 0x50, 0x1a) - suggest we would wait until the other drivers are updated first; then check system stability as the 3 potential hardware bugchecks may be flukes.



John

BSOD: Geek Squad did not fix. Now no more League of Legends

BC thread - https://www.bleepingcomputer.com/forums/t/702605/bsod-geek-squad-did-not-fix-now-no-more-league-of-legends/

 

jcgriff2

• 
• BSOD Kernel Dump Expert
• 1,238 posts
• ONLINE
 

• Gender:Male
• Location:New Jersey Shore
• Local time:12:47 PM

Posted Today, 12:47 PM

Hi. . .

 

I hope that you did not pay Geek Squad because they missed a most obvious clue.

 

The problem appears to be an outdated Broadcom wifi driver, which unfortunately can only be obtained from the system msnufacturer and they rarely ever update wifi drivers. This is why I tell people to only buy systems with Intel wifi as Intel always keeps their drivers updated.

 

bcmwl63a.sys Thu Feb  6 01:57:28 2014 (52F35C88)

Your driver is from February 2014 - an eternity in the life of a wifi driver. Intel updates their drivers every 4-6 months.

 

Be sure to check the system manufacturer's site for a driver update - miracles do happen.

 

If this is a laptop, probably the only way to stop the blue screens is to purchase a USB wifi adapter; something like one of these -  

 

https://www.amazon.com/s?i=computers&bbn=13983791&rh=n%3A172282%2Cn%3A493964%2Cn%3A541966%2Cn%3A172504%2Cn%3A490499011%2Cn%3A13983791%2Cp_n_feature_four_browse-bin%3A5662324011%5Cc5928098011&dc&fst=as%3Aoff&qid=1566233166&rnid=5662319011&ref=sr_nr_p_n_feature_four_browse-bin_5

 

Good luck to you.

 

Regards. . .

 

jcgriff2

Computer crashes after few minutes when putting to sleep - BSOD

BC - https://www.bleepingcomputer.com/forums/t/702602/computer-crashes-after-few-minutes-when-putting-to-sleep/?p=4852247



jcgriff2

BSOD Kernel Dump Expert

1,237 posts

ONLINE

 

• Gender:Male
• Location:New Jersey Shore
• Local time:12:33 PM

Posted Today, 12:33 PM

Hi. . .

 

You are getting closer - but no cigar yet!

 

With 0x9f (0x3,,,) bugcheck dumps, you need to run the !irp command on P4 (Paremeter 4 - the 4th number inside the parenthesis after the 0x9f bugcheck).

 

So... after you run !analyze-v and perhaps one of the list [loaded] modules commands (like lmnt or lmntsm to view the loaded [into RAM] drivers, you then want to run a  .bugcheck command to obtain P4, then run the   !irp command. It should then tell you the 3rd party driver that is hiding under pci.sys. pci.sys is a Microsoft Windows driver and therefore cannot be the actual cause of your BSODs as Windows drivers are sacrosanct.

 

Anyway, in one of your dumps (all 3 dumps, by the way, had 0x9f (0x3,,,) bugchecks). So I just selected one of them - filename = 081419-18203-01.dmp

 

As I mentioned, I first executed a Windbg kd> command - .bugcheck (note the period before "bugcheck"); the result -

Bugcheck code 0000009F
Arguments 00000000`00000003 ffff970c`7019f060 fffff807`6058e8b0 ffff970c`7e96f620

The number we are after here is P4 - the 4th number (the memory address of the blocked IRP), which is ffff970c`7e96f620

 

Then you issue the !irp command followed by P4, like this -

!irp ffff970c`7e96f620 

-

 

 

. . .the output will be this -

0: kd> !irp ffff970c`7e96f620
Irp is active with 5 stacks 4 is current (= 0xffff970c7e96f7c8)
 No Mdl: No System Buffer: Thread 00000000:  Irp stack trace. 
     cmd  flg cl Device   File     Completion-Context
 [N/A(0), N/A(0)]
            0  0 00000000 00000000 00000000-00000000      Args: 00000000 00000000 00000000 00000000
 [N/A(0), N/A(0)]
            0  0 00000000 00000000 00000000-00000000      Args: 00000000 00000000 00000000 00000000
 [N/A(0), N/A(0)]
            0  0 00000000 00000000 00000000-00000000      Args: 00000000 00000000 00000000 00000000
>[IRP_MJ_POWER(16), IRP_MN_SET_POWER(2)]
            0 e1 ffff970c7f0c7050 00000000 fffff8076399b3d0-ffff970c84fcdc00 Success Error Cancel pending
       *** WARNING: Unable to verify timestamp for L1C63x64.sys
*** ERROR: Module load completed but symbols could not be loaded for L1C63x64.sys
 \Driver\L1C nt!PopSystemIrpCompletion
   Args: 00014400 00000000 00000004 00000002
 [N/A(0), N/A(0)]
            0  0 00000000 00000000 00000000-ffff970c84fcdc00      Args: 00000000 00000000 00000000 00000000

... but you are only after the portion of non-zero numbers in the center -

>[IRP_MJ_POWER(16), IRP_MN_SET_POWER(2)]
            0 e1 ffff970c7f0c7050 00000000 fffff8076399b3d0-ffff970c84fcdc00 Success Error Cancel pending
       *** WARNING: Unable to verify timestamp for L1C63x64.sys
*** ERROR: Module load completed but symbols could not be loaded for L1C63x64.sys
 \Driver\L1C nt!PopSystemIrpCompletion
   Args: 00014400 00000000 00000004 00000002

If you look through that jumbled mess of data, you will see    L1C63x64.sys  

 

That is your  Qualcomm Atheros AR8171/8175 PCI-E Gigabit Ethernet Controller (NDIS 6.30) driver (this info came from a file in your zip attachment - systeminfo - at the very bottom of the report).

 

Next, we look up the driver in the Sysnative Driver Reference Table (DRT) as we need a driver update site. The DRT contains over 4,500 drivers in it that we've been working on for over 9 years now. Drivers are manually added 1-by-1 to the SQL DRT table.

 

DRT - https://www.sysnative.com/drivers/ -- enter the driver name in the search box

 

It returns - https://www.sysnative.com/drivers/driver.php?id=L1C63x64.sys - and lists 2 possible driver update sites.

 

Please note that Atheros in general does not keep their drivers updated, so you may not be able to find an update. If so and your system is a desktop PC, you'll need to purchase a new(er) PCIe Ethernet card to continue using Ethernet or live with the blue screens as they will likely increase in number and frequency as time goes on. Basically, you have another app or it could be a Windows networking related driver that is not playing nice with your current Atheros Ethernet driver. Some other driver has a conflict with it. 

 

The likely problem with your Atheros driver is its age -

L1C63x64.sys Mon Sep 18 13:32:11 2017 (59C02D4B)

Two years old for a networking driver in today's world is very old. Most driver developers (like Intel, Netgear, etc...) update every 4-6 months - both Ethernet and wifi.

 

So, you need to locate an Atheros driver update with a timestamp greater than September 2017.

 

Please let me know how you make out.

 

Also, try the !irp command on the dumps. I think that you did very well with Windbg, especially setting up the symbol path, which is where most people trying Windbg fail.

 

Regards. . .

 

jcgriff2