Question Several different BSOD while refurbing system

Jul 1, 2022
2
0
10
0
Hi all, long time lurker here finally posting for some direct help!

I'm refurbishing an old system of mine I'd given to a friend that has been returned since they'd had start up issues and attempted to diagnose it themselves. The idea is it'll be good to use for gaming by someone else. The specs are as follows:
Asus P8Z77-V LX
i5 3570k
8GB Corsair Vengeance 1600 MHz RAM
NVidia GTX 960
2 x SSDs (~100Gb and 500Gb)
Windows 10 64 bit

After cleaning it out, reseating components, wiping drives and reinstalling Windows etc I've had several different BSOD. Initially it was very unstable and a BSOD would occur within a minute or two of booting into Windows; these were typically IP_MISALIGNED or SYSTEM_SERVICE_EXCEPTION errors associated with GenuineIntel.sys in the associated dump files. I resolved these by cleaning out what was likely a bad Avira Antivirus installation and managing to update the chipset drivers in the short window between booting and a BSOD (This was a pain; Safe Mode was perfectly stable I couldn't install said drivers in this state). The system is now more stable, but BSODs still occur; these are typically CLOCK_WATCHDOG_TIMEOUT exceptions and are rarer (have occurred while downloading a game on Steam, and have occurred while playing said game after a couple of hours of doing browsing/work).

I've attached the contents of the latest two dump logs below. For some reason I can't include two spoilers so apologies for the two logs in one spoiler, I've separated them as best I can:

The system is currently not being overclocked.

-----------------------------------------
FIRST DUMP LOG

Response Time (ms) Location
Deferred srv*
Symbol search path is: srv*
Executable search path is:
Windows 10 Kernel Version 19041 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Edition build lab: 19041.1.amd64fre.vb_release.191206-1406
Machine Name:
Kernel base = 0xfffff8026d400000 PsLoadedModuleList = 0xfffff8026e02a2b0
Debug session time: Fri Jul 1 15:08:30.089 2022 (UTC + 8:00)
System Uptime: 0 days 0:00:11.750
Loading Kernel Symbols
...............................................................
................................................................
............................................................
Loading User Symbols
Loading unloaded module list
.......
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff8026d7f7dd0 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:fffff181ea916440=0000000000000139
0: kd> !analyze -v
***
  • *
  • Bugcheck Analysis *
  • *
***

KERNEL_SECURITY_CHECK_FAILURE (139)
A kernel component has corrupted a critical data structure. The corruption
could potentially allow a malicious user to gain control of this machine.
Arguments:
Arg1: 0000000000000000, A stack-based buffer has been overrun.
Arg2: 0000000000000000, Address of the trap frame for the exception that caused the BugCheck
Arg3: 0000000000000000, Address of the exception record for the exception that caused the BugCheck
Arg4: fffff181ea916bf0, Reserved

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

*** WARNING: Unable to verify checksum for win32k.sys

KEY_VALUES_STRING: 1

Key : Analysis.CPU.mSec
Value: 3640

Key : Analysis.DebugAnalysisManager
Value: Create

Key : Analysis.Elapsed.mSec
Value: 10218

Key : Analysis.Init.CPU.mSec
Value: 984

Key : Analysis.Init.Elapsed.mSec
Value: 27015

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

Key : Bugcheck.Code.DumpHeader
Value: 0x139

Key : Bugcheck.Code.Register
Value: 0x139

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


FILE_IN_CAB: 070122-4484-01.dmp

BUGCHECK_CODE: 139

BUGCHECK_P1: 0

BUGCHECK_P2: 0

BUGCHECK_P3: 0

BUGCHECK_P4: fffff181ea916bf0

TRAP_FRAME: 0000000000000000 -- (.trap 0x0)

EXCEPTION_RECORD: 0000000000000000 -- (.exr 0x0)
Cannot read Exception record @ 0000000000000000

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: WerFault.exe

