BSOD while browsing firefox

OK, so just test the CPU with Prime95 and OCCT as I asked you before

Please restart Windows driver verifier.
Run the tool for 48 hours with 19 customized tests.
If there are no BSOD then turn off the tool.
If there are BSOD then upload a new V2 and memory.dmp if the size is < 1.5 GB.

After testing with Windows driver verifier comment into the thread.
Then test hardware.

zbook said:

Please restart Windows driver verifier.
Run the tool for 48 hours with 19 customized tests.
If there are no BSOD then turn off the tool.
If there are BSOD then upload a new V2 and memory.dmp if the size is < 1.5 GB.

After testing with Windows driver verifier comment into the thread.
Then test hardware.

okay will do,im running the commands at the moment

- - - Updated - - -

zbook said:

Please restart Windows driver verifier.
Run the tool for 48 hours with 19 customized tests.
If there are no BSOD then turn off the tool.
If there are BSOD then upload a new V2 and memory.dmp if the size is < 1.5 GB.

After testing with Windows driver verifier comment into the thread.
Then test hardware.

Microsoft Windows [Version 10.0.18362.295]
(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 found corrupt files but was unable to fix some of 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.

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

Deployment Image Servicing and Management tool
Version: 10.0.18362.1

Image Version: 10.0.18362.295

[==========================100.0%==========================] The component store is repairable.
The operation completed successfully.

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

Deployment Image Servicing and Management tool
Version: 10.0.18362.1

Image Version: 10.0.18362.295

[==========================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 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.

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

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

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

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

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

976166911 KB total disk space.
180530052 KB in 187446 files.
139824 KB in 47736 indexes.
0 KB in bad sectors.
409251 KB in use by the system.
65536 KB occupied by the log file.
795087784 KB available on disk.

4096 bytes in each allocation unit.
244041727 total allocation units on disk.
198771946 allocation units available on disk.

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

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

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

C:\Windows\system32>

Code:

Windows Resource Protection found corrupt files but was unable to fix some of them.

Code:

Windows Resource Protection found corrupt files and successfully repaired them.

Looks good.

zbook said:

Code:

Windows Resource Protection found corrupt files but was unable to fix some of them.

Code:

Windows Resource Protection found corrupt files and successfully repaired them.

Looks good.

Okay nice thanks. Now just got to wait and see if verifier causes a BSOD

camthemanzx said:

Okay nice thanks. Now just got to wait and see if verifier causes a BSOD

PC has been on for about 48 hours,no bsod

v2 attached

1) The last BSOD seen in the logs was: Date: 2019-09-16 T01:22:47.577

2) Turn off Windows driver verifier tonight.

3) Open administrative command prompt and type or copy and paste:
chkdsk /r /v
This may take hours to run so plan to run overnight.
Run on all drives using the syntax: chkdsk /r /v C: or chkdsk /r /v D: changing the drive letter to the applicable drive.

C:\Windows\system32>chkdsk /r /v
The type of the file system is NTFS.
Cannot lock current drive.

Chkdsk cannot run because the volume is in use by another
process. Would you like to schedule this volume to be
checked the next time the system restarts? (Y/N)

Type: Y
reboot


4) Use the information in this link to find the chkdsk report in the event viewer.
Copy and paste into notepad > save to desktop > post into the thread using one drive or drop box share link:
Read Chkdsk Log in Event Viewer in Windows 10 Windows 10 Performance Maintenance Tutorials
Read Chkdsk Log in Event Viewer in Windows 10

zbook said:

1) The last BSOD seen in the logs was: Date: 2019-09-16 T01:22:47.577

2) Turn off Windows driver verifier tonight.

3) Open administrative command prompt and type or copy and paste:
chkdsk /r /v
This may take hours to run so plan to run overnight.
Run on all drives using the syntax: chkdsk /r /v C: or chkdsk /r /v D: changing the drive letter to the applicable drive.

C:\Windows\system32>chkdsk /r /v
The type of the file system is NTFS.
Cannot lock current drive.

Chkdsk cannot run because the volume is in use by another
process. Would you like to schedule this volume to be
checked the next time the system restarts? (Y/N)

Type: Y
reboot


4) Use the information in this link to find the chkdsk report in the event viewer.
Copy and paste into notepad > save to desktop > post into the thread using one drive or drop box share link:
Read Chkdsk Log in Event Viewer in Windows 10 Windows 10 Performance Maintenance Tutorials
Read Chkdsk Log in Event Viewer in Windows 10

I think this is it,the source in event viewer for this file was wininit,there are two more from a few days ago with chkdsk source. disk.txt - Google Drive

The link that was posted was without a date.
If it was recent then it displayed only cleaning.
If it was not recent then run chkdsk /r /v overnight.

The hardware stress tests can be ran while monitoring temperatures.

Please download and install:
https://www.nirsoft.net/utils/driverview.html
Post a share link into the thread.
Upload a new V2 into the thread.