Question Need Help Debugging Crash Dump With WinDBG

The_Gen_Eric

Reputable
Aug 23, 2016
56
0
4,530
0
I recently bluescreened (System_Service_Exception blaming ntoskrnl and nvlddmkm) immediately after another, potentially unrelated bluescreen (Reference_By_Pointer, which blames ntoskrnl and occurred after closing out of Yakuza 0 using Alt + F4), and I'd just like some help looking into these debug files to see what was at fault.

***
  • *
  • Bugcheck Analysis *
  • *
***

SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: fffff800705f128e, Address of the instruction which caused the bugcheck
Arg3: ffff8608ec9c5df0, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.

Debugging Details:
------------------


KEY_VALUES_STRING: 1

Key : Analysis.CPU.Sec
Value: 6

Key : Analysis.DebugAnalysisProvider.CPP
Value: Create: 8007007e on DESKTOP-TESBBSR

Key : Analysis.DebugData
Value: CreateObject

Key : Analysis.DebugModel
Value: CreateObject

Key : Analysis.Elapsed.Sec
Value: 19

Key : Analysis.Memory.CommitPeak.Mb
Value: 70

Key : Analysis.System
Value: CreateObject


ADDITIONAL_XML: 1

BUGCHECK_CODE: 3b

BUGCHECK_P1: c0000005

BUGCHECK_P2: fffff800705f128e

BUGCHECK_P3: ffff8608ec9c5df0

BUGCHECK_P4: 0

CONTEXT: ffff8608ec9c5df0 -- (.cxr 0xffff8608ec9c5df0)
rax=01d5e7cb7d714cc4 rbx=ffffa40bf74fd400 rcx=ffff9080916bcb80
rdx=0000000000000d48 rsi=0000000000000000 rdi=01d5e7cb7d714cc4
rip=fffff800705f128e rsp=ffff8608ec9c67e0 rbp=0000000000000d48
r8=01d5e7cb7d7117a4 r9=ffff9080916bcb80 r10=0000fffff800705e
r11=ffff8608ec9c6a18 r12=ffff8608ec9c6918 r13=0000000000000000
r14=0000000000000000 r15=ffffa40c0b391080
iopl=0 nv up ei pl nz na pe nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00050202
nt!ObpReferenceObjectByHandleWithTag+0xfe:
fffff800705f128e 488b08 mov rcx,qword ptr [rax] ds:002b:01d5e7cb7d714cc4=????????????????
Resetting default scope

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: nvcontainer.exe

STACK_TEXT:
ffff8608ec9c67e0 fffff800705f117e : ffffa40bf75b9080 0000000000000000 ffffa40bf74fd400 ffffa40c00000001 : nt!ObpReferenceObjectByHandleWithTag+0xfe
ffff8608ec9c6870 fffff8007003aa01 : 0000000000000001 ffffcb806c186180 0000000000000000 0000000000000000 : nt!ObReferenceObjectByHandle+0x2e
ffff8608ec9c68c0 fffff800705e8ae2 : 0000000000000d48 ffff860800000000 ffffa40c00000000 0000000000000000 : nt!IopReferenceFileObject+0x31
ffff8608ec9c6900 fffff800705e8966 : a40c08fde5304aab 0000000000000d44 0000000000000000 0000000000000000 : nt!IopXxxControlFile+0x162
ffff8608ec9c6a20 fffff800701d2e18 : 0000000000000001 0000000000000001 0000000000000000 ffff8608ec9c6a00 : nt!NtDeviceIoControlFile+0x56
ffff8608ec9c6a90 00007ffa1761c1a4 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : nt!KiSystemServiceCopyEnd+0x28
000000196d1ff658 0000000000000000 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : 0x00007ffa1761c1a4


SYMBOL_NAME: nt!ObpReferenceObjectByHandleWithTag+fe

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

IMAGE_VERSION: 10.0.18362.657

STACK_COMMAND: .cxr 0xffff8608ec9c5df0 ; kb

BUCKET_ID_FUNC_OFFSET: fe

FAILURE_BUCKET_ID: 0x3B_c0000005_nt!ObpReferenceObjectByHandleWithTag

