3-7 BSODs each day any help appreciated

zbook · Sep 1, 2021

Please check the box to Automatically manage paging file size for all drives.
Then reboot to save the changes.

When available please update the progress with the steps in the earlier post.

These were some of the findings in the logs:

Code:

Event[4625]:
  Log Name: System
  Source: Ntfs
  Date: 2021-08-28T19:34:12.3070000Z
  Event ID: 131
  Task: N/A
  Level: Error
  Opcode: Info
  Keyword: N/A
  User: S-1-5-18
  User Name: NT AUTHORITY\SYSTEM
  Computer: Max
  Description:
The file system structure on volume C: cannot be corrected.
Please run the chkdsk utility on the volume C:.

Event[4626]:
  Log Name: System
  Source: Ntfs
  Date: 2021-08-28T19:34:12.3060000Z
  Event ID: 131
  Task: N/A
  Level: Error
  Opcode: Info
  Keyword: N/A
  User: S-1-5-18
  User Name: NT AUTHORITY\SYSTEM
  Computer: Max
  Description:
The file system structure on volume C: cannot be corrected.
Please run the chkdsk utility on the volume C:.

Event[4627]:
  Log Name: System
  Source: Ntfs
  Date: 2021-08-28T19:34:12.3040000Z
  Event ID: 131
  Task: N/A
  Level: Error
  Opcode: Info
  Keyword: N/A
  User: S-1-5-18
  User Name: NT AUTHORITY\SYSTEM
  Computer: Max
  Description:
The file system structure on volume C: cannot be corrected.
Please run the chkdsk utility on the volume C:.

Event[4628]:
  Log Name: System
  Source: Ntfs
  Date: 2021-08-28T19:34:12.3030000Z
  Event ID: 55
  Task: N/A
  Level: Error
  Opcode: Info
  Keyword: N/A
  User: S-1-5-18
  User Name: NT AUTHORITY\SYSTEM
  Computer: Max
  Description:
A corruption was discovered in the file system structure on volume C:.

The exact nature of the corruption is unknown.  The file system structures need to be scanned and fixed offline.

Code:

Event[4814]:
  Log Name: System
  Source: disk
  Date: 2021-08-28T15:44:21.4540000Z
  Event ID: 153
  Task: N/A
  Level: Warning
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: Max
  Description:
The IO operation at logical block address 0xe0cf780 for Disk 1 (PDO name: \Device\0000003f) was retried.

Event[4815]:
  Log Name: System
  Source: disk
  Date: 2021-08-28T15:44:21.4540000Z
  Event ID: 153
  Task: N/A
  Level: Warning
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: Max
  Description:
The IO operation at logical block address 0x1928b00 for Disk 1 (PDO name: \Device\0000003f) was retried.

Event[4816]:
  Log Name: System
  Source: disk
  Date: 2021-08-28T15:44:21.4540000Z
  Event ID: 153
  Task: N/A
  Level: Warning
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: Max
  Description:
The IO operation at logical block address 0x59f06840 for Disk 1 (PDO name: \Device\0000003f) was retried.

Event[4817]:
  Log Name: System
  Source: disk
  Date: 2021-08-28T15:44:21.4540000Z
  Event ID: 153
  Task: N/A
  Level: Warning
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: Max
  Description:
The IO operation at logical block address 0x3818dfb7 for Disk 1 (PDO name: \Device\0000003f) was retried.

Event[4818]:
  Log Name: System
  Source: disk
  Date: 2021-08-28T15:44:21.4540000Z
  Event ID: 153
  Task: N/A
  Level: Warning
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: Max
  Description:
The IO operation at logical block address 0x45884718 for Disk 1 (PDO name: \Device\0000003f) was retried.

Event[4820]:
  Log Name: System
  Source: disk
  Date: 2021-08-28T15:43:21.4540000Z
  Event ID: 153
  Task: N/A
  Level: Warning
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: Max
  Description:
The IO operation at logical block address 0x45884518 for Disk 1 (PDO name: \Device\0000003f) was retried.

Code:

2021-08-28T19:41:58.3150000Z

