Hello,
I am having irregular BSODs if and only if I have sent my PC to standby and am resuming from it.
If I remember correctly, these BSODs come with different error codes.
I have run the V2 log collector, the output is attached to this post.
Thank you very much in advance for helping me resolve the issue.
Hi Nox997,
Please change the system language on your pc to English as it is difficult for most of us to translate german(?) to english.
Change System UI Language in Windows 10
I haven't worked with a Xeon processor in a long time. Are you certain that all of your software/hardware is fully compatible w/this processor (it's architecture is different from the i series processors)
Gigabyte H97-D3H-CF motherboard UEFI/BIOS dates from 2015. Please visit the Gigabyte support site for your motherboard to ensure that you have downloaded/installed the latest available version
Very few entries in the WER section of the MSINFO32 report. It appears that you reinstalled Windows earlier this month.
Did you have the problem before you reinstalled? Did the problem persist after the reinstall?
Please note these older drivers that were present in the crash dump
I suggest uninstalling the programs associated with the drivers dated from 2015 and earlier
I suggest updating the programs assoicated with the drivers dated from 2016 and later:
You can find most of these with a Google search. More info on them is available at Driver Reference Table (DRT) (search function is just before the table starts)Code:DDCDrv.sys Tue Apr 8 03:50:11 2008 (47FB23B3) lirsgt.sys Sun May 17 09:06:57 2009 (4A100BF1) atksgt.sys Sun May 17 09:36:34 2009 (4A1012E2) vwifibus.sys Tue Feb 14 21:47:58 2012 (4F3B1CDE) WindowsTrustedRTProxy.sys Sat Mar 23 18:43:47 2013 (514E3023) iaStorA.sys Wed Jun 3 05:38:57 2015 (556ECB31) BthA2dp.sys Fri Jun 19 07:17:39 2015 (5583FA53) spvdbus.sys Thu Oct 29 01:59:11 2015 (5631B5AF) spvve.sys Thu Oct 29 01:59:12 2015 (5631B5B0) WMILIB.SYS Thu Apr 27 12:37:17 2017 (59021E3D) RTKVHD64.sys Wed Jun 14 01:58:31 2017 (5940D087) TeeDriverW8x64.sys Tue Jul 18 10:15:12 2017 (596E17F0) IntelHaxm.sys Mon Aug 21 04:19:47 2017 (599A97A3) semav6msr64.sys Mon Jan 22 12:35:46 2018 (5A6620F2) logi_joy_vir_hid.sys Mon Apr 2 21:02:23 2018 (5AC2D29F) VBoxNetLwf.sys Thu Nov 8 14:35:01 2018 (5BE48FE5) VBoxUSBMon.sys Thu Nov 8 14:35:01 2018 (5BE48FE5) VBoxDrv.sys Thu Nov 8 14:35:38 2018 (5BE4900A) logi_core_temp.sys Fri Nov 16 03:23:07 2018 (5BEE7E6B) logi_joy_bus_enum.sys Tue Nov 20 10:28:21 2018 (5BF42815) logi_joy_xlcore.sys Tue Nov 20 10:28:25 2018 (5BF42819)
Most of the Intel drivers can be located at the motherboard manufacturer's website.
Ensure that Windows is set to update drivers also: Enable or Disable Driver Updates in Windows Update in Windows 10
If none of this helps, please run Driver Verifier according to these instructions: Enable and Disable Driver Verifier in Windows 10
Hello,
thank you for your replies.
@axe0: My Windows display language *is* set to English. My keyboard layout as well as "local" options are set to German however (e.g. how dates are displayed). Maybe that caused the logs to be in German instead of English.
@jdc1:
thank you for your hints!
- I am certain my soft- and hardware is fully compatible with this processor.
- The BIOS is the most recent one that can be obtained for my mainboard.
- I have updated to Windows 10 1903 rather recently, maybe that is the reason for the few entries in WER section of MSINFO32? Otherwise, my OS is *pretty* old (maybe first install date around 2011). It was already running on a completely different PC.
- I will try to remove the older drivers and see if the problem persists.
Best,
Nox
Reason I suggested it, is because since I personally can't read your logs, there is only 1 dump and you say there are multiple crashes with different errors it is difficult to narrow it down right now.
However, typically with multiple different error codes it rarely is a driver issue so I wouldn't be worried about drivers for now.
Hello,
after I cleaned up several of the old drivers (not all I guess), I tried to get the system to a BSOD again by going to sleep - waking p again and so on.
took me maybe 4 tries, then a BSOD with a different exception happened.
Log is attached.
@axe0: If you assume it is not a driver issue, what might cause it then?
Personally, I think it could be either the graphics card or my screen - the screen sometimes blocks the system (during POST) from booting until I turn the screen off and on again. Not sure if this is due to the screen itself (HDMI) or due to the USB Hub that is built-in.
Thank you very much in advance!
First of all, I would recommend running Driver Verifier to test the system for faulty drivers (Enable and Disable Driver Verifier in Windows 10)
Could you crash the pc a few more times, about 3 times please. I have a hunch of a possible cause, but would like to see more crash dumps.
The last crash occured, because the system tried to access memory which it should not have.
What worries me more, however, is that the address bfff9e8a`1d4e3b28 starts with a b.Code:2: kd> .cxr 0xfffff88bd0516b90 rax=400000000654e000 rbx=ffff9e8a04400290 rcx=0000000000000000 rdx=ffff9e8a1b1adb18 rsi=0000000000000000 rdi=ffff9e8a1b142b18 rip=fffff805516442bd rsp=fffff88bd0517588 rbp=ffff9e8a1b954b18 r8=0000000000000001 r9=bfff9e8a1d4e3b18 r10=ffff9e8a1b142b18 r11=0000000000000000 r12=0000000000000000 r13=ffff9e8a1b946000 r14=0000000000000000 r15=ffff9e8a04a078f0 iopl=0 nv up ei pl zr na po nc cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010246 nt!RtlRbRemoveNode+0x3dd: fffff805`516442bd 410fb64110 movzx eax,byte ptr [r9+10h] ds:002b:bfff9e8a`1d4e3b28=?? 2: kd> !pte bfff9e8a`1d4e3b28 VA bfff9e8a1d4e3b28 PXE at FFFFD86C361B09E8 PPE at FFFFD86C3613D140 PDE at FFFFD86C27A28750 PTE at FFFFD84F450EA718 Unable to get PXE FFFFD86C361B09E8 WARNING: noncanonical VA, accesses will fault !
This may mean nothing to you, but in kernel mode memory addresses start with ffff8. This is called a bit flip and is often a result of a faulty CPU which inadvertently flipped a bit.
Code:2: kd> .formats bfff9e8a1d4e3b18 Evaluate expression: Hex: bfff9e8a`1d4e3b18 Decimal: -4611793177369756904 Octal: 1377774750503523435430 Binary: 10111111 11111111 10011110 10001010 00011101 01001110 00111011 00011000 Chars: .....N;. Time: ***** Invalid FILETIME Float: low 2.72944e-021 high -1.99703 Double: -1.97621 2: kd> .formats ffff9e8a1b142b18 Evaluate expression: Hex: ffff9e8a`1b142b18 Decimal: -107158979728616 Octal: 1777774750503305025430 Binary: 11111111 11111111 10011110 10001010 00011011 00010100 00101011 00011000 Chars: ......+. Time: ***** Invalid FILETIME Float: low 1.22562e-022 high -1.#QNAN Double: -1.#QNAN
Although my initial suspicion was the CPU what I posted earlier, I'd like you to run a memory test first.
Please run the below-referenced memory test.
Run MemTest86+ to analyse your RAM. MemTest86+ - Test RAM - Windows 10 Forums
Note
MemTest86+ needs to be run for at least 8 complete passes for conclusive results. Set it running before you go to bed and leave it overnight. We're looking for zero errors here. Even a single error will indicate RAM failure.
Make a photo of the result and post it.
Addition:
If errors show up you can stop the test, remove all sticks but 1 and test this single stick in each slot for 8 passes or until errors show, switch sticks and repeat.
If errors show up and you see them a lot later, no problem, the errors don't affect the test.
Quote