BSODs

Good Afternoon

A little background- frequent BSODs led to inability to boot into Windows at all - I was sent to Startup Repair.

I reinstalled Windows, thought all was well. This was two weeks ago.

BSODs have started again. I updated my drivers / BIOS/ Windows to the latest versions.

I tried Windows Memory tool and it froze at 54%.

Sometimes my machine boots, sometimes it doesn't. Seems random. It will get stuck at the POST screen, or it will work fine.

Just now, I removed 2 of my 4 RAM Modules and the machine booted, but i can't say for sure that was the problem. I've thought other things were the solution too.

I am including the Log Collector file, as instructed in the BSOD guidance.

Windows Version 1909 (OS Build 18363.836)

Much appreciated.

Hello saturn2187 and thanks for your first post!

You have chosen the right approach and I would like to see how you get on with the 2 RAM modules removed. If you are free from BSOD it will suggest that one of the two you removed was faulty. A bit of trial and error will determine which one it is but generally you need to replace them in matched pairs anyway.

The crash dumps do indicate memory corruption as one possible reason.

The logs displayed that RAM has predicted to fail and memory regions have been blocked.

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) Check the motherboard manufacturer's Qualified Vendor List (QVL) for tested RAM modules

14) Run the crucial scanner to view possible replacement options
Crucial System Scanner

Code:

Location     : A0
BankLabel    : Bank0/1
Manufacturer :  
MemoryType   : Unknown
FormFactor   : DIMM
Capacity     : 2GB
Speed        : 800
Serial       :  
PartNumber   :  
ECC          : False
TypeDetail   : Dimm.TypeDetail field was null.

Location     : A1
BankLabel    : Bank2/3
Manufacturer :  
MemoryType   : Unknown
FormFactor   : DIMM
Capacity     : 2GB
Speed        : 800
Serial       :  
PartNumber   :  
ECC          : False
TypeDetail   : Dimm.TypeDetail field was null.

Code:

Event[3085]:
  Log Name: System
  Source: Microsoft-Windows-Memory-Diagnostic-Task-Handler
  Date: 2020-05-31T15:42:07.777
  Event ID: 1001
  Task: N/A
  Level: Information
  Opcode: Info
  Keyword: N/A
  User: S-1-5-21-1365009253-2790186875-3177115537-1001
  User Name: DESKTOP-M474VKR\Craig
  Computer: DESKTOP-M474VKR
  Description: 
Windows removed bad memory regions from this PC.

zbook said:

The logs displayed that RAM has predicted to fail and memory regions have been blocked.

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) Check the motherboard manufacturer's Qualified Vendor List (QVL) for tested RAM modules

14) Run the crucial scanner to view possible replacement options
Crucial System Scanner

Code:

Location     : A0
BankLabel    : Bank0/1
Manufacturer :  
MemoryType   : Unknown
FormFactor   : DIMM
Capacity     : 2GB
Speed        : 800
Serial       :  
PartNumber   :  
ECC          : False
TypeDetail   : Dimm.TypeDetail field was null.

Location     : A1
BankLabel    : Bank2/3
Manufacturer :  
MemoryType   : Unknown
FormFactor   : DIMM
Capacity     : 2GB
Speed        : 800
Serial       :  
PartNumber   :  
ECC          : False
TypeDetail   : Dimm.TypeDetail field was null.

Code:

Event[3085]:
  Log Name: System
  Source: Microsoft-Windows-Memory-Diagnostic-Task-Handler
  Date: 2020-05-31T15:42:07.777
  Event ID: 1001
  Task: N/A
  Level: Information
  Opcode: Info
  Keyword: N/A
  User: S-1-5-21-1365009253-2790186875-3177115537-1001
  User Name: DESKTOP-M474VKR\Craig
  Computer: DESKTOP-M474VKR
  Description: 
Windows removed bad memory regions from this PC.

Probably a dumb question, but can i do this with the (possibly) defective RAM out? So far, it hasn't locked up yet since i removed 2 of the 4 modules.

Please post the results of the above commands.

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.836

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

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

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

Deployment Image Servicing and Management tool
Version: 10.0.18362.1

Image Version: 10.0.18363.836

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

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 ...
738816 file records processed.
File verification completed.
6523 large file records processed.
0 bad file records processed.

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

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

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

116084481 KB total disk space.
72237352 KB in 249487 files.
151028 KB in 51695 indexes.
0 KB in bad sectors.
849349 KB in use by the system.
65536 KB occupied by the log file.
42846752 KB available on disk.

4096 bytes in each allocation unit.
29021120 total allocation units on disk.
10711688 allocation units available on disk.

C:\Windows\system32>wmic recoveros set autoreboot = false
Updating property(s) of '\\DESKTOP-M474VKR\ROOT\CIMV2:Win32_OSRecoveryConfiguration.Name="Microsoft Windows 10 Home|C:\\Windows|\\Device\\Harddisk0\\Partition2"'
Property(s) update successful.

C:\Windows\system32>wmic recoveros set debuginfotype = 7
Updating property(s) of '\\DESKTOP-M474VKR\ROOT\CIMV2:Win32_OSRecoveryConfiguration.Name="Microsoft Windows 10 Home|C:\\Windows|\\Device\\Harddisk0\\Partition2"'
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}
badmemorylist 0x1a8e5a

C:\Windows\system32>

This is the memory region that Windows predicted would fail and has blocked:

Code:

identifier {badmemory}
badmemorylist 0x1a8e5a

RAM memory regions that have not yet been blocked are likely causing the BSOD.

If you can determine which RAM module is malfunctioning it can be removed.

Phic43 had posted steps.

Thank you. As i have already removed 2 of the 4 modules, does that definitely mean the error resides on one of the still inserted modules?

Or, were those instructions referencing previously caused errors that may have been related to a now removed RAM stick

I just got another BSOD with the two inserted RAM modules that I thought were showing stability .

"Unexpected store exception"

I tried switching to the other two and I'm only getting Black screen upon boot . Ugh.