[SOLVED] Any help on this BSOD Windows 10

Nikon187

Distinguished
Jan 12, 2011
38
0
18,530
0
My system is not over heating..
It will reboot 2 or 3 times a day.







Microsoft (R) Windows Debugger Version 10.0.22473.1005 AMD64
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:
Page 20010486b too large to be in the dump file.
Windows 10 Kernel Version 19041 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Edition build lab: 19041.1.amd64fre.vb_release.191206-1406
Machine Name:
Kernel base = 0xfffff8007a000000 PsLoadedModuleList = 0xfffff8007ac2a2d0
Debug session time: Mon Nov 22 12:33:04.902 2021 (UTC - 6:00)
System Uptime: 0 days 0:56:44.582
Loading Kernel Symbols
...............................................................
................................................................
................................................................
...
Loading User Symbols
PEB is paged out (Peb.Ldr = 00000084fe468018). Type ".hh dbgerr001" for details
Loading unloaded module list
..........
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff800
7a3f72a0 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:ffff870d88060e30=0000000000000109
2: kd> !analyze -v
*******************************************************************************
[LIST]
[*]*
[*]Bugcheck Analysis *
[*]*
[/LIST]
*******************************************************************************

CRITICAL_STRUCTURE_CORRUPTION (109)
This BugCheck is generated when the kernel detects that critical kernel code or
data have been corrupted. There are generally three causes for a corruption:
1) A driver has inadvertently or deliberately modified critical kernel code
or data. See [url=http://www.microsoft.com/whdc/driver/kernel/64bitPatching.mspx]http://www.microsoft.com/whdc/driver/kernel/64bitPatching.mspx[/url]
2) A developer attempted to set a normal kernel breakpoint using a kernel
debugger that was not attached when the system was booted. Normal breakpoints,
"bp", can only be set if the debugger is attached at boot time. Hardware
breakpoints, "ba", can be set at any time.
3) A hardware corruption occurred, e.g. failing RAM holding kernel code or data.
Arguments:
Arg1: a39fd65e7cb8d788, Reserved
Arg2: b3b6e2e4cf372040, Reserved
Arg3: fffff8007a2bf736, Failure type dependent information
Arg4: 0000000000000001, Type of corrupted region, can be
0 : A generic data region
1 : Modification of a function or .pdata
2 : A processor IDT
3 : A processor GDT
4 : Type 1 process list corruption
5 : Type 2 process list corruption
6 : Debug routine modification
7 : Critical MSR modification
8 : Object type
9 : A processor IVT
a : Modification of a system service function
b : A generic session data region
c : Modification of a session function or .pdata
d : Modification of an import table
e : Modification of a session import table
f : Ps Win32 callout modification
10 : Debug switch routine modification
11 : IRP allocator modification
12 : Driver call dispatcher modification
13 : IRP completion dispatcher modification
14 : IRP deallocator modification
15 : A processor control register
16 : Critical floating point control register modification
17 : Local APIC modification
18 : Kernel notification callout modification
19 : Loaded module list modification
1a : Type 3 process list corruption
1b : Type 4 process list corruption
1c : Driver object corruption
1d : Executive callback object modification
1e : Modification of module padding
1f : Modification of a protected process
20 : A generic data region
21 : A page hash mismatch
22 : A session page hash mismatch
23 : Load config directory modification
24 : Inverted function table modification
25 : Session configuration modification
26 : An extended processor control register
27 : Type 1 pool corruption
28 : Type 2 pool corruption
29 : Type 3 pool corruption
2a : Type 4 pool corruption
2b : Modification of a function or .pdata
2c : Image integrity corruption
2d : Processor misconfiguration
2e : Type 5 process list corruption
2f : Process shadow corruption
30 : Retpoline code page corruption
101 : General pool corruption
102 : Modification of win32k.sys

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

Page 4f00 not present in the dump file. Type ".hh dbgerr004" for details
Page 4f00 not present in the dump file. Type ".hh dbgerr004" for details

KEY_VALUES_STRING: 1

