Had BSOD coming out of sleep mode

Hi all came home from work , opened laptop hit space bar and was faced with the dreaded stop screen happened so fast did not even get a chance to see it. not sure maybe this could be due to a firmware update on my crucial ssd there trying to fix the overtemp error crap with the P2 model well not sure what they did to it as now there own dumb program dont scan it right, go figure, and now it reports over temp all the time LOL, dumb crucial support. got a call in to them tomorrow. anyhow here is V2 logs.

Hi Tonyb,

There were recent BSOD.
Windows did not create dump files.

The RAM modules are mismatched.
Also they displayed different speeds.
When were each module added?


Please perform the following steps:

1) Run:
Tuneup.bat - Click here to go to the BSOD batch repository to download and run this batch file.

2) 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


3) Run Crystal Disk standard edition:
CrystalDiskInfo – Crystal Dew World
Post images into the thread.

4) Download and install fresh AMD video drivers:
https://support.hp.com/us-en/drivers...91?sku=7MP82UA

5) The logs displayed a newer BIOS than what was displayed on the HP website.
Which HP software was used to find and install the F.45 BIOS?

Code:

Location     : Bottom - Slot 1 (left)
BankLabel    : P0 CHANNEL A
Manufacturer : Samsung
MemoryType   : DDR4
FormFactor   : SODIMM
Capacity     : 8GB
Speed        : 2133
Serial       : 92504EDB
PartNumber   : M471A1K43BB0-CPB    
ECC          : False
TypeDetail   : {Synchronous, Unbuffered (Unregistered)}

Location     : Bottom - Slot 2 (right)
BankLabel    : P0 CHANNEL B
Manufacturer : Samsung
MemoryType   : DDR4
FormFactor   : SODIMM
Capacity     : 8GB
Speed        : 2667
Serial       : 32349C15
PartNumber   : M471A1K43DB1-CTD    
ECC          : False
TypeDetail   : {Synchronous, Unbuffered (Unregistered)}

A HP service center added them they have been in the pc since i bought it, were added at the HP service and support center, i asked them about it and they said nothing wrong with it like that.

- - - Updated - - -

im thinking BSOD was related to the SSD firmware update that crucial storage executive did this morning as now the errors are worse in there than they were before that update i have a call back set for crucial tomorrow.

- - - Updated - - -

also edge is blocking tuneupbat ??

Bat files are blocked.
To run them go through the prompts.

The earlier post was in progress and was edited.

i got it to run dumb smart filter its running now as we speak. :) whole thing closed out running it again ugh !!!

- - - Updated - - -

Code:

############################################################ The following commands will be run in sequence.         ## The first 5 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 DebugInfoTypewmic pagefile list /format:listwmic Computersystem where name="LAPTOP-EVII47JS" get AutomaticManagedPagefilewmic Computersystem where name="LAPTOP-EVII47JS" set AutomaticManagedPagefile=Truewmic Computersystem where name="LAPTOP-EVII47JS" get AutomaticManagedPagefilebcdedit /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.572Image Version: 10.0.19042.630[==========================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.572Image Version: 10.0.19042.630[==========================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.Volume label is Windows.Stage 1: Examining basic file system structure ...  613120 file records processed.File verification completed. Phase duration (File record verification): 7.15 seconds.  33784 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.55 milliseconds.Stage 2: Examining file name linkage ...  83993 reparse records processed.  824086 index entries processed.Index verification completed. Phase duration (Index verification): 14.24 seconds.  0 unindexed files scanned. Phase duration (Orphan reconnection): 3.27 seconds.  0 unindexed files recovered to lost and found. Phase duration (Orphan recovery to lost and found): 0.60 milliseconds.  83993 reparse records processed. Phase duration (Reparse point and Object ID verification): 238.47 milliseconds.Stage 3: Examining security descriptors ...Security descriptor verification completed. Phase duration (Security descriptor verification): 137.69 milliseconds.  105484 data files processed. Phase duration (Data attribute verification): 0.43 milliseconds.CHKDSK is verifying Usn Journal...  37803808 USN bytes processed.Usn Journal verification completed. Phase duration (USN journal verification): 152.25 milliseconds.Windows has scanned the file system and found no problems.No further action is required. 487099391 KB total disk space.  65752192 KB in 344183 files.    240648 KB in 105485 indexes.         0 KB in bad sectors.    752211 KB in use by the system.     65536 KB occupied by the log file. 420354340 KB available on disk.      4096 bytes in each allocation unit. 121774847 total allocation units on disk. 105088585 allocation units available on disk.Total duration: 25.23 seconds (25239 ms).C:\WINDOWS\system32>wmic recoveros get autorebootAutoRebootFALSEC:\WINDOWS\system32>wmic recoveros set autoreboot = falseUpdating property(s) of '\\LAPTOP-EVII47JS\ROOT\CIMV2:Win32_OSRecoveryConfiguration.Name="Microsoft Windows 10 Pro|C:\\WINDOWS|\\Device\\Harddisk1\\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 '\\LAPTOP-EVII47JS\ROOT\CIMV2:Win32_OSRecoveryConfiguration.Name="Microsoft Windows 10 Pro|C:\\WINDOWS|\\Device\\Harddisk1\\Partition3"'Property(s) update successful.C:\WINDOWS\system32>wmic recoveros get DebugInfoTypeDebugInfoType7C:\WINDOWS\system32>wmic pagefile list /format:listAllocatedBaseSize=896CurrentUsage=580Description=C:\pagefile.sysInstallDate=20191225235922.549952-480Name=C:\pagefile.sysPeakUsage=580Status=TempPageFile=FALSEC:\WINDOWS\system32>wmic Computersystem where name="LAPTOP-EVII47JS" get AutomaticManagedPagefileAutomaticManagedPagefileTRUEC:\WINDOWS\system32>wmic Computersystem where name="LAPTOP-EVII47JS" set AutomaticManagedPagefile=TrueUpdating property(s) of '\\LAPTOP-EVII47JS\ROOT\CIMV2:Win32_ComputerSystem.Name="LAPTOP-EVII47JS"'Property(s) update successful.C:\WINDOWS\system32>wmic Computersystem where name="LAPTOP-EVII47JS" get AutomaticManagedPagefileAutomaticManagedPagefileTRUEC:\WINDOWS\system32>bcdedit /enum {badmemory}RAM Defects-----------identifier              {badmemory}Press any key to continue . . .

- - - Updated - - -
@zbook ok that did not work uploaded a note pad view i cant seem to get the code thing to work tried four times if someone else want to try the notepad with the info is attached .

When posting from notepad use:
How to Change Post Editor to Source or WYSIWYG Mode at TenForums.com

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