BSOD Address caused by address : ntoskrnl.exe+3f7dd0

Anonymous
2022-07-12T15:29:15+00:00

Facing BSOD Errors frequently. Pasting Details of the last BSOD Error :

Bug Check String : Kernel Security Check Failure

Bug Check Code : 0x00000139

Parameter 1 : 00000000`00000004

Parameter 2 : ffff9b00`de5bc010

Parameter 3 : ffff9b00`de5bbf68

Parameter 4 : 00000000`00000000

Caused by Driver : ntoskrnl.exe

Caused by Address : ntoskrnl.exe+3f7dd0

Had around 7 BSOD's in the last 2 Hours., out of which past 5 are Kernel Security Check Failure. Frustrated by this.

Link for the MiniDumps : This GoogleDrive Link

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

55 answers

Sort by: Oldest
Most helpful Newest Oldest
  1. DaveM121 933.9K Reputation points Independent Advisor
    2022-07-12T16:07:36+00:00

    Hi Rakesh0710

    I am Dave, I will help you with this.

    Your minidump files just indicate memory (RAM) corruption no specific driver is listed

    1

    The best option is to download the widely available free utility MemTest86, then run a full 4 pass scan with that to test your RAM for physical errors

    2

    If no RAM errors are found, to try to force Windows 10 show any faulting drivers, the best option would be to turn on Driver Verifier, let your PC crash 3 times, then you must turn off Driver Verifier, and finally, upload any newly created minidump files

    https://answers.microsoft.com/en-us/windows/for...

    Was this answer helpful?

    0 comments
  2. Anonymous
    2022-07-13T06:02:49+00:00

    Hi Rakesh0710

    I am Dave, I will help you with this.

    Your minidump files just indicate memory (RAM) corruption no specific driver is listed

    1
    The best option is to download the widely available free utility MemTest86, then run a full 4 pass scan with that to test your RAM for physical errors

    2
    If no RAM errors are found, to try to force Windows 10 show any faulting drivers, the best option would be to turn on Driver Verifier, let your PC crash 3 times, then you must turn off Driver Verifier, and finally, upload any newly created minidump files

    https://answers.microsoft.com/en-us/windows/for...

    Thanks for the Reply, Dave.

    1. Ran Windows Memory Diagnostics. It found no error in the RAM.
    2. Used the Driver Verifier. After enabling it, BSOD error was caused 2 times. Here is the Link MiniDump_13072022 .

    Additionally, the Screen gets stuck occassionally while using Windows. After waiting for 15-20 minutes, I have to restart the Windows forcefully.

    Eagerly waiting for your reply, Dave.

    Was this answer helpful?

    0 comments
  3. Anonymous
    2022-07-13T06:26:18+00:00

    Please run the V2 log collector and post a share link into this thread using one drive, drop box, or google drive.

    https://www.tenforums.com/bsod-crashes-debugging/2198-bsod-posting-instructions.html

    https://www.elevenforum.com/t/bsod-posting-instructions.103/

    Was this answer helpful?

    0 comments
  4. Anonymous
    2022-07-13T06:41:42+00:00

    Thanks for your concern. The Log Files from the V2 Log collector are on the Link : V2 Log Collector

    Regards,

    Rakesh0710

    Was this answer helpful?

    0 comments
  5. DaveM121 933.9K Reputation points Independent Advisor
    2022-07-13T07:08:02+00:00

    Hi Rakesh0710

    Sorry, I was offline, those minidump files also just listed memory (RAM) corruption, nothing specific was listed, I also did not see Driver Verifier listed as enabled on those dump files.

    Was this answer helpful?

    0 comments