[SOLVED] Help | Random BSODs. FIX: CLEAN INSTALLATION; later, SET RAM voltages/frequencies like advised by the manufacturer.

xman323 · Nov 6, 2021

Hello,

A brief description of your problem (but you can also include the steps you tried) :
I've been receiving random BSODs every day or so
System Manufacturer?
parts assembled
Laptop or Desktop?
Desktop
Exact model number (if laptop, check label on bottom)
Desktop
OS ? (Windows 10, 8.1, 8, 7, Vista)
Windows 10
x86 (32bit) or x64 (64bit)?
64bit
What was original installed OS on system?
windows 10
Is the OS an OEM version (came pre-installed on system) or full retail version (YOU purchased it from retailer)?
full retail version
Age of system? (hardware)
less than 3 years
Age of OS installation?
Original Install Date: 13-Jun-20, 10:52:01 AM
Have you re-installed the OS?
no
CPU
Ryzen 5 3600
RAM (brand, EXACT model, what slots are you using?)
Crucial Ballistix Sport LT 3000
using all slots (8 GB * 4 slots)
Video Card
Nvidia GTX 1050 Ti
MotherBoard - (if NOT a laptop)
aorus elite b450 v1
Power Supply - brand & wattage (if laptop, skip this one)
COUGAR GEX750 850W ATX12V 80 PLUS GOLD
Is driver verifier enabled or disabled?
Disabled
What security software are you using? (Firewall, antivirus, antimalware, antispyware, and so forth)
Kaspersky Anti-Virus 21.31.391(g)
Are you using proxy, vpn, ipfilters or similar software?
No
Are you using Disk Image tools? (like daemon tools, alcohol 52% or 120%, virtual CloneDrive, roxio software)
No
Are you currently under/overclocking? Are there overclocking software installed on your system?
No

http://speccy.piriform.com/results/sEkiwzYmdjWFTR4iBj8FYky

x BlueRobot · Nov 6, 2021

I'll completely remove Kaspersky using their official removal tool, it appears to be causing problems.

Rich (BB code):

4: kd> lmvm kneps
Browse full module list
start             end                 module name
fffff800`30cf0000 fffff800`30d39000   kneps    T (no symbols)           
    Loaded symbol image file: kneps.sys
    Image path: \SystemRoot\system32\DRIVERS\kneps.sys
    Image name: kneps.sys
    Browse all global symbols  functions  data
    Timestamp:        ***** Invalid (CEAE8F0E)
    CheckSum:         00049AF2
    ImageSize:        00049000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
    Information from resource tables:

I noticed an interesting entry in your Hosts file, I'm not sure if you're aware of it or not?

Rich (BB code):

194.59.249.242 fr-006.whiskergalaxy.com   #added by Windscribe, do not modify.

xman323 · Nov 6, 2021

x BlueRobot said:

I'll completely remove Kaspersky using their official removal tool, it appears to be causing problems.

Rich (BB code):

4: kd> lmvm kneps
Browse full module list
start             end                 module name
fffff800`30cf0000 fffff800`30d39000   kneps    T (no symbols)          
    Loaded symbol image file: kneps.sys
    Image path: \SystemRoot\system32\DRIVERS\kneps.sys
    Image name: kneps.sys
    Browse all global symbols  functions  data
    Timestamp:        ***** Invalid (CEAE8F0E)
    CheckSum:         00049AF2
    ImageSize:        00049000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
    Information from resource tables:

I noticed an interesting entry in your Hosts file, I'm not sure if you're aware of it or not?

Rich (BB code):

194.59.249.242 fr-006.whiskergalaxy.com   #added by Windscribe, do not modify.

Many thanks Mr. x BlueRobot I'll uninstall Kaspersky using the removal tool, as for the hosts entry, I'm aware of it as it was needed for an uninstalled vpn app, I've removed the entry now.
many thanks again and I'll report back if issue is solved or not.

zbook · Nov 7, 2021

Was there a drive replaced earlier this year?

The logs displayed many types of bugchecks:

A
10E
3B
141
119
116
117
193
139

The GPU driver was seen in the BSOD 10e: VIDEO_MEMORY_MANAGEMENT_INTERNAL (10e)

1) uninstall the Nvidia GPU driver using DDU (display driver uninstaller)
2) re-install the Nvidia GPU driver from the Nvidia website
3) make sure that you check the clean install box and if available install the physx driver.

Display Driver Uninstaller Download version 18.0.4.3 (or newer version if available)
Wagnardsoft

