BSOD on Windows Start-up.


  1. SpringbokNZ
    Posts : 1
    Windows 7 Home x64
       New #1

    BSOD on Windows Start-up.


    Hi all,

    When I start my pc it will post but once the windows logo appears it goes to a blue (Green) screen and crashes. In the past it would only do this when I restarted from win desktop now it does it from a fresh start.
    I have attached my dump file for the info.
    Thank you in advance.
      My Computer
    Quote Quote

  3. Arc
    Posts : 35,373
    Microsoft Windows 10 Pro Insider Preview 64-bit
       New #2

    Hi SpringbokNZ.

    There are multiple issues. Display and network.

    For the network issue, download and install Drivers for Atheros AR922X and Windows 7. Follow Driver Install - Device Manager to install it. Then we have to observe if the network issue bounces back or not.

    For the display issue, better to go slowly. As you are getting BSODs, you should stop overclocking and run all the hardware components like CPU, GPU and RAM to their default settings.

    When done, stress test the Graphics Card using Furmark.Let us know the results.
    _________________________________________________
    Code:
    *******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck D1, {10, 2, 0, fffff880018cb566}

*** WARNING: Unable to verify timestamp for athrx.sys
*** ERROR: Module load completed but symbols could not be loaded for athrx.sys
Probably caused by : athrx.sys ( athrx+47677 )

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

0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high.  This is usually
caused by drivers using improper addresses.
If kernel debugger is available get stack backtrace.
Arguments:
Arg1: 0000000000000010, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
Arg4: fffff880018cb566, address which referenced memory

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


READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800026af100
GetUlongFromAddress: unable to read from fffff800026af1c0
 0000000000000010 Nonpaged pool

CURRENT_IRQL:  2

FAULTING_IP: 
ndis!NdisFreeTimerObject+16
fffff880`018cb566 488b5310        mov     rdx,qword ptr [rbx+10h]

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

BUGCHECK_STR:  0xD1

PROCESS_NAME:  System

ANALYSIS_VERSION: 6.3.9600.17237 (debuggers(dbg).140716-0327) amd64fre

TRAP_FRAME:  fffff880021a3770 -- (.trap 0xfffff880021a3770)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=fffff88001901ac8
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff880018cb566 rsp=fffff880021a3900 rbp=fffff8000261d280
 r8=0000000000011120  r9=0000000000000000 r10=fffff80002402000
r11=fffffa8008f72040 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na pe nc
ndis!NdisFreeTimerObject+0x16:
fffff880`018cb566 488b5310        mov     rdx,qword ptr [rbx+10h] ds:00000000`00000010=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002477169 to fffff80002477bc0

STACK_TEXT:  
fffff880`021a3628 fffff800`02477169 : 00000000`0000000a 00000000`00000010 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff880`021a3630 fffff800`02475de0 : 00d80104`100000d8 40000000`00008020 fffffa80`08f73000 00000000`00000000 : nt!KiBugCheckDispatch+0x69
fffff880`021a3770 fffff880`018cb566 : fffffa80`06d30660 00000000`000007ff fffffa80`08f72388 00000000`00000000 : nt!KiPageFault+0x260
fffff880`021a3900 fffff880`05098677 : fffffa80`08f72388 fffff880`0509134f fffff880`0517f588 fffff880`0517f578 : ndis!NdisFreeTimerObject+0x16
fffff880`021a3930 fffffa80`08f72388 : fffff880`0509134f fffff880`0517f588 fffff880`0517f578 00000000`00011120 : athrx+0x47677
fffff880`021a3938 fffff880`0509134f : fffff880`0517f588 fffff880`0517f578 00000000`00011120 fffff880`0507db83 : 0xfffffa80`08f72388
fffff880`021a3940 fffff880`0517f588 : fffff880`0517f578 00000000`00011120 fffff880`0507db83 fffffa80`08f722b8 : athrx+0x4034f
fffff880`021a3948 fffff880`0517f578 : 00000000`00011120 fffff880`0507db83 fffffa80`08f722b8 fffffa80`08820000 : athrx+0x12e588
fffff880`021a3950 00000000`00011120 : fffff880`0507db83 fffffa80`08f722b8 fffffa80`08820000 fffffa80`08418050 : athrx+0x12e578
fffff880`021a3958 fffff880`0507db83 : fffffa80`08f722b8 fffffa80`08820000 fffffa80`08418050 fffff880`05080d88 : 0x11120
fffff880`021a3960 fffffa80`08f722b8 : fffffa80`08820000 fffffa80`08418050 fffff880`05080d88 fffffa80`0882e030 : athrx+0x2cb83
fffff880`021a3968 fffffa80`08820000 : fffffa80`08418050 fffff880`05080d88 fffffa80`0882e030 fffff880`050805e9 : 0xfffffa80`08f722b8
fffff880`021a3970 fffffa80`08418050 : fffff880`05080d88 fffffa80`0882e030 fffff880`050805e9 fffffa80`08f72040 : 0xfffffa80`08820000
fffff880`021a3978 fffff880`05080d88 : fffffa80`0882e030 fffff880`050805e9 fffffa80`08f72040 00000000`00000000 : 0xfffffa80`08418050
fffff880`021a3980 fffffa80`0882e030 : fffff880`050805e9 fffffa80`08f72040 00000000`00000000 00000000`00000000 : athrx+0x2fd88
fffff880`021a3988 fffff880`050805e9 : fffffa80`08f72040 00000000`00000000 00000000`00000000 fffffa80`08f72010 : 0xfffffa80`0882e030
fffff880`021a3990 fffffa80`08f72040 : 00000000`00000000 00000000`00000000 fffffa80`08f72010 fffffa80`086ae240 : athrx+0x2f5e9
fffff880`021a3998 00000000`00000000 : 00000000`00000000 fffffa80`08f72010 fffffa80`086ae240 fffff880`05080589 : 0xfffffa80`08f72040


STACK_COMMAND:  kb

FOLLOWUP_IP: 
athrx+47677
fffff880`05098677 ??              ???

