Windows 8 and 8.1 Forums

New computer, BSOD 0x00000109

  1. #1

    Posts : 3
    Windows 8.1

    New computer, BSOD 0x00000109

    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!

      My System SpecsSystem Spec

  2. #2

    Posts : 2,097
    Windows 8.1 Industry Pro B-)

    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 :-
    1: kd> !analyze -v
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    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 Kernel patch protection for x64-based operating systems
    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.
    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 : 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
    Debugging Details:
    PG_MISMATCH:  1000
    fffff803`04a5c268 4053            push    rbx
    BUGCHECK_STR:  0x109
    PROCESS_NAME:  System
    ANALYSIS_VERSION: 6.3.9600.17237 (debuggers(dbg).140716-0327) amd64fre
    ffffd001`249ef258 00000000`00000000 : 00000000`00000109 a3a01f59`340264f9 b3b72bdf`867fa77c fffff803`04a5c268 : nt!KeBugCheckEx
    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
    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 :-
    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:
    Dism /Online /Cleanup-Image /ScanHealth
    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:
    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 ^_^
      My System SpecsSystem Spec

  3. #3

    Posts : 3
    Windows 8.1

    No component store corruption detected.
    No component store corruption detected.
    sfc /scannow
    Verification 100% complete.

    Windows Resource Protection did not find any integrity violations.
      My System SpecsSystem Spec

  4. #4

    Posts : 3
    Windows 8.1

    Attached is the debug log from the kernel debugger's report on MEMORY.DMP
      My System SpecsSystem Spec

  5. #5

    Posts : 2,097
    Windows 8.1 Industry Pro B-)

    Quote Originally Posted by encip View Post
    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.
      My System SpecsSystem Spec

New computer, BSOD 0x00000109
Related Threads
New Computer Please help BSOD in BSOD Crashes and Debugging
I just bought new laptop, but few days later i have BSOD, the error is "DRIVER_POWER_STATE_FAILURE" .
BSOD - Computer sleeps - computer crashes in BSOD Crashes and Debugging
Have a dell xps 12, a few days ago, I was having some serious wireless communication issues and after several reboots, it stopped, but from that point forward when it tried to sleep it crashed. I had previously installed then turned off netgears parental controls (and have since removed). Get...
BSOD when computer not in use in BSOD Crashes and Debugging
The crashes usually occur when the computer is not in use. I will move the mouse and either the screen will come to life... or the computer has crashed. I updated NVIDEA drivers end of July and thought I fixed it. But apparently not.
Solved BSOD while normally using the computer in BSOD Crashes and Debugging
Hi, About 2 - 3 weeks ago, I've got a lot of bluescreens, and with the help of a member here, I've solved it by removing my USB wireless adapter and connecting to my router by using an Ethernet cable, this reduced the amount of them, I think that I only got one after that. In the last sunday,...
New computer gets BSoD too often in BSOD Crashes and Debugging
I got this computer 5 days ago and I get BSoD so often and I don't know why. Every time, the error is DRIVER_POWER_STATE_FAILURE with a value of 0000009f. Pretty sure it has happened 8-9 times overall. Sometimes I'm in a game, sometimes I'm installing something but most of the time I'm not...
BSOD on new computer. in BSOD Crashes and Debugging
Hi Recently got a new computer. I get BSOD just randomly, it doesnt seem to happen while playing games, they only crash. When i get the BSOD the sounds also get stuck, if you know what i mean. The error messages ive gotten so far: NTFS_File_System Page_fault_in_nonpaged_area...
Windows 8 keeps getting 0x00000109 blue screen in BSOD Crashes and Debugging
Hi, I have had a problem lately since installing windows 8 my machine gives me random blue screens, rarely I get watchdog blue screen and lately I have been getting 0x00000109 almost every day, even when the computer is sleeping. The wired thing is when I use the machine play a game etc the...
Eight Forums Android App Eight Forums IOS App Follow us on Facebook