CHKDSK is scanning unindexed files for reconnect to their original directory.
Recovering orphaned file WA316A~1.ETL (9DA) into directory file DE818.
Recovering orphaned file waasmedic.20210809_090428_970.etl (9DA) into directory file DE818.
Recovering orphaned file NGENDI~1.TXT (D49) into directory file 73CBD.
Recovering orphaned file NGenDisable.txt (D49) into directory file 73CBD.
Recovering orphaned file 57B79F~1.TOC (114BB) into directory file 3FB96.
Recovering orphaned file 57b79fa153af5bcf84b9d1f4bf58bf56_fce8395c8fd8a999_5c484b625abcc9f9_0_0.0.toc (114BB) into directory file 3FB96.
Recovering orphaned file 57B79F~1.BIN (1155C) into directory file 3FB96.
Recovering orphaned file 57b79fa153af5bcf84b9d1f4bf58bf56_fce8395c8fd8a999_5c484b625abcc9f9_0_0.0.bin (1155C) into directory file 3FB96.
Recovering orphaned file 7BA320~1 (27DDF) into directory file B2C41.
Recovering orphaned file 7ba320d98cf61ae9_0 (27DDF) into directory file B2C41.
Skipping further messages about recovering orphans.




Lost and found is located at \found.000




Correcting errors in the master file table's (MFT) BITMAP attribute.
Correcting errors in the Volume Bitmap.

Windows has made corrections to the file system.

Code:

Event[5911]:
  Log Name: Application
  Source: Microsoft-Windows-Search
  Date: 2021-08-27T09:18:59.1250000Z
  Event ID: 7042
  Task: Search service
  Level: Error
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: Max
  Description:
The Windows Search Service is being stopped because there is a problem with the indexer: The catalog is corrupt.

Details:
    The content index catalogue is corrupt.   0xc0041801 (0xc0041801)


The search service has detected corrupted data files in the index {id=4810 - onecoreuap\base\appmodel\search\search\ytrip\common\util\jetutil.cpp (310)}. The service will attempt to automatically correct this problem by rebuilding the index.

Details:
     0x8e5e0713 (0x8e5e0713)

Code:

2021-08-13T20:45:01.4830000Z


    Found an unneeded link ($FILE_NAME: "URLCAC~1.BIN") in index "$I30" of directory "\Users\Nigel\AppData\Local\Mozilla\Firefox\Profiles\285146hk.default\startupCache <0x241,0x7209>"
        ... repaired online.
    Found an unneeded link ($FILE_NAME: "LOG") in index "$I30" of directory "\Users\Nigel\AppData\Roaming\WhatsApp\File System\Origins <0x24,0xd573>"
        ... repaired online.
    Found an unneeded link ($FILE_NAME: "PHXS-2~1.JSO") in index "$I30" of directory "\Users\Nigel\AppData\Roaming\Adobe\CCX Welcome\discover_panel\assets <0x9f6,0x1f0fd>"
        ... repaired online.
    Found an unneeded link ($FILE_NAME: "main-process.log.0") in index "$I30" of directory "\Users\Nigel\AppData\Roaming\WhatsApp <0x357,0x2059b>"
        ... repaired online.
    Found an unneeded link ($FILE_NAME: "MAIN-P~1.0") in index "$I30" of directory "\Users\Nigel\AppData\Roaming\WhatsApp <0x357,0x2059b>"
        ... repaired online.
    Found an unneeded link ($FILE_NAME: "LOG") in index "$I30" of directory "\Users\Nigel\AppData\Roaming\WhatsApp\Local Storage\leveldb <0x206,0x21578>"
        ... repaired online.
    Found an unneeded link ($FILE_NAME: "ADDONS~1.LZ4") in index "$I30" of directory "\Users\Nigel\AppData\Roaming\Mozilla\Firefox\Profiles\285146hk.default <0x7,0x5b96f>"
        ... repaired online.
    Found an unneeded link ($FILE_NAME: "BROADC~1.JSO") in index "$I30" of directory "\Users\Nigel\AppData\Roaming\Mozilla\Firefox\Profiles\285146hk.default <0x7,0x5b96f>"
        ... repaired online.
    Found an unneeded link ($FILE_NAME: "EXTENS~1.JSO") in index "$I30" of directory "\Users\Nigel\AppData\Roaming\Mozilla\Firefox\Profiles\285146hk.default <0x7,0x5b96f>"
        ... repaired online.
    Found an unneeded link ($FILE_NAME: "sessionstore.jsonlz4") in index "$I30" of directory "\Users\Nigel\AppData\Roaming\Mozilla\Firefox\Profiles\285146hk.default <0x7,0x5b96f>"
        ... repaired online.
    Found an unneeded link ($FILE_NAME: "SESSIO~1.JSO") in index "$I30" of directory "\Users\Nigel\AppData\Roaming\Mozilla\Firefox\Profiles\285146hk.default <0x7,0x5b96f>"
        ... repaired online.
    Found an unneeded link ($FILE_NAME: "SESSIO~2.JSO") in index "$I30" of directory "\Users\Nigel\AppData\Roaming\Mozilla\Firefox\Profiles\285146hk.default <0x7,0x5b96f>"
        ... repaired online.
    Found an unneeded link ($FILE_NAME: "SHADER~1") in index "$I30" of directory "\Users\Nigel\AppData\Roaming\Mozilla\Firefox\Profiles\285146hk.default <0x7,0x5b96f>"
        ... repaired online.
    Found an unneeded link ($FILE_NAME: "WAC506~1.ETL") in index "$I30" of directory "\Windows\Logs\waasmedic <0x5a,0xde818>"
        ... repaired online.
    Found an unneeded link ($FILE_NAME: "LOG") in index "$I30" of directory "\Users\Nigel\AppData\Roaming\WhatsApp\Session Storage <0x17,0x18be3d>"
        ... repaired online.
  2914318 index entries processed.                                                      

