New
#1
Very strange BSOD, once a week with no obvious solutions
Hi
I've seen many BSODs over the years, and I've been able to solve them all until this one..
So a friend of mine has been having BSODs for a few months now, since he bought a new PC for work. And I'm writing here because I recommended the components and the computer shop put it together. I feel a bit responsible.
The thing is that he bought 2 PCs, identical hardware, identical software that's being used for work. One of them gets a BSOD, maybe once a month, sometimes every week.
Typically it's RAM, so he bought a new RAM kit, some G-skill royals, still.. the same issue, random BSOD.
The only thing that's not typical in the PC build, is that he has 2 GPUs (GTX 1070), since he needs like 6 monitors.
I can get the full list of software and hardware later, but the PC has an ASUS Workstation motherboard, intel 9900K CPU, 32G of g-skill ram, samsung 970 pro ssd and the latest windows 10 installed. No games, just a few software installs and browsers.
BSOD stop code: IRQL_NOT_LESS_OR_EQUAL
I asked for the dump file from the last BSOD (Today)
So I will copy some of the outputs from windbg here. I'm sure you have more experience and hopefully can help with this BSOD.
3: 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: ffffd0017dfe0e50
Arg3: ffffbd0e4ba19000
Arg4: fffff80479212842
Debugging Details:
------------------
Page 1a5ad7 not present in the dump file. Type ".hh dbgerr004" for details
KEY_VALUES_STRING: 1
Key : Analysis.CPU.mSec
Value: 1936
Key : Analysis.DebugAnalysisProvider.CPP
Value: Create: 8007007e on DESKTOP-2NIFJTE
Key : Analysis.DebugData
Value: CreateObject
Key : Analysis.DebugModel
Value: CreateObject
Key : Analysis.Elapsed.mSec
Value: 1935
Key : Analysis.Memory.CommitPeak.Mb
Value: 81
Key : Analysis.System
Value: CreateObject
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
ADDITIONAL_XML: 1
OS_BUILD_LAYERS: 1
BUGCHECK_CODE: 7f
BUGCHECK_P1: 8
BUGCHECK_P2: ffffd0017dfe0e50
BUGCHECK_P3: ffffbd0e4ba19000
BUGCHECK_P4: fffff80479212842
TRAP_FRAME: ffffd0017dfe0e50 -- (.trap 0xffffd0017dfe0e50)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=000000000000020e rbx=0000000000000000 rcx=0000000000000001
rdx=000511ac00000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80479212842 rsp=ffffbd0e4ba19000 rbp=ffffbd0e4ba1f470
r8=0000000000000000 r9=0000000000000001 r10=0000000000000000
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up di pl nz na pe nc
nt!KiPageFaultShadow+0x2:
fffff804`79212842 2410 and al,10h
Resetting default scope
BLACKBOXBSD: 1 (!blackboxbsd)
BLACKBOXNTFS: 1 (!blackboxntfs)
BLACKBOXPNP: 1 (!blackboxpnp)
BLACKBOXWINLOGON: 1
PROCESS_NAME: chrome.exe
BAD_STACK_POINTER: ffffbd0e4ba19000
MISALIGNED_IP:
nt!KiPageFaultShadow+2
fffff804`79212842 2410 and al,10h
SYMBOL_NAME: nt!KiDoubleFaultAbort+2c3
IMAGE_NAME: hardware
STACK_COMMAND: .thread ; .cxr ; kb
MODULE_NAME: hardware
FAILURE_BUCKET_ID: IP_MISALIGNED
OS_VERSION: 10.0.19041.1
BUILDLAB_STR: vb_release
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
FAILURE_ID_HASH: {201b0e5d-db2a-63d2-77be-8ce8ff234750}
Followup: MachineOwner
---------
3: kd> .trap 0xffffd0017dfe0e50
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=000000000000020e rbx=0000000000000000 rcx=0000000000000001
rdx=000511ac00000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80479212842 rsp=ffffbd0e4ba19000 rbp=ffffbd0e4ba1f470
r8=0000000000000000 r9=0000000000000001 r10=0000000000000000
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up di pl nz na pe nc
nt!KiPageFaultShadow+0x2:
fffff804`79212842 2410 and al,10h
3: kd> !blackboxbsd
Stream size mismatch (expected = 192, read = 168)
3: kd> !blackboxntfs
NTFS Blackbox Data
0 Slow I/O Timeout Records Found
0 Oplock Break Timeout Records Found
3: kd> !blackboxpnp
PnpActivityId : {00000000-0000-0000-0000-000000000000}
PnpActivityTime : 132457781173217899
PnpEventInformation: 3
PnpEventInProgress : 0
PnpProblemCode : 24
PnpVetoType : 0
DeviceId : SWD\MMDEVAPI\{0.0.0.00000000}.{a279cb63-94ae-4721-b369-4106d1f5e5da}
VetoString :
I will share more details when I have access to the PC.
Thx
- - - Updated - - -
https://docs.microsoft.com/en-us/win...rnel-mode-trap
This says that motherboard might be injured, among other things, not much help.
Quote