Sign in with
Sign up | Sign in
Your question

BSOD BCCODE "a"

Last response: in Systems
Share
April 6, 2012 4:16:10 AM

I have had this nagging BSOD after my computer has been up for more than a week and I try to share a DVD across my home network (too poor and too much of a tightwad to spend money for a DVD drive for my netbook hooked to my sound system and TV in my bedroom upstairs).

A crash every 8-9 days really isn't that big of a deal for me (and will be a pain to diagnose as it doesn't happen frequently) as I like to shut it down every night anyways but I wanted to figure the root cause. Could be a malfunctioning part, but I have thoroughly tested my RAM after I got it, my CPU unlock is stable and has been for some time, even under Prime95 for several hours, and my GPU has been stable even OC'ed for about a year and a half but who knows. Here are two copies of the Windows Recovery prompt that I have recorded:


BSOD 1

Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7601.2.1.0.768.3
Locale ID: 1033

Additional information about the problem:
BCCode: a
BCP1: 0000000000000000
BCP2: 0000000000000002
BCP3: 0000000000000001
BCP4: FFFFF80002ED4704
OS Version: 6_1_7601
Service Pack: 1_0
Product: 768_1

Files that help describe the problem:
C:\Windows\Minidump\031812-11871-01.dmp
C:\Users\USER\AppData\Local\Temp\WER-24960-0.sysdata.xml

Read our privacy statement online:
http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0...

If the online privacy statement is not available, please read our privacy statement offline:
C:\Windows\system32\en-US\erofflps.txt


BSOD 2

Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7601.2.1.0.768.3
Locale ID: 1033

Additional information about the problem:
BCCode: a
BCP1: 0000000000000000
BCP2: 0000000000000002
BCP3: 0000000000000001
BCP4: FFFFF80002ECA704
OS Version: 6_1_7601
Service Pack: 1_0
Product: 768_1

Files that help describe the problem:
C:\Windows\Minidump\040512-15490-01.dmp
C:\Users\USER2\AppData\Local\Temp\WER-26379-0.sysdata.xml

Read our privacy statement online:
http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0...

If the online privacy statement is not available, please read our privacy statement offline:
C:\Windows\system32\en-US\erofflps.txt

My Rig
Windows 7 Home Premium 64 Bit
AMD Phenom II x4 B45 @3.2GHz
MSI 870-G45
8GB G. Skill DDR3 1333 RAM
MSI GTX 460 1GB (Stock since the first BSOD)

This evening I got it to share the DVD and then it hit a bad part of the DVD and froze. VLC wouldn't connect to the rig after it crashed then when I came down it was slow and then it crashed. VLC 2.0.1 also had a hard time installing before I started... I just thought I would post this to see if anyone would have any ideas. Any would be greatly appreciated. Thanks!

More about : bsod bccode

April 6, 2012 4:48:47 AM

Here is the dmp in case anyone was wondering:


Bugcheck Analysis *
* *
*******************************************************************************

IRQL_NOT_LESS_OR_EQUAL (a)
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.
Arguments:
Arg1: 0000000000000000, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000001, 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: fffff80002eca704, address which referenced memory

Debugging Details:
------------------


WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff8000310a100
0000000000000000

CURRENT_IRQL: 2

FAULTING_IP:
nt!KiInsertQueueApc+74
fffff800`02eca704 488910 mov qword ptr [rax],rdx

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

BUGCHECK_STR: 0xA

TRAP_FRAME: fffff8800a5cb650 -- (.trap 0xfffff8800a5cb650)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=fffffa8008fcda20
rdx=fffffa800d78f020 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002eca704 rsp=fffff8800a5cb7e0 rbp=fffff8000304de80
r8=fffffa80076f9b00 r9=fffffa8008fcda20 r10=fffff80003062301
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei ng nz na pe nc
nt!KiInsertQueueApc+0x74:
fffff800`02eca704 488910 mov qword ptr [rax],rdx ds:6000:00000000`00000000=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER: from fffff80002ed82e9 to fffff80002ed8d40

STACK_TEXT:
fffff880`0a5cb508 fffff800`02ed82e9 : 00000000`0000000a 00000000`00000000 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
fffff880`0a5cb510 fffff800`02ed6f60 : 8cfd2d25`40e9389a 99b64386`68a3a8ed 00000000`00000000 fffffa80`08fcd7e0 : nt!KiBugCheckDispatch+0x69
fffff880`0a5cb650 fffff800`02eca704 : fffff800`0304de80 fffffa80`0b612aa0 fffff800`030624e0 00000000`00000000 : nt!KiPageFault+0x260
fffff880`0a5cb7e0 fffff800`02eb97a4 : fffffa80`08fcd7e0 00000000`00000000 fffffa80`08e06010 fffffa80`0d78f010 : nt!KiInsertQueueApc+0x74
fffff880`0a5cb810 fffff800`02fe643d : fffffa80`08e06010 fffff880`0a5cbb20 fffffa80`08e06010 00000000`000007ff : nt!KeInsertQueueApc+0x80
fffff880`0a5cb870 fffff880`07b275d0 : fffffa80`08e06010 fffffa80`08fce010 fffffa80`076f9bd0 fffffa80`0dde5700 : nt!IoRaiseHardError+0xed
fffff880`0a5cb930 fffffa80`08e06010 : fffffa80`08fce010 fffffa80`076f9bd0 fffffa80`0dde5700 00000000`00000000 : 0xfffff880`07b275d0
fffff880`0a5cb938 fffffa80`08fce010 : fffffa80`076f9bd0 fffffa80`0dde5700 00000000`00000000 fffffa80`08e06488 : 0xfffffa80`08e06010
fffff880`0a5cb940 fffffa80`076f9bd0 : fffffa80`0dde5700 00000000`00000000 fffffa80`08e06488 00000000`00000001 : 0xfffffa80`08fce010
fffff880`0a5cb948 fffffa80`0dde5700 : 00000000`00000000 fffffa80`08e06488 00000000`00000001 fffffa80`08e06010 : 0xfffffa80`076f9bd0
fffff880`0a5cb950 00000000`00000000 : fffffa80`08e06488 00000000`00000001 fffffa80`08e06010 fffffa80`0dde5760 : 0xfffffa80`0dde5700


STACK_COMMAND: kb

FOLLOWUP_IP:
nt!KiInsertQueueApc+74
fffff800`02eca704 488910 mov qword ptr [rax],rdx

SYMBOL_STACK_INDEX: 3

SYMBOL_NAME: nt!KiInsertQueueApc+74

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 4ec79dd2

FAILURE_BUCKET_ID: X64_0xA_nt!KiInsertQueueApc+74

BUCKET_ID: X64_0xA_nt!KiInsertQueueApc+74

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

And a quick Google Search pulls up "Probably caused by : ntkrnlmp.exe" means one of the following:


•Require a microcode update that is not applied by the computer's basic input/output system (BIOS).
•Are damaged or defective.
•Are operating outside their specified ranges for temperature, power, or other conditions.

So my guess is my unlocked CPU is throwing fits... Guess I can add some more voltage and if that does work just make sure to restart it every now and again cause I like my unlock. :) 
m
0
l
April 24, 2012 2:51:04 PM

Your best bet is to run Memtest86

And then check what drivers you have installed that are either un-needed, or incorrect for the hardware.. and then remove them

Good luck :) 
m
0
l
!