Windows 7 Forums
Welcome to Windows 7 Forums. Our forum is dedicated to helping you find support and solutions for any problems regarding your Windows 7 PC be it Dell, HP, Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.

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

02 Nov 2014   #1

Windows 7 Professional x64 SP1
BSOD after installing fresh windows, caused by what seem ntoskrnl.exe

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.

My System SpecsSystem Spec
04 Nov 2014   #2

Microsoft Community Contributor Award Recipient

Windows 10 Home 64Bit

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:-

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*
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                                    *
*                                                                             *

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.
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
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

fffff800`02a94dac f0480fc11f      lock xadd qword ptr [rdi],rbx







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
fffff800`02a94dac f0480fc11f      lock xadd qword ptr [rdi],rbx ds:00000000`00000000=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002b09bf0 to fffff80002a8bbc0

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


fffff880`02dd5681 ??              ???


SYMBOL_NAME:  UsbCharger+1681

FOLLOWUP_NAME:  MachineOwner


IMAGE_NAME:  UsbCharger.sys


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
My System SpecsSystem Spec

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

Thread Tools

Similar help and support threads
Thread Forum
Random BSOD after installing new components/fresh install of Windows
Hey, I have been asked by a friend to help with their BSOD issues and am having trouble finding the cause, they have just recently upgraded their Motherboard, CPU as well as installing a new SSD and HDD, they received the first BSOD about 2 days after re installing windows after installing the...
BSOD Help and Support
BSOD after installing new hard drive and fresh copy of Windows 7
I have a HP Envy 14 running Windows Home Premium. Over the past few months I was receiving a BSOD 1-2 times a day on average. A few days ago my hard disk burnt out and yesterday I installed a new hard drive with a fresh copy of Windows 7 on it. Today I again received a BSOD with this error report:...
BSOD Help and Support
BSOD when start windows, error 0x0000006b,caused by driver ntoskrnl.ex
Hi, I need your help, got startup problem like in title. Computer works, but when I tried to reboot, the BSOD comes out and I must start system using my backup file. Please help or comments. I don't know how to change that driver file or disable it. I think it may works.. Thx for everything
BSOD Help and Support
BSOD ntoskrnl.exe fresh windows 7 install
Hey guys, I have been having a problem with blue screens on this computer for a few weeks now. I finally got frustrated with it yesterday and reinstalled windows 7. The issues would happen any time I ran windows update. To fix it, I would have to restore to the oldest possible point, run the...
BSOD Help and Support
frequent BSOD caused by ntoskrnl.exe and many others on windows 7
Hi. i just want to ask for help on how to solve random blue screen of deaths on my newly purchased netbook. if i'm not mistaken it is caused by these drivers: ntoskrnl.exe and ntfs.sys ; i don't know to fix the problem. i've already brought it back where i purchased it and they sent it on repair...
BSOD Help and Support

Our Sites

Site Links

About Us

Find Us

Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd

All times are GMT -5. The time now is 17:18.
Twitter Facebook Google+ Seven Forums iOS App Seven Forums Android App