Download Drivers | NVIDIA
Download Drivers | NVIDIA

Run Memtest86 version 9.2 (or newer version if available) for four passes.
Repeat the test so that eight passes are performed.

MemTest86 - Official Site of the x86 Memory Testing Tool

Use a camera or smart phone camera to take pictures and post images into the thread.
In case there are any problems uploading images use share links (one drive, drop box, or google drive)

Memtest86 has a feature to produce a text report.
Please post this in addition to the images.

Code:

Event[21770]:
  Log Name: System
  Source: disk
  Date: 2021-05-11T01:36:31.1580000Z
  Event ID: 154
  Task: N/A
  Level: Error
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: DESKTOP-HTB91TU
  Description:
The IO operation at logical block address 0x800c000 for Disk 5 (PDO name: \Device\000019b9) failed due to a hardware error.

Event[21771]:
  Log Name: System
  Source: disk
  Date: 2021-05-11T01:36:31.1580000Z
  Event ID: 154
  Task: N/A
  Level: Error
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: DESKTOP-HTB91TU
  Description:
The IO operation at logical block address 0x800c000 for Disk 5 (PDO name: \Device\000019b9) failed due to a hardware error.

Event[21772]:
  Log Name: System
  Source: disk
  Date: 2021-05-11T01:36:19.8910000Z
  Event ID: 154
  Task: N/A
  Level: Error
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: DESKTOP-HTB91TU
  Description:
The IO operation at logical block address 0x0 for Disk 5 (PDO name: \Device\000019b9) failed due to a hardware error.

Event[21773]:
  Log Name: System
  Source: disk
  Date: 2021-05-11T01:36:19.8910000Z
  Event ID: 154
  Task: N/A
  Level: Error
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: DESKTOP-HTB91TU
  Description:
The IO operation at logical block address 0x0 for Disk 5 (PDO name: \Device\000019b9) failed due to a hardware error.

Event[21774]:
  Log Name: System
  Source: disk
  Date: 2021-05-11T01:36:19.8910000Z
  Event ID: 154
  Task: N/A
  Level: Error
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: DESKTOP-HTB91TU
  Description:
The IO operation at logical block address 0x0 for Disk 5 (PDO name: \Device\000019b9) failed due to a hardware error.

Event[21775]:
  Log Name: System
  Source: disk
  Date: 2021-05-11T01:36:19.8900000Z
  Event ID: 154
  Task: N/A
  Level: Error
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: DESKTOP-HTB91TU
  Description:
The IO operation at logical block address 0x0 for Disk 5 (PDO name: \Device\000019b9) failed due to a hardware error.

Event[21776]:
  Log Name: System
  Source: disk
  Date: 2021-05-11T01:36:19.7560000Z
  Event ID: 154
  Task: N/A
  Level: Error
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: DESKTOP-HTB91TU
  Description:
The IO operation at logical block address 0x0 for Disk 5 (PDO name: \Device\000019b9) failed due to a hardware error.

Event[21777]:
  Log Name: System
  Source: disk
  Date: 2021-05-11T01:36:19.7550000Z
  Event ID: 154
  Task: N/A
  Level: Error
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: DESKTOP-HTB91TU
  Description:
The IO operation at logical block address 0x0 for Disk 5 (PDO name: \Device\000019b9) failed due to a hardware error.

Event[21778]:
  Log Name: System
  Source: disk
  Date: 2021-05-11T01:36:19.7550000Z
  Event ID: 154
  Task: N/A
  Level: Error
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: DESKTOP-HTB91TU
  Description:
The IO operation at logical block address 0x0 for Disk 5 (PDO name: \Device\000019b9) failed due to a hardware error.

Event[21779]:
  Log Name: System
  Source: disk
  Date: 2021-05-11T01:36:19.7430000Z
  Event ID: 154
  Task: N/A
  Level: Error
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: DESKTOP-HTB91TU
  Description:
The IO operation at logical block address 0x0 for Disk 5 (PDO name: \Device\000019b9) failed due to a hardware error.

Event[21780]:
  Log Name: System
  Source: disk
  Date: 2021-05-11T01:36:14.2290000Z
  Event ID: 154
  Task: N/A
  Level: Error
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: DESKTOP-HTB91TU
  Description:
The IO operation at logical block address 0x0 for Disk 5 (PDO name: \Device\000019b9) failed due to a hardware error.

