BSOD Issues for the Past Couple of Days - Windows 10 - Version 21H2

solkiske said:

I've run diagnostics on all of my drives and found that one my storage drives had bad blocks so I disconnected it from my system, still crashing though. I ran a system file check, no integrity issues. I ran extensive diagnostics on my RAM and found one module was faulty so I removed it, still crashing. Neither my GPU nor my CPU have been showing symptoms of being faulty so it seems to be a driver issue but I don't know which one it might be.

do you have raid enabled in the bios even tho its not being used?

ubuysa said:

I apologise, I was looking at the wrong data collection file! You do have only one RAM module installed.

But this is your 1st April dump though?

Code:

Microsoft (R) Windows Debugger Version 10.0.20348.1 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [DESKTOP-CVJ9NOT-(2023-04-01_10-08-42)(1).zip\Crash Dumps\040123-6171-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available


************* Path validation summary **************
Response                         Time (ms)     Location
Deferred                                       SRV*C:\SymCache*https://msdl.microsoft.com/download/symbols
Symbol search path is: SRV*C:\SymCache*https://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 10 Kernel Version 19041 MP (12 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Machine Name:
Kernel base = 0xfffff805`2a400000 PsLoadedModuleList = 0xfffff805`2b02a310
Debug session time: Sat Apr  1 16:44:31.346 2023 (UTC + 3:00)
System Uptime: 0 days 1:05:08.993

That dump definitely has calls to nvlddmkm.sys in the call stack....

Code:

fffffc03`22e649b0  00000000`00000000
fffffc03`22e649b8  00000000`00000000
fffffc03`22e649c0  ffffcc8e`d91ec0a0
fffffc03`22e649c8  fffff805`44daa5fb nvlddmkm+0xca5fb
fffffc03`22e649d0  ffffcc8e`d91ec0a0
fffffc03`22e649d8  fffff805`44daa5fb nvlddmkm+0xca5fb
fffffc03`22e649e0  00000000`00000000
fffffc03`22e649e8  025000a0`00000000
fffffc03`22e649f0  00000000`00000000
fffffc03`22e649f8  fffff805`44e48d24 nvlddmkm+0x168d24
fffffc03`22e64a00  ffffcc8e`d91ec0a0
fffffc03`22e64a08  00000000`4d52564e
fffffc03`22e64a10  00000000`000000a0
fffffc03`22e64a18  00000000`00000527
fffffc03`22e64a20  00000000`00000002
fffffc03`22e64a28  ffffcc8e`e1544510
fffffc03`22e64a30  00000000`00000000
fffffc03`22e64a38  ffffcc8e`d834e200
fffffc03`22e64a40  ffffcc8e`d2010100
fffffc03`22e64a48  fffff805`2a68f072 nt!ExFreeHeapPool+0x362
fffffc03`22e64a50  ffffcc8e`d2010340
fffffc03`22e64a58  fffff805`44e490ff nvlddmkm+0x1690ff
fffffc03`22e64a60  00000000`00000000
fffffc03`22e64a68  fffff805`00000000
fffffc03`22e64a70  ffffcc8e`d91ec0a0
fffffc03`22e64a78  fffffc03`22e64b10
fffffc03`22e64a80  00000000`00000000
fffffc03`22e64a88  00000000`00000020
fffffc03`22e64a90  00000000`00000103
fffffc03`22e64a98  00000000`00000000
fffffc03`22e64aa0  00000000`00000000
fffffc03`22e64aa8  ffffcc8e`d91ec0a0
fffffc03`22e64ab0  00000000`000000a4
fffffc03`22e64ab8  00000000`00000000
fffffc03`22e64ac0  ffffcc8e`d91ec0a0
fffffc03`22e64ac8  fffff805`44e48ef8 nvlddmkm+0x168ef8
fffffc03`22e64ad0  00000000`00000103
fffffc03`22e64ad8  00000000`00000000
fffffc03`22e64ae0  00000000`00000000
fffffc03`22e64ae8  00000000`00000000
fffffc03`22e64af0  00000000`00040293
fffffc03`22e64af8  fffff805`2a6a07fb nt!KeQueryCurrentStackInformationEx+0x8b
fffffc03`22e64b00  ffffcc8e`e1a95000
fffffc03`22e64b08  fffff805`2a693239 nt!RtlpHpLfhSlotAllocate+0x179

Have you ever had an Nvidia graphics card installed?

Yes, I have only ever had one card installed in my system and it's an Nvidia GPU.

- - - Updated - - -

tomdsr said:

do you have raid enabled in the bios even tho its not being used?

No.

solkiske said:

I've run diagnostics on all of my drives and found that one my storage drives had bad blocks so I disconnected it from my system, still crashing though. I ran a system file check, no integrity issues. I ran extensive diagnostics on my RAM and found one module was faulty so I removed it, still crashing. Neither my GPU nor my CPU have been showing symptoms of being faulty so it seems to be a driver issue but I don't know which one it might be.

When available please post images or share links displaying test results.

Post a new V2 share link into the newest post

I updated my GPU's driver to the latest version about a week or so ago and didn't have any issues. Ran the computer for 3 consecutive days while running tests on my drives without a single crash. Until the past 24 hours where my PC has crashed 3 times including a hard-lock where I had to manually restart the computer.



DESKTOP-CVJ9NOT-(2023-04-13_04-13-41).zip

These errors may be significant. If you're running out of space on the system drive you might see all sorts of problems...

Code:

Event[5287]:
  Log Name: System
  Source: Microsoft-Windows-WER-SystemErrorReporting
  Date: 2023-04-12T23:16:45.0130000Z
  Event ID: 1018
  Task: N/A
  Level: Information
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: DESKTOP-CVJ9NOT
  Description: 
The dump file at location: C:\WINDOWS\MEMORY.DMP was deleted because the disk volume had less than 25 GB free space.

Event[5432]:
  Log Name: System
  Source: Microsoft-Windows-WER-SystemErrorReporting
  Date: 2023-04-13T03:51:52.7400000Z
  Event ID: 1018
  Task: N/A
  Level: Information
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: DESKTOP-CVJ9NOT
  Description: 
The dump file at location: C:\WINDOWS\MEMORY.DMP was deleted because the disk volume had less than 25 GB free space.

So you're saying that a lack of space on my OS drive could be the problem?

solkiske said:

So you're saying that a lack of space on my OS drive could be the problem?

A lack of space on the system drive can lead to problems, but I'm not saying that this IS your problem. It's certainly something you don't want to see. I would strongly suggest moving anything that doesn't absolutely need to be on the OS drive to somewhere else if you can. If that drive is the 1TB 970 EVO then there will be a ton of stuff on there that doesn't need to be.

BTW: SSDs wear out much faster when they are very full, because the internal 'wear levelling' algorithm has fewer spare cells to work with.

ubuysa said:

A lack of space on the system drive can lead to problems, but I'm not saying that this IS your problem. It's certainly something you don't want to see. I would strongly suggest moving anything that doesn't absolutely need to be on the OS drive to somewhere else if you can. If that drive is the 1TB 970 EVO then there will be a ton of stuff on there that doesn't need to be.

BTW: SSDs wear out much faster when they are very full, because the internal 'wear levelling' algorithm has fewer spare cells to work with.

I've run tests on my OS drive and it passed all of them. The drive you're referencing was the drive that I disconnected a couple of weeks ago after testing it a finding that it had back blocks.

solkiske said:

I've run tests on my OS drive and it passed all of them. The drive you're referencing was the drive that I disconnected a couple of weeks ago after testing it a finding that it had back blocks.

Ah. Fair enough.

I think I'm going to leave you with @zbook for now, having two different people trying to help in different directions isn't helpful I think. I'll keep an eye on this thread though.