Index verification completed.
 Phase duration (Index verification): 1.26 minutes.
    Found corrupt basic file structure for "\Users\Nigel\AppData\Roaming\Mozilla\Firefox\Profiles\285146hk.default\BROADC~1.JSO <0xfd,0x147a1>"
        ... queued for offline repair.
    Found corrupt basic file structure for "\Users\Nigel\AppData\Roaming\Mozilla\Firefox\Profiles\285146hk.default\SHADER~1 <0x41,0x1568f>"
        ... queued for offline repair.
    Found corrupt basic file structure for "\Users\Nigel\AppData\Roaming\Mozilla\Firefox\Profiles\285146hk.default\SESSIO~1.JSO <0x63,0x86e4b>"
        ... queued for offline repair.
    Found corrupt basic file structure for "\Users\Nigel\AppData\Roaming\Mozilla\Firefox\Profiles\285146hk.default\EXTENS~1.JSO <0x1df,0x8b41b>"
        ... queued for offline repair.
    Found corrupt basic file structure for "\Users\Nigel\AppData\Roaming\Mozilla\Firefox\Profiles\285146hk.default\ADDONS~1.LZ4 <0x3d,0x8b607>"
        ... queued for offline repair.

 Phase duration (Orphan reconnection): 0.00 milliseconds.

    Found 2 lost files (\Users\Nigel\AppData\Roaming\WhatsApp\IndexedDB\file__0.indexeddb.leveldb\LOG <0x66d,0x4529>, ...); requesting reconnection to index "$I30" of directory "\Device\HarddiskVolume3\found.000"
        ... repaired online.
    Found lost file "\Users\Nigel\AppData\Local\Packages\microsoft.windowscommunicationsapps_8wekyb3d8bbwe\AC\Temp\mat-debug-26228.log <0x3f,0x5d093>"; requesting reconnection to index "$I30" of directory "\Users\Nigel\AppData\Local\Packages\microsoft.windowscommunicationsapps_8wekyb3d8bbwe\AC\Temp <0x3,0x4751f>"
        ... repaired online.
    Found 6 missing entries (\Users\Nigel\AppData\Roaming\Mozilla\Firefox\Profiles\285146hk.default\broadcast-listeners.json <0xfd,0x147a1>, ...) in index "$I30" of directory "\Users\Nigel\AppData\Roaming\Mozilla\Firefox\Profiles\285146hk.default <0x7,0x5b96f>"
        ... queued for offline repair.
    Found 2 missing entries (\Users\Nigel\AppData\Roaming\WhatsApp\Session Storage\LOG <0x4de,0x4508>, ...) in index "$I30" of directory "\Users\Nigel\AppData\Roaming\WhatsApp\Session Storage <0x17,0x18be3d>"
        ... repaired online.
    Found 2 missing entries (\Users\Nigel\AppData\Roaming\WhatsApp\File System\Origins\LOG <0x3e0,0x4501>, ...) in index "$I30" of directory "\Users\Nigel\AppData\Roaming\WhatsApp\File System\Origins <0x24,0xd573>"
        ... repaired online.
    Found 2 lost files (...\abe82e6549161bdc_0 <0x61,0xdb0b2>, ...\3ae6fb702f8c7164_0 <0x5b,0xdb19c>); requesting reconnection to index "$I30" of directory "\Device\HarddiskVolume3\found.001"
