BSOD 0x109:CRITICAL_STRUCTURE_CORRUPTION

[KindredPhantom]

Hello i am currently experiencing a BSOD, the BSOD's stop error code is 0x00000109: CRITICAL_STRUCTURE_CORRUPTION.
I am running on Windows 7 Home Premium 64bit. I have attached a zip of my crash dumps to this thread.

 

[usasma]

Please start by running these hardware diagnostics:
Memory Diagnostics (read the details at the link)
HD Diagnostic (read the details at the link)

Please start by running these hardware diagnostics:
Memory Diagnostics (read the details at the link)
HD Diagnostic (read the details at the link)

Also, please run one of these free, independent online malware scans to ensure that your current protection hasn't been compromised: Malware (read the details at the link)

Please update these older drivers:

timntr.sys   Thu Dec 28 11:30:38 2006
snapman.sys  Fri Oct 06 09:43:53 2006
tifsfilt.sys Fri Feb 09 09:37:31 2007
krait.sys    Mon Jan 23 22:11:23 2006

I would suspect that this is a driver issue (from the last parameter of the bugcheck codes). But I'm not certain about this. Please run the tools that I suggested and update those drivers.

If the system continues to BSOD, please post back with the details and we'll work on it some more.

 

[KindredPhantom]

I got a new BSOD. This one is different from the last. 0x50: PAGE_FAULT_IN_NONPAGED_AREA

Please start by running these hardware diagnostics:
Memory Diagnostics (read the details at the link)
HD Diagnostic (read the details at the link)
.

I ran the memory diagnostic for 10 minutes and it showed some errors. I have not run the HD diagnostic. Like you, i think this may be a driver issue and not hardware related. I think this because it was only recently that i had an extra 2GB of RAM installed. Also i have been running Windows 7 RC1 for a while without frequent BSOD's, but that was 32-bit.

Also, please run one of these free, independent online malware scans to ensure that your current protection hasn't been compromised: Malware (read the details at the link)

I was running that before i BSOD, it had not found anything before i BSOD.

Please update these older drivers:

timntr.sys   Thu Dec 28 11:30:38 2006
snapman.sys  Fri Oct 06 09:43:53 2006
tifsfilt.sys Fri Feb 09 09:37:31 2007
krait.sys    Mon Jan 23 22:11:23 2006

The first three are from Acronis True Image, i am running an older version of the program and cannot update it without purchasing the newer copy. The last driver is for my mouse and is the most up to date driver available for it. I am going to uninstall all three programs and then reinstall them just in case they were corrupted during install, a couple of programs have been corrupted and i have had to reinstall them.

 

[zigzag3143]

I got a new BSOD. This one is different from the last. 0x50: PAGE_FAULT_IN_NONPAGED_AREA

Please start by running these hardware diagnostics:
Memory Diagnostics (read the details at the link)
HD Diagnostic (read the details at the link)
.

I ran the memory diagnostic for 10 minutes and it showed some errors. I have not run the HD diagnostic. Like you, i think this may be a driver issue and not hardware related. I think this because it was only recently that i had an extra 2GB of RAM installed. Also i have been running Windows 7 RC1 for a while without frequent BSOD's, but that was 32-bit.

Also, please run one of these free, independent online malware scans to ensure that your current protection hasn't been compromised: Malware (read the details at the link)

I was running that before i BSOD, it had not found anything before i BSOD.

Please update these older drivers:

timntr.sys   Thu Dec 28 11:30:38 2006
snapman.sys  Fri Oct 06 09:43:53 2006
tifsfilt.sys Fri Feb 09 09:37:31 2007
krait.sys    Mon Jan 23 22:11:23 2006

The first three are from Acronis True Image, i am running an older version of the program and cannot update it without purchasing the newer copy. The last driver is for my mouse and is the most up to date driver available for it. I am going to uninstall all three programs and then reinstall them just in case they were corrupted during install, a couple of programs have been corrupted and i have had to reinstall them.

Just to save some time I took a quick look.

