cybercore
New Member
- Joined
- Jul 7, 2009
loaded defaults in bios and got bsod as soon as i logged on, quickest its happened. back in xp now, i guess ill just have to buy some ram and hope it works
View attachment 12868
Ya, go ahead buy it.
PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced.
Could not read faulting driver name
Probably caused by : hardware ( nt!AlpcpCancelMessagesByRequestor+159 )
Code:
Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [F:\DMP\041011-14656-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*c:\websymbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17514.amd64fre.win7sp1_rtm.101119-1850
Machine Name:
Kernel base = 0xfffff800`02a60000 PsLoadedModuleList = 0xfffff800`02ca5e90
Debug session time: Sun Apr 10 07:12:17.956 2011 (UTC - 4:00)
System Uptime: 0 days 0:08:05.394
Loading Kernel Symbols
...............................................................
................................................................
................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 50, {ffffffffffffff8e, 1, fffff80002d8512d, 0}
Could not read faulting driver name
Probably caused by : hardware ( nt!AlpcpCancelMessagesByRequestor+159 )
Followup: MachineOwner
---------
2: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
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: ffffffffffffff8e, memory referenced.
Arg2: 0000000000000001, value 0 = read operation, 1 = write operation.
Arg3: fffff80002d8512d, If non-zero, the instruction address which referenced the bad memory
address.
Arg4: 0000000000000000, (reserved)
Debugging Details:
------------------
Could not read faulting driver name
WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff80002d110e8
ffffffffffffff8e
FAULTING_IP:
nt!AlpcpCancelMessagesByRequestor+159
fffff800`02d8512d 10488d adc byte ptr [rax-73h],cl
MM_INTERNAL_CODE: 0
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0x50
PROCESS_NAME: chrome.exe
CURRENT_IRQL: 0
TRAP_FRAME: fffff880072526f0 -- (.trap 0xfffff880072526f0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000001 rbx=0000000000000000 rcx=fffff8a0074a8420
rdx=fffff8a00716122c rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002d8512d rsp=fffff88007252888 rbp=0000000000000029
r8=0000000000000000 r9=0000000000000001 r10=fffff88002f647e0
r11=fffffa8001bce640 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl zr na po cy
nt!AlpcpCancelMessagesByRequestor+0x159:
fffff800`02d8512d 10488d adc byte ptr [rax-73h],cl ds:1200:ffffffff`ffffff8e=??
Resetting default scope
MISALIGNED_IP:
nt!AlpcpCancelMessagesByRequestor+159
fffff800`02d8512d 10488d adc byte ptr [rax-73h],cl
LAST_CONTROL_TRANSFER: from fffff80002a8c2ac to fffff80002ae0640
STACK_TEXT:
fffff880`07252588 fffff800`02a8c2ac : 00000000`00000050 ffffffff`ffffff8e 00000000`00000001 fffff880`072526f0 : nt!KeBugCheckEx
fffff880`07252590 fffff800`02ade76e : 00000000`00000001 ffffffff`ffffff8e fffff880`01083400 fffff8a0`08cbc3c0 : nt! ?? ::FNODOBFM::`string'+0x4621f
fffff880`072526f0 fffff800`02d8512d : fffff880`00eaf162 fffff8a0`0840a5c0 fffffa80`02de9850 fffff880`072528e8 : nt!KiPageFault+0x16e
fffff880`07252888 fffff880`07252a10 : 00000000`000007ff 00000029`02de9801 fffff8a0`0840a5c0 00000000`00000029 : nt!AlpcpCancelMessagesByRequestor+0x159
fffff880`072528d8 00000000`000007ff : 00000029`02de9801 fffff8a0`0840a5c0 00000000`00000029 fffffa80`01bce640 : 0xfffff880`07252a10
fffff880`072528e0 00000029`02de9801 : fffff8a0`0840a5c0 00000000`00000029 fffffa80`01bce640 fffff8a0`08975ba0 : 0x7ff
fffff880`072528e8 fffff8a0`0840a5c0 : 00000000`00000029 fffffa80`01bce640 fffff8a0`08975ba0 fffffa80`03971940 : 0x29`02de9801
fffff880`072528f0 00000000`00000029 : fffffa80`01bce640 fffff8a0`08975ba0 fffffa80`03971940 00000000`00000000 : 0xfffff8a0`0840a5c0
fffff880`072528f8 fffffa80`01bce640 : fffff8a0`08975ba0 fffffa80`03971940 00000000`00000000 fffff8a0`07161220 : 0x29
fffff880`07252900 fffff8a0`08975ba0 : fffffa80`03971940 00000000`00000000 fffff8a0`07161220 fffffa80`03971940 : 0xfffffa80`01bce640
fffff880`07252908 fffffa80`03971940 : 00000000`00000000 fffff8a0`07161220 fffffa80`03971940 fffff8a0`07161270 : 0xfffff8a0`08975ba0
fffff880`07252910 00000000`00000000 : fffff8a0`07161220 fffffa80`03971940 fffff8a0`07161270 fffff880`07252a20 : 0xfffffa80`03971940
STACK_COMMAND: kb
FOLLOWUP_IP:
nt!AlpcpCancelMessagesByRequestor+159
fffff800`02d8512d 10488d adc byte ptr [rax-73h],cl
SYMBOL_STACK_INDEX: 3
SYMBOL_NAME: nt!AlpcpCancelMessagesByRequestor+159
FOLLOWUP_NAME: MachineOwner
IMAGE_NAME: hardware
DEBUG_FLR_IMAGE_TIMESTAMP: 0
MODULE_NAME: hardware
FAILURE_BUCKET_ID: X64_IP_MISALIGNED
BUCKET_ID: X64_IP_MISALIGNED
Followup: MachineOwner
---------
