
Quote: Originally Posted by
Wlada
My computer is old 10 days:
i5 processor
gigabyte p67a mainboard
6gb of ddr3 ram memory - 4db and 2gb
Windows 7 Ultimate x64
Please help
This one was related to your apple charger. That is gigabytes on off charge and can be updated here.
http://www.gigabyte.us/support-downl...downloads.aspx Code:
Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Users\K\Desktop\Windows_NT6_BSOD_jcgriff2\051111-23992-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*C:\Symbols*http://msdl.microsoft.com/download/symbols;srv*e:\symbols
*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16792.amd64fre.win7_gdr.110408-1633
Machine Name:
Kernel base = 0xfffff800`02c55000 PsLoadedModuleList = 0xfffff800`02e92e50
Debug session time: Wed May 11 13:23:52.744 2011 (GMT-4)
System Uptime: 0 days 0:01:04.852
Loading Kernel Symbols
...............................................................
................................................................
.......................
Loading User Symbols
Loading unloaded module list
.............
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 50, {ffffffffffffffd0, 1, fffff80002cca80c, 0}
Unable to load image \SystemRoot\system32\DRIVERS\AppleCharger.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for AppleCharger.sys
*** ERROR: Module load completed but symbols could not be loaded for AppleCharger.sys
Could not read faulting driver name
Probably caused by : AppleCharger.sys ( AppleCharger+1947 )
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: ffffffffffffffd0, memory referenced.
Arg2: 0000000000000001, value 0 = read operation, 1 = write operation.
Arg3: fffff80002cca80c, 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 fffff80002efd0e0
ffffffffffffffd0
FAULTING_IP:
nt!ObfDereferenceObject+2c
fffff800`02cca80c f0480fc11f lock xadd qword ptr [rdi],rbx
MM_INTERNAL_CODE: 0
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0x50
PROCESS_NAME: System
CURRENT_IRQL: 0
TRAP_FRAME: fffff880031af8a0 -- (.trap 0xfffff880031af8a0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=00000000c0000034 rbx=0000000000000000 rcx=0000000000000000
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002cca80c rsp=fffff880031afa30 rbp=fffff880031afb90
r8=fffffa8007c2eb10 r9=fffffa8004ed1248 r10=fffffa8004ef15f0
r11=fffff880031afa80 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei ng nz na po nc
nt!ObfDereferenceObject+0x2c:
fffff800`02cca80c f0480fc11f lock xadd qword ptr [rdi],rbx ds:0010:00000000`00000000=????????????????
Resetting default scope
LAST_CONTROL_TRANSFER: from fffff80002d46024 to fffff80002cc5700
STACK_TEXT:
fffff880`031af738 fffff800`02d46024 : 00000000`00000050 ffffffff`ffffffd0 00000000`00000001 fffff880`031af8a0 : nt!KeBugCheckEx
fffff880`031af740 fffff800`02cc37ee : 00000000`00000001 ffffffff`ffffffff fffff6fb`7ea00200 fffffa80`00000001 : nt! ?? ::FNODOBFM::`string'+0x427f7
fffff880`031af8a0 fffff800`02cca80c : fffff8a0`04af4560 00000000`00000020 fffff880`031afb98 fffff800`00000030 : nt!KiPageFault+0x16e
fffff880`031afa30 fffff880`03f7a947 : fffff880`031afb90 fffff880`031afb98 00000000`001f01ff fffff880`03f7c390 : nt!ObfDereferenceObject+0x2c
fffff880`031afa90 fffff880`031afb90 : fffff880`031afb98 00000000`001f01ff fffff880`03f7c390 fffff800`031907c0 : AppleCharger+0x1947
fffff880`031afa98 fffff880`031afb98 : 00000000`001f01ff fffff880`03f7c390 fffff800`031907c0 fffff8a0`003ebb90 : 0xfffff880`031afb90
fffff880`031afaa0 00000000`001f01ff : fffff880`03f7c390 fffff800`031907c0 fffff8a0`003ebb90 00000000`00000000 : 0xfffff880`031afb98
fffff880`031afaa8 fffff880`03f7c390 : fffff800`031907c0 fffff8a0`003ebb90 00000000`00000000 00000000`00000000 : 0x1f01ff
fffff880`031afab0 fffff800`031907c0 : fffff8a0`003ebb90 00000000`00000000 00000000`00000000 fffff880`031afb90 : AppleCharger+0x3390
fffff880`031afab8 fffff8a0`003ebb90 : 00000000`00000000 00000000`00000000 fffff880`031afb90 fffff800`02f2f790 : nt!PnpDeviceClassNotifyList+0xa0
fffff880`031afac0 00000000`00000000 : 00000000`00000000 fffff880`031afb90 fffff800`02f2f790 00000000`00000202 : 0xfffff8a0`003ebb90
STACK_COMMAND: kb
FOLLOWUP_IP:
AppleCharger+1947
fffff880`03f7a947 ?? ???
SYMBOL_STACK_INDEX: 4
SYMBOL_NAME: AppleCharger+1947
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: AppleCharger
IMAGE_NAME: AppleCharger.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4bd65fdd
FAILURE_BUCKET_ID: X64_0x50_AppleCharger+1947
BUCKET_ID: X64_0x50_AppleCharger+1947
Followup: MachineOwner
---------