Windows 7 - BSOD 0x0000000a problem

**mosjos** · 02-27-2010

Hi,
I constantly keep getting a BSOD with code 0x0000000a on my windows 7 machine

Would someone please be able to help me as I am completely stuck (i am attaching the minidump logs).

OS: Windows 7 ultimate
CPU:Intel Core2 Quad CPU Q9400 @ 2.66GHz
Motherboard : Gygabyte EP45-UD3P V1.0
Memory: 4Gb
Graphics Card: NVIDIA GeForce 9600GSO
SoundCard: Realtek High Definition Audio

Many thanks in advance

**Capt.Jack Sparrow** · 02-27-2010

Quote: Originally Posted by mosjos

Hi,
I constantly keep getting a BSOD with code 0x0000000a on my windows 7 machine

Would someone please be able to help me as I am completely stuck (i am attaching the minidump logs).

OS: Windows 7 ultimate
CPU:Intel Core2 Quad CPU Q9400 @ 2.66GHz
Motherboard : Gygabyte EP45-UD3P V1.0
Memory: 4Gb
Graphics Card: NVIDIA GeForce 9600GSO
SoundCard: Realtek High Definition Audio

Many thanks in advance

Hello Welcome to SF,

I guess multiple issues are going on. Let’s start with basics. If your Overclocking please stop. Make sure your BIOS have the latest firmware. If you using any Antivirus or Firewall uninstall it and see whether that makes any difference.

Quote:

Run the Memory Diagnostic & HD Diagnostic

Also i would recommend to run System Integrity Checker
Start > Run > CMD >Right Click and Run as administrator > SFC/ SCANNOW

Bugcheck Analysis

Code:

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: fffffd6f800ac15b, memory referenced.
Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
Arg3: fffff80002cd0dff, If non-zero, the instruction address which referenced the bad memory
    address.
Arg4: 0000000000000007, (reserved)

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

Could not read faulting driver name
READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002ef30e0
 fffffd6f800ac15b 
FAULTING_IP: 
nt!MiAgeWorkingSet+4df
fffff800`02cd0dff 410fb6471b      movzx   eax,byte ptr [r15+1Bh]
MM_INTERNAL_CODE:  7
CUSTOMER_CRASH_COUNT:  1
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x50
PROCESS_NAME:  winlogon.exe
CURRENT_IRQL:  0
TRAP_FRAME:  fffff88003316760 -- (.trap 0xfffff88003316760)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=00000000ffffffff rbx=0000000000000000 rcx=fffff683ff7ebf70
rdx=0000000000000001 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002cd0dff rsp=fffff880033168f0 rbp=0000000000000000
 r8=0000000000000001  r9=fffffa80060909c8 r10=0000000000000005
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz ac po cy
nt!MiAgeWorkingSet+0x4df:
fffff800`02cd0dff 410fb6471b      movzx   eax,byte ptr [r15+1Bh] ds:00000000`0000001b=??Resetting default scope
LAST_CONTROL_TRANSFER:  from fffff80002d3ab19 to fffff80002cbcf00
STACK_TEXT:  
fffff880`033165f8 fffff800`02d3ab19 : 00000000`00000050 fffffd6f`800ac15b 00000000`00000000 fffff880`03316760 : nt!KeBugCheckEx
fffff880`03316600 fffff800`02cbafee : 00000000`00000000 fffffa80`0395c125 00000000`00000000 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x40edb
fffff880`03316760 fffff800`02cd0dff : 00000003`00000000 10900001`0ae99025 00000000`00000000 00000000`00000109 : nt!KiPageFault+0x16e
fffff880`033168f0 fffff800`02d3da0e : fffffa80`060909c8 fffff880`00000001 00000000`00000001 fffff880`03316b70 : nt!MiAgeWorkingSet+0x4df
fffff880`03316aa0 fffff800`02cd16e2 : 00000000`00000053 00000000`00000000 fffffa80`00000000 00000000`00000007 : nt! ?? ::FNODOBFM::`string'+0x49926
fffff880`03316b40 fffff800`02cd196f : 00000000`00000008 fffff880`03316bd0 00000000`00000001 fffffa80`00000000 : nt!MmWorkingSetManager+0x6e
fffff880`03316b90 fffff800`02f60166 : fffffa80`039ed1a0 00000000`00000080 fffffa80`039cd040 00000000`00000001 : nt!KeBalanceSetManager+0x1c3
fffff880`03316d00 fffff800`02c9b486 : fffff880`02f63180 fffffa80`039ed1a0 fffff880`02f6dfc0 ffffffff`ffffffff : nt!PspSystemThreadStartup+0x5a
fffff880`03316d40 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16
STACK_COMMAND:  kb
FOLLOWUP_IP: 
nt!MiAgeWorkingSet+4df
fffff800`02cd0dff 410fb6471b      movzx   eax,byte ptr [r15+1Bh]
SYMBOL_STACK_INDEX:  3
SYMBOL_NAME:  nt!MiAgeWorkingSet+4df
FOLLOWUP_NAME:  MachineOwner
MODULE_NAME: nt
DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bc600
IMAGE_NAME:  memory_corruption
FAILURE_BUCKET_ID:  X64_0x50_nt!MiAgeWorkingSet+4df
BUCKET_ID:  X64_0x50_nt!MiAgeWorkingSet+4df

Hope this helps,
Captain

**mosjos** · 02-27-2010

Hi Captain,

thanks for your reply.

I am not overclocking the PC although there is some software installed from the motherboard manufacturer to overclock the machine. I will remove this.

I will unistall the anti-virus and firewall (kaspersky) although not very keen on using the machine without anti-virus.

Do you think that the bad memory reference would be caused by bad memory sims? should i replace the memory?

If the BSOD happens again I will update this thread.

**mosjos** · 02-27-2010

Hi, As requested i ran sfc /scannow

It completed doing the scan, however i got some errors (see below

Code:

C:\Windows\system32>sfc /scannow

Beginning system scan.  This process will take some time.

Beginning verification phase of system scan.
Verification 100% complete.
Windows Resource Protection found corrupt files but was unable to fix some of th
em.
Details are included in the CBS.Log windir\Logs\CBS\CBS.log. For example
C:\Windows\Logs\CBS\CBS.log

C:\Windows\system32>

I looked through the CBS.log file for todays date (27/02/2010) but cannot work out what the problem is or how to fix it. Could these files be causing the BSOD?