STACK_TEXT:
fffff181ea916438 fffff8026d80090b : 0000000000000139 0000000000000000 0000000000000000 0000000000000000 : nt!KeBugCheckEx
fffff181ea916440 fffff8026d800c92 : fffff8026d8008f0 0000000000000000 0000000000000000 0000000000000000 : nt!guard_icall_handler+0x1b
fffff181ea916470 fffff8026d6dd7b7 : fffff181ea9169e0 0000000000000000 fffff181ea916bf0 fffff8026d80098c : nt!RtlpExecuteHandlerForException+0x12
fffff181ea9164a0 fffff8026d6dc3b6 : fffff181ea9173b8 fffff181ea9170f0 fffff181ea9173b8 fffff8026da7e3d0 : nt!RtlDispatchException+0x297
fffff181ea916bc0 fffff8026d809eac : ffff000000000000 0000000000000000 0000000000000000 0000000000000000 : nt!KiDispatchException+0x186
fffff181ea917280 fffff8026d805be0 : 0000001a02000000 fffff181ffff0012 ffffffff80001f24 ffffffff80001f20 : nt!KiExceptionDispatch+0x12c
fffff181ea917460 fffff8026d80098c : fffff8026da7fc76 0000000000000000 ffffd90860220bc0 fffff181ea9176a1 : nt!KiGeneralProtectionFault+0x320
fffff181ea9175f8 fffff8026da7fc76 : 0000000000000000 ffffd90860220bc0 fffff181ea9176a1 ffffd9085914a6a0 : nt!guard_dispatch_icall+0x1c
fffff181ea917600 fffff8026da7cc83 : 0000000000000000 ffffd908604a9dc0 0000000000000001 fffff18100000000 : nt!_PnpGetObjectProperty+0x13a
fffff181ea9176d0 fffff8026da7c88b : 898184932270fa3b 0000000000120089 00000000000000b1 0000000000000000 : nt!PiCMGetObjectProperty+0x187
fffff181ea9177f0 fffff8026da7c7f3 : fffff181ea917938 0000000000000003 000000000000024c fffff8026da16b6e : nt!PiCMHandleIoctl+0x7b
fffff181ea917830 fffff8026dad2c5a : 0000000000000000 fffff8026dad2bf0 0000000000000000 fffff8026d6538ba : nt!PiCMFastIoDeviceDispatch+0x53
fffff181ea917880 fffff8026da0e5b8 : 000000000000024c 0000000000000000 0000000000000000 ffff8981849322a0 : nt!PiDaFastIoDispatch+0x6a
fffff181ea9178e0 fffff8026da0de76 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : nt!IopXxxControlFile+0x728
fffff181ea917a20 fffff8026d8097b8 : fffff181ea917b18 0000000000000000 ffff89817b7455c0 0000000000000004 : nt!NtDeviceIoControlFile+0x56
fffff181ea917a90 00007ff83c22ce24 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : nt!KiSystemServiceCopyEnd+0x28
00000034da7fc458 0000000000000000 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : 0x00007ff83c22ce24


SYMBOL_NAME: nt!guard_icall_handler+1b

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

IMAGE_VERSION: 10.0.19041.1766

STACK_COMMAND: .cxr; .ecxr ; kb

BUCKET_ID_FUNC_OFFSET: 1b

FAILURE_BUCKET_ID: 0x139_0_LEGACY_GS_VIOLATION_nt!guard_icall_handler

OS_VERSION: 10.0.19041.1

BUILDLAB_STR: vb_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {9ac18088-8c91-40fd-01fb-5255bc467cba}

Followup: MachineOwner


------------------------------------------------------------------

SECOND DUMP LOG


Response Time (ms) Location
Deferred srv*
Symbol search path is: srv*
Executable search path is:
Unable to load image Unknown_Module_00000000
00000000, Win32 error 0n2
*** WARNING: Unable to verify timestamp for Unknown_Module_0000000000000000
*** ERROR: Module load completed but symbols could not be loaded for Unknown_Module_00000000
00000000
Unable to add module at 0000000000000000
WARNING: .reload failed, module list may be incomplete
Debugger can not determine kernel base address
Windows 10 Kernel Version 19041 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Machine Name:
Kernel base = 0xfffff805
26c00000 PsLoadedModuleList = 0xfffff8052782a2b0
Debug session time: Fri Jul 1 15:07:48.128 2022 (UTC + 8:00)
System Uptime: 4 days 19:55:21.343
Unable to load image Unknown_Module_00000000
00000000, Win32 error 0n2
*** WARNING: Unable to verify timestamp for Unknown_Module_0000000000000000
*** ERROR: Module load completed but symbols could not be loaded for Unknown_Module_00000000
00000000
Unable to add module at 0000000000000000
WARNING: .reload failed, module list may be incomplete
Debugger can not determine kernel base address
Loading Kernel Symbols
.Unable to load image Unknown_Module_00000000
00000000, Win32 error 0n2
*** WARNING: Unable to verify timestamp for Unknown_Module_0000000000000000
*** ERROR: Module load completed but symbols could not be loaded for Unknown_Module_00000000
00000000
Unable to add module at 0000000000000000

