New Machine Constantly Having BSOD

T

TehFamine

Hello!


I have a new pre-built machine that has the following hardware:

  • AMD Ryzen 5 3600 6-core Processor @ 3593 MHz
  • 16 GB of Thermaltake ram (RGB)
  • Gigabyte GeForce RTX 3060 Ti OC 8GB
  • B450 AORUS PRO WIFI (rev. 1.x) motherboard
  • Thermaltake Water 3.0 360 ARGB cooler


Long story short. I bought the pre-built as parts are scarce right now. I've done a number of things from updating the bios, updating the drivers, doing full scans, memory testing, you name it to find out what is going on. I've disabled devices such as the onboard wifi, tried various drivers such as the driver recommended by Gigabyte and the one by NVIDA. All still crashing.


Crash errors are all over the board from Kernal issues and IRQL issues to today, APC INDEX MISMATCHES. Chrome for example crashes due to errors and causes BSOD among other programs like last night, DirectX 10 caused it.


I've analyzed the core dumps. I'm not really seeing much of the process impacted, not really what specific device is causing the issues. My best guess is either faulty memory or faulty GPU. Memory tests seem to be okies, but last nights test never completed. It froze.


1c3afdee-40e5-416c-af68-c7ca16af4230?upload=true.png


Analyzing MEMORY.DMP


Microsoft (R) Windows Debugger Version 10.0.19041.685 X86​

Copyright (c) Microsoft Corporation. All rights reserved.​





Loading Dump File [C:\Windows\MEMORY.DMP]​

Kernel Bitmap Dump File: Kernel address space is available, User address space may not be available.​



Symbol search path is: srv*​

Executable search path is:​

Windows 10 Kernel Version 19041 MP (12 procs) Free x64​

Product: WinNt, suite: TerminalServer SingleUserTS Personal​

Built by: 19041.1.amd64fre.vb_release.191206-1406​

Machine Name:​

Kernel base = 0xfffff805`49000000 PsLoadedModuleList = 0xfffff805`49c2a390​

Debug session time: Thu Feb 18 10:34:59.046 2021 (UTC - 5:00)​

System Uptime: 0 days 0:50:09.671​

Loading Kernel Symbols​

...............................................................​

..Page 4039d2 not present in the dump file. Type ".hh dbgerr004" for details​

..............................................................​

......................................................​

Loading User Symbols​

PEB is paged out (Peb.Ldr = 0000009e`608e0018). Type ".hh dbgerr001" for details​

Loading unloaded module list​

..........​

For analysis of this file, run !analyze -v​

10: kd> !analyze -v​

*******************************************************************************​

* *​

* Bugcheck Analysis *​

* *​

*******************************************************************************​



APC_INDEX_MISMATCH (1)​

This is a kernel internal error. The most common reason to see this​

bugcheck is when a filesystem or a driver has a mismatched number of​

calls to disable and re-enable APCs. The key data item is the​

Thread->CombinedApcDisable field. This consists of two separate 16-bit​

fields, the SpecialApcDisable and the KernelApcDisable. A negative value​

of either indicates that a driver has disabled special or normal APCs​

(respectively) without re-enabling them; a positive value indicates that​

a driver has enabled special or normal APCs (respectively) too many times.​

Arguments:​

Arg1: 00007ffa33941064, Address of system call function or worker routine​

Arg2: 0000000000000000, Thread->ApcStateIndex​

Arg3: 000000000000ffff, (Thread->SpecialApcDisable << 16) | Thread->KernelApcDisable​

Arg4: ffffa905e355bb80, Call type (0 - system call, 1 - worker routine)​



Debugging Details:​

------------------​





KEY_VALUES_STRING: 1​



Key : Analysis.CPU.Sec​

Value: 3​



Key : Analysis.DebugAnalysisProvider.CPP​

Value: Create: 8007007e on DESKTOP-7ODGTC3​



Key : Analysis.DebugData​

Value: CreateObject​



Key : Analysis.DebugModel​

Value: CreateObject​



Key : Analysis.Elapsed.Sec​

Value: 3​



Key : Analysis.Memory.CommitPeak.Mb​

Value: 65​



Key : Analysis.System​

Value: CreateObject​





BUGCHECK_CODE: 1​



BUGCHECK_P1: 7ffa33941064​



BUGCHECK_P2: 0​



BUGCHECK_P3: ffff​



BUGCHECK_P4: ffffa905e355bb80​



BLACKBOXBSD: 1 (!blackboxbsd)​





BLACKBOXNTFS: 1 (!blackboxntfs)​





BLACKBOXPNP: 1 (!blackboxpnp)​





BLACKBOXWINLOGON: 1​



PROCESS_NAME: chrome.exe​



STACK_TEXT:​

ffffa905`e355b948 fffff805`49407a69 : 00000000`00000001 00007ffa`33941064 00000000`00000000 00000000`0000ffff : nt!KeBugCheckEx​

ffffa905`e355b950 fffff805`49407933 : 000001d6`e76fe840 00000000`00000200 00000000`00000040 000001d6`ec004700 : nt!KiBugCheckDispatch+0x69​

ffffa905`e355ba90 00007ffa`33941064 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceExitPico+0x1fe​

0000009e`611fec88 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffa`33941064​





SYMBOL_NAME: nt!KiSystemServiceExitPico+1fe​



MODULE_NAME: nt​



IMAGE_NAME: ntkrnlmp.exe​



STACK_COMMAND: .thread ; .cxr ; kb​



BUCKET_ID_FUNC_OFFSET: 1fe​



FAILURE_BUCKET_ID: 0x1_SysCallNum_1001_nt!KiSystemServiceExitPico​



OS_VERSION: 10.0.19041.1​



BUILDLAB_STR: vb_release​



OSPLATFORM_TYPE: x64​



OSNAME: Windows 10​



FAILURE_ID_HASH: {83101497-6ca6-daf7-dce0-7e8a9ba9cbff}​



Followup: MachineOwner​

---------​

Continue reading...
 

Similar threads

M
Replies
0
Views
70
Marko Mäkiranta
M
G
Replies
0
Views
256
Gyorken Mudin
G
P
Replies
0
Views
711
P
Back
Top Bottom