Blue Screen of Death

Ilvico · 02 Jun 2011

Hey all, it's my 1st time here, so I am sorry for some errors that I might make while here.

My problem is related to the BSOD. A month ago I had 2 BSOD, ( one after another immediately) I did not know what to do so I left it and they stopped, until today. I just had another one while surfing the web. It said Page_Fault_In_NONPAGED AREA: Stop 0x000000x50. I havent Run any mem tests yet, simply because my Ram cards are new. Im uploading the minidump files so you guys can see and hopefully help me.

I have Windows 7 Ultimate x64 installed 2 months ago
All the components in the computer are fairly new, only the cpu is 3 years old.

yowanvista · 02 Jun 2011

ASACPI.sys the 2005 version is a huge cause of BSODs

Information

The 2005 version of this driver is a known BSOD cause.
Please visit this link: ASUSTeK Computer Inc. -Support- Drivers and Download P7P55D LE
Scroll down to the Utilities category, then scroll down to the "ATK0110 driver for WindowsXP/Vista/Windows 7 32&64-bit" (it's about the 12th item down).
Download and install it.
Go to C:\Windows\System32\drivers to check and make sure that the ASACPI.sys file is date stamped from 2009 or 2010 (NOT 2005)

Code:

ASACPI.sys        fffff880`03df4000    fffff880`03dfc000    0x00008000    0x42476c4c    28/03/2005 06:30:36

Remove Avast and WinEmuCD for diagnostic purposes, use MSE instead. Is your computer overclocked?

Code:

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

Use !analyze -v to get detailed debugging information.

BugCheck 50, {fffff68040001be0, 0, fffff80002a6e31b, 5}


Could not read faulting driver name
Probably caused by : memory_corruption ( nt!MiAgeWorkingSet+1d1 )

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

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


Could not read faulting driver name

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002cb3100
 fffff68040001be0 

FAULTING_IP: 
nt!MiAgeWorkingSet+1d1
fffff800`02a6e31b 488b19          mov     rbx,qword ptr [rcx]

MM_INTERNAL_CODE:  5

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x50

PROCESS_NAME:  CCC.exe

CURRENT_IRQL:  0

TRAP_FRAME:  fffff880031397c0 -- (.trap 0xfffff880031397c0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000007ffffffff8 rbx=0000000000000000 rcx=fffff68040001be0
rdx=0000000000000001 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002a6e31b rsp=fffff88003139950 rbp=0000000040001be0
 r8=0000000000000001  r9=fffffa8003e4d3f8 r10=0000000000000005
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na pe cy
nt!MiAgeWorkingSet+0x1d1:
fffff800`02a6e31b 488b19          mov     rbx,qword ptr [rcx] ds:fffff680`40001be0=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002a2e3cf to fffff80002a83d00

STACK_TEXT:  
fffff880`03139658 fffff800`02a2e3cf : 00000000`00000050 fffff680`40001be0 00000000`00000000 fffff880`031397c0 : nt!KeBugCheckEx
fffff880`03139660 fffff800`02a81e2e : 00000000`00000000 fffff680`40001be0 00000000`00000000 00000980`00000000 : nt! ?? ::FNODOBFM::`string'+0x44891
fffff880`031397c0 fffff800`02a6e31b : 00000000`00000002 00000000`00000001 fffff880`03139ba0 00000000`000003ea : nt!KiPageFault+0x16e
fffff880`03139950 fffff800`02afd4f5 : fffffa80`03e4d3f8 fffff800`00000001 00000000`00000001 fffff880`03139bb0 : nt!MiAgeWorkingSet+0x1d1
fffff880`03139b00 fffff800`02a6e8c6 : 00000000`00006aba 00000000`00000000 fffffa80`00000000 00000000`00000003 : nt! ?? ::FNODOBFM::`string'+0x4d886
fffff880`03139b80 fffff800`02a6ed67 : 00000000`00000008 fffff880`03139c10 00000000`00000001 fffffa80`00000000 : nt!MmWorkingSetManager+0x6e
fffff880`03139bd0 fffff800`02d2032e : fffffa80`039efb60 00000000`00000080 fffffa80`0396d9e0 00000000`00000001 : nt!KeBalanceSetManager+0x1c3
fffff880`03139d40 fffff800`02a75666 : fffff800`02bf6e80 fffffa80`039efb60 fffff800`02c04cc0 ffffffff`ffffffff : nt!PspSystemThreadStartup+0x5a
fffff880`03139d80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!MiAgeWorkingSet+1d1
fffff800`02a6e31b 488b19          mov     rbx,qword ptr [rcx]

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  nt!MiAgeWorkingSet+1d1

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP:  4d9fdd5b

IMAGE_NAME:  memory_corruption

FAILURE_BUCKET_ID:  X64_0x50_nt!MiAgeWorkingSet+1d1

BUCKET_ID:  X64_0x50_nt!MiAgeWorkingSet+1d1

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

Ilvico · 02 Jun 2011

Thanks for the reply, Im going to do what you told me. No, my pc is not overclocked.