- Jul 28, 2020
- 2
- 0
- 10
Please bear with me on this one, this has been happening for a long time and I've about reached the end of my rope here. I suffer from depression and this issue is really getting me down, because no matter how hard I try I never seem to get anywhere with it.
So, previously:
I started getting BSOD a couple of weeks ago, they are now getting more and more prominent.
Downloaded WinDBG and had a look through the errors.
HERE you can have a look through some older minidumps, my latest crashes are below.
People seemed to suggest it was a PS4 controller dongle I had inserted into my PC, removed that, seemed to not crash for a while but then it happened again.
Then a couple errors seemed to point towards iCUE.
"WARNING: Unable to verify timestamp for CorsairGamingAudioamd64.sys"
And "iCUE.exe" were being underlined in WinDBG, so I uninstalled and reinstalled iCUE, removed all of it from my registry, removed the Corsair appdata folder and forced firmware updates on all my peripherals.
Crashed. Again.
Then I bit the bullet and reinstalled Windows, got all my drivers updated, installed chipset, audio, graphics drivers etc.
Then, my PC crashed again at 1pm today, I didn't see this error so it must have happened while I was away at my PC.
Then, to make sure my PC was stable after reinstalling my graphics card drivers (for the 4th time using DDU in Safe Mode) then, lo-and-behold.
My latest crash.
Here is my most recent crash report which happened at 5pm today:
What I have tried:
Is this looking to potentially be my motherboard at this point?
Any help will be massively appreciated, thanks.
So, previously:
I started getting BSOD a couple of weeks ago, they are now getting more and more prominent.
Downloaded WinDBG and had a look through the errors.
HERE you can have a look through some older minidumps, my latest crashes are below.
People seemed to suggest it was a PS4 controller dongle I had inserted into my PC, removed that, seemed to not crash for a while but then it happened again.
Then a couple errors seemed to point towards iCUE.
"WARNING: Unable to verify timestamp for CorsairGamingAudioamd64.sys"
And "iCUE.exe" were being underlined in WinDBG, so I uninstalled and reinstalled iCUE, removed all of it from my registry, removed the Corsair appdata folder and forced firmware updates on all my peripherals.
Crashed. Again.
Then I bit the bullet and reinstalled Windows, got all my drivers updated, installed chipset, audio, graphics drivers etc.
Then, my PC crashed again at 1pm today, I didn't see this error so it must have happened while I was away at my PC.
Code:
Microsoft (R) Windows Debugger Version 10.0.19041.1 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Users\scott\Desktop\072820-15500-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: srv*
Executable search path is:
Windows 10 Kernel Version 18362 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 18362.1.amd64fre.19h1_release.190318-1202
Machine Name:
Kernel base = 0xfffff801`10e00000 PsLoadedModuleList = 0xfffff801`11248150
Debug session time: Tue Jul 28 13:13:05.153 2020 (UTC + 1:00)
System Uptime: 0 days 0:06:51.844
Loading Kernel Symbols
...............................................................
................................................................
................................................................
.........
Loading User Symbols
Loading unloaded module list
............
For analysis of this file, run !analyze -v
1: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
This is a very common bugcheck. Usually the exception address pinpoints
the driver/function that caused the problem. Always note this address
as well as the link date of the driver/image that contains this address.
Some common problems are exception code 0x80000003. This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG. This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG. This will let us see why this breakpoint is
happening.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff8012045a872, The address that the exception occurred at
Arg3: ffff918f8434f6e8, Exception Record Address
Arg4: ffff918f8434ef30, Context Record Address
Debugging Details:
------------------
*** WARNING: Unable to verify timestamp for nvhda64v.sys
*** WARNING: Unable to verify timestamp for win32k.sys
KEY_VALUES_STRING: 1
Key : AV.Dereference
Value: NullClassPtr
Key : AV.Fault
Value: Write
Key : Analysis.CPU.Sec
Value: 3
Key : Analysis.DebugAnalysisProvider.CPP
Value: Create: 8007007e on GLADOS
Key : Analysis.DebugData
Value: CreateObject
Key : Analysis.DebugModel
Value: CreateObject
Key : Analysis.Elapsed.Sec
Value: 41
Key : Analysis.Memory.CommitPeak.Mb
Value: 77
Key : Analysis.System
Value: CreateObject
BUGCHECK_CODE: 7e
BUGCHECK_P1: ffffffffc0000005
BUGCHECK_P2: fffff8012045a872
BUGCHECK_P3: ffff918f8434f6e8
BUGCHECK_P4: ffff918f8434ef30
EXCEPTION_RECORD: ffff918f8434f6e8 -- (.exr 0xffff918f8434f6e8)
ExceptionAddress: fffff8012045a872 (nvhda64v+0x000000000002a872)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000001
Parameter[1]: 0000000000000014
Attempt to write to address 0000000000000014
CONTEXT: ffff918f8434ef30 -- (.cxr 0xffff918f8434ef30)
rax=0000000000000000 rbx=ffffa90e830cc3a0 rcx=9db3e1ad2d2d0000
rdx=ffff918f8434eb20 rsi=ffff9403540dc010 rdi=0000000000000000
rip=fffff8012045a872 rsp=ffff918f8434f920 rbp=ffff940355385a70
r8=ffff918f8434e654 r9=0000000000000000 r10=0000000000000007
r11=ffff918f8434f8f0 r12=0000000000000000 r13=fffff8011c9131c0
r14=ffff940355385b30 r15=0000000000000000
iopl=0 nv up ei pl zr na po nc
cs=0010 ss=0000 ds=002b es=002b fs=0053 gs=002b efl=00010246
nvhda64v+0x2a872:
fffff801`2045a872 c7401402000000 mov dword ptr [rax+14h],2 ds:002b:00000000`00000014=????????
Resetting default scope
BLACKBOXBSD: 1 (!blackboxbsd)
BLACKBOXNTFS: 1 (!blackboxntfs)
BLACKBOXPNP: 1 (!blackboxpnp)
BLACKBOXWINLOGON: 1
CUSTOMER_CRASH_COUNT: 1
PROCESS_NAME: System
WRITE_ADDRESS: fffff801113733b8: Unable to get MiVisibleState
Unable to get NonPagedPoolStart
Unable to get NonPagedPoolEnd
Unable to get PagedPoolStart
Unable to get PagedPoolEnd
fffff8011122a3b8: Unable to get Flags value from nt!KdVersionBlock
fffff8011122a3b8: Unable to get Flags value from nt!KdVersionBlock
unable to get nt!MmSpecialPagesInUse
0000000000000014
ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%p referenced memory at 0x%p. The memory could not be %s.
EXCEPTION_CODE_STR: c0000005
EXCEPTION_PARAMETER1: 0000000000000001
EXCEPTION_PARAMETER2: 0000000000000014
EXCEPTION_STR: 0xc0000005
STACK_TEXT:
ffff918f`8434f920 00000000`000000e0 : ffffa90e`830cc3a0 ffff9403`540dc010 00000000`00000000 ffff9403`540dc010 : nvhda64v+0x2a872
ffff918f`8434f928 ffffa90e`830cc3a0 : ffff9403`540dc010 00000000`00000000 ffff9403`540dc010 fffff801`2045a8fe : 0xe0
ffff918f`8434f930 ffff9403`540dc010 : 00000000`00000000 ffff9403`540dc010 fffff801`2045a8fe ffff9403`540dc010 : 0xffffa90e`830cc3a0
ffff918f`8434f938 00000000`00000000 : ffff9403`540dc010 fffff801`2045a8fe ffff9403`540dc010 ffff9403`540dc030 : 0xffff9403`540dc010
SYMBOL_NAME: nvhda64v+2a872
MODULE_NAME: nvhda64v
IMAGE_NAME: nvhda64v.sys
STACK_COMMAND: .cxr 0xffff918f8434ef30 ; kb
BUCKET_ID_FUNC_OFFSET: 2a872
FAILURE_BUCKET_ID: AV_nvhda64v!unknown_function
OS_VERSION: 10.0.18362.1
BUILDLAB_STR: 19h1_release
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
FAILURE_ID_HASH: {c13eb64a-9cde-4879-da51-f7aaf1513c01}
Followup: MachineOwner
---------Then, to make sure my PC was stable after reinstalling my graphics card drivers (for the 4th time using DDU in Safe Mode) then, lo-and-behold.
My latest crash.
Here is my most recent crash report which happened at 5pm today:
Code:
Microsoft (R) Windows Debugger Version 10.0.19041.1 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Users\scott\Desktop\072820-21468-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: srv*
Executable search path is:
Windows 10 Kernel Version 18362 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 18362.1.amd64fre.19h1_release.190318-1202
Machine Name:
Kernel base = 0xfffff806`6c40e000 PsLoadedModuleList = 0xfffff806`6c856150
Debug session time: Tue Jul 28 17:49:21.505 2020 (UTC + 1:00)
System Uptime: 0 days 0:14:40.275
Loading Kernel Symbols
...............................................................
................................................................
................................................................
........
Loading User Symbols
Loading unloaded module list
...........
For analysis of this file, run !analyze -v
0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
UNEXPECTED_KERNEL_MODE_TRAP (7f)
This means a trap occurred in kernel mode, and it's a trap of a kind
that the kernel isn't allowed to have/catch (bound trap) or that
is always instant death (double fault). The first number in the
bugcheck params is the number of the trap (8 = double fault, etc)
Consult an Intel x86 family manual to learn more about what these
traps are. Here is a *portion* of those codes:
If kv shows a taskGate
use .tss on the part before the colon, then kv.
Else if kv shows a trapframe
use .trap on that value
Else
.trap on the appropriate frame will show where the trap was taken
(on x86, this will be the ebp that goes with the procedure KiTrap)
Endif
kb will then show the corrected stack.
Arguments:
Arg1: 0000000000000008, EXCEPTION_DOUBLE_FAULT
Arg2: fffff8066f421e50
Arg3: fffff98f1ca4e000
Arg4: fffff8066cec7227
Debugging Details:
------------------
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
KEY_VALUES_STRING: 1
Key : Analysis.CPU.Sec
Value: 3
Key : Analysis.DebugAnalysisProvider.CPP
Value: Create: 8007007e on GLADOS
Key : Analysis.DebugData
Value: CreateObject
Key : Analysis.DebugModel
Value: CreateObject
Key : Analysis.Elapsed.Sec
Value: 73
Key : Analysis.Memory.CommitPeak.Mb
Value: 77
Key : Analysis.System
Value: CreateObject
BUGCHECK_CODE: 7f
BUGCHECK_P1: 8
BUGCHECK_P2: fffff8066f421e50
BUGCHECK_P3: fffff98f1ca4e000
BUGCHECK_P4: fffff8066cec7227
TRAP_FRAME: fffff8066f421e50 -- (.trap 0xfffff8066f421e50)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=0000000000000001
rdx=fffff98f1ca4e100 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8066cec7227 rsp=fffff98f1ca4e000 rbp=fffff98f1ca4e130
r8=0000000000000000 r9=0000000000000000 r10=fffff8066cec7220
r11=ffff978198689078 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei ng nz na po nc
hal!HalRequestIpi+0x7:
fffff806`6cec7227 4155 push r13
Resetting default scope
BLACKBOXBSD: 1 (!blackboxbsd)
BLACKBOXNTFS: 1 (!blackboxntfs)
BLACKBOXPNP: 1 (!blackboxpnp)
BLACKBOXWINLOGON: 1
CUSTOMER_CRASH_COUNT: 1
PROCESS_NAME: csrss.exe
IRP_ADDRESS: ffffde86b71ee778
STACK_OVERFLOW: Stack Limit: fffff98f1ca4e000. Use (kF) and (!stackusage) to investigate stack usage.
STACK_TEXT:
fffff806`6f421d08 fffff806`6c5e21e9 : 00000000`0000007f 00000000`00000008 fffff806`6f421e50 fffff98f`1ca4e000 : nt!KeBugCheckEx
fffff806`6f421d10 fffff806`6c5dd043 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69
fffff806`6f421e50 fffff806`6cec7227 : 00000000`00000001 fffff98f`1ca4e2f8 00000000`00000004 fffcc78e`52717c04 : nt!KiDoubleFaultAbort+0x2c3
fffff98f`1ca4e000 fffff806`6c424be6 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalRequestIpi+0x7
fffff98f`1ca4e030 fffff806`6c487f7c : 00000000`00000000 00000000`00000000 fffff98f`1ca4e900 00000000`00000000 : nt!KiIpiSendRequest+0x3d6
fffff98f`1ca4e2b0 fffff806`6c529469 : 00000000`00000000 fffff98f`1ca4e930 fffff806`6c877040 ffff976f`435cc8f8 : nt!MiFlushTbList+0x36c
fffff98f`1ca4e400 fffff806`6c4815e2 : fffff806`6c877040 fffff98f`1ca4e930 00000000`00000003 00000000`00000000 : nt!MiDeleteNonPagedPoolTail+0x19
fffff98f`1ca4e430 fffff806`6c481771 : fffff98f`1ca4e930 fffff98f`1ca4e930 00000000`00000000 00000000`00000000 : nt!MiWalkPageTablesRecursively+0x512
fffff98f`1ca4e4f0 fffff806`6c481771 : fffff98f`1ca4e930 fffff98f`1ca4e930 00000000`00000000 00000000`00000000 : nt!MiWalkPageTablesRecursively+0x6a1
fffff98f`1ca4e5b0 fffff806`6c481771 : fffff98f`1ca4e930 fffff98f`0000001a ffff974b`00000000 00000000`0000001a : nt!MiWalkPageTablesRecursively+0x6a1
fffff98f`1ca4e670 fffff806`6c480efc : fffff98f`1ca4e930 00000000`00000000 00000000`00000000 00000000`00000003 : nt!MiWalkPageTablesRecursively+0x6a1
fffff98f`1ca4e730 fffff806`6c4f59aa : fffff98f`1ca4e930 fffff806`00000002 00000000`00000001 00000000`00000001 : nt!MiWalkPageTables+0x36c
fffff98f`1ca4e830 fffff806`6c4f5870 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!MiClearNonPagedPtes+0xe6
fffff98f`1ca4ea30 fffff806`6c4f5696 : 00000000`00000000 fffff98f`1ca4ebd1 ffffde86`9081d100 00000000`00000000 : nt!MmFreePoolMemory+0x1a8
fffff98f`1ca4eac0 fffff806`6c4f562a : ffff0f6c`6183d88f 00000000`00000000 fffff806`6cec8230 00000000`00000000 : nt!RtlpHpEnvFreeVA+0x12
fffff98f`1ca4eaf0 fffff806`6c447287 : 00000000`00000282 fffff806`6c424c00 00000000`00000000 00000000`00000000 : nt!RtlpHpFreeVA+0x3a
fffff98f`1ca4eb30 fffff806`6c444d58 : ffffde86`b9900300 ffffde86`b9900000 ffffde86`9081d100 00000000`00000000 : nt!RtlpHpSegMgrCommit+0x207
fffff98f`1ca4ec20 fffff806`6c44380d : 00000000`00007fff 00000000`00000002 fffff806`00000000 fffff806`00000001 : nt!RtlpHpSegPageRangeCommit+0x124
fffff98f`1ca4ecb0 fffff806`6c44315e : ffffde86`b991e000 00000000`00000180 ffffde86`b99003c0 fffff806`6cdd9368 : nt!RtlpHpSegPageRangeCoalesce+0x22d
fffff98f`1ca4ed30 fffff806`6c441d5e : ffffde86`00000000 00000000`00000a80 00000000`b9900001 00000000`00000000 : nt!RtlpHpSegPageRangeShrink+0x12e
fffff98f`1ca4edc0 fffff806`6c441c20 : 00000000`00000000 00000000`00000180 ffffde86`b991ee80 fffff806`6c6523e8 : nt!RtlpHpSegFree+0x96
fffff98f`1ca4ee00 fffff806`6c74e4d1 : 00000000`000d038f 00000000`20206f49 ffffde86`b991e000 00000000`000009c8 : nt!RtlpHpFreeHeap+0xac
fffff98f`1ca4ee50 fffff806`6c632fa2 : ffffde86`9081d000 fffff98f`1ca4f139 ffffde86`b991ee80 a2e64ead`a2e64ead : nt!ExpFreeHeapSpecialPool+0x221
fffff98f`1ca4eea0 fffff806`6c77d0a9 : fffff98f`1ca4f360 fffff806`6c529469 0a000002`e0de5863 01000000`00100000 : nt!ExFreeHeapPool+0x177532
fffff98f`1ca4efc0 fffff806`6c4bc3fe : 00000000`00004000 fffff806`6c487ee4 00000000`00000000 fffff98f`1ca4f440 : nt!ExFreePool+0x9
fffff98f`1ca4eff0 fffff806`6c4b415d : ffffde86`b71ee7f0 fffff98f`1ca4e000 fffff803`c1fda400 fffff806`6c877040 : nt!IopCompleteRequest+0x8e
fffff98f`1ca4f0e0 fffff806`6c5d46e0 : fffff803`c1620000 00000000`00000000 ffff9781`00000000 fffff806`6c877040 : nt!KiDeliverApc+0x19d
fffff98f`1ca4f1a0 fffff806`6c49b4be : 00000000`00000000 fffff98f`1ca4f4e8 00000000`00000009 fffff806`6c49aa3d : nt!KiApcInterrupt+0x2f0
fffff98f`1ca4f330 fffff806`6c49aa3d : fffff803`c175cb1e fffff806`6c45ed18 fffff98f`00000001 00000000`000001be : nt!RtlpxLookupFunctionTable+0xbe
fffff98f`1ca4f390 fffff806`6c4980fb : 00000000`00000000 fffff98f`1ca4f528 00000000`00000000 00000000`00000000 : nt!RtlpLookupFunctionEntryForStackWalks+0x1ad
fffff98f`1ca4f410 fffff806`6c417e32 : fffff98f`1ca4e000 00000000`00000000 00000000`00000001 fffff806`6cd8952b : nt!RtlpWalkFrameChain+0x25b
fffff98f`1ca4fb00 fffff806`6c417d82 : 00000000`00000002 ffffde86`90e5a6c0 00000000`00000000 00000000`00000005 : nt!RtlWalkFrameChain+0x72
fffff98f`1ca4fb30 fffff806`6cd8952b : ffffde86`90e5a6b0 fffff98f`1ca4fd30 00000000`00000005 fffff806`6c417e32 : nt!RtlCaptureStackBackTrace+0x42
fffff98f`1ca4fb60 fffff806`6cd88328 : fffff98f`1ca4fd00 fffff98f`1ca4fd30 00000000`00000005 00000000`00000000 : nt!ViKeIrqlLogCommon+0x4f
fffff98f`1ca4fb90 fffff803`c175cb1e : fffff98f`1ca4fd00 00000000`00000005 fffff806`6c4aef40 fffff806`6c42b9f4 : nt!VerifierKeLowerIrql+0x38
fffff98f`1ca4fbc0 fffff98f`1ca4fd00 : 00000000`00000005 fffff806`6c4aef40 fffff806`6c42b9f4 ffffde86`90e66d80 : nvlddmkm+0x11cb1e
fffff98f`1ca4fbc8 00000000`00000005 : fffff806`6c4aef40 fffff806`6c42b9f4 ffffde86`90e66d80 fffff803`c175e12b : 0xfffff98f`1ca4fd00
fffff98f`1ca4fbd0 fffff806`6c4aef3f : fffff806`6c42b9f4 ffffde86`90e66d80 fffff803`c175e12b ffffde86`9926ad10 : 0x5
fffff98f`1ca4fbd8 fffff806`6c42b9f4 : ffffde86`90e66d80 fffff803`c175e12b ffffde86`9926ad10 ffffde86`a3eee080 : nt!PsBoostThreadIoEx+0x24f
fffff98f`1ca4fbe0 fffff803`c175e3ba : 00000000`00000000 fffff98f`1ca4fd30 fffff803`c1fcdae0 00000000`00000000 : nt!KeSetPriorityThread+0x144
fffff98f`1ca4fc50 00000000`00000000 : fffff98f`1ca4fd30 fffff803`c1fcdae0 00000000`00000000 fffff98f`1ca4fd90 : nvlddmkm+0x11e3ba
SYMBOL_NAME: nt!KiDoubleFaultAbort+2c3
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
IMAGE_VERSION: 10.0.18362.997
STACK_COMMAND: .thread ; .cxr ; kb
BUCKET_ID_FUNC_OFFSET: 2c3
FAILURE_BUCKET_ID: 0x7f_8_VRF_nt!KiDoubleFaultAbort
OS_VERSION: 10.0.18362.1
BUILDLAB_STR: 19h1_release
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
FAILURE_ID_HASH: {2575f830-7dd8-52d7-e1be-20f8274db764}
Followup: MachineOwner
---------What I have tried:
- Completely removing and installing NVIDIA drivers using DDU in Safe Mode and reinstalling the drivers. I left out the audio drivers, however, as I didn't think I needed them as I don't use HDMI and it's just another driver that could go awry.
- Running memtest 86, no errors after turning off XMP and setting the mHz and voltage manually, so memory now seems fine.
- All windows updates have been installed.
- I checked the health of my HDD's, according to crystaldiskinfo they are all healthy. I have also done all the sfc /scannow and /fixnow and chkdsk on all my HDDs and SSD, etc. No bad sectors detected.
| My PC Specs | : |
|---|---|
| Motherboard | MSI Z97 Gaming 7 |
| Processor | Intel i5-4690K @ 3.5GHz (Stock) |
| RAM | Corsair Vengeance 1600MHz (CMZ8GX3M2A1600C9B) (4x4Gb) |
| Graphics Card | NVIDIA GeForce GTX1070 |
| SSD | Kingston SSD SA1000M8960G 1TB |
| HDD(1) | SAMSUNG HD103SJ 1TB |
| HDD(2) | WDC WD30EZRX-22D8PB0 3TB |
| Power Supply | Corsair HX850i |
| Operating System | Windows 10 Pro (x64) |
Is this looking to potentially be my motherboard at this point?
Any help will be massively appreciated, thanks.
Facebook
Twitter
Instagram