Unpredictable BSODs with different stop codes

Okay, I'll follow the steps to uninstall Avira when I wake up (about to go to bed). I'll also see if I can get stable enough WiFi to reasonably stay on only WiFi for a while to see if the BSODs cease. If they do, and it is the LAN adapter, is that a physical component that would lead to the motherboard needing to be replaced?

If it is the motherboard LAN adapter you could just disable it and get a LAN PCIe card instead.

After the troubleshooting has completed plan to recustomize the computer.

During the troubleshooting these errors had been reported in the log files:

a) Dump file creation failed due to error during dump creation.

b) Unable to produce a minidump file from the full dump file.

c) The dump file at location: C:\WINDOWS\MEMORY.DMP was deleted because the disk volume had less than 25 GB free space.


Having the page file on the Windows drive and >30 GB free space may reduce these failures/errors and increase the number of mini dump and memory dump files available for troubleshooting.


1) Open administrative command prompt and copy and paste:

msdt.exe -id BITSDiagnostic
msdt.exe -id DeviceDiagnostic
msdt.exe -id NetworkDiagnosticsNetworkAdapter
msdt.exe -id WindowsUpdateDiagnostic
powercfg -h off

For each Windows troubleshooter, if available, click view detailed information > post images or share links

powercfg -h off will turn off hibernation and windows fast startup.
When troubleshooting has completed run powercfg -h on


2) Download and install: Intel Driver & Support Assistant

Access Denied


3) Disconnect from the Internet (Ethernet and Wifi)


4) Open administrative command prompt and copy and paste:

pnputil /delete-driver oem27.inf /uninstall /force


5) Reconnect to Wifi.


6) Reinstall the Intel Ethernet drivers using the Intel driver and support assistant.

Code:

Event[13388]:
  Log Name: System
  Source: Microsoft-Windows-WER-SystemErrorReporting
  Date: 2023-09-06T02:24:12.1010000Z
  Event ID: 1018
  Task: N/A
  Level: Information
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: NotQuantic
  Description: 
The dump file at location: C:\WINDOWS\MEMORY.DMP was deleted because the disk volume had less than 25 GB free space.

Code:

Event[9228]:
  Log Name: System
  Source: Microsoft-Windows-WER-SystemErrorReporting
  Date: 2023-08-31T03:01:16.4930000Z
  Event ID: 1005
  Task: N/A
  Level: Error
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: NotQuantic
  Description: 
Unable to produce a minidump file from the full dump file.

Code:

Event[9128]:
  Log Name: System
  Source: Microsoft-Windows-WER-SystemErrorReporting
  Date: 2023-08-31T02:07:30.9440000Z
  Event ID: 1005
  Task: N/A
  Level: Error
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: NotQuantic
  Description: 
Unable to produce a minidump file from the full dump file.

Code:

Event[9067]:
  Log Name: System
  Source: volmgr
  Date: 2023-08-31T02:05:21.2910000Z
  Event ID: 161
  Task: N/A
  Level: Error
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: NotQuantic
  Description: 
Dump file creation failed due to error during dump creation.

Code:

Event[7094]:
  Log Name: System
  Source: Microsoft-Windows-WER-SystemErrorReporting
  Date: 2023-08-27T19:59:10.3570000Z
  Event ID: 1018
  Task: N/A
  Level: Information
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: NotQuantic
  Description: 
The dump file at location: C:\WINDOWS\MEMORY.DMP was deleted because the disk volume had less than 25 GB free space.

Code:

Event[6511]:
  Log Name: System
  Source: Microsoft-Windows-WER-SystemErrorReporting
  Date: 2023-08-19T17:17:21.1180000Z
  Event ID: 1018
  Task: N/A
  Level: Information
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: NotQuantic
  Description: 
The dump file at location: C:\WINDOWS\MEMORY.DMP was deleted because the disk volume had less than 25 GB free space.

Code:

Event[6379]:
  Log Name: System
  Source: Microsoft-Windows-WER-SystemErrorReporting
  Date: 2023-08-19T09:02:23.2340000Z
  Event ID: 1018
  Task: N/A
  Level: Information
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: NotQuantic
  Description: 
The dump file at location: C:\WINDOWS\MEMORY.DMP was deleted because the disk volume had less than 25 GB free space.

Code:

Event[4425]:
  Log Name: System
  Source: Microsoft-Windows-WER-SystemErrorReporting
  Date: 2023-08-15T23:03:12.0580000Z
  Event ID: 1005
  Task: N/A
  Level: Error
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: NotQuantic
  Description: 
Unable to produce a minidump file from the full dump file.

Code:

Event[4371]:
  Log Name: System
  Source: volmgr
  Date: 2023-08-15T23:01:40.1030000Z
  Event ID: 161
  Task: N/A
  Level: Error
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: NotQuantic
  Description: 
Dump file creation failed due to error during dump creation.

Code:

Event[2559]:
  Log Name: System
  Source: Microsoft-Windows-WER-SystemErrorReporting
  Date: 2023-08-12T21:52:22.9910000Z
  Event ID: 1018
  Task: N/A
  Level: Information
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: NotQuantic
  Description: 
The dump file at location: C:\WINDOWS\MEMORY.DMP was deleted because the disk volume had less than 25 GB free space.