Key : Analysis.CPU.mSec
Value: 4671

Key : Analysis.DebugAnalysisManager
Value: Create

Key : Analysis.Elapsed.mSec
Value: 6216

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

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

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

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: MEMORY.DMP

BUGCHECK_CODE: 109

BUGCHECK_P1: a39fd65e7cb8d788

BUGCHECK_P2: b3b6e2e4cf372040

BUGCHECK_P3: fffff8007a2bf736

BUGCHECK_P4: 1

MEMORY_CORRUPTOR: ONE_BIT

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

PROCESS_NAME: csrss.exe

STACK_TEXT:
ffff870d
88060e28 0000000000000000 : 0000000000000109 a39fd65e7cb8d788 b3b6e2e4cf372040 fffff800`7a2bf736 : nt!KeBugCheckEx


CHKIMG_EXTENSION: !chkimg -lo 50 -d !nt
fffff8007a131620-fffff8007a131622 3 bytes - nt!_guard_check_icall_fptr
[ 20 80 39:f0 fd 3f ]
fffff8007a131628-fffff8007a131629 2 bytes - nt!_guard_dispatch_icall_fptr (+0x08)
[ 70 2f:40 fe ]
fffff8007a2bf74c - nt!KeReleaseInStackQueuedSpinLock+2c
[ 48:4a ]
Page 4f00 not present in the dump file. Type ".hh dbgerr004" for details
Page 4f00 not present in the dump file. Type ".hh dbgerr004" for details
6 errors : !nt (fffff8007a131620-fffff8007a2bf74c)

SYMBOL_NAME: nt!KeReleaseInStackQueuedSpinLock+16

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

STACK_COMMAND: .cxr; .ecxr ; kb

FAILURE_BUCKET_ID: MEMORY_CORRUPTION_ONE_BIT

OS_VERSION: 10.0.19041.1

BUILDLAB_STR: vb_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {e3faf315-c3d0-81db-819a-6c43d23c63a7}

Followup: MachineOwner

<Moderator Note: Please use the 'spoiler' tags around log listings>
 
Last edited by a moderator:

Colif

Win 11 Master
Moderator
Try running memtest86 on each of your ram sticks, one stick at a time, up to 4 passes. Only error count you want is 0, any higher could be cause of the BSOD. Remove/replace ram sticks with errors. Memtest is created as a bootable USB so that you don’t need windows to run it

Can you follow option one on the following link - here - and then do this step below: Small memory dumps - Have Windows Create a Small Memory Dump (Minidump) on BSOD - that creates a file in c windows/minidump after the next BSOD

  1. Open Windows File Explore
  2. Navigate to C:\Windows\Minidump
  3. Copy the mini-dump files out onto your Desktop
  4. Do not use Winzip, use the built in facility in Windows
  5. Select those files on your Desktop, right click them and choose 'Send to' - Compressed (zipped) folder
  6. Upload the zip file to the Cloud (OneDrive, DropBox . . . etc.)
  7. Then post a link here to the zip file, so we can take a look for you . . .
 

Colif

Win 11 Master
Moderator
Try running memtest86 on each of your ram sticks, one stick at a time, up to 4 passes. Only error count you want is 0, any higher could be cause of the BSOD. Remove/replace ram sticks with errors. Memtest is created as a bootable USB so that you don’t need windows to run it

Can you follow option one on the following link - here - and then do this step below: Small memory dumps - Have Windows Create a Small Memory Dump (Minidump) on BSOD - that creates a file in c windows/minidump after the next BSOD

  1. Open Windows File Explore
  2. Navigate to C:\Windows\Minidump
  3. Copy the mini-dump files out onto your Desktop
  4. Do not use Winzip, use the built in facility in Windows
  5. Select those files on your Desktop, right click them and choose 'Send to' - Compressed (zipped) folder
  6. Upload the zip file to the Cloud (OneDrive, DropBox . . . etc.)
  7. Then post a link here to the zip file, so we can take a look for you . . .
 

ASK THE COMMUNITY

TRENDING THREADS