Windows 7 Forums

Welcome to Windows 7 Forums. Our forum is dedicated to helping you find support and solutions for any problems regarding your Windows 7 PC be it Dell, HP, Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.


Windows 7: BSOD of ntoskrnl.exe process with 0x00000109 error

24 Nov 2013   #1
balax85

Windows 8.1 Pro
 
 
BSOD of ntoskrnl.exe process with 0x00000109 error

Hi,
I've a problem with an HP all in one pc. The pc is a Hp TouchSmart 7320 EnergStar. The problem is a BSOD error after about half hour the pc is on. I see the minidump and the process that cause the error is ntoskrnl.exe with 0x00000109 error. The hardware configuration of the pc is this :

4 GB di SDRAM DDR3 a 1333 MHz
Realtek RTL8171EH GbE integrata; Minicard HP Wireless NIC 802.11b/g/n
Intel® Core™ i3 2120 (3,30 GHz, 3 MB di cache, 2 core)Chipset Intel® H61
Windows® 7 Professional autentico 64
Video card integrated on h61 chipset

I attach the file generated by SF Diagnostic Tool.

I updated the hardware driver with the last that i found on the hp site. I tested to stop the ESET NOD32 verson 5. This test has not had good result. The bsod is always present.


My System SpecsSystem Spec
.
28 Nov 2013   #2
Arc

Microsoft Community Contributor Award Recipient

Microsoft Windows 10 Pro Insider Preview 64-bit
 
 

Such PCs are hard to debug.

Can you upload your MSINFO32.nfo file?
  1. Click on the start button
  2. Type "msinfo32" (without quotes) in the search bar of the start menu, click the resulting link. It will open the System Information window.
  3. File>Save. In the "File Name" filed, put "MSINFO32" (without Quote), give the save location to desktop, and click the "save" button.
  4. Give the time for processing, it will save a .nfo file on your desktop.
  5. Zip it, and upload it following the instruction.
My System SpecsSystem Spec
07 Dec 2013   #3
balax85

Windows 8.1 Pro
 
 

Hi Arc, sorry for my late response but i hadn't the pc with the problem with me. I did what do you say me and I attach the file result.
Thanks for the reply.
My System SpecsSystem Spec
.

07 Dec 2013   #4
Arc

Microsoft Community Contributor Award Recipient

Microsoft Windows 10 Pro Insider Preview 64-bit
 
 

Stop 0x109 BSODs may take some time to fix.

Free up the startup. Windows does not need any other program to auto start with it, but the auto start programs often conflicts and causes various problems including BSODs.
  1. Click on the Start button
  2. Type “msconfig (without quotes), click the resulting link. It will open the System Configuration window.
  3. Select the “Startup” tab.
  4. Deselect all items other than the antivirus.
  5. Apply > OK
  6. Accept then restart.
Are you overclocking? As you are getting BSODs, you should stop overclocking and run all the hardware components like CPU, GPU and RAM to their default settings.

Check if the Power Supply Unit (PSU) supplying adequate power to the computer or not.
http://www.extreme.outervision.com/p...ulatorlite.jsp
Also let us know the wattage of the PSU, too.

Test your RAM modules for possible errors.
How to Test and Diagnose RAM Issues with Memtest86+
Run memtest for at least 8 passes, preferably overnight.
If it start showing errors/red lines, stop testing. A single error is enough to determine that something is going bad there.

Stress test the CPU.
Hardware - Stress Test With Prime95

Is the computer hot? Report us the heat of the computer after a couple of hours of your normal usage. Upload a screenshot of the summery tab of Speccy. Alternatively, you can publish a Speccy snapshot too: Speccy - Publish Snapshot of your System Specs .

Update the Intel HD Graphics Driver, either from our forum link, Latest Intel HD Graphics Driver for Windows 7, or You may get it from Intel Download Center.
Moreover, you may run the Intel (R) Driver Update Utility to auto detect the appropriate driver for your computer.