SYMBOL_STACK_INDEX:  4

SYMBOL_NAME:  athrx+47677

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: athrx

IMAGE_NAME:  athrx.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4a2ea4b9

FAILURE_BUCKET_ID:  X64_0xD1_athrx+47677

BUCKET_ID:  X64_0xD1_athrx+47677

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:x64_0xd1_athrx+47677

FAILURE_ID_HASH:  {e2448d56-6af4-b542-128b-9142b27237e9}

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

0: kd> lmvm athrx
start             end                 module name
fffff880`05051000 fffff880`051a9000   athrx    T (no symbols)           
    Loaded symbol image file: athrx.sys
    Image path: \SystemRoot\system32\DRIVERS\athrx.sys
    Image name: athrx.sys
    Timestamp:        Tue Jun 09 23:36:49 2009 (4A2EA4B9)
    CheckSum:         0015FE99
    ImageSize:        00158000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
    Code:
    *******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 116, {fffffa800e6c54e0, fffff88003e95f80, 0, d}

Unable to load image \SystemRoot\system32\DRIVERS\atikmpag.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for atikmpag.sys
*** ERROR: Module load completed but symbols could not be loaded for atikmpag.sys
Probably caused by : atikmpag.sys ( atikmpag+af80 )

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

0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

VIDEO_TDR_FAILURE (116)
Attempt to reset the display driver and recover from timeout failed.
Arguments:
Arg1: fffffa800e6c54e0, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff88003e95f80, The pointer into responsible device driver module (e.g. owner tag).
Arg3: 0000000000000000, Optional error code (NTSTATUS) of the last failed operation.
Arg4: 000000000000000d, Optional internal context dependent data.

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


