Bsod page_fault_in_nonpaged_area

thank you for your help, but i'm starting to believe it's a hardware problem and not software... If you check my initial post, i have already formatted once the computer and performed a very thorough and clean setup (installing only windows updates and driver updates at first), and i had 2 BSOD... I will take it back to the store and ask them to check all hardware components... Thank you for your time :)

Thank you for keeping us updated.
Good luck.

umm.. is anyone listening to me? This is your problem!!

applecharger.sys is bluescreening your PC

download and run the gigabyte charger on/off utility and turn the charging utility OFF! http://download.gigabyte.us/FileList...el-7series.exe

event3horizon said:

umm.. is anyone listening to me? This is your problem!!

applecharger.sys is bluescreening your PC

download and run the gigabyte charger on/off utility and turn the charging utility OFF! http://download.gigabyte.us/FileList...el-7series.exe

And your proof is? What tool did you use to find this? You cant just throw out "this is your problem" unless you can back it up.

Perhaps that is why now one is listening.

zigzag3143 said:

event3horizon said:

umm.. is anyone listening to me? This is your problem!!

applecharger.sys is bluescreening your PC

download and run the gigabyte charger on/off utility and turn the charging utility OFF! http://download.gigabyte.us/FileList...el-7series.exe

And your proof is? What tool did you use to find this? You cant just throw out "this is your problem" unless you can back it up.

Perhaps that is why now one is listening.

Proof is dump file.

Could not read faulting driver name
Probably caused by : AppleCharger.sys ( AppleCharger+1a93 )

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

4: 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: fffff80002ceae4c, 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 fffff80002f13100
ffffffffffffffd0

FAULTING_IP:
nt!ObfDereferenceObject+2c
fffff800`02ceae4c 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: fffff880033857a0 -- (.trap 0xfffff880033857a0)
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=fffff80002ceae4c rsp=fffff88003385930 rbp=0000000000000020
r8=fffffa8009103680 r9=fffffa8006a01248 r10=fffffa8006a355b0
r11=fffff88003385980 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei ng nz na po nc
nt!ObfDereferenceObject+0x2c:
fffff800`02ceae4c f0480fc11f lock xadd qword ptr [rdi],rbx ds:0010:00000000`00000000=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER: from fffff80002c8e25c to fffff80002ce1c80

STACK_TEXT:
fffff880`03385638 fffff800`02c8e25c : 00000000`00000050 ffffffff`ffffffd0 00000000`00000001 fffff880`033857a0 : nt!KeBugCheckEx
fffff880`03385640 fffff800`02cdfdae : 00000000`00000001 ffffffff`ffffffd0 fffff6fb`7ea00200 ffffffff`ffffffff : nt! ?? ::FNODOBFM::`string'+0x456cf
fffff880`033857a0 fffff800`02ceae4c : fffff8a0`07c0ee50 fffff880`03385b40 fffff880`03385a98 fffff800`00000030 : nt!KiPageFault+0x16e
fffff880`03385930 fffff880`041a7a93 : 00000000`00000020 fffff880`03385a98 00000000`001f01ff fffff880`041a91c0 : nt!ObfDereferenceObject+0x2c
fffff880`03385990 00000000`00000020 : fffff880`03385a98 00000000`001f01ff fffff880`041a91c0 fffff800`031ab7c0 : AppleCharger+0x1a93
fffff880`03385998 fffff880`03385a98 : 00000000`001f01ff fffff880`041a91c0 fffff800`031ab7c0 fffff8a0`0054c9d0 : 0x20
fffff880`033859a0 00000000`001f01ff : fffff880`041a91c0 fffff800`031ab7c0 fffff8a0`0054c9d0 00000000`00000000 : 0xfffff880`03385a98
fffff880`033859a8 fffff880`041a91c0 : fffff800`031ab7c0 fffff8a0`0054c9d0 00000000`00000000 00000000`00000000 : 0x1f01ff
fffff880`033859b0 fffff800`031ab7c0 : fffff8a0`0054c9d0 00000000`00000000 00000000`00000000 fffff880`03385a90 : AppleCharger+0x31c0
fffff880`033859b8 fffff8a0`0054c9d0 : 00000000`00000000 00000000`00000000 fffff880`03385a90 fffff800`02f4b89c : nt!PnpDeviceClassNotifyList+0xa0
fffff880`033859c0 00000000`00000000 : 00000000`00000000 fffff880`03385a90 fffff800`02f4b89c 00000000`00000202 : 0xfffff8a0`0054c9d0


STACK_COMMAND: kb

FOLLOWUP_IP:
AppleCharger+1a93
fffff880`041a7a93 ?? ???

SYMBOL_STACK_INDEX: 4

SYMBOL_NAME: AppleCharger+1a93

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: AppleCharger

IMAGE_NAME: AppleCharger.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 4d2ad809

FAILURE_BUCKET_ID: X64_0x50_AppleCharger+1a93

BUCKET_ID: X64_0x50_AppleCharger+1a93

Followup: MachineOwner

thank you for trying to help, but just to be safe, i will return it to them and ask for a full hardware and software check...

gkouk said:

thank you for trying to help, but just to be safe, i will return it to them and ask for a full hardware and software check...

You are welcome.
Good luck.
Would be interesting to know the result.

event3horizon

Of the 4 DMPS three were driver verified and pointed elsewhere, one mentions Applecharger and says "could not read faulting driver name".

Which would you believe?

Since Applecharger is only mentioned in one as "probably caused by" and since the others (which were verified and in the stack at the right point) I would tend to believe the latter.

One offs (especially non verified ones) happen all the time and are usually discounted.

Thanks for posting the info but please add the top of the DMPS in the future so we know what DMP you have read without having to WDB all of them.

If I could rep, I would rep you on this.

Ok I appreciate it thanks. I will back up my analysis next time. I didn't know the "probably caused" wasn't counted but I'd rather have some clue than no clue if I had those bsod's.

Good Job anyway. Its always good to have another set of eyes and welcome to BSOD.