OS_VERSION: 10.0.18362.1

BUILDLAB_STR: 19h1_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {3d4819ec-af64-be43-ac98-a6e960db3861}

Followup: MachineOwner
---------[/SPOILER]

[SPOILER="Reference_By_Pointer Dump"]*******************************************************************************
[LIST]
[*]*
[*]Bugcheck Analysis *
[*]*
[/LIST]
*******************************************************************************

REFERENCE_BY_POINTER (18)
Arguments:
Arg1: ffff98863fab02a0, Object type of the object whose reference count is being lowered
Arg2: ffff988662399600, Object whose reference count is being lowered
Arg3: 0000000000000001, Reserved
Arg4: 000000f000000000, Reserved
The reference count of an object is illegal for the current state of the object.
Each time a driver uses a pointer to an object the driver calls a kernel routine
to increment the reference count of the object. When the driver is done with the
pointer the driver calls another kernel routine to decrement the reference count.
Drivers must match calls to the increment and decrement routines. This bugcheck
can occur because an object's reference count goes to zero while there are still
open handles to the object, in which case the fourth parameter indicates the number
of opened handles. It may also occur when the object's reference count drops below zero
whether or not there are open handles to the object, and in that case the fourth parameter
contains the actual value of the pointer references count.

Debugging Details:
------------------


KEY_VALUES_STRING: 1

Key : Analysis.CPU.Sec
Value: 3

Key : Analysis.DebugAnalysisProvider.CPP
Value: Create: 8007007e on DESKTOP-TESBBSR

Key : Analysis.DebugData
Value: CreateObject

Key : Analysis.DebugModel
Value: CreateObject

Key : Analysis.Elapsed.Sec
Value: 5

Key : Analysis.Memory.CommitPeak.Mb
Value: 68

Key : Analysis.System
Value: CreateObject


ADDITIONAL_XML: 1

BUGCHECK_CODE: 18

BUGCHECK_P1: ffff98863fab02a0

BUGCHECK_P2: ffff988662399600

BUGCHECK_P3: 1

BUGCHECK_P4: f000000000

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: Yakuza0.exe

STACK_TEXT:
ffffb484
642ad908 fffff8057bbf759e : 0000000000000018 ffff98863fab02a0 ffff988662399600 0000000000000001 : nt!KeBugCheckEx
ffffb484
642ad910 fffff8057bfec5f7 : 00000000ffff8003 ffff9886623995d0 ffff9886623995d0 ffffcb88d0715dc0 : nt!ObfDereferenceObjectWithTag+0x1bccbe
ffffb484
642ad950 fffff8057bff18ee : 0000000000000b68 ffffb484642adb00 ffffb48400000002 ffffb484642ada00 : nt!ObCloseHandleTableEntry+0x2c7
ffffb484
642ada90 fffff8057bbd2e18 : ffff98865118e080 000000000014f4a8 ffffb484642adb80 fffffffffa0a1f00 : nt!NtClose+0xde
ffffb484
642adb00 00007ff8a99fc2a4 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : nt!KiSystemServiceCopyEnd+0x28
00000000
0014f4e8 0000000000000000 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : 0x00007ff8a99fc2a4


SYMBOL_NAME: nt!ObfDereferenceObjectWithTag+1bccbe

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

IMAGE_VERSION: 10.0.18362.657

STACK_COMMAND: .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET: 1bccbe

FAILURE_BUCKET_ID: 0x18_CORRUPT_REF_COUNT_nt!ObfDereferenceObjectWithTag

OS_VERSION: 10.0.18362.1

BUILDLAB_STR: 19h1_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {fa6b3516-71cb-1e92-b987-b8bebd3458ac}

Followup: MachineOwner
---------
 

The_Gen_Eric

Reputable
Aug 23, 2016
56
0
4,530
0
It didn't show up in the original post, but here's the Reference By Pointer dump.

***
  • *
  • Bugcheck Analysis *
  • *
***