Event[21781]:
  Log Name: System
  Source: disk
  Date: 2021-05-11T01:35:52.6260000Z
  Event ID: 154
  Task: N/A
  Level: Error
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: DESKTOP-HTB91TU
  Description:
The IO operation at logical block address 0x0 for Disk 5 (PDO name: \Device\000019b9) failed due to a hardware error.

Event[21782]:
  Log Name: System
  Source: disk
  Date: 2021-05-11T01:35:52.6260000Z
  Event ID: 154
  Task: N/A
  Level: Error
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: DESKTOP-HTB91TU
  Description:
The IO operation at logical block address 0x0 for Disk 5 (PDO name: \Device\000019b9) failed due to a hardware error.

Event[21783]:
  Log Name: System
  Source: disk
  Date: 2021-05-11T01:35:52.6150000Z
  Event ID: 154
  Task: N/A
  Level: Error
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: DESKTOP-HTB91TU
  Description:
The IO operation at logical block address 0x0 for Disk 5 (PDO name: \Device\000019b9) failed due to a hardware error.

Event[21784]:
  Log Name: System
  Source: disk
  Date: 2021-05-11T01:35:52.6150000Z
  Event ID: 154
  Task: N/A
  Level: Error
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: DESKTOP-HTB91TU
  Description:
The IO operation at logical block address 0x0 for Disk 5 (PDO name: \Device\000019b9) failed due to a hardware error.

Event[21785]:
  Log Name: System
  Source: disk
  Date: 2021-05-11T01:35:52.6140000Z
  Event ID: 154
  Task: N/A
  Level: Error
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: DESKTOP-HTB91TU
  Description:
The IO operation at logical block address 0x0 for Disk 5 (PDO name: \Device\000019b9) failed due to a hardware error.

Event[21786]:
  Log Name: System
  Source: disk
  Date: 2021-05-11T01:35:52.6010000Z
  Event ID: 154
  Task: N/A
  Level: Error
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: DESKTOP-HTB91TU
  Description:
The IO operation at logical block address 0x800c000 for Disk 5 (PDO name: \Device\000019b9) failed due to a hardware error.

Event[21787]:
  Log Name: System
  Source: disk
  Date: 2021-05-11T01:35:52.6010000Z
  Event ID: 154
  Task: N/A
  Level: Error
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: DESKTOP-HTB91TU
  Description:
The IO operation at logical block address 0x800c000 for Disk 5 (PDO name: \Device\000019b9) failed due to a hardware error.

Event[21788]:
  Log Name: System
  Source: disk
  Date: 2021-05-11T01:35:52.5990000Z
  Event ID: 154
  Task: N/A
  Level: Error
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: DESKTOP-HTB91TU
  Description:
The IO operation at logical block address 0x1c00c000 for Disk 5 (PDO name: \Device\000019b9) failed due to a hardware error.

Event[21789]:
  Log Name: System
  Source: disk
  Date: 2021-05-11T01:35:52.5990000Z
  Event ID: 154
  Task: N/A
  Level: Error
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: DESKTOP-HTB91TU
  Description:
The IO operation at logical block address 0x0 for Disk 5 (PDO name: \Device\000019b9) failed due to a hardware error.

Code:

Event[7401]:
  Log Name: System
  Source: disk
  Date: 2021-08-31T18:53:26.6120000Z
  Event ID: 153
  Task: N/A
  Level: Warning
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: DESKTOP-HTB91TU
  Description:
The IO operation at logical block address 0x458d28c0 for Disk 5 (PDO name: \Device\00000083) was retried.



Event[10828]:
  Log Name: System
  Source: disk
  Date: 2021-07-30T15:29:21.9510000Z
  Event ID: 153
  Task: N/A
  Level: Warning
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: DESKTOP-HTB91TU
  Description:
The IO operation at logical block address 0x5d35630 for Disk 5 (PDO name: \Device\0000026f) was retried.

Code:

nvlddmkm.sys Wed Sep 30 21:08:42 2020 (5F75564A)

xman323 · Nov 7, 2021

zbook said:
Was there a drive replaced earlier this year?

I have an external HDD that I plug in regularly, is it the reason behind Disk 5 IO errors?

zbook said:
The logs displayed many types of bugchecks:

A
10E
3B
141
119
116
117
193
139

The GPU driver was seen in the BSOD 10e: VIDEO_MEMORY_MANAGEMENT_INTERNAL (10e)

1) uninstall the Nvidia GPU driver using DDU (display driver uninstaller)
2) re-install the Nvidia GPU driver from the Nvidia website
3) make sure that you check the clean install box and if available install the physx driver.