FAULTING_IP: 
atikmpag+af80
fffff880`03e95f80 4883ec28        sub     rsp,28h

DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_TDR_FAULT

CUSTOMER_CRASH_COUNT:  1

BUGCHECK_STR:  0x116

PROCESS_NAME:  System

CURRENT_IRQL:  0

ANALYSIS_VERSION: 6.3.9600.17237 (debuggers(dbg).140716-0327) amd64fre

STACK_TEXT:  
fffff880`05d97758 fffff880`0450a134 : 00000000`00000116 fffffa80`0e6c54e0 fffff880`03e95f80 00000000`00000000 : nt!KeBugCheckEx
fffff880`05d97760 fffff880`04509ebb : fffff880`03e95f80 fffffa80`0e6c54e0 00000000`00000000 fffffa80`09083010 : dxgkrnl!TdrBugcheckOnTimeout+0xec
fffff880`05d977a0 fffff880`045b1f13 : fffffa80`0e6c54e0 00000000`00000000 00000000`00000000 fffffa80`09083010 : dxgkrnl!TdrIsRecoveryRequired+0x21f
fffff880`05d977d0 fffff880`045dfed6 : 00000000`00000000 00000000`0082dc10 fffff880`05d97930 fffffa80`09083010 : dxgmms1!VidSchiReportHwHang+0x40b
fffff880`05d978b0 fffff880`045db91a : fffffa80`09083010 ffffffff`feced300 00000000`00000002 fffff880`045ae2fe : dxgmms1!VidSchWaitForCompletionEvent+0x196
fffff880`05d978f0 fffff880`045da1b0 : fffffa80`09083010 00000000`00000002 fffff880`045d9f3c 00000000`00000000 : dxgmms1!VidSchiWaitForDrainFlipQueue+0x92
fffff880`05d979e0 fffff880`045da47a : 00000000`00000000 00000000`00000002 00000000`00000002 00000000`00000000 : dxgmms1!VidSchiHandleControlEvent+0x4c
fffff880`05d97a10 fffff880`045ad2d2 : ffffffff`ff676980 fffffa80`09083010 00000000`00000000 00000000`00000000 : dxgmms1!VidSchiWaitForSchedulerEvents+0x23e
fffff880`05d97ab0 fffff880`045d9ff6 : 00000000`00000000 fffffa80`0a14b190 00000000`00000080 fffffa80`09083010 : dxgmms1!VidSchiScheduleCommandToRun+0x1da
fffff880`05d97bc0 fffff800`0332173a : 00000000`fffffc32 fffffa80`092c6b50 fffffa80`06c779e0 fffffa80`092c6b50 : dxgmms1!VidSchiWorkerThread+0xba
fffff880`05d97c00 fffff800`030768e6 : fffff880`009ef180 fffffa80`092c6b50 fffff880`009f9fc0 fffffa80`08d9ac10 : nt!PspSystemThreadStartup+0x5a
fffff880`05d97c40 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND:  .bugcheck ; kb

FOLLOWUP_IP: 
atikmpag+af80
fffff880`03e95f80 4883ec28        sub     rsp,28h

SYMBOL_NAME:  atikmpag+af80

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: atikmpag

IMAGE_NAME:  atikmpag.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  53e96f06

FAILURE_BUCKET_ID:  X64_0x116_IMAGE_atikmpag.sys

BUCKET_ID:  X64_0x116_IMAGE_atikmpag.sys

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:x64_0x116_image_atikmpag.sys

FAILURE_ID_HASH:  {83e844bc-fe68-2042-4230-7f5d3e90b48a}

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

0: kd> lmvm atikmpag
start             end                 module name
fffff880`03e8b000 fffff880`03f19000   atikmpag T (no symbols)           
    Loaded symbol image file: atikmpag.sys
    Image path: \SystemRoot\system32\DRIVERS\atikmpag.sys
    Image name: atikmpag.sys
    Timestamp:        Tue Aug 12 07:03:58 2014 (53E96F06)
    CheckSum:         00091AAB
    ImageSize:        0008E000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
      My Computer
    Quote Quote

 

  Related Discussions
BSOD at start up Windows 10
in BSOD Help and Support

Hi I recently upgrade my pc to windows 10. I now get random BSOD at startup. When windows logo starts i get black screen on monitor, basicly monitor goes on sleep mode. After some time pc restart and then botup goes normal without BSOD. I think its my soundcard Asus Xonar D2X but i am not...
BSOD after Windows start-up
in BSOD Help and Support

Hey guys, hope you can help me. Blue screen appears right after the desktop starts loading. Safe mode worked fine until just now - whenever I try to open a page in a browser - it crashes again. Attached debug info. BugCheck 1E, {ffffffffc0000005, fffffa80056323ef, 0, fffa003c} BCCode: 1E BCP1:...
Hi guys, I encountered BSOD for the first time. Very annoying. Right now I have to run this on Safe Mode in order to access the internet. I also noticed I can't use Firefox right now, and instead am using iE. I couldn't run the the performance scan report either (time out?), but I did attach the...
BSOD mostly at windows start up
in BSOD Help and Support

i have installed a fresh copy of windows 7 32 bit...... every morning the cpu....gives a strange sound....i have cleaned the towers of cpu and power supply box.....one slap to the cpu stops the sound for few seconds......and it crashes.....BSOD......kindly help...... Dump files are...
BSOD on windows 7 start up
in BSOD Help and Support

Hey guys Having some problems with my computer blue screening on me when it goes to launch the OS (this problem happens before I make it to the log in screen). Usually it goes to a system repair and then asks me to do a system restore. I dont have to actually do a system restore and it normally...
Our Sites
Site Links
About 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 03:26.
Find Us