Share via

Frequent bluescreen errors randomly started happening

Anonymous
2024-07-21T04:26:16+00:00

I have been having frequent bluescreen errors including: KERNEL_MODE_HEAP_CURRUPTION, SYSTEM_THREAD_EXCEPTION_NOT_HANDLED and POOL_CORRUPTION_IN_FILE_AREA. Ive checked all drivers and they are up to date as is all windows updates, i then ran sfc/scannow and got the response that it found corrupted files but it could not repair them and showed the location of the CBS log file. I have no idea what im looking at in the log file and i need some help, the pc runs perfectly fine them randomly i will get bluescreen and the pc restarts. I have the cbs file copied to a .txt file

Windows 10 64 bit

AMD Ryzen 7 3700x

32gb DDR4 Ram

1tb m.2 nvme ssd

500gb HDD

RX580 GPU

Windows for home | Windows 10 | Performance and system failures

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments

1 answer

Sort by: Most helpful
Most helpful Newest Oldest
  1. Anonymous
    2024-07-21T07:00:26+00:00

    Hello Mitch, I'm Quinn, and I'm happy to help you.

    It seems your computer is experiencing blue screen errors due to corrupted files. To further diagnose and fix the issue, we'll take a closer look at the scan details and use advanced tools. If the previous SFC command didn't work, we'll use a tool called DISM to fix any issues with the core system files. This involves checking the current status of the system, scanning for corruption, and then attempting to repair any problems.

    Open Command Prompt as an administrator. Run the following commands one by one:

    DISM /Online /Cleanup-Image /CheckHealth




DISM /Online /Cleanup-Image /ScanHealth




DISM /Online /Cleanup-Image /RestoreHealth

    This scan may take a while, so please wait patiently. After the system image repair, please restart your PC to ensure any repairs or changes made by the DISM tool are properly applied.

    After restarting, open Command Prompt as an administrator again and run the following command: 

    sfc /scannow

    Once you run sfc /scannow again after the DISM commands, if it successfully repairs the corrupted files, restart your PC to apply these repairs.

    If this does not fix the issue. A log file from the initial scan contains important information about the corrupted files. Feel free to share the log file so I can help analyze it.

    Was this answer helpful?

    0 comments