Loading User Symbols
Loading unloaded module list
.....................
For analysis of this file, run !analyze -v
fffff805
26ff7dd0 ?? ???
2: kd> !analyze -v
***
  • *
  • Bugcheck Analysis *
  • *
***

CLOCK_WATCHDOG_TIMEOUT (101)
An expected clock interrupt was not received on a secondary processor in an
MP system within the allocated interval. This indicates that the specified
processor is hung and not processing interrupts.
Arguments:
Arg1: 0000000000000030, Clock interrupt time out interval in nominal clock ticks.
Arg2: 0000000000000000, 0.
Arg3: ffff938063680180, The PRCB address of the hung processor.
Arg4: 0000000000000001, The index of the hung processor.

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

* Debugger could not find nt in module list, module list might be corrupt, error 0x80070057.


KEY_VALUES_STRING: 1

Key : Analysis.CPU.mSec
Value: 15

Key : Analysis.DebugAnalysisManager
Value: Create

Key : Analysis.Elapsed.mSec
Value: 20

Key : Analysis.Init.CPU.mSec
Value: 140

Key : Analysis.Init.Elapsed.mSec
Value: 9471

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

Key : Bugcheck.Code.DumpHeader
Value: 0x101

Key : Bugcheck.Code.Register
Value: 0x101

Key : WER.CorruptModuleList
Value: 1


FILE_IN_CAB: 070122-4593-01.dmp

BUGCHECK_CODE: 101

BUGCHECK_P1: 30

BUGCHECK_P2: 0

BUGCHECK_P3: ffff938063680180

BUGCHECK_P4: 1

CUSTOMER_CRASH_COUNT: 1

STACK_TEXT:
ffff938063788c88 fffff80527036f60 : 0000000000000101 0000000000000030 0000000000000000 ffff938063680180 : 0xfffff80526ff7dd0
ffff9380
63788c90 0000000000000101 : 0000000000000030 0000000000000000 ffff938063680180 0000000000000001 : 0xfffff80527036f60
ffff938063788c98 0000000000000030 : 0000000000000000 ffff938063680180 0000000000000001 0000000000000000 : 0x101
ffff938063788ca0 0000000000000000 : ffff938063680180 0000000000000001 0000000000000000 ffffffffffffff00 : 0x30


SYMBOL_NAME: ANALYSIS_INCONCLUSIVE

MODULE_NAME: Unknown_Module

IMAGE_NAME: Unknown_Image

STACK_COMMAND: .cxr; .ecxr ; kb

FAILURE_BUCKET_ID: CORRUPT_MODULELIST_CLOCK_WATCHDOG_TIMEOUT

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {505a7e83-2b57-2f1c-5666-16c4a774a5e4}

Followup: MachineOwner

In parallel with this, I'm also trying to resolve an issue with the display. The monitor is of a similar age to the system and will not recognise an input while the system boots up. It works perfectly fine, however, if I use a different monitor to boot and log in, and then switch back to the old monitor. This appears to be an issue exclusive to the graphics card as when the monitor is plugged into the motherboard there is no issue. I'll be looking for the latest graphics drivers to see if this fixes it.

Thanks in advance for any help or advice offered!
 

Lutfij

Titan
Moderator
Welcome to the forums, newcomer!

Where did you source the installer for the OS that's installed on the platform? As for your specs, the make and model of the PSU doesn't come up in dump files, neither the age of the unit. Might want to include them. Make and model of your SSD's?

likely a bad Avira Antivirus installation
If you're on Windows 10 and beyond, Windows Defender is more than plenty, provided you practice healthy browsing habits and don't allow unwanted/suspicious app's installing themselves onto your platform.
 
Jul 1, 2022
2
0
10
0
Welcome to the forums, newcomer!

Where did you source the installer for the OS that's installed on the platform? As for your specs, the make and model of the PSU doesn't come up in dump files, neither the age of the unit. Might want to include them. Make and model of your SSD's?

likely a bad Avira Antivirus installation
If you're on Windows 10 and beyond, Windows Defender is more than plenty, provided you practice healthy browsing habits and don't allow unwanted/suspicious app's installing themselves onto your platform.
Thank you!

The OS was sourced from the Microsoft website via the media creation tool.

The PSU is an OCZ ModXStream Pro 600W power supply around the same age as the rest of the hardware (~2014). The SSDs are a Samsung Evo 860 (500Gb) and an 850 (120Gb).

Regarding Windows Defender, yes it's good these days but old habits die hard! Regardless, I'll not be adding any other third part antivirus to this system in future.
 

ASK THE COMMUNITY

TRENDING THREADS