Display Driver Uninstaller Download version 18.0.4.3 (or newer version if available)
Wagnardsoft

Download Drivers | NVIDIA
Download Drivers | NVIDIA

should I use this method instead of leaving windows install Nvidia drivers on it's own?
I've already used DDU during safe mode to uninstall drivers completely and let windows update install the appropriate drivers without any interaction from my side

zbook said:
Run Memtest86 version 9.2 (or newer version if available) for four passes.
Repeat the test so that eight passes are performed.

MemTest86 - Official Site of the x86 Memory Testing Tool

Use a camera or smart phone camera to take pictures and post images into the thread.
In case there are any problems uploading images use share links (one drive, drop box, or google drive)

Memtest86 has a feature to produce a text report.
Please post this in addition to the images.

I will stress test my RAM and report back.

zbook · Nov 7, 2021

If multiple driver versions are tested and there are recurrent BSOD then consider swap testing the hardware.
Windows updates of non-Microsoft drivers can be modified.
Let's see what happens after the DDU uninstallation and replacement.

For any new BSOD please post new Sysnative log collector results.

After posting the Memtest86 results please perform the following steps:

Test all drives:

HD Tune (free or trial version)
HD Tune website
Post images or share links for results on these tabs:
a) Health
b) Benchmark
c) Full error scan

Sea Tools for Windows
SeaTools (Windows) | Seagate
long generic test

These tests can be performed overnight:
a) HD Tune Full error scan
b) Sea Tools for Windows

Run after completing the above tests:
Hard Disk Sentinel (free or trial version)
Hard Disk Sentinel - HDD health and temperature monitoring
Post images or share links for results on these tabs:
Overview
Temperature
SMART

Code:

------------------------
Disk & DVD/CD-ROM Drives
------------------------
      Drive: C:
 Free Space: 111.0 GB
Total Space: 214.0 GB
File System: NTFS
      Model: Samsung SSD 850 EVO 250GB

      Drive: D:
 Free Space: 111.3 GB
Total Space: 500.2 GB
File System: NTFS
      Model: WDC WD1002FAEX-00Z3A0

      Drive: E:
 Free Space: 401.4 GB
Total Space: 453.7 GB
File System: NTFS
      Model: WDC WD1002FAEX-00Z3A0

      Drive: F:
 Free Space: 30.2 GB
Total Space: 913.0 GB
File System: NTFS
      Model: WDC WD20EZRZ-00Z5HB0

      Drive: G:
 Free Space: 250.4 GB
Total Space: 994.7 GB
File System: NTFS
      Model: WDC WD20EZRZ-00Z5HB0

      Drive: H:
 Free Space: 32.1 GB
Total Space: 476.9 GB
File System: NTFS
      Model: WDC WD5000AAVS-98ZTB0

      Drive: I:
 Free Space: 356.1 GB
Total Space: 488.3 GB
File System: NTFS
      Model: HS-SSD-E100N 512G

xman323 · Nov 7, 2021

zbook said:
If multiple driver versions are tested and there are recurrent BSOD then consider swap testing the hardware.
Windows updates of non-Microsoft drivers can be modified.
Let's see what happens after the DDU uninstallation and replacement.

For any new BSOD please post new Sysnative log collector results.

After posting the Memtest86 results please perform the following steps:

Test all drives:

HD Tune (free or trial version)
HD Tune website
Post images or share links for results on these tabs:
a) Health
b) Benchmark
c) Full error scan

Sea Tools for Windows
SeaTools (Windows) | Seagate
long generic test

These tests can be performed overnight:
a) HD Tune Full error scan
b) Sea Tools for Windows

Run after completing the above tests:
Hard Disk Sentinel (free or trial version)
Hard Disk Sentinel - HDD health and temperature monitoring
Post images or share links for results on these tabs:
Overview
Temperature
SMART

Code:

------------------------ Disk & DVD/CD-ROM Drives ------------------------ Drive: C: Free Space: 111.0 GB Total Space: 214.0 GB File System: NTFS Model: Samsung SSD 850 EVO 250GB Drive: D: Free Space: 111.3 GB Total Space: 500.2 GB File System: NTFS Model: WDC WD1002FAEX-00Z3A0 Drive: E: Free Space: 401.4 GB Total Space: 453.7 GB File System: NTFS Model: WDC WD1002FAEX-00Z3A0 Drive: F: Free Space: 30.2 GB Total Space: 913.0 GB File System: NTFS Model: WDC WD20EZRZ-00Z5HB0 Drive: G: Free Space: 250.4 GB Total Space: 994.7 GB File System: NTFS Model: WDC WD20EZRZ-00Z5HB0 Drive: H: Free Space: 32.1 GB Total Space: 476.9 GB File System: NTFS Model: WDC WD5000AAVS-98ZTB0 Drive: I: Free Space: 356.1 GB Total Space: 488.3 GB File System: NTFS Model: HS-SSD-E100N 512G

