Iv been dealing with kernel problems. pfn list corrupt, memory management. I dont understand? i tested my memory with mem86 test and 0 errors. Microsoft OneDrive - Access files anywhere. Create docs with free Office Online.
Some of the BSODs are from having Driver Verifier running which is testing your drivers. This should only be run for a maximum of 48hrs or until you get a BSOD so that you can check out the drivers it finds that are not working correctly.
So far Driver Verifier seems to have identified two drivers as problematic:
semav6msr64.sys Fri Jul 19 04:49:03 2019 (5D313DAF) - SEMA Software Driver Download
nordlwf.sys Wed Jul 8 07:53:44 2020 (5F056D78) - Nord VPN
Please make sure you turn Driver Verifier off - in a command prompt type verifier /reset
However, I believe the main reason for your BSODs is that you have overclocked your memory. Please reset your memory to the recommended memory clock speed for your system (2666MHz) and see if this helps.
The computer has malfunctioning RAM.
Had you identified the malfunctioning module(s).
Did you want to replace or remove the malfunctioning RAM?
@charbel1011 - have you completed the items in post #2 - has this worked?
Memtest may display pass when there:
a) is incompatible RAM (RAM modules not displayed on the Qualified Vendor List (QVL)
Memtest does not test for incompatible RAM.
b) is a bad memory region that is already blocked by Windows
Please run tuneup.bat and post results into this thread:
Batch files for use in BSOD debugging
Use this link as needed when posting results:
How to Change Post Editor to Source or WYSIWYG Mode at TenForums.com
Code:Event[6284]: Log Name: System Source: Microsoft-Windows-Memory-Diagnostic-Task-Handler Date: 2020-08-10T16:47:28.2660000Z Event ID: 1001 Task: N/A Level: Information Opcode: Info Keyword: N/A User: S-1-5-21-2376795469-3730613445-1686695157-1001 User Name: DESKTOP-VUHJQ7V\17748 Computer: DESKTOP-VUHJQ7V Description: Windows removed bad memory regions from this PC.
Code:Event[16347]: Log Name: System Source: Microsoft-Windows-Memory-Diagnostic-Task-Handler Date: 2020-08-24T09:23:01.6560000Z Event ID: 1001 Task: N/A Level: Information Opcode: Info Keyword: N/A User: S-1-5-21-2376795469-3730613445-1686695157-1001 User Name: DESKTOP-VUHJQ7V\17748 Computer: DESKTOP-VUHJQ7V Description: Windows removed bad memory regions from this PC.
Code:Event[16529]: Log Name: System Source: Microsoft-Windows-Memory-Diagnostic-Task-Handler Date: 2020-08-24T20:51:15.9580000Z Event ID: 1001 Task: N/A Level: Information Opcode: Info Keyword: N/A User: S-1-5-21-2376795469-3730613445-1686695157-1001 User Name: DESKTOP-VUHJQ7V\17748 Computer: DESKTOP-VUHJQ7V Description: Windows removed bad memory regions from this PC.
Okay i got another bsod yesterday and it didnt go through the mini dump. however i got a picture. Imgur: The magic of the Internet
https://imgur.com/t2IDHBQ
i took 2 sticks of my memory this morning and im only running with 2 sticks only to test. i did the test u asked me about here's the results:
############################################################ The following commands will be run in sequence. ## The first 4 will take quite a while to run, be patient. ############################################################sfc /scannowdism /online /cleanup-image /scanhealthdism /online /cleanup-image /restorehealthsfc /scannowchkdsk /scanwmic recoveros get autorebootwmic recoveros set autoreboot = falsewmic recoveros get autorebootwmic recoveros get DebugInfoTypewmic recoveros set DebugInfoType = 7wmic recoveros get DebugInfoTypebcdedit /enum {badmemory}C:\Windows\system32>sfc /scannowBeginning 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 /scanhealthDeployment Image Servicing and Management toolVersion: 10.0.19041.329Image Version: 10.0.19041.450[==========================100.0%==========================] No component store corruption detected.The operation completed successfully.C:\Windows\system32>dism /online /cleanup-image /restorehealthDeployment Image Servicing and Management toolVersion: 10.0.19041.329Image Version: 10.0.19041.450[==========================100.0%==========================] The restore operation completed successfully.The operation completed successfully.C:\Windows\system32>sfc /scannowBeginning 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 /scanThe type of the file system is NTFS.Stage 1: Examining basic file system structure ... 323584 file records processed.File verification completed. Phase duration (File record verification): 1.92 seconds. 4676 large file records processed. Phase duration (Orphan file record recovery): 0.00 milliseconds. 0 bad file records processed. Phase duration (Bad file record checking): 0.30 milliseconds.Stage 2: Examining file name linkage ... 203 reparse records processed. 426460 index entries processed.Index verification completed. Phase duration (Index verification): 7.39 seconds. 0 unindexed files scanned. Phase duration (Orphan reconnection): 168.88 milliseconds. 0 unindexed files recovered to lost and found. Phase duration (Orphan recovery to lost and found): 0.21 milliseconds. 203 reparse records processed. Phase duration (Reparse point and Object ID verification): 1.92 milliseconds.Stage 3: Examining security descriptors ...Security descriptor verification completed. Phase duration (Security descriptor verification): 62.53 milliseconds. 51439 data files processed. Phase duration (Data attribute verification): 0.84 milliseconds.CHKDSK is verifying Usn Journal... 39304376 USN bytes processed.Usn Journal verification completed. Phase duration (USN journal verification): 137.66 milliseconds.Windows has scanned the file system and found no problems.No further action is required. 243559465 KB total disk space. 90342376 KB in 264197 files. 150188 KB in 51440 indexes. 0 KB in bad sectors. 438905 KB in use by the system. 65536 KB occupied by the log file. 152627996 KB available on disk. 4096 bytes in each allocation unit. 60889866 total allocation units on disk. 38156999 allocation units available on disk.Total duration: 9.68 seconds (9689 ms).C:\Windows\system32>wmic recoveros get autorebootAutoRebootFALSEC:\Windows\system32>wmic recoveros set autoreboot = falseUpdating property(s) of '\\DESKTOP-VUHJQ7V\ROOT\CIMV2:Win32_OSRecoveryConfiguration.Name="Microsoft Windows 10 Home|C:\\Windows|\\Device\\Harddisk2\\Partition3"'Property(s) update successful.C:\Windows\system32>wmic recoveros get autorebootAutoRebootFALSEC:\Windows\system32>wmic recoveros get DebugInfoTypeDebugInfoType7C:\Windows\system32>wmic recoveros set DebugInfoType = 7Updating property(s) of '\\DESKTOP-VUHJQ7V\ROOT\CIMV2:Win32_OSRecoveryConfiguration.Name="Microsoft Windows 10 Home|C:\\Windows|\\Device\\Harddisk2\\Partition3"'Property(s) update successful.C:\Windows\system32>wmic recoveros get DebugInfoTypeDebugInfoType7C:\Windows\system32>bcdedit /enum {badmemory}RAM Defects-----------identifier {badmemory}badmemorylist 0x6b420d 0x91b6e0 0xc75571########################################################################## Now copy the results in this window to the Clipboard so you can paste ## it into a post in your tenforums BSOD thread. ## See here for directions: #Batch files for use in BSOD debugging any key to continue . . .
1) Please rerun tuneup.bat and use the information in this link:
Batch files for use in BSOD debugging
How to Change Post Editor to Source or WYSIWYG Mode at TenForums.com
How to Change Post Editor to Source or WYSIWYG Mode at TenForums.com
Code:bcdedit /enum {badmemory}RAM Defects-----------identifier {badmemory}badmemorylist 0x6b420d 0x91b6e0
2) Open administrative command prompt and type or copy and paste:
bcdedit /enum {badmemory}
bcdedit /deletevalue {badmemory} badmemorylist
3) 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
4) Use this link as needed when posting results:
How to Change Post Editor to Source or WYSIWYG Mode at TenForums.com
5) For any BSOD:
a) run the V2 log collector to collect new log files
b) open file explorer> this PC > C: > in the right upper corner search for: C:\Windows\memory.dmp
> if the file size is < 1.5 GB then zip > post a separate share link into the thread using one drive, drop box, or google drive
6) When posting share links please use one drive, drop box, or google drive.
BSOD - Posting Instructions
Quote