REFERENCE_BY_POINTER (18)
Arguments:
Arg1: ffff98863fab02a0, Object type of the object whose reference count is being lowered
Arg2: ffff988662399600, Object whose reference count is being lowered
Arg3: 0000000000000001, Reserved
Arg4: 000000f000000000, Reserved
The reference count of an object is illegal for the current state of the object.
Each time a driver uses a pointer to an object the driver calls a kernel routine
to increment the reference count of the object. When the driver is done with the
pointer the driver calls another kernel routine to decrement the reference count.
Drivers must match calls to the increment and decrement routines. This bugcheck
can occur because an object's reference count goes to zero while there are still
open handles to the object, in which case the fourth parameter indicates the number
of opened handles. It may also occur when the object's reference count drops below zero
whether or not there are open handles to the object, and in that case the fourth parameter
contains the actual value of the pointer references count.

Debugging Details:
------------------


KEY_VALUES_STRING: 1

Key : Analysis.CPU.Sec
Value: 3

Key : Analysis.DebugAnalysisProvider.CPP
Value: Create: 8007007e on DESKTOP-TESBBSR

Key : Analysis.DebugData
Value: CreateObject

Key : Analysis.DebugModel
Value: CreateObject

Key : Analysis.Elapsed.Sec
Value: 5

Key : Analysis.Memory.CommitPeak.Mb
Value: 68

Key : Analysis.System
Value: CreateObject


ADDITIONAL_XML: 1

BUGCHECK_CODE: 18

BUGCHECK_P1: ffff98863fab02a0

BUGCHECK_P2: ffff988662399600

BUGCHECK_P3: 1

BUGCHECK_P4: f000000000

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: Yakuza0.exe

