New computer, BSOD 0x00000109

encip · Sep 24, 2014

Hey there folks. I was hoping one of you experts could review my logs and point me in the right direction- hardware, driver, etc.

This is a computer I just built, running Windows 8.1, and a couple of days ago I got this single unspecific BSOD - 0x00000109 in ntoskrnl.exe+5d7268. I was just browsing the web, nothing unusual. Mostly, I want to figure out if this is a hardware issue, because it would be a lot easier to return a part now rather than make a warranty claim later.

I ran memtest86+ for ~20 hours and completed 18 passes with no errors.

Doing some research on this error pointed me to a couple of things - possibly STPD driver. I don't think any software I installed contains it. There may be a reference or two to it in the logs because I did install it and remove it as a troubleshooting step, but this was after the BSOD.

Let me know what you think!

blueelvis · Sep 25, 2014

Hi Encip & Welcome to the forums ^_^,

I have analysed your dump files and below has been provided an analysis of the same for informative purposes :-

Code:

1: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
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"]Kernel patch protection for x64-based operating systems[/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: a3a01f59340264f9, Reserved
Arg2: b3b72bdf867fa77c, Reserved
Arg3: fffff80304a5c268, Failure type dependent information
Arg4: 0000000000000001, Type of corrupted region, can be
 0 : A generic data region
 1[U][B] : Modification of a function or .pdata[/B][/U]
 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
Debugging Details:
------------------

PG_MISMATCH:  1000
MEMORY_CORRUPTOR:  STRIDE
FAULTING_IP: 
nt!IopAcquireReleaseDispatcherLock+0
fffff803`04a5c268 4053            push    rbx
CUSTOMER_CRASH_COUNT:  1
DEFAULT_BUCKET_ID:  CODE_CORRUPTION
BUGCHECK_STR:  0x109
PROCESS_NAME:  System
CURRENT_IRQL:  2
ANALYSIS_VERSION: 6.3.9600.17237 (debuggers(dbg).140716-0327) amd64fre
DPC_STACK_BASE:  FFFFD001249F7FB0
STACK_TEXT:  
ffffd001`249ef258 00000000`00000000 : 00000000`00000109 a3a01f59`340264f9 b3b72bdf`867fa77c fffff803`04a5c268 : nt!KeBugCheckEx

STACK_COMMAND:  kb
CHKIMG_EXTENSION: !chkimg -lo 50 -db !nt
3 errors : !nt (fffff80304a5c292-fffff80304a5d8ea)
fffff80304a5c290  c9  33 *d0  48  89  5c  24  20  e8  d3  87  a7  ff  48  83  c4 .3.H.\$ .....H..
...
fffff80304a5cf60  74  07  8b  d6  e8  03  b0  e3  ff  80 *7a  59  00  74  09  48 t.........zY.t.H
...
fffff80304a5d8e0  db  ff  85  c0  78  2b  4c  8b  07  48 *8c  55  d7  b9  04  00 ....x+L..H.U....
MODULE_NAME: memory_corruption
IMAGE_NAME:  memory_corruption
FOLLOWUP_NAME:  memory_corruption
DEBUG_FLR_IMAGE_TIMESTAMP:  0
FAILURE_BUCKET_ID:  MEMORY_CORRUPTION_STRIDE
BUCKET_ID:  MEMORY_CORRUPTION_STRIDE
ANALYSIS_SOURCE:  KM
FAILURE_ID_HASH_STRING:  km:memory_corruption_stride
FAILURE_ID_HASH:  {574dbc1b-92cb-fb09-cb7a-cacc1bb2c511}
Followup: memory_corruption
---------

As we can see from the dump file, the corrupted region is a function so I would firstly ask you to run the DISM and SFC Scannow using this below commands :-

Code:
Then please run the following DISM commands to see if there's any problems with the system (from an elevated (Run as administrator) Command Prompt). Press Enter after each one:

Code:

Code: Dism /Online /Cleanup-Image /ScanHealth

Code:

Code: Dism /Online /Cleanup-Image /CheckHealth

If the problem is fixable, you can use this command to repair it (from an elevated (Run as administrator) Command Prompt). Press Enter after typing it:

Code:

Code: Dism /Online /Cleanup-Image /RestoreHealth

From this article: Repair a Windows Image

You can also run sfc.exe /scannow from an elevated (Run as administrator) Command Prompt to check for further corruption.

If you are still getting errors, could you please upload a ZIPPED copy of the Memory.DMP file which is located at "C:\Windows\Memory.DMP" so that could be analysed?

Let me know how it goes ^_^

encip · Sep 25, 2014

ScanHealth

No component store corruption detected.

CheckHealth

No component store corruption detected.

sfc /scannow

Verification 100% complete.

Windows Resource Protection did not find any integrity violations.

encip · Sep 25, 2014

Attached is the debug log from the kernel debugger's report on MEMORY.DMP

blueelvis · Sep 27, 2014

encip said:
Attached is the debug log from the kernel debugger's report on MEMORY.DMP

Hello Encip ^_^,

Unfortunately, I would be needing the dump file itself which is ZIPPED so that I can analyse it.

New computer, BSOD 0x00000109

encip

New Member

My Computer

System One

blueelvis

OMG Debugger!

My Computer

System One

encip

New Member

My Computer

System One

encip

New Member

My Computer

System One

blueelvis

OMG Debugger!

My Computer

System One