Getting random BSODs for a while now

Update Realtek LAN driver - Realtek PCIe FE / GBE / 2.5G / Gaming Ethernet Family Controller Software - REALTEK

See posting instructions:

BSOD - Posting Instructions

MrPepka said:

Update Realtek LAN driver

Did that, restarted and tried again, got another BSOD with a "DRIVER_IRQL_NOT_LESS_OR_EQUAL" pointing me to "dxgmms2", heres the new .dmp: Microsoft OneDrive - Access files anywhere. Create docs with free Office Online.

zbook said:

See posting instructions]

Edit: I'll try to do the collector thing, sorry.

Edit 2: Here it is Microsoft OneDrive - Access files anywhere. Create docs with free Office Online.

The log files were in a foreign language and could not be scanned.

Please use English as the default language and post a new V2.

https://www.tenforums.com/tutorials/...dows-10-a.html
Change Display Language in Windows 10

1. Run Driver Verifier Manager through type "verifier" in search bottom
2. Select "Create custom settings (for code developers)"
3. Tick all standard settings and 1 additional setting (NDIS/WIFI verification)
4. Select "Select driver names from a list"
5. Tick all 3rd party drivers and 10 Microsoft drivers (ntoskrnl.exe, hal.dll, ndis.sys, tcpip.sys, fwpkclnt.sys, ntfs.sys, fileinfo.sys, fltmgr.sys and dxgmms2.sys)
6. Apply changes and reboot computer

zbook said:

The log files were in a foreign language and could not be scanned.

Please use English as the default language and post a new V2.

Sorry, didn't take that into account, here it is Microsoft OneDrive - Access files anywhere. Create docs with free Office Online.

What is/are the warranty status for the computer / components?

1) Open administrative command prompt and type or copy and paste:
2) sfc /scannow
3) dism /online /cleanup-image /scanhealth
4) dism /online /cleanup-image /restorehealth
5) sfc /scannow
6) chkdsk /scan
7) wmic recoveros set autoreboot = false
8) wmic recoveros set DebugInfoType = 7
9) wmic recoveros get autoreboot
10) wmic recoveros get DebugInfoType
11) bcdedit /enum {badmemory}

12) When these have completed > right click on the top bar or title bar of the administrative command prompt box > left click on edit then select all > right click on the top bar again > left click on edit then copy > paste into the thread

13) Make sure that there is no over clocking while troubleshooting

14) To ensure that there are no improper bios settings please reset the bios

How to Clear Your Computers CMOS to Reset BIOS Settings:
How to Clear Your Computer’s CMOS to Reset BIOS Settings
3 Ways to Reset Your BIOS - wikiHow:
3 Ways to Reset Your BIOS - wikiHow
3 Easy Ways to Clear CMOS (Reset BIOS)
How to Clear CMOS (AKA Reset BIOS Settings)


15) In the left lower corner search type: system or system control > open system control panel > on the left pane click advanced system settings

a) > on the advanced tab under startup and recovery > click settings > post an image of the startup and recovery window into the thread

b) > on the advanced tab under performance > click on settings > on the performance options window > click on the advanced tab > under virtual memory > click on change > post an image of the virtual memory window into the thread

16) Run Memtest86 version 8.3 (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.

17) Please post a share link for c:\windows\memory.dmp

Code:

LastWriteTime       Size (MB) FullName             
-------------       --------- --------             
01/03/2020 18:53:00    738.92 C:\WINDOWS\MEMORY.DMP

Ok, this is from the steps 1 to 11

Microsoft Windows [Version 10.0.18363.657]
(c) 2019 Microsoft Corporation. All rights reserved.

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 did not find any integrity violations.

C:\WINDOWS\system32>dism /online /cleanup-image /scanhealth

Deployment Image Servicing and Management tool
Version: 10.0.18362.1

Image Version: 10.0.18363.657

[==========================100.0%==========================] No component store corruption detected.
The operation completed successfully.

C:\WINDOWS\system32>dism /online /cleanup-image /restorehealth

Deployment Image Servicing and Management tool
Version: 10.0.18362.1

Image Version: 10.0.18363.657

[==========================100.0%==========================] The restore operation completed successfully.
The operation completed successfully.

C:\WINDOWS\system32>
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 did not find any integrity violations.

C:\WINDOWS\system32>chkdsk /scan
The type of the file system is NTFS.

Stage 1: Examining basic file system structure ...
729600 file records processed.
File verification completed.
5489 large file records processed.
0 bad file records processed.

Stage 2: Examining file name linkage ...
337 reparse records processed.
824426 index entries processed.
Index verification completed.
0 unindexed files scanned.
0 unindexed files recovered to lost and found.
337 reparse records processed.

Stage 3: Examining security descriptors ...
Security descriptor verification completed.
47414 data files processed.
CHKDSK is verifying Usn Journal...
34995784 USN bytes processed.
Usn Journal verification completed.

Windows has scanned the file system and found no problems.
No further action is required.

243536895 KB total disk space.
108200648 KB in 329909 files.
181524 KB in 47415 indexes.
0 KB in bad sectors.
840083 KB in use by the system.
65536 KB occupied by the log file.
134314640 KB available on disk.

4096 bytes in each allocation unit.
60884223 total allocation units on disk.
33578660 allocation units available on disk.

C:\WINDOWS\system32>wmic recoveros set autoreboot = false
Updating property(s) of '\\DESKTOP-QGSI0SV\ROOT\CIMV2:Win32_OSRecoveryConfiguration.Name="Microsoft Windows 10 Pro|C:\\WINDOWS|\\Device\\Harddisk2\\Partition4"'
Property(s) update successful.

C:\WINDOWS\system32>wmic recoveros set DebugInfoType = 7
Updating property(s) of '\\DESKTOP-QGSI0SV\ROOT\CIMV2:Win32_OSRecoveryConfiguration.Name="Microsoft Windows 10 Pro|C:\\WINDOWS|\\Device\\Harddisk2\\Partition4"'
Property(s) update successful.

C:\WINDOWS\system32>wmic recoveros get autoreboot
AutoReboot
FALSE


C:\WINDOWS\system32>wmic recoveros get DebugInfoType
DebugInfoType
7


C:\WINDOWS\system32>bcdedit /enum {badmemory}

RAM Defects
-----------
identifier {badmemory}

C:\WINDOWS\system32>

Step 15

Attachment 268786

Attachment 268787

I'll run another memtest then although I already did it a few days ago with no errors, but I suppose is never hurts to try again.

Here's the memory.dmp without the new memtest memory.dmp

Btw.. is it really that bad?

- - - Updated - - -

Ok here are the pictures from the memtest plus the new memory.dmp (Only ran memtest for 4 passes, don't have time for more, but if it's absolutely neccesary, I'll do it tomorrow)

Memtest and memory.dmp