Having random BSOD after a few hardware changes (but could not be related)

M

manubesada

Hello everyone. I want to go on to comment on my problem.

I have a 2070 super and decided to buy a 3070. My system, in general, was extremely stable, without major problems.

A couple of weeks ago, I updated windows to its latest version and together, I installed the new gpu. The crashes randomly started to appear (mostly BSOD and idle reboot).

This is what I did:

-clean installation of windows and roll back to 2004.

-change of thermal paste, reinstallation of rams and adjustment of psu cables.

-reinstallation with ddu of video drivers.

-change to stock of rams.

This persisted with the problems and evidently did not solve anything.

-memtest 4 passes (3 times); win on all records, prime 95, occt multiple passes; heaven benchmark and furmark, ALL WITHOUT PROBLEMS.

-temperatures and voltages are within normal parameters.

Although the problems persisted, since I rolled back to 2004, the system went almost 24 hours without crashes until... BSOD (APC MISMATCH, like almost all the previous ones). I have a debug to paste here and everything points to the culprit being the EPIC laucnher but I'm not sure, that's why I ask you.

This is my configuration: -3600xt stock -2x8 ram 3200xmp team group. -3070 zotac -psu seasonic m12II 750w bronze. -asrock b550 gaming velocita. -nvm drive 500gb wd blue. -id cooling 224.

This is the debug:

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: 00007fff16acc034, Address of system call function or worker routine

Arg2: 0000000000000000, Thread->ApcStateIndex

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

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



Debugging Details:

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





KEY_VALUES_STRING: 1



Key : Analysis.CPU.Sec

Value: 1



Key : Analysis.DebugAnalysisProvider.CPP

Value: Create: 8007007e on DESKTOP-6FSP1S8



Key : Analysis.DebugData

Value: CreateObject



Key : Analysis.DebugModel

Value: CreateObject



Key : Analysis.Elapsed.Sec

Value: 12



Key : Analysis.Memory.CommitPeak.Mb

Value: 71



Key : Analysis.System

Value: CreateObject





BUGCHECK_CODE: 1



BUGCHECK_P1: 7fff16acc034



BUGCHECK_P2: 0



BUGCHECK_P3: ffff



BUGCHECK_P4: ffff9003193f7b80



BLACKBOXBSD: 1 (!blackboxbsd)





BLACKBOXNTFS: 1 (!blackboxntfs)





BLACKBOXPNP: 1 (!blackboxpnp)





BLACKBOXWINLOGON: 1



PROCESS_NAME: EpicGamesLauncher.exe



STACK_TEXT:

ffff9003`193f79b8 fffff807`75207769 : 00000000`00000001 00007fff`16acc034 00000000`00000000 00000000`0000ffff : nt!KeBugCheckEx

ffff9003`193f79c0 fffff807`75207633 : 00000000`00000000 ffffe288`ff4d8360 ffff9003`193f7b18 ffffffff`fffe7960 : nt!KiBugCheckDispatch+0x69

ffff9003`193f7b00 00007fff`16acc034 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceExitPico+0x1fe

000000e8`7f10f948 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007fff`16acc034





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_4_nt!KiSystemServiceExitPico



OS_VERSION: 10.0.19041.1



BUILDLAB_STR: vb_release



OSPLATFORM_TYPE: x64



OSNAME: Windows 10



FAILURE_ID_HASH: {52cd694c-15ec-48c3-924a-3539560711db}



Followup: MachineOwner


Continue reading...
 

Similar threads

M
Replies
0
Views
69
Marko Mäkiranta
M
G
Replies
0
Views
255
Gyorken Mudin
G
T
Replies
0
Views
211
TehFamine
T
Back
Top Bottom