Win7 BSOD 0x0000000a, long-time issue, stumped

March 4, 2012 at 22:44:55
Specs: Windows 7 Ultimate 64 bit, Phenom 9850 / 4 Gigs
I have been attempting for over a year to resolve this problem. Periodically, my machine crashes with a BSOD and the error is 0x0000000a. Having done lots of research on this stop error, I have attempted to isolate RAM and driver issues, to no avail. I have used verifier.exe, I have changed msconfig settings, and nothing changes, just every so often *pop* BSOD.
I downloaded and installed the MS Debugging tools for Windows X64 so I can view the crash dump info, but to me that looks like a generic pile of doodoo. See latest dump below, with additional "detailed" crash dump info, as well as a brand-new HJT log. Any insight and assistance would be greatly appreciated!!!

Asus M3A78EMH-HDMI (AMI Bios version 1302)
AMD Phenom 9850 Black (not OC'd)
Diamond brand ATI Radeon 4350 512MB
2x Team Group Inc Team-Elite-800 PC2-6400 2GB unganged dual-channel RAM


* Bugcheck Analysis *
* *

An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high. This is usually
caused by drivers using improper addresses.
If a kernel debugger is available get the stack backtrace.
Arg1: fffff800034092f0, memory referenced
Arg2: 000000000000000d, IRQL
Arg3: 0000000000000000, bitfield :
bit 0 : value 0 = read operation, 1 = write operation
bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: fffff8000308515e, address which referenced memory

Debugging Details:

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800032c1100


fffff800`0308515e 4c8b8370440000 mov r8,qword ptr [rbx+4470h]




PROCESS_NAME: plugin-contain

TRAP_FRAME: fffff880093de450 -- (.trap 0xfffff880093de450)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=d717548f5385d2ba rbx=0000000000000000 rcx=fffff80003204e80
rdx=0000000000002711 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8000308515e rsp=fffff880093de5e0 rbp=0000000000000001
r8=0000000000000000 r9=0000000000000000 r10=0000000000000000
r11=fffff880093de6c0 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl nz na po nc
fffff800`0308515e 4c8b8370440000 mov r8,qword ptr [rbx+4470h] ds:afe0:00000000`00004470=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER: from fffff8000308e1e9 to fffff8000308ec40

fffff880`093de308 fffff800`0308e1e9 : 00000000`0000000a fffff800`034092f0 00000000`0000000d 00000000`00000000 : nt!KeBugCheckEx
fffff880`093de310 fffff800`0308ce60 : fffffa80`0009b160 fffff780`00001000 fffff800`032c4500 fffff800`03204e80 : nt!KiBugCheckDispatch+0x69
fffff880`093de450 fffff800`0308515e : 00000000`000013bc fffff6fc`00019f58 fffff780`00001000 00000000`00000000 : nt!KiPageFault+0x260
fffff880`093de5e0 fffff800`03099497 : fffff800`032c4500 fffff800`03204e80 00000000`00002711 fffff800`033eb628 : nt!KeAccumulateTicks+0x6e
fffff880`093de670 fffff800`03605895 : fffff800`0362b460 fffff880`093de820 fffff800`0362b460 fffff880`00000000 : nt!KeUpdateSystemTime+0x377
fffff880`093de770 fffff800`0308b173 : 00000000`00000000 00000000`00000001 00000000`00000008 fffff880`093de840 : hal!HalpHpetClockInterrupt+0x8d
fffff880`093de7a0 fffff800`030d6c25 : fffff800`0304e74e fffff6fc`40018c78 fffff880`0318f000 00000000`0000318f : nt!KiInterruptDispatchNoLock+0x163
fffff880`093de938 fffff800`0304e74e : fffff6fc`40018c78 fffff880`0318f000 00000000`0000318f 0000318e`0001212a : nt!KeZeroSinglePage+0x35
fffff880`093de940 fffff800`0309f9e0 : 80000000`277cb867 00000000`00000002 fffff700`00003190 fffffa80`00000000 : nt!MiZeroPhysicalPage+0x21a
fffff880`093de9d0 fffff800`0309c19e : 00000000`00000001 00000000`067e1838 fffff880`093dec20 fffff680`00033f08 : nt!MiResolveDemandZeroFault+0x6e0
fffff880`093deac0 fffff800`0308cd6e : 00000000`00000001 00000000`067e1838 fffff880`093deb01 00000000`00000c30 : nt!MmAccessFault+0x5de
fffff880`093dec20 00000000`697afce6 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x16e
00000000`0027d9e0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x697afce6


fffff800`0308515e 4c8b8370440000 mov r8,qword ptr [rbx+4470h]


SYMBOL_NAME: nt!KeAccumulateTicks+6e



IMAGE_NAME: ntkrnlmp.exe


FAILURE_BUCKET_ID: X64_0xA_VRF_nt!KeAccumulateTicks+6e

BUCKET_ID: X64_0xA_VRF_nt!KeAccumulateTicks+6e

Followup: MachineOwner


edited by moderator: Unsolicited HJT Log removed

See More: Win7 BSOD 0x0000000a, long-time issue, stumped

Report •

March 4, 2012 at 22:51:51
More potentially helpful info:

I have replaced the RAM, both sticks, and I have replaced the HDD (now have a Seagate Barracuda 1TB that replaced a Samsung 1TB that replaced a WD 1TB) and I have run TDSS Killer, MBAM (both in safe and regular modes), the KAV Rescue disc (updated), SUPER Antispyware, and I used to run MsSE but I thought this was a virus problem so I installed KIS 2012 trial to try to find it. I believe that, after three F/R and no change in behavior that it isn't a virus issue - but I could be missing something, too. Anyway, again, any advice would be appreciated.

Report •

March 5, 2012 at 02:31:12
The only hardware you appear not to have checked is the actual Graphics Card !!

"Stop error code 0x0000000A (IRQL_NOT_LESS_OR_EQUAL)" ??

Also only post logs if requested, I see the moderator removed yours......

Googling is quicker than waiting for an answer....

Report •

March 5, 2012 at 03:49:44
Jolicloud could be right. Gfx card has RAM, too, which could be defective.

I would also suggest increasing RAM timings from 1T to 2T and from, let's say, 8-8-8-21 to 9-9-9-24. These values, given as an example, depend on your RAM.

What about PSU ? It may be failing or inadequate altogether.


Report •

Related Solutions

March 5, 2012 at 10:00:13
The graphics card is listed. It is a Diamond Multimedia branded ATI Radeon 4350 with 512 MB DDR4 GDRam. Also, the board has onboard graphics - no difference either way.
The PSU is an A-Power brand 850W w/ 2 rails Previously I had used an Antec 430W PSU and the ASUS PSU calculator said that wasn't enough juice so I switched it out.

As for the logs, thanks for the advice. I was just trying to cover all my bases.

As for Googling being faster than waiting... It's been over a year & Mr Google has been a lot of help but hasn't provided a solution yet.

Thanks again!

Report •

March 5, 2012 at 10:04:54
....but have you tried running on on-board graphics, or tried another graphics card ???

You should use Single Rail quality power supply with 12V 35A or more, and spend at least $60.00, Corsair are good at that price....

Googling is quicker than waiting for an answer....

Report •

March 5, 2012 at 10:47:57
I have a Corsair 750W single rail sitting here, I'll try it. Also, yes, I have used the onboard GFX and removed the PCIx card, no difference, random 0x0000000a either way.

Report •

March 5, 2012 at 12:20:35
Replaced PSU, got BSOD 20 minutes after booting. I'm fed up. I put another HDD in and am now running the Win8 Consumer Preview. Let's see how long before that dumps.
What's really interesting is that Ubuntu, WinXP, and Fedora never crash on this hardware. ONLY WinVista and Win7...

Report •

March 7, 2012 at 04:18:21
The most important Blue Screen of Death troubleshooting step you can take is to ask yourself what you just did.

1) Did you just install a new program or a piece of hardware, update a driver, install an update, etc.? If so, there's a very good chance that the change you made caused the BSOD:

Startup using Last Known Good Configuration to undo recent registry and driver changes.
Use System Restore to undo recent system changes.
Roll Back device driver to version prior to your driver update.

2) Scan your computer for viruses. Some viruses can cause a Blue Screen of Death, especially ones that infect the master boot record (MBR) or boot sector.

3) Update drivers for your hardware. Most Blue Screens of Death are hardware or driver related so updated drivers could fix the cause of the STOP error.

4) Return hardware settings to default in Device Manager. Unless you have a specific reason to do so, the system resources that an individual piece of hardware is configured to use in Device Manager should be set to default. Non-default hardware settings have been known to cause a Blue Screen of Death.

5) Return BIOS settings to their default levels. An overclocked or misconfigured BIOS can cause all sorts of random issues, including BSODs.

Report •

Ask Question