Let us know the results. We will decide the further steps seeing the situation.
_____________________________________________________________________________________
Code:
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 109, {a3a039d895f3565f, b3b7465ee8719409, fffff80000b96bb0, 6}

*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Probably caused by : ntoskrnl.exe ( nt_fffff80000b95000+1bb0 )

Followup: MachineOwner
---------

2: 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 http://www.microsoft.com/whdc/driver/kernel/64bitPatching.mspx
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: a3a039d895f3565f, Reserved
Arg2: b3b7465ee8719409, Reserved
Arg3: fffff80000b96bb0, Failure type dependent information
Arg4: 0000000000000006, 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:
------------------


FAULTING_IP: 
nt_fffff80000b95000+1bb0
fffff800`00b96bb0 48895c2408      mov     qword ptr [rsp+8],rbx

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

BUGCHECK_STR:  0x109

PROCESS_NAME:  System

CURRENT_IRQL:  0

STACK_TEXT:  
fffff880`035bd498 00000000`00000000 : 00000000`00000109 a3a039d8`95f3565f b3b7465e`e8719409 fffff800`00b96bb0 : nt!KeBugCheckEx


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt_fffff80000b95000+1bb0
fffff800`00b96bb0 48895c2408      mov     qword ptr [rsp+8],rbx

SYMBOL_NAME:  nt_fffff80000b95000+1bb0

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt_fffff80000b95000

IMAGE_NAME:  ntoskrnl.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  5149a99c

FAILURE_BUCKET_ID:  X64_0x109_6_nt_fffff80000b95000+1bb0

BUCKET_ID:  X64_0x109_6_nt_fffff80000b95000+1bb0

Followup: MachineOwner
---------
My System SpecsSystem Spec
Reply

 BSOD of ntoskrnl.exe process with 0x00000109 error




Thread Tools Search this Thread
Search this Thread:

Advanced Search




Similar help and support threads
Thread Forum
Daily BSOD, error 0x00000109
I've been struggling with two different BSODs - a memory_management issue I fixed after running memtest86+ (one of my two 4 GB modules was corrupted) and then there is the remaining ntoskrnl.exe bug check code 0X00000109. I understand this to be a CRITICAL_STRUCTURE_CORRUPTION. Unfortunately, this...
BSOD Help and Support
Repeated BSOD errors with ntoskrnl.exe and STOP: 0x00000109
Hello, For the last several days, I have repeatedly gotten multiple BSOD errors with ntoskrnl.exe and STOP: 0x00000109. It's been like that ever since my computer got infected with some viruses from a malicious website/download--Delta Search virus, I believe (which I was able to eliminate all of...
BSOD Help and Support
Random BSOD - error 0x00000109
Hello, I'm trying to figure out why this laptop randomly blue screens... thought it was drive but ran chkdsk and defrag with no issues... checked memory with memtest - let it do 3 passes, no errors... stumped now
BSOD Help and Support
BSOD while doing nothing, error 0x00000109
Hi guys I had my computer for about 2 years now and have been getting BSOD several times in the last month and a half.I get the blue screen simply when my computer is on and not running any specific programs. The dump file reads:...
BSOD Help and Support
BSOD error 0x00000109
For about the past week, I've been getting this blue screen within about 30-40 minutes of turning my computer on. Works fine in safe mode, but on a normal boot it's consistently crashing with this same error every time. I've attempted to follow various other threads of users who had similar issues,...
BSOD Help and Support
BSOD (randomly) error 0x00000109
Hello folks, My system has been randomly BSOD-ing, but usually when idle. Temperatures seem to be stable. The event log says: The computer has rebooted from a bugcheck. The bugcheck was: 0x00000109 (0xa3a039d89ddab4f8, 0xb3b7465ef05883ee, 0xfffff800035c3510, 0x0000000000000000). A dump...
BSOD Help and Support


Our Sites

Site Links

About Us

Find Us

Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd

All times are GMT -5. The time now is 20:11.

Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App