was not able to send command for self-healing due to lack of memory.
    Found lost file "\Windows\Prefetch\UPDATE.EXE-6EA23C3A.pf <0x70,0xdad90>"; requesting reconnection to index "$I30" of directory "\Windows\Prefetch <0x194,0x1eab>"
was not able to send command for self-healing due to lack of memory.
    Found 2 missing entries (\Users\Nigel\AppData\Roaming\WhatsApp\Local Storage\leveldb\LOG.old <0x5d8,0x247c>, ...) in index "$I30" of directory "\Users\Nigel\AppData\Roaming\WhatsApp\Local Storage\leveldb <0x206,0x21578>"
was not able to send command for self-healing due to lack of memory.
    Found 4 missing entries (\Users\Nigel\AppData\Local\Mozilla\Firefox\Profiles\285146hk.default\startupCache\urlCache-current.bin <0x3d,0x27bf2>, ...) in index "$I30" of directory "\Users\Nigel\AppData\Local\Mozilla\Firefox\Profiles\285146hk.default\startupCache <0x241,0x7209>"
was not able to send command for self-healing due to lack of memory.
    Found lost file "\Users\Nigel\AppData\Roaming\WhatsApp\blob_storage\f459f4d3-5020-4e2a-af3a-73fe8f4313e4 <0x84,0x3803b>"; requesting reconnection to index "$I30" of directory "\Users\Nigel\AppData\Roaming\WhatsApp\blob_storage <0x33b,0x20f22>"
was not able to send command for self-healing due to lack of memory.
    Found 2 lost files (...\main-process.log.1 <0x5db,0x4486>, ...\main-process.log <0x136,0xdad7a>); requesting reconnection to index "$I30" of directory "\Device\HarddiskVolume3\found.002"
was not able to send command for self-healing due to lack of memory.
    Found lost file "\Users\Nigel\AppData\Roaming\Adobe\CCX Welcome\discover_panel\assets\PHXS-22.4.3-en_GB-8a433609-70da-45b2-b412-0042628068d9.json <0x178,0xd46a3>"; requesting reconnection to index "$I30" of directory "\Users\Nigel\AppData\Roaming\Adobe\CCX Welcome\discover_panel\assets <0x9f6,0x1f0fd>"
was not able to send command for self-healing due to lack of memory.
    Found 5 files (\Users\Nigel\AppData\Roaming\Mozilla\Firefox\Profiles\285146hk.default\broadcast-listeners.json <0xfd,0x147a1>, ...) with bad links
        ... queued for offline repair.
 Phase duration (Orphan recovery to lost and found): 0.00 milliseconds.
  1421 reparse records processed.                                    

 Phase duration (Reparse point and Object ID verification): 9.17 milliseconds.

Stage 3: Examining security descriptors ...
Security descriptor verification completed.
 Phase duration (Security descriptor verification): 94.16 milliseconds.
  271880 data files processed.                                          

 Phase duration (Data attribute verification): 0.02 milliseconds.
CHKDSK is verifying Usn Journal...
Usn Journal verification completed.
Windows has found problems and some were fixed online;
the remaining problems must be fixed offline.
Please run "chkdsk /spotfix" to fix the issues.

Grisham · Sep 1, 2021

Completed chkdsk and drive was repaired

I'm working through the HD Tune reports. So far the only flag is crc error count on the Toshiba X300 6GB which I use to store the backups from Acronis True Image.

Grisham · Sep 2, 2021

Quick thought along the lines of chicken/egg
I've realised looking back that there have been frequent errors reported on the C: drive. I have run the Intel Solid State Drive Toolbox and its previous version. The firmware is up to date. The drive has been running for nearly 5 years but is still within warranty (1 month left). Is there enough evidence to make a warranty claim?

