BSOD after installing fresh windows, caused by what seem ntoskrnl.exe

DurtyGemini · 02 Nov 2014

so i was reading up on it, and it was saying that a short in my keyboard could be the problem? so far it seems to be the same bug check code. and bug check string, but im not sure what to do with this information? i've attached all my information.

koolkat77 · 04 Nov 2014

Uninstall all gigabyte related software and see if you still get BSOD's. Driver Reference Table

Use Revo Uninstaller to uninstall stubborn software. Opt for Advance Mode while uninstalling which allows you to remove leftover registry:-

Download Revo Uninstaller Freeware - Free and Full Download - Uninstall software, remove programs, solve uninstall problems

Code:


Microsoft (R) Windows Debugger Version 6.2.9200.20512 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\USER\Downloads\Compressed\SF_02-11-2014\110214-68858-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
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.18409.amd64fre.win7sp1_gdr.140303-2144
Machine Name:
Kernel base = 0xfffff800`02a16000 PsLoadedModuleList = 0xfffff800`02c59890
Debug session time: Sun Nov  2 16:42:19.961 2014 (UTC + 6:00)
System Uptime: 0 days 0:02:24.726
Loading Kernel Symbols
...............................................................
................................................................
..........................
Loading User Symbols
Loading unloaded module list
..........................
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 50, {ffffffffffffffd0, 1, fffff80002a94dac, 0}

*** WARNING: Unable to verify timestamp for UsbCharger.sys
*** ERROR: Module load completed but symbols could not be loaded for UsbCharger.sys

Could not read faulting driver name
Probably caused by : UsbCharger.sys ( UsbCharger+1681 )

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: fffff80002a94dac, If non-zero, the instruction address which referenced the bad memory
	address.
Arg4: 0000000000000000, (reserved)

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


Could not read faulting driver name

OVERLAPPED_MODULE: Address regions for 'kbdhid' and 'usbccgp.sys' overlap

WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff80002cc3100
GetUlongFromAddress: unable to read from fffff80002cc31c0
 ffffffffffffffd0 

FAULTING_IP: 
nt!ObfDereferenceObject+2c
fffff800`02a94dac f0480fc11f      lock xadd qword ptr [rdi],rbx

MM_INTERNAL_CODE:  0

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

BUGCHECK_STR:  0x50

PROCESS_NAME:  System

CURRENT_IRQL:  0

TRAP_FRAME:  fffff88003362790 -- (.trap 0xfffff88003362790)
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=fffff80002a94dac rsp=fffff88003362920 rbp=0000000000000020
 r8=fffffa800f4959c0  r9=fffffa800ca46ce8 r10=fffffa800ca5ec80
r11=fffff88003362970 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na po nc
nt!ObfDereferenceObject+0x2c:
fffff800`02a94dac f0480fc11f      lock xadd qword ptr [rdi],rbx ds:00000000`00000000=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002b09bf0 to fffff80002a8bbc0

STACK_TEXT:  
fffff880`03362628 fffff800`02b09bf0 : 00000000`00000050 ffffffff`ffffffd0 00000000`00000001 fffff880`03362790 : nt!KeBugCheckEx
fffff880`03362630 fffff800`02a89cee : 00000000`00000001 ffffffff`ffffffd0 00000000`00000000 ffffffff`ffffffff : nt! ?? ::FNODOBFM::`string'+0x4518f
fffff880`03362790 fffff800`02a94dac : 00000000`00000000 00000000`00000410 00000000`00000001 00000000`00000030 : nt!KiPageFault+0x16e
fffff880`03362920 fffff880`02dd5681 : 00000000`00000020 00000000`c0000034 fffffa80`0e782470 fffffa80`0e782470 : nt!ObfDereferenceObject+0x2c
fffff880`03362980 00000000`00000020 : 00000000`c0000034 fffffa80`0e782470 fffffa80`0e782470 fffff880`03362a98 : UsbCharger+0x1681
fffff880`03362988 00000000`c0000034 : fffffa80`0e782470 fffffa80`0e782470 fffff880`03362a98 fffff880`02dd5790 : 0x20
fffff880`03362990 fffffa80`0e782470 : fffffa80`0e782470 fffff880`03362a98 fffff880`02dd5790 fffff880`03362b40 : 0xc0000034
fffff880`03362998 fffffa80`0e782470 : fffff880`03362a98 fffff880`02dd5790 fffff880`03362b40 fffff800`03002b7f : 0xfffffa80`0e782470
fffff880`033629a0 fffff880`03362a98 : fffff880`02dd5790 fffff880`03362b40 fffff800`03002b7f 00000000`00000000 : 0xfffffa80`0e782470
fffff880`033629a8 fffff880`02dd5790 : fffff880`03362b40 fffff800`03002b7f 00000000`00000000 00000000`00000001 : 0xfffff880`03362a98
fffff880`033629b0 fffff880`03362b40 : fffff800`03002b7f 00000000`00000000 00000000`00000001 fffff800`02f597c0 : UsbCharger+0x1790
fffff880`033629b8 fffff800`03002b7f : 00000000`00000000 00000000`00000001 fffff800`02f597c0 fffff800`02cf7300 : 0xfffff880`03362b40
fffff880`033629c0 fffff880`03362a90 : 00000000`00000000 00000000`00000000 fffff8a0`02000000 fffff8a0`03c1bb20 : hal!HalSendSoftwareInterrupt+0x48
fffff880`033629f0 00000000`00000000 : 00000000`00000000 fffff8a0`02000000 fffff8a0`03c1bb20 00000000`00000000 : 0xfffff880`03362a90


STACK_COMMAND:  kb

FOLLOWUP_IP: 
UsbCharger+1681
fffff880`02dd5681 ??              ???

SYMBOL_STACK_INDEX:  4

SYMBOL_NAME:  UsbCharger+1681

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: UsbCharger

IMAGE_NAME:  UsbCharger.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  5268e7d3

FAILURE_BUCKET_ID:  X64_0x50_UsbCharger+1681

BUCKET_ID:  X64_0x50_UsbCharger+1681

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

4: kd> lmvm UsbCharger
start             end                 module name
fffff880`02dd4000 fffff880`02ddc000   UsbCharger T (no symbols)           
    Loaded symbol image file: UsbCharger.sys
    Image path: \SystemRoot\system32\DRIVERS\UsbCharger.sys
    Image name: UsbCharger.sys
    Timestamp:        Thu Oct 24 15:26:43 2013 (5268E7D3)
    CheckSum:         00009792
    ImageSize:        00008000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4