Hi Dyari,
I did the following fixes you suggested but still get BSOD crashes and did the memtest86 for 13 passes and got no errors.
Would a bios update potentially fix the issue, I know my bios is not up to date.
Thanks,
Matthew
This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
Built a new PC about 2 weeks ago and have been getting blue screens and/or crashes of google chrome and games fairly frequently. The blue screens error messages aren't always for the same error. And blue screens can happen randomly, sometimes overnight when computer is in sleep mode. The most recent Blue Screen happened when I did a fresh install of display driver and did a 3d Mark timespy benchmark. The benchmark went fine, but when I closed the application that is when the blue screen happened. Another one happened same day, when I was just doing work (using Toonboom Harmony 20 an animation program) and computer froze and crashed.
My system information is:
OS Name: Microsoft Windows 10 Home
Version: 10.0.19045 Build 19045
Processor: AMD Ryzen 9 7900X 12-Core Processor, 4701 Mhz, 12 Core(s), 24 Logical Processor(s)
BIOS Version/Date: American Megatrends Inc. 0603, 2022-09-08
BaseBoard Manufacturer: ASUSTeK COMPUTER INC.
BaseBoard Product: TUF GAMING X670E-PLUS WIFI
BaseBoard Version: Rev 1.xx
Installed Physical Memory (RAM): 32.0 GB (Corsair Vengeance @ 5600mhz)
Total Physical Memory: 31.7 GB
Graphics card: EVGA 3080ti FTW3 ultra
This is the latest MEMORY.DMP from most recent blue screen.
Microsoft (R) Windows Debugger Version 10.0.25200.1003 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\MEMORY.DMP]
Kernel Bitmap Dump File: Kernel address space is available, User address space may not be available.
************* Path validation summary **************
Response Time (ms) Location
Deferred srv*
Symbol search path is: srv*
Executable search path is:
Windows 10 Kernel Version 19041 MP (24 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Edition build lab: 19041.1.amd64fre.vb_release.191206-1406
Machine Name:
Kernel base = 0xfffff805`32000000 PsLoadedModuleList = 0xfffff805`32c2a290
Debug session time: Thu Dec 22 14:01:06.034 2022 (UTC - 5:00)
System Uptime: 0 days 0:10:43.647
Loading Kernel Symbols
...............................................................
.....Page 2146 not present in the dump file. Type ".hh dbgerr004" for details
...........................................................
................................................................
....................
Loading User Symbols
Loading unloaded module list
.............
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff805`323f92a0 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:fffff805`36862ca0=0000000000000139
0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
KERNEL_SECURITY_CHECK_FAILURE (139)
A kernel component has corrupted a critical data structure. The corruption
could potentially allow a malicious user to gain control of this machine.
Arguments:
Arg1: 0000000000000003, A LIST_ENTRY has been corrupted (i.e. double remove).
Arg2: fffff80536862fc0, Address of the trap frame for the exception that caused the BugCheck
Arg3: fffff80536862f18, Address of the exception record for the exception that caused the BugCheck
Arg4: 0000000000000000, Reserved
Debugging Details:
------------------
KEY_VALUES_STRING: 1
Key : Analysis.CPU.mSec
Value: 1655
Key : Analysis.DebugAnalysisManager
Value: Create
Key : Analysis.Elapsed.mSec
Value: 1681
Key : Analysis.IO.Other.Mb
Value: 0
Key : Analysis.IO.Read.Mb
Value: 0
Key : Analysis.IO.Write.Mb
Value: 0
Key : Analysis.Init.CPU.mSec
Value: 983
Key : Analysis.Init.Elapsed.mSec
Value: 2883
Key : Analysis.Memory.CommitPeak.Mb
Value: 96
Key : Bugcheck.Code.DumpHeader
Value: 0x139
Key : Bugcheck.Code.KiBugCheckData
Value: 0x139
Key : Bugcheck.Code.Register
Value: 0x139
Key : FailFast.Name
Value: CORRUPT_LIST_ENTRY
Key : FailFast.Type
Value: 3
Key : WER.OS.Branch
Value: vb_release
Key : WER.OS.Timestamp
Value: 2019-12-06T14:06:00Z
Key : WER.OS.Version
Value: 10.0.19041.1
FILE_IN_CAB: MEMORY.DMP
BUGCHECK_CODE: 139
BUGCHECK_P1: 3
BUGCHECK_P2: fffff80536862fc0
BUGCHECK_P3: fffff80536862f18
BUGCHECK_P4: 0
TRAP_FRAME: fffff80536862fc0 -- (.trap 0xfffff80536862fc0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=ffffd2093e949158 rbx=0000000000000000 rcx=0000000000000003
rdx=ffffd20944aab158 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80532418b96 rsp=fffff80536863150 rbp=fffff8052e3fe180
r8=0000000000000102 r9=0000000000000000 r10=0000000000000000
r11=fffff80536863240 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl nz ac pe cy
nt!KiTryUnwaitThread+0x1f5086:
fffff805`32418b96 cd29 int 29h
Resetting default scope
EXCEPTION_RECORD: fffff80536862f18 -- (.exr 0xfffff80536862f18)
ExceptionAddress: fffff80532418b96 (nt!KiTryUnwaitThread+0x00000000001f5086)
ExceptionCode: c0000409 (Security check failure or stack buffer overrun)
ExceptionFlags: 00000001
NumberParameters: 1
Parameter[0]: 0000000000000003
Subcode: 0x3 FAST_FAIL_CORRUPT_LIST_ENTRY
BLACKBOXBSD: 1 (!blackboxbsd)
BLACKBOXNTFS: 1 (!blackboxntfs)
BLACKBOXPNP: 1 (!blackboxpnp)
BLACKBOXWINLOGON: 1
PROCESS_NAME: System
ERROR_CODE: (NTSTATUS) 0xc0000409 - The system detected an overrun of a stack-based buffer in this application. This overrun could potentially allow a malicious user to gain control of this application.
EXCEPTION_CODE_STR: c0000409
EXCEPTION_PARAMETER1: 0000000000000003
EXCEPTION_STR: 0xc0000409
STACK_TEXT:
fffff805`36862c98 fffff805`3240d329 : 00000000`00000139 00000000`00000003 fffff805`36862fc0 fffff805`36862f18 : nt!KeBugCheckEx
fffff805`36862ca0 fffff805`3240d890 : fffff805`2e3fe180 ffffe400`021e5180 00000000`00000246 fffff805`322d0fd2 : nt!KiBugCheckDispatch+0x69
fffff805`36862de0 fffff805`3240b85d : 00000000`00000001 00000000`00000000 00000000`00000002 ffffe400`021e5180 : nt!KiFastFailDispatch+0xd0
fffff805`36862fc0 fffff805`32418b96 : 00000000`00400a02 00000000`00000000 00400a02`00000010 000002e7`0b469aba : nt!KiRaiseSecurityCheckFailure+0x31d
fffff805`36863150 fffff805`3221ce96 : ffffd209`3e949188 fffff805`00000000 ffffd209`3e949250 00000000`00000000 : nt!KiTryUnwaitThread+0x1f5086
fffff805`368631b0 fffff805`3221ca3c : ffffd209`3e949180 00000000`00000002 fffff805`36863498 00000000`00000002 : nt!KiTimerWaitTest+0x1e6
fffff805`36863260 fffff805`32233fcd : 00000000`00000000 fffff805`3227e855 00000000`00140001 00000000`00006001 : nt!KiProcessExpiredTimerList+0xdc
fffff805`36863350 fffff805`323fdb9e : 00000000`00000000 fffff805`2e3fe180 fffff805`32d27a00 ffffd209`46244080 : nt!KiRetireDpcList+0x5dd
fffff805`368635e0 00000000`00000000 : fffff805`36864000 fffff805`3685d000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x9e
SYMBOL_NAME: nt!KiTimerWaitTest+1e6
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
STACK_COMMAND: .cxr; .ecxr ; kb
BUCKET_ID_FUNC_OFFSET: 1e6
FAILURE_BUCKET_ID: 0x139_3_CORRUPT_LIST_ENTRY_KTIMER_LIST_CORRUPTION_nt!KiTimerWaitTest
OS_VERSION: 10.0.19041.1
BUILDLAB_STR: vb_release
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
FAILURE_ID_HASH: {efb56395-a173-53f8-073d-d3c8cfd50e2b}
Followup: MachineOwner
---------
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.
Hi Dyari,
I did the following fixes you suggested but still get BSOD crashes and did the memtest86 for 13 passes and got no errors.
Would a bios update potentially fix the issue, I know my bios is not up to date.
Thanks,
Matthew
Hi Matthew,
Thanks for sharing the minidump files.
The minidump files indicate nvlddmkm.sys file as a cause of the BSOD which is related to the Nvidia Graphics card driver.
If you do have an Nvidia graphics card installed on your computer, try to uninstall its driver completely using this DDU free utility, then download/install the latest graphics card driver or a driver that is compatible with your computer from the manufacturer's official website:
https://www.guru3d.com/files-details/display-dr...
If it did not help, install an older version of the graphics card driver. Sometimes, older versions work more smoothly rather than the latest ones.
Or, you can download GeForce Experience to keep your drivers up to date:
https://www.nvidia.com/en-us/geforce/geforce-ex...
If you are overclocking your PC, try running everything (CPU, GPU, system memory) at their stock speeds. See if the issue is still reproducible. Turn off XMP profile or set it to Auto.
If your computer still encounters BSOD, test the RAM with the free utility MemTest86, then run a full 8 pass scan to test your RAM for physical errors:
https://www.tenforums.com/tutorials/14201-memte...
Please do not hesitate to ask if you need further assistance.
Stay safe
____________________________________________________________
Standard Disclaimer: There are links to non-Microsoft websites. The pages appear to be providing accurate, safe information. Watch out for ads on the sites that may advertise products frequently classified as a PUP (Potentially Unwanted Products). Thoroughly research any product advertised on the sites before you decide to download and install it.
Hi Dyari,
Thanks for replying here is a link to all the minidumps that were on my computer.
Hi Matthew ,
I'm Dyari. Thanks for reaching out. I will be happy to assist you in this regard.
Kindly check C:\Windows\Minidump and copy available minidump files to the desktop then share them via One Drive or Google Drive in order to be analyzed and indicate which file is causing the crash.
Regards,
None of the text posted provides any real info
If you are in the habit of leaving the PC in sleep overnight, that is a seriously bad idea on many levels The system should be shutdown at the end of the day.
You update bios & drivers from the mobo maker, set bios to defaults and Pwr to balanced, and drivers from the vid card maker
Then see how you go