I will be contacting Intel support later today. I have a second 750 series 1.2TB drive on another PC. I am intending to back up that PC and then replace the existing drive and see if the BSODs stop.

Thanks,

zbook · Sep 2, 2021

A Sea Tools Long Generic test fail or long DST fail are often used for warranty replacement.

For HDs with recurrent Chkdsk problems some options are to run diskpart clean all or disk sanitizer or secure erase.

If they fix the recurrent Chkdsk problems then your set.

If there are recurrent chkdsk despite the clean all or disk sanitizer or secure erase then replace the drive.

Overview
Temperature
SMART

See this link for the cables: Hard disk case: communication errors

Chkdsk /b /v offers the deepest testing of the drive. The v is for the most detailed report.

For Chkdsk reports please run https://www.dropbox.com/s/xfsr4yyg5yun3k1/ListChkdskResult.exe?dl=1

zbook · Sep 3, 2021

This is an edit of the prior post:

After completing all Chkdsk /b /v

Run HD Sentinel (free or trial version)
Hard Disk Sentinel - HDD health and temperature monitoring

For each drive post images of these tabs:
Overview
Temperature
SMART

Grisham · Sep 4, 2021

I have been testing the drives but this is a long tedious process and I am not quite there yet. The results so far are that no drives are showing errors.

I started to use driver verifier to see if I could generate some specific error messages. To start with the PC wouldn't boot when I had set the drivers to be verified. I patiently worked through the list separating the list into two and then seeing if one list would boot and one not - which was the case. I was then able to identify one driver that if it was being verified would not allow the boot process to complete - I went about this the wrong way and didn't keep notes of the list and which specific drivers were tied to specific outputs are the inability to boot. However, The last dump a memory dump (1.69GB) I was able to generate identified an issue with semav6mrs64.sys from the Intel Drivers Update tool - which I had uninstalled. Apparently this driver is not uninstalled in that process and is still referenced in the registry.

The driver file remained in C:\Program Files\Intel\SUR\QUEENCREEK\semav6mrs64.sys and was manually deleted
It was also in a second location C:\Windows\System32\drivers\semav6mrs64.sys and this was also manually deleted

I then searched the registry and found two entries:
HKEY_LOCAL_MACHINE\System\CurrentControlSet\services\semav6mrs64
HKEY_LOCAL_MACHINE\SYSTEM\Setup\FirstBoot\Services\semav6msr64
Both of these entries were deleted.

For some reason minidumps are no longer being produced?
I tried using Event Viewer to check for events leading up to the crashes and an attempt to run semav6msr64.sys was failing - because it no longer exists.
I searched the registry and found HKEY_LOCAL_MACHINE\System\CurrentControlSet\services\semav6mrs64 had been restored
So I deleted it again and rebooted and it was restored again.

I used Microsoft Autoruns but it only identifies the restored registry entry and nothing else?

Any suggestions?

I know there must be something restoring it but I have no idea where to look next.

The latest SysNative report file is here:
20210904-SysnativeFileCollectionApp.zip (19MB)

Thanks,

xilolee · Sep 4, 2021

Check if you have got Intel computer improvement program and Intel Energy checker SDK, and remove them.

Grisham · Sep 4, 2021

From Intel I have the following:
Intel ® C++ Redistributables for Windows* on Intel(R) 64
Intel ® C++ Redistributables on Intel(R) 64
Intel ® Intel Computer Improvement Program
Intel ® Memory and Storage Tool
Intel ® Network Connections 23.5.1.0
Intel ® Rapid Storage Technology
Intel ® Management Engine Components
Intel ® NVME Miniport and Filter Device Management
Intel ® Optane Pinning Explorer Extensions
Intel ® SSD Toolbox
Intel ® USB 3.0 eXtensible Host Controller Driver
Intel ® Watchdog Timer, Driver (Intel Intel ® WDT)

I don't appear to have either of the programs you mentioned.

Grisham · Sep 4, 2021

zbook said:
A Sea Tools Long Generic test fail or long DST fail are often used for warranty replacement.

For HDs with recurrent Chkdsk problems some options are to run diskpart clean all or disk sanitizer or secure erase.