Code:

Event[331]:
  Log Name: System
  Source: volmgr
  Date: 2023-08-07T03:53:52.1520000Z
  Event ID: 161
  Task: N/A
  Level: Error
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: NotQuantic
  Description: 
Dump file creation failed due to error during dump creation.

Code:

Event[252]:
  Log Name: System
  Source: volmgr
  Date: 2023-08-07T03:46:47.7450000Z
  Event ID: 161
  Task: N/A
  Level: Error
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: NotQuantic
  Description: 
Dump file creation failed due to error during dump creation.

Code:

Event[184]:
  Log Name: System
  Source: Microsoft-Windows-WER-SystemErrorReporting
  Date: 2023-08-07T03:20:02.6730000Z
  Event ID: 1005
  Task: N/A
  Level: Error
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: NotQuantic
  Description: 
Unable to produce a minidump file from the full dump file.

Code:

Event[129]:
  Log Name: System
  Source: volmgr
  Date: 2023-08-07T03:18:40.4490000Z
  Event ID: 161
  Task: N/A
  Level: Error
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: NotQuantic
  Description: 
Dump file creation failed due to error during dump creation.

Here are the results from Macrorit for the ST3000DM001-1ER166 drive that has the bad sector. How much of a risk of total disk failure is there when a disk has a bad sector like this? It's a pretty important drive, unfortunately, rather than a disk holding a bunch of older files I don't use much, and I live paycheck to paycheck, so I want to know how imperative it is for me to work extra hours to afford a replacement drive.



Here is the text log for the scan: scan_log_2023-09-06.txt

- - - Updated - - -

ubuysa said:

If it is the motherboard LAN adapter you could just disable it and get a LAN PCIe card instead.

Are these expensive? I live paycheck to paycheck so I really don't have any disposable income (even $20 is considered an expensive "splurge" for me).

- - - Updated - - -

zbook said:

1) Open administrative command prompt and copy and paste:

msdt.exe -id BITSDiagnostic
msdt.exe -id DeviceDiagnostic
msdt.exe -id NetworkDiagnosticsNetworkAdapter
msdt.exe -id WindowsUpdateDiagnostic
powercfg -h off

For each Windows troubleshooter, if available, click view detailed information > post images or share links

For msdt.exe -id NetworkDiagnosticsNetworkAdapter, I'm not sure which options to select because I'm not having an issue accessing the internet?

- - - Updated - - -

Here are the results for the other msdt.exe commands. Obviously for the one that requires a restart, I restarted right after finishing the troubleshooter. I only skipped it in the moment in order to acquire the Detailed Information for the screenshot.

BitsDiagnostic:


DeviceDiagnostic:


WindowsUpdateDiagnostic:


- - - Updated - - -

zbook said:

4) Open administrative command prompt and copy and paste:

pnputil /delete-driver oem27.inf /uninstall /force


5) Reconnect to Wifi.


6) Reinstall the Intel Ethernet drivers using the Intel driver and support assistant.

After reconnecting to WiFi, the Driver and Support Assistant says there are no driver updates available for my computer. I went into Device Manager and attempted to update the driver for my Intel(R) Ethernet Connection (2) I219-V and it said the drivers were already up to date. Does that mean the delete-driver command didn't work? Or is something else going on?

I didn't expect connecting via WiFi to find a better LAN driver. The point of using WiFi is to see whether it still BSODs.

Please ensure that the LAN adapter is disabled in Device Manager and then reboot (to ensure that the suspect driver isn't loaded).

ubuysa said:

I didn't expect connecting via WiFi to find a better LAN driver. The point of using WiFi is to see whether it still BSODs.

Please ensure that the LAN adapter is disabled in Device Manager and then reboot (to ensure that the suspect driver isn't loaded).

Yeah that part of the post was in response to the steps zbook was having me take, not anything to do with the reasoning behind connecting to WiFi. In his steps, he asked me to reinstall the LAN driver. Is the LAN adapter just the Intel(R) Ethernet Connection (2) I219-V?

The most up to date driver can become corrupt or misbehave so drivers are uninstalled and reinstalled.

The drive chkdsk /b /v is pending.

The bad block(s) can be followed over time using:
HD Tune
Macrorit
Chkdsk /b /v

If they are increasing then use this as an early warning sign to replace the drive.

If data is backed up then the drive can be used until the terminal event.

Before the terminal event there may be:
slow read
slow write
hangs
freezes
BSOD
unexpected shutdowns and restarts
data loss
etc.

This link may be useful:

13 Best Free Software To Check Hard Drive Bad Sectors For Windows

zbook said:

The drive chkdsk /b /v is pending.

Yes, I looked it up and it can take 5 hours for a 1 TB drive, so it's the sort of thing I'll have to leave running overnight. The past few nights, I've run the other tests you've requested overnight, one by one. I don't have another computer to use in the meantime so I cannot be running these tests 24/7, so it will take a day per test. Sorry.

You're making good progress as the drive sizes, drive problems, and drive free space all impact the run times.

The log files are loaded with many Razer errors.

7) list Razer hardware / software

If possible plan to uninstall all Razer hardware / software.

If it is not possible then uninstall and reinstall all Razer hardware / software.