Hello, Just now I received another BSOD , I've reinstalled Nvidia drivers after using DU, removed Kaspersky antivirus and started using windows defender
after BSOD occured I've tried to run sc /scannow

Code:

C:\WINDOWS\system32>sfc /scannow

Beginning system scan.  This process will take some time.

Beginning verification phase of system scan.
Verification 100% complete.

Windows Resource Protection found corrupt files and successfully repaired them.
For online repairs, details are included in the CBS log file located at
windir\Logs\CBS\CBS.log. For example C:\Windows\Logs\CBS\CBS.log. For offline
repairs, details are included in the log file provided by the /OFFLOGFILE flag.

I've attached the log files and latest mini-dumd, I'll be running HD Tune and memtest overnight and report back

xman323 · Nov 7, 2021

latest Sysnative files attached

x BlueRobot · Nov 8, 2021

Rich (BB code):

2: kd> .exr 0xffffa50ec02b5738
ExceptionAddress: fffff6145bec0eed (win32kfull!DecTimerCount+0x0000000000000041)
   ExceptionCode: c0000409 (Security check failure or stack buffer overrun)
  ExceptionFlags: 00000001
NumberParameters: 1
   Parameter[0]: 0000000000000003
Subcode: 0x3 FAST_FAIL_CORRUPT_LIST_ENTRY

Stop 0x139's are typically caused by drivers, especially if a linked list structure has been corrupted. I'll recommend running Driver Verifier for now - Driver Verifier - BSOD related - Windows 10, 8.1, 8, 7 + Vista

xman323 · Nov 9, 2021

zbook said:
If multiple driver versions are tested and there are recurrent BSOD then consider swap testing the hardware.
Windows updates of non-Microsoft drivers can be modified.
Let's see what happens after the DDU uninstallation and replacement.

For any new BSOD please post new Sysnative log collector results.

After posting the Memtest86 results please perform the following steps:

Test all drives:

HD Tune (free or trial version)
HD Tune website
Post images or share links for results on these tabs:
a) Health
b) Benchmark
c) Full error scan

Sea Tools for Windows
SeaTools (Windows) | Seagate
long generic test

These tests can be performed overnight:
a) HD Tune Full error scan
b) Sea Tools for Windows

Run after completing the above tests:
Hard Disk Sentinel (free or trial version)
Hard Disk Sentinel - HDD health and temperature monitoring
Post images or share links for results on these tabs:
Overview
Temperature
SMART

Code:

------------------------ Disk & DVD/CD-ROM Drives ------------------------ Drive: C: Free Space: 111.0 GB Total Space: 214.0 GB File System: NTFS Model: Samsung SSD 850 EVO 250GB Drive: D: Free Space: 111.3 GB Total Space: 500.2 GB File System: NTFS Model: WDC WD1002FAEX-00Z3A0 Drive: E: Free Space: 401.4 GB Total Space: 453.7 GB File System: NTFS Model: WDC WD1002FAEX-00Z3A0 Drive: F: Free Space: 30.2 GB Total Space: 913.0 GB File System: NTFS Model: WDC WD20EZRZ-00Z5HB0 Drive: G: Free Space: 250.4 GB Total Space: 994.7 GB File System: NTFS Model: WDC WD20EZRZ-00Z5HB0 Drive: H: Free Space: 32.1 GB Total Space: 476.9 GB File System: NTFS Model: WDC WD5000AAVS-98ZTB0 Drive: I: Free Space: 356.1 GB Total Space: 488.3 GB File System: NTFS Model: HS-SSD-E100N 512G

thanks for your follow up, I've run HDD tools. HDD Sentinel and WD seatools as attached, no errors were found and no BSOD occurred during the tests

x BlueRobot said:
Rich (BB code):