If they fix the recurrent Chkdsk problems then your set.

If there are recurrent chkdsk despite the clean all or disk sanitizer or secure erase then replace the drive.

Overview
Temperature
SMART

See this link for the cables: Hard disk case: communication errors

Chkdsk /b /v offers the deepest testing of the drive. The v is for the most detailed report.

For Chkdsk reports please run https://www.dropbox.com/s/xfsr4yyg5yun3k1/ListChkdskResult.exe?dl=1

I will certainly test the drive using the Sea Tools provided it is OK for SSDs. Thanks for feeding back on the earlier chkdsk results. As I mentioned before I confused by the use of /v switch as it is described as being only for FA/FAT32 partitions. I am preparing myself to switch to a PCIe version of the drive - the current one is a U.2 drive with a PCIe adaptor. I'm just making sure everything is backed up before I start. If the erros stop once the drive is switched this will be definitive in itself. My suspicion is that if it is a hardware fault, that it is to do with a faulty controller.

Because these are drives connected via PCIe then the cable issue is not a factor here. However, you make a good point and for completeness I will swap out the cables for all the other drives.

As I mentioned, this is painful process in parts. HD Tools took 7 hours scanning the 6GB HDD and just as it was about to finish the PC crashed and I had to start again.

With the chkdsk I can run them in parallel by opening 5 command prompt windows.

zbook · Sep 4, 2021

HD Tune and Sea Tools can run simultaneously overnight.
Chkdsk /b /v can run on any non-Windows drive during the day and night.
So a log of progress can be made with drive testing while using Windows and while away from the computer.

To reduce the likelihood of BSOD the computer can run in safe mode (shift + restart)
or administrative command prompt shutdown /r /o /f /t 00

For the /v switch and other switches see:
chkdsk

Code:

/v    Displays the name of each file in every directory as the disk is checked.

Running Windows driver verifier on your own will interfere with disk drive testing.
Please don't run the tool at this time and catch up on all of the prior steps.

Please post command with results images of scannow, restorehealth, and run the Windows troubleshooter detailed results (see post #10 step #1) to see if this was fixed after reboot.

The latest logs displayed that the page file is on F:

Please make sure that the page file is on the Windows drive and that the startup and recovery system failure and virtual memory/page file settings display:
Page file C:
system managed size
Automatically manage paging file size for all drives

Reboot to maintain settings.

Code:

FAILURE_ID_HASH_STRING:  km:0x154_c0000006_c00000c0_image_hardware_disk


IO_ERROR: (NTSTATUS) 0xc00000c0 - This device does not exist.

EXCEPTION_STR:  0xc0000006_c00000c0

ERROR_CODE: (NTSTATUS) 0xc0000006 - The instruction at 0x%p referenced memory at 0x%p.
The required data was not placed into memory because of an I/O error status of 0x%x.

xilolee · Sep 5, 2021

xilolee said:
Check if you have got Intel computer improvement program...

Grisham said:
From Intel I have the following:
...
Intel ® Intel Computer Improvement Program
...

Grisham · Sep 8, 2021

Quick update:

I swapped out the 2.5" U.2 drive for a PCIe version that wasn't displaying any issues. It's been running for 48 hours with one BSOD. When I swapped it I restored the back up from earlier in the day - up to then I had been getting 7-8 BSODs a day. ON restore I had a historic BSOD showing in Reliability History. At midnight (more than 36 hours later) I had an actual BSOD but no minidump. I added the faulting drive into the into the donor PC and restored the backup for that drive. Both PCs have the same motherboard. Despite a couple of tries, I couldn't get the drive to boot. I had already contacted Intel Customer support on the 3rd September. I let them know the updated information and they have agreed a replacement. Hopefully this is the main cause of the problems and I can get back to being productive.

Just wanted to say thanks to everyone that took an interest and offered assistance.

I'll let you know in a couple of weeks time if this has solved the issue.

Search

Search

3-7 BSODs each day any help appreciated

zbook

Member

Grisham

Member

Attachments

Grisham

Member

zbook

Member

zbook

Member

Grisham

Member

xilolee

Moderator

Grisham

Member

Grisham

Member

zbook

Member

xilolee

Moderator

Grisham

Member