STACK_TEXT:
ffffb484642ad908 fffff8057bbf759e : 0000000000000018 ffff98863fab02a0 ffff988662399600 0000000000000001 : nt!KeBugCheckEx
ffffb484642ad910 fffff8057bfec5f7 : 00000000ffff8003 ffff9886623995d0 ffff9886623995d0 ffffcb88d0715dc0 : nt!ObfDereferenceObjectWithTag+0x1bccbe
ffffb484642ad950 fffff8057bff18ee : 0000000000000b68 ffffb484642adb00 ffffb48400000002 ffffb484642ada00 : nt!ObCloseHandleTableEntry+0x2c7
ffffb484642ada90 fffff8057bbd2e18 : ffff98865118e080 000000000014f4a8 ffffb484642adb80 fffffffffa0a1f00 : nt!NtClose+0xde
ffffb484642adb00 00007ff8a99fc2a4 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : nt!KiSystemServiceCopyEnd+0x28
000000000014f4e8 0000000000000000 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : 0x00007ff8`a99fc2a4


SYMBOL_NAME: nt!ObfDereferenceObjectWithTag+1bccbe

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

IMAGE_VERSION: 10.0.18362.657

STACK_COMMAND: .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET: 1bccbe

FAILURE_BUCKET_ID: 0x18_CORRUPT_REF_COUNT_nt!ObfDereferenceObjectWithTag

OS_VERSION: 10.0.18362.1

BUILDLAB_STR: 19h1_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {fa6b3516-71cb-1e92-b987-b8bebd3458ac}

Followup: MachineOwner
---------
 

Colif

Win 10 Master
Moderator
it does show in top one, its just at bottom of first.

Don't see reference by pointer often, I think it can be caused by old lan drivers.

Can you follow option one on the following link - here - and then do this step below: Small memory dumps - Have Windows Create a Small Memory Dump (Minidump) on BSOD - that creates a file in c windows/minidump after the next BSOD

copy that file to documents (If you try to upload direct from minidump folder you will get a permissions error)

upload the copy from documents to a file sharing web site, and share the link in your thread so we can help fix the problem

ntoskrnl = windows kernel. It handles all driver requests, power management, and memory management. It sits between Hardware and Applications. It got blamed but its not the cause
 

gardenman

Admirable
Ambassador
Hi, I ran the dump files through the debugger and got the following information: https://thromboticdouche.htmlpasta.com/
File information:022020-9593-01.dmp (Feb 20 2020 - 22:19:06)
Bugcheck:SYSTEM_SERVICE_EXCEPTION (3B)
Probably caused by:memory_corruption (Process: nvcontainer.exe)
Uptime:0 Day(s), 0 Hour(s), 15 Min(s), and 41 Sec(s)

File information:022020-12203-01.dmp (Feb 20 2020 - 22:01:16)
Bugcheck:REFERENCE_BY_POINTER (18)
Probably caused by:memory_corruption (Process: Yakuza0.exe)
Uptime:8 Day(s), 6 Hour(s), 19 Min(s), and 12 Sec(s)

File information:021220-9078-01.dmp (Feb 12 2020 - 14:52:07)
Bugcheck:MEMORY_MANAGEMENT (1A)
Probably caused by:memory_corruption (Process: chrome.exe)
Uptime:0 Day(s), 1 Hour(s), 41 Min(s), and 42 Sec(s)

File information:021220-10375-01.dmp (Feb 12 2020 - 13:08:44)
Bugcheck:SYSTEM_SERVICE_EXCEPTION (3B)
Probably caused by:memory_corruption (Process: Steam.exe)
Uptime:3 Day(s), 21 Hour(s), 39 Min(s), and 48 Sec(s)

File information:101519-7609-01.dmp (Oct 15 2019 - 11:17:51)
Bugcheck:DRIVER_IRQL_NOT_LESS_OR_EQUAL (D1)
Driver warnings:*** WARNING: Unable to verify timestamp for nvlddmkm.sys
Probably caused by:memory_corruption (Process: System)
Uptime:0 Day(s), 8 Hour(s), 52 Min(s), and 45 Sec(s)
Comment: The overclocking driver "RTCore64.sys" was found on your system. (MSI Afterburner)

The nvlddmkm.sys file is a NVIDIA graphics card driver. There are a few things you can do to fix this problem. First off, try a full uninstall using DDU in Safe Mode then re-install the driver (more information). Or try getting the latest version of the driver. Or try one of the 3 most recent drivers released by NVIDIA. Drivers can be found here: http://www.nvidia.com/ or you can allow Windows Update to download the driver for you, which might be a older/better version.

Possible Motherboard page: https://www.msi.com/Motherboard/B450M-PRO-M2
There is a BIOS update available for your system. You are using version 2.9 and the latest is version 2.D. Wait for additional information before deciding to update or not. Important: Verify that I have linked to the correct motherboard. Updating your BIOS can be risky. Never try it when you might lose power (lightning storms, recent power outages, etc).

This information can be used by others to help you. I can't help you with this. Someone else will post with more information. Please wait for additional answers. Good luck.
 

Colif

Win 10 Master
Moderator
2 mention Nvidia, another 2 probably also caused by Nvidia as Desktop Windows Manager involved, and its the interface between windows and GPU, so I would bet all 5 are Nvidia

you have latest version of drivers now, so try an older version or the windows update versions if its an older card.
 

The_Gen_Eric

Reputable
Aug 23, 2016
56
0
4,530
0
Hi, I ran the dump files through the debugger and got the following information: https://thromboticdouche.htmlpasta.com/
File information:022020-9593-01.dmp (Feb 20 2020 - 22:19:06)
Bugcheck:SYSTEM_SERVICE_EXCEPTION (3B)
Probably caused by:memory_corruption (Process: nvcontainer.exe)
Uptime:0 Day(s), 0 Hour(s), 15 Min(s), and 41 Sec(s)

File information:022020-12203-01.dmp (Feb 20 2020 - 22:01:16)
Bugcheck:REFERENCE_BY_POINTER (18)
Probably caused by:memory_corruption (Process: Yakuza0.exe)
Uptime:8 Day(s), 6 Hour(s), 19 Min(s), and 12 Sec(s)

File information:021220-9078-01.dmp (Feb 12 2020 - 14:52:07)
Bugcheck:MEMORY_MANAGEMENT (1A)
Probably caused by:memory_corruption (Process: chrome.exe)
Uptime:0 Day(s), 1 Hour(s), 41 Min(s), and 42 Sec(s)

File information:021220-10375-01.dmp (Feb 12 2020 - 13:08:44)
Bugcheck:SYSTEM_SERVICE_EXCEPTION (3B)
Probably caused by:memory_corruption (Process: Steam.exe)
Uptime:3 Day(s), 21 Hour(s), 39 Min(s), and 48 Sec(s)

File information:101519-7609-01.dmp (Oct 15 2019 - 11:17:51)
Bugcheck:DRIVER_IRQL_NOT_LESS_OR_EQUAL (D1)
Driver warnings:*** WARNING: Unable to verify timestamp for nvlddmkm.sys
Probably caused by:memory_corruption (Process: System)
Uptime:0 Day(s), 8 Hour(s), 52 Min(s), and 45 Sec(s)
Comment: The overclocking driver "RTCore64.sys" was found on your system. (MSI Afterburner)

The nvlddmkm.sys file is a NVIDIA graphics card driver. There are a few things you can do to fix this problem. First off, try a full uninstall using DDU in Safe Mode then re-install the driver (more information). Or try getting the latest version of the driver. Or try one of the 3 most recent drivers released by NVIDIA. Drivers can be found here: http://www.nvidia.com/ or you can allow Windows Update to download the driver for you, which might be a older/better version.

Possible Motherboard page: https://www.msi.com/Motherboard/B450M-PRO-M2
There is a BIOS update available for your system. You are using version 2.9 and the latest is version 2.D. Wait for additional information before deciding to update or not. Important: Verify that I have linked to the correct motherboard. Updating your BIOS can be risky. Never try it when you might lose power (lightning storms, recent power outages, etc).

This information can be used by others to help you. I can't help you with this. Someone else will post with more information. Please wait for additional answers. Good luck.
A few notes, I don't use Afterburner to overclock, only to keep my fans running, since they have a bad habit to rattling when they turn on and off.

As far as the motherboard you linked, that was my old one before I got it replaced, though I still had issues after replacement until I manually updated my Ryzen chipset drivers that got messed with in a Windows update.

This all relates back to Nvlddmkm.sys being blamed, however I will attempt to DDU my driver if my computer goes down again, since one of the recent ones blames nvcontainer.exe.

2 mention Nvidia, another 2 probably also caused by Nvidia as Desktop Windows Manager involved, and its the interface between windows and GPU, so I would bet all 5 are Nvidia

you have latest version of drivers now, so try an older version or the windows update versions if its an older card.
As I said previously, that first Nvidia blame is from old hardware, so I don't know necessarily if that means the other 2 are at Nvidia's fault. However, I feel like you might be right, as the only two things I updated before these issues cropped up again were Windows and Nvidia Drivers. If my computer goes down again, I will attempt to DDU and install drivers from Windows Update, as the card is from back in 2016.
 

Colif

Win 10 Master
Moderator
top error dated 20th Feb blames Nvidia
2nd error dated 20th Feb mentions Desktop Windows Manager. This makes me think its the GPU drivers.
3rd error from 12th Feb is only one I am not sure about
4th error from Feb 12th mentions Desktop Windows Manager. This makes me think its the GPU drivers.
5th is from October and mentions Nvidia again.

I don't know when you swapped but they all follow a theme except the 3rd error. Not all bsod are obvious.
 

gardenman

Admirable
Ambassador
I ran the new dump files through the debugger and got the following information: https://unthankfulboard.htmlpasta.com/

File information:030620-9687-01.dmp (Mar 6 2020 - 19:28:51)
Bugcheck:KERNEL_SECURITY_CHECK_FAILURE (139)
Probably caused by:memory_corruption (Process: software_reporter_tool.exe)
Uptime:0 Day(s), 0 Hour(s), 02 Min(s), and 42 Sec(s)

File information:030620-19531-01.dmp (Mar 6 2020 - 13:42:07)
Bugcheck:PAGE_FAULT_IN_NONPAGED_AREA (50)
Probably caused by:memory_corruption (Process: PersistentWindows.exe)
Uptime:14 Day(s), 15 Hour(s), 22 Min(s), and 18 Sec(s)

This information can be used by others to help you. I can't help you with this. Someone else will post with more information. Please wait for additional answers. Good luck.
 

The_Gen_Eric

Reputable
Aug 23, 2016
56
0
4,530
0
I ran the new dump files through the debugger and got the following information: https://unthankfulboard.htmlpasta.com/

File information:030620-9687-01.dmp (Mar 6 2020 - 19:28:51)
Bugcheck:KERNEL_SECURITY_CHECK_FAILURE (139)
Probably caused by:memory_corruption (Process: software_reporter_tool.exe)
Uptime:0 Day(s), 0 Hour(s), 02 Min(s), and 42 Sec(s)

File information:030620-19531-01.dmp (Mar 6 2020 - 13:42:07)
Bugcheck:PAGE_FAULT_IN_NONPAGED_AREA (50)
Probably caused by:memory_corruption (Process: PersistentWindows.exe)
Uptime:14 Day(s), 15 Hour(s), 22 Min(s), and 18 Sec(s)

This information can be used by others to help you. I can't help you with this. Someone else will post with more information. Please wait for additional answers. Good luck.
Thanks for the help anyway; given that it seems to be a common thread throughout these crashes, is it possible my memory's just defective, since it keeps throwing memory_corruption at different processes?
 

Colif

Win 10 Master
Moderator
top one was a USB device
Perhaps the Occulus?
Is the logitech software for a keyboard?
Scarlet crush can cause BSOD. Its commonly used with software for PS3/PS4 controllers.

2nd one i have seen 3 times today (or similar) and I was looking for the Nvidia drivers until I read you had just run DDU... and that makes me go hmmm... I can't blame the drivers if they aren't installed... (I wish I had seen yours first so I didn't jump to wrong conclusions) . So although this action involved both WIndows desktop manager & Direct Composition, I should just ignore both of those are GPU related

Memory corruption doesn't mean its a memory problem. Often it is just corrupted drivers.
 

The_Gen_Eric

Reputable
Aug 23, 2016
56
0
4,530
0
top one was a USB device
Perhaps the Occulus?
Is the logitech software for a keyboard?
Scarlet crush can cause BSOD. Its commonly used with software for PS3/PS4 controllers.

2nd one i have seen 3 times today (or similar) and I was looking for the Nvidia drivers until I read you had just run DDU... and that makes me go hmmm... I can't blame the drivers if they aren't installed... (I wish I had seen yours first so I didn't jump to wrong conclusions) . So although this action involved both WIndows desktop manager & Direct Composition, I should just ignore both of those are GPU related

Memory corruption doesn't mean its a memory problem. Often it is just corrupted drivers.
i'll list off the devices I have in USB, but I don't know how much any could be causing;
-logitech mouse
-saitek keyboard
-wireless adapter
-portable hard drive
-bluetooth adapter

The interesting thing is that if you run the second one through WhoCrashed, it specifically tells you that there's no driver to blame, and evidently the first can't be identified through WinDBG.
 

Colif

Win 10 Master
Moderator
I almost asked if you had an USB hdd. Dump 1 looks like it could be a data transfer
all the transactions are on the USBXHCI which is the USB extensible Host controller. Last one before error was Bulk_TransferData

if drive is attached. maybe run chkdsk on it.

wish I had an answer for number 2, finding that you didn't have nvidia drivers installed al all has made me rethink what it all means. Thats twice in 2 days I have had to question if I know anything :)
 

The_Gen_Eric

Reputable
Aug 23, 2016
56
0
4,530
0
I almost asked if you had an USB hdd. Dump 1 looks like it could be a data transfer
all the transactions are on the USBXHCI which is the USB extensible Host controller. Last one before error was Bulk_TransferData

if drive is attached. maybe run chkdsk on it.

wish I had an answer for number 2, finding that you didn't have nvidia drivers installed al all has made me rethink what it all means. Thats twice in 2 days I have had to question if I know anything :)
I ran chkdsk on all three of my drives (internal ssd, internal hdd, external hdd) and got nothing back. however, while in safe mode I checked my ssd and it said problems were found and that I needed to boot out of safemode to run the cleanup, but when I did and re-ran, it said everything was clean. additionally, both sfc and dism come out clean. is this because ssd's are made of volatile memory that's liable to shift around?
 

Colif

Win 10 Master
Moderator

The_Gen_Eric

Reputable
Aug 23, 2016
56
0
4,530
0
That's still something I need to check (I'm a bit busy, my bad lol), but I did get another random one today after a good streak of no crashes; https://drive.google.com/file/d/1Sfgto_lRa8z9ZKms42WOvs1JDCXmq-Bj/view?usp=sharing

I apologize for resurrecting this thread so many times, but this almost seems anomalous; I feel I should ask again, is it possible that my memory has an issue? This dump comes back with the faulting program being DiscordPTB
 

gardenman

Admirable
Ambassador
I ran the dump file through the debugger and got the following information: https://fleshierpiranha.htmlpasta.com/

File information:032120-15312-01.dmp (Mar 21 2020 - 02:16:57)
Bugcheck:PAGE_FAULT_IN_NONPAGED_AREA (50)
Probably caused by:memory_corruption (Process: DiscordPTB.exe)
Uptime:1 Day(s), 4 Hour(s), 08 Min(s), and 11 Sec(s)

This information can be used by others to help you. I can't help you with this. Someone else will post with more information. Please wait for additional answers. Good luck.
 

Colif

Win 10 Master
Moderator
is that just discord or a special version? https://portapps.io/app/discord-ptb-portable/

part of me wants to blame Nvidia again. I am going to have to work out if something I see on some BSOD reports actually means anything.

have a look at the 2nd post in here, follow precautions as it can cause boot loops (tell me if it does). Its part of windows so it should be safer than that -- https://forums.tomshardware.com/threads/handy-details-to-include-in-blue-screen-of-death-posts.3468965/ - it tests drivers and should reveal any bad ones if you have them.
 

gardenman

Admirable
Ambassador
I ran the dump file through the debugger and got the following information: https://importantmatter.htmlpasta.com/

File information:032120-13687-01.dmp (Mar 21 2020 - 13:54:39)
Bugcheck:DRIVER_VERIFIER_DETECTED_VIOLATION (C4)
Probably caused by:memory_corruption (Process: System)
Uptime:0 Day(s), 0 Hour(s), 00 Min(s), and 08 Sec(s)

This information can be used by others to help you. I can't help you with this. Someone else will post with more information. Please wait for additional answers. Good luck.
 

Colif

Win 10 Master
Moderator
i would fix the logitech driver and see if that is all you need to fix.

if you get more bsod, run dv again. I really wish it wouldn't cause those boot loops. Makes me sad and a villian for making you run it.

tired of dumps not actually showing the driver name. You know its logitech but it doesn't mention it in the dump.

if I suggested this already, I am blind (as I looked) - Try running memtest86 on each of your ram sticks, one stick at a time, up to 4 passes. Only error count you want is 0, any higher could be cause of the BSOD. Remove/replace ram sticks with errors.
 

The_Gen_Eric

Reputable
Aug 23, 2016
56
0
4,530
0
Two quick remarks -- yeah, I noticed that the actual dump itself didn't list Logitech as an issue, and no worries, Windows 10 seems to get you out of a boot loop fairly quickly once it fails to launch twice.

In addition, I have tried memtest86, but I've been warned that DDR4 RAM has a high possibility of false-positives because of the way bit-flipping works in DDR4. Needless to say, when I ran I did encounter errors, but I would almost venture to say too many showed up for how seemingly infrequently my computer crashes,

I'll go through all the drivers and figure out which I need to reinstall, though, hopefully that can lead to some sort of resolution.
 

Colif

Win 10 Master
Moderator
In addition, I have tried memtest86, but I've been warned that DDR4 RAM has a high possibility of false-positives because of the way bit-flipping works in DDR4. Needless to say, when I ran I did encounter errors, but I would almost venture to say too many showed up for how seemingly infrequently my computer crashes,
there are 2 versions of memtest86
memtest86 works with UEFI or BIOS and has worked with >4GB memory since 2002, 15 years ago.

memtest86+ does not work with UEFI unless you set it to "Legacy Boot" BIOS mode and then has a known issue with test #7 generating false positives with DDR4.
https://forums.tomshardware.com/threads/memtest-vs-memtest.2932378/

I believe you mean the other one :)

If you are getting errors, I would remove ram. Its possible the parts of ram which are corrupted may only be used at certain times, and so you can run fine most of the time. Win 10 uses ram in different ways to previous versions.
 

ASK THE COMMUNITY

TRENDING THREADS