2: kd> .exr 0xffffa50ec02b5738 ExceptionAddress: fffff6145bec0eed (win32kfull!DecTimerCount+0x0000000000000041) ExceptionCode: c0000409 (Security check failure or stack buffer overrun) ExceptionFlags: 00000001 NumberParameters: 1 Parameter[0]: 0000000000000003 Subcode: 0x3 FAST_FAIL_CORRUPT_LIST_ENTRY

Stop 0x139's are typically caused by drivers, especially if a linked list structure has been corrupted. I'll recommend running Driver Verifier for now - Driver Verifier - BSOD related - Windows 10, 8.1, 8, 7 + Vista

Thanks, I'm running Driver verified now and will report after 24 hours

xman323 · Nov 10, 2021

Hello, I've received a new BSOD when running verifier overnight, I've attached the latest sysnative logs now.

x BlueRobot · Nov 10, 2021

Are you running in a virtual machine?

xman323 · Nov 10, 2021

x BlueRobot said:
Are you running in a virtual machine?

No, why?

x BlueRobot · Nov 10, 2021

Just wondering because I noticed on the thread which had the crash, there was a pending IRP associated to it for a VMware keyboard filter driver. Hmm, just thinking if it is the issue or not.

x BlueRobot · Nov 10, 2021

If possible, could you please check the following directory and upload a zipped version of the memory dump file to a file sharing site such as Google Drive? It will be too large to attach to a forum post unfortunately.

Rich (BB code):

%systemroot%\MEMORY.DMP

xman323 · Nov 10, 2021

x BlueRobot said:
Just wondering because I noticed on the thread which had the crash, there was a pending IRP associated to it for a VMware keyboard filter driver. Hmm, just thinking if it is the issue or not.

I have VMware workstation installed but have no machines running when any of the BSODs occurred, might the app and its services are the problem?

x BlueRobot said:
If possible, could you please check the following directory and upload a zipped version of the memory dump file to a file sharing site such as Google Drive? It will be too large to attach to a forum post unfortunately.

Rich (BB code):

%systemroot%\MEMORY.DMP

sure, I've uploaded it on Gdrive

x BlueRobot · Nov 10, 2021

I suspect that issue may lie with the VMware keyboard filter driver at the moment, and therefore would suggest that you update VMWare or remove it completely.

Rich (BB code):

2: kd> lmvm vmkbd
Browse full module list
start             end                 module name
fffff803`219b0000 fffff803`219be000   vmkbd      (no symbols)           
    Loaded symbol image file: vmkbd.sys
    Image path: \SystemRoot\system32\DRIVERS\vmkbd.sys
    Image name: vmkbd.sys
    Browse all global symbols  functions  data
    Timestamp:        Thu Aug  6 14:14:41 2020 (5F2C0241)
    CheckSum:         00012167
    ImageSize:        0000E000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
    Information from resource tables:

You can disable Driver Verifier as well, it probably won't find anything useful unfortunately.

xman323 · Nov 10, 2021

x BlueRobot said:
I suspect that issue may lie with the VMware keyboard filter driver at the moment, and therefore would suggest that you update VMWare or remove it completely.

Rich (BB code):

2: kd> lmvm vmkbd Browse full module list start end module name fffff803`219b0000 fffff803`219be000 vmkbd (no symbols) Loaded symbol image file: vmkbd.sys Image path: \SystemRoot\system32\DRIVERS\vmkbd.sys Image name: vmkbd.sys Browse all global symbols functions data Timestamp: Thu Aug 6 14:14:41 2020 (5F2C0241) CheckSum: 00012167 ImageSize: 0000E000 Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4 Information from resource tables:

You can disable Driver Verifier as well, it probably won't find anything useful unfortunately.

will do @x BlueRobot many thanks for your support, will report if the BSODs sopped or not and will be using Hyper-V instead of VMware workstation for now.

xman323 · Nov 11, 2021

I've received another BSOD today while watching a movie, (reference_by_pointer) BSOD, attached are the new logs.
I'm starting to think that I need a new clean installation, but I hope I will not be forced to do that.

x BlueRobot · Nov 11, 2021

Could you please provide another MEMORY.DMP like you did before? They'll only be one copy since the other one would have been overwritten which is fine since it should be a Stop 0x18 now.

[SOLVED] Help | Random BSODs. FIX: CLEAN INSTALLATION; later, SET RAM voltages/frequencies like advised by the manufacturer.

Member

Attachments

Administrator

Member

Member

Member

Member

Member

Attachments

Member

Attachments

Administrator

Member

Attachments

Member

Attachments

Administrator

Member

Administrator

Administrator

Member

Administrator

Member

Member

Attachments

Administrator