Memory mangement and these old drivers. I will let usamsa do the heavy lifting as he is much better at this than I. I would run memtestx86 if you havent already.

Ken J+

krait.sys        fffff880`04100000    fffff880`04102880    0x00002880    0x43d59adb    1/23/2006 10:11:23 PM                        
secdrv.SYS        fffff880`076ef000    fffff880`076fa000    0x0000b000    0x4508052e    9/13/2006 8:18:38 AM                        
snapman.sys        fffff880`0199a000    fffff880`019cd000    0x00033000    0x45265d99    10/6/2006 8:43:53 AM                        
timntr.sys        fffff880`0189e000    fffff880`01946000    0x000a8000    0x4593f12e    12/28/2006 11:30:38 AM                        
tifsfilt.sys        fffff880`041a8000    fffff880`041bd000    0x00015000    0x45cc872b    2/9/2007 9:37:31 AM

Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\K\Desktop\121909-22921-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*d:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
[B]Built by: 7600.16385.amd64fre.win7_rtm.090713-1255[/B]
Machine Name:
Kernel base = 0xfffff800`02c4d000 PsLoadedModuleList = 0xfffff800`02e8ae50
Debug session time: Sat Dec 19 09:29:18.642 2009 (GMT-5)
System Uptime: 0 days 0:51:22.236
Loading Kernel Symbols
...............................................................
................................................................
..................
Loading User Symbols
Loading unloaded module list
.......
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

[U][I][B]BugCheck 50, {fffff8a0120099cc, 1, fffff88000d07046, 2}


Could not read faulting driver name
Probably caused by : memory_corruption

Followup: memory_corruption[/B][/I][/U]
---------

0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

[B]PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced.  This cannot be protected by try-except,
it must be protected by a Probe.  Typically the address is just plain bad or it
is pointing at freed memory.
Arguments:
Arg1: fffff8a0120099cc, memory referenced.
Arg2: 0000000000000001, value 0 = read operation, 1 = write operation.
Arg3: fffff88000d07046, If non-zero, the instruction address which referenced the bad memory
    address.
Arg4: 0000000000000002, (reserved)
[/B]
Debugging Details:
------------------


Could not read faulting driver name

WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff80002ef50e0
 fffff8a0120099cc 

FAULTING_IP: 
CI!MFKeyIsTrustedRootKey+da8a
fffff880`00d07046 46890409        mov     dword ptr [rcx+r9],r8d

MM_INTERNAL_CODE:  2

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  CODE_CORRUPTION

BUGCHECK_STR:  0x50
[B]
PROCESS_NAME:  audiodg.exe
[/B]
CURRENT_IRQL:  0

TRAP_FRAME:  fffff880085ea3f0 -- (.trap 0xfffff880085ea3f0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=000000003c4c64af rbx=0000000000000000 rcx=000000001200000c
rdx=0000000073e30179 rsi=0000000000000000 rdi=0000000000000000
rip=fffff88000d07046 rsp=fffff880085ea580 rbp=fffff880085ea790
 r8=00000000363b5779  r9=fffff8a0000099c0 r10=00000000ab799e43
r11=fffff880085ea648 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz na po nc
CI!MFKeyIsTrustedRootKey+0xda8a:
fffff880`00d07046 46890409        mov     dword ptr [rcx+r9],r8d ds:0020:fffff8a0`120099cc=????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002d3cbc2 to fffff80002cbef00

STACK_TEXT:  
fffff880`085ea288 fffff800`02d3cbc2 : 00000000`00000050 fffff8a0`120099cc 00000000`00000001 fffff880`085ea3f0 : nt!KeBugCheckEx
fffff880`085ea290 fffff800`02cbcfee : 00000000`00000001 00000000`781f802a fffff880`01a00000 fffff880`01dffff8 : nt! ?? ::FNODOBFM::`string'+0x40f90
fffff880`085ea3f0 fffff880`00d07046 : 3c4c64af`781f802a fffff880`ab799e43 fffff880`085ea648 00000000`73e30179 : nt!KiPageFault+0x16e
fffff880`085ea580 fffff880`00d37418 : fffff880`085ea790 fffff880`085ea780 00000000`ca5697b4 f89a35d5`0ed57f24 : CI!MFKeyIsTrustedRootKey+0xda8a
fffff880`085ea620 fffff880`00d375a3 : 00000000`0003028f 00000000`00000005 00000000`00000000 00000000`00000002 : CI!MFKeyIsTrustedRootKey+0x3de5c
fffff880`085ea980 fffff880`00ce4526 : c11b999c`187b4d0e 00000000`0003028f 00000000`00000001 00000000`00000000 : CI!peauthvbn_StoreParameter+0x3f
fffff880`085ea9d0 fffff880`00cf883f : fffff880`00d4b998 00000000`00000000 fffff880`00d49970 fffff8a0`000a8630 : CI!PEAuthStoreParameter+0x5a
fffff880`085eaa00 fffff880`00cf8bbc : 00000000`00000c30 00000000`00000001 fffff8a0`00281d10 fffffa80`0464d720 : CI!I_PEUpdatePEHashBucket+0x1f7
fffff880`085eaa40 fffff800`02f7aaca : fffff8a0`00294930 fffffa80`061ec160 fffffa80`061ec160 fffffa80`05b7db80 : CI!I_PEProcessNotify+0x28
fffff880`085eaa70 fffff800`02fa16eb : 000007ff`fffde000 00000000`00000001 00000000`00000000 fffffa80`05928540 : nt!PspExitProcess+0x156
fffff880`085eaad0 fffff800`02f7acb8 : 00000000`c000004b 00000000`00000001 000007ff`fffde000 00000000`00000000 : nt!PspExitThread+0x3bb
fffff880`085eaba0 fffff800`02cbe153 : fffffa80`061ec160 fffff880`c000004b fffffa80`0464d720 00000000`00000000 : nt!NtTerminateProcess+0x138
fffff880`085eac20 00000000`771d017a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`0023f1e8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x771d017a


STACK_COMMAND:  kb

CHKIMG_EXTENSION: !chkimg -lo 50 -d !CI
    fffff88000d07045 - CI!MFKeyIsTrustedRootKey+da89
    [ 00:12 ]
1 error : !CI (fffff88000d07045)

MODULE_NAME: memory_corruption

IMAGE_NAME:  memory_corruption

FOLLOWUP_NAME:  memory_corruption

DEBUG_FLR_IMAGE_TIMESTAMP:  0

MEMORY_CORRUPTOR:  ONE_BYTE

FAILURE_BUCKET_ID:  X64_MEMORY_CORRUPTION_ONE_BYTE

BUCKET_ID:  X64_MEMORY_CORRUPTION_ONE_BYTE

Followup: memory_corruption
---------

 

[KindredPhantom]

Just to save some time I took a quick look.

Memory mangement and these old drivers. I will let usamsa do the heavy lifting as he is much better at this than I. I would run memtestx86 if you havent already.

I did, i ran it for 10 minutes and it showed some errors. But to be honest i do not fully understand it. I gathered it was testing my memory and there were some errors but i am not sure how long i needed to run it for and what to make of the result.

 

[Tews]

You should run it over night... ten minutes is no where near enough...

 

[zigzag3143]

Just to save some time I took a quick look.

Memory mangement and these old drivers. I will let usamsa do the heavy lifting as he is much better at this than I. I would run memtestx86 if you havent already.

I did, i ran it for 10 minutes and it showed some errors. But to be honest i do not fully understand it. I gathered it was testing my memory and there were some errors but i am not sure how long i needed to run it for and what to make of the result.

KP

As our faster than light collegue Tews said overnight, but if it is showing errors in 10 m inutes you can be sure it will have tons overnight. You might want to check temps for heat sometimes manifests itself like this. DL cpu-z, and gpu-z both free to keep an eye on them

Ken J+

 

[KindredPhantom]

I already use CoreTemp to monitor my CPU temp, the temperate is fine.
I gathered ten minutes wasn't a good amount of time to judge. I'll see about running it overnight but i usually don't have my computer running overnight due to the fact it is in my bedroom.

Thinking back to the crashes, they seem to have occurred when I'm browsing in Chromium.

 

[zigzag3143]

I already use CoreTemp to monitor my CPU temp, the temperate is fine.
I gathered ten minutes wasn't a good amount of time to judge. I'll see about running it overnight but i usually don't have my computer running overnight due to the fact it is in my bedroom.

Thinking back to the crashes, they seem to have occurred when I'm browsing in Chromium.

KP

Core temp is fine. well test for as long as you can. Might want to pull some of the ram and retest. BTW this last dmp you were running _NAME: audiodg.exe when it happened. May also have had chrome open doesnt say

Good Luck


Ken J+

 

[KindredPhantom]

That's interesting because i have recently updated my audio drivers and have heard of someone getting a BSOD from realtek HD audio drivers.

 

[zigzag3143]

That's interesting because i have recently updated my audio drivers and have heard of someone getting a BSOD from realtek HD audio drivers.

I highlighted where audiodx was running in the DMP analysis.

 

[chev65]

If you can't make it ten minutes on Memtest then the dmp's aren't really worth reading until you get that problem sorted out. Memory problems will cause all sorts of BSOD's and they won't stop until the memory problem is fixed. I would make some Memory setting adjustments in bios or use some different memory if that doesn't work.

 

[KindredPhantom]

But what do i do with the results after leaving memtest running for several hours? Is it supposed to give me a answer? I'm just not sure what the next step is after it has run and gone through it's test.

 

[zigzag3143]

But what do i do with the results after leaving memtest running for several hours? Is it supposed to give me answer? I'm just not sure what is the next step after it has run and gone through it's test.

If your results are not 100% clean you need to start thinking about what you want to do. maybe one of the ram sticks went bad, maybe they dont match exactly. take to message that memtest generates and either google it or post it and we will

Ken J+

 

[chev65]

But what do i do with the results after leaving memtest running for several hours? Is it supposed to give me a answer? I'm just not sure what the next step is after it has run and gone through it's test.

I just gave you the answer, either make adjustments to the memory settings in bios or try some other memory.

I would first try making sure the memory is set to specs in bios, voltage, timings and divider settings correctly set, and that your other voltages are enough to support your memory. Sometimes the NB voltage needs a bump, it's hard to say from here what it might need.

If you can't pass those memory tests nothing is going to work right, and you will keep getting different bsod's.

 

[sfarmer14]

Having same code error

I am running Windows 7 64 bit. i am getting random BSOD's whether in a game or just sitting at idle. I have ran the Mem test no errors were detected. Have not ran the HD test. i have bumped up the DIMM Voltage to 1.64 from 1.5. I am running a EVGA P55 FTW motherboard with a 15 Quad core processor, and Corsair 4 gb RAM. And my program will freeze if i click on a .dmp file or right click to zip it.. Help??? My error is 0x109 (0x00000109)

 

[KindredPhantom]

I would advise you start a thread of your own and read this topic before creating it.

Just an update on my issue, i uninstalled and reinstalled Acronis True Image and my mouse software restarting after uninstalling each and that seemed to have fixed my BSOD's (touch wood).

 

[KindredPhantom]

So i thought it was fixed but turns out that it isn't.
I ran windows memory test which win7 recommended and that told me it was a memory problem.
For the past 5 hours i have been running memtest86 and it has come up with 427 errors. How much longer do you think i should keep it running as i have read it will continue running until i stop it?

 

[zigzag3143]

So i thought it was fixed but turns out that it isn't.
I ran windows memory test which win7 recommended and that told me it was a memory problem.
For the past 5 hours i have been running memtest86 and it has come up with 427 errors. How much longer do you think i should keep it running as i have read it will continue running until i stop it?

with 427 errors stop now. return the memory.

Ken J+