BSOD occurring during boot


  1. Posts : 5
    Windows 7 Professional K 64bit
       #1

    BSOD occurring during boot


    Hello. I am getting frequent BSOD during boot, usually after the Windows logo appears. The computer is fine when it loads, it is only during the boot that this is happening. Any help is greatly appreciated, thank you.

    My computer/windows specs are:

    Windows 7 Professional K Service Pack 1 (64bit)
    Intel(R) Core(TM) i3-2100 CPU @ 3.10GHZ
    RAM is 4.00GB

    Please help!
    Last edited by hkim175; 24 Jan 2012 at 02:50.
      My Computer


  2. Posts : 5
    Windows 7 Professional K 64bit
    Thread Starter
       #2

    Are there any methods available to solve this?
      My Computer


  3. Posts : 11,269
    Windows 7 Home Premium 64 Bit
       #3

    Code:
    
    Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
    Copyright (c) Microsoft Corporation. All rights reserved.
    
    
    Loading Dump File [J:\BSODDmpFiles\hkim175\012212-19437-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available
    
    Symbol search path is: SRV*c:\users\mike\documents\symbols*http://msdl.microsoft.com/download/symbols
    Executable search path is: 
    Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
    Machine Name:
    Kernel base = 0xfffff800`03266000 PsLoadedModuleList = 0xfffff800`034ab670
    Debug session time: Sat Jan 21 17:29:25.043 2012 (UTC - 7:00)
    System Uptime: 0 days 0:00:22.292
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    ............
    Loading User Symbols
    Loading unloaded module list
    .......
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 116, {fffffa8006441010, fffff8800e97c9c8, 0, 2}
    
    Unable to load image \SystemRoot\system32\DRIVERS\nvlddmkm.sys, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for nvlddmkm.sys
    *** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
    Probably caused by : nvlddmkm.sys ( nvlddmkm+1759c8 )
    
    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: fffffa8006441010, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
    Arg2: fffff8800e97c9c8, The pointer into responsible device driver module (e.g. owner tag).
    Arg3: 0000000000000000, Optional error code (NTSTATUS) of the last failed operation.
    Arg4: 0000000000000002, Optional internal context dependent data.
    
    Debugging Details:
    ------------------
    
    
    FAULTING_IP: 
    nvlddmkm+1759c8
    fffff880`0e97c9c8 4883ec28        sub     rsp,28h
    
    DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_TDR_FAULT
    
    CUSTOMER_CRASH_COUNT:  1
    
    BUGCHECK_STR:  0x116
    
    PROCESS_NAME:  System
    
    CURRENT_IRQL:  0
    
    STACK_TEXT:  
    fffff880`034e8888 fffff880`0f4e0000 : 00000000`00000116 fffffa80`06441010 fffff880`0e97c9c8 00000000`00000000 : nt!KeBugCheckEx
    fffff880`034e8890 fffff880`0f4dfd0a : fffff880`0e97c9c8 fffffa80`06441010 fffffa80`0609fd50 fffffa80`06089410 : dxgkrnl!TdrBugcheckOnTimeout+0xec
    fffff880`034e88d0 fffff880`0f586f07 : fffffa80`06441010 00000000`00000000 fffffa80`0609fd50 fffffa80`06089410 : dxgkrnl!TdrIsRecoveryRequired+0x1a2
    fffff880`034e8900 fffff880`0f5b0b75 : 00000000`ffffffff 00000000`000004d7 00000000`00000000 00000000`00000002 : dxgmms1!VidSchiReportHwHang+0x40b
    fffff880`034e89e0 fffff880`0f5af2bb : 00000000`00000102 00000000`00000000 00000000`000004d7 00000000`00000000 : dxgmms1!VidSchiCheckHwProgress+0x71
    fffff880`034e8a10 fffff880`0f5822c6 : ffffffff`ff676980 fffffa80`06089410 00000000`00000000 00000000`00000000 : dxgmms1!VidSchiWaitForSchedulerEvents+0x1fb
    fffff880`034e8ab0 fffff880`0f5aee7a : 00000000`00000000 00000000`0000000f 00000000`00000080 fffffa80`058d3c68 : dxgmms1!VidSchiScheduleCommandToRun+0x1da
    fffff880`034e8bc0 fffff800`0357dfee : 00000000`02fd0555 fffffa80`061b6b60 fffffa80`03c585f0 fffffa80`061b6b60 : dxgmms1!VidSchiWorkerThread+0xba
    fffff880`034e8c00 fffff800`032d45e6 : fffff800`03458e80 fffffa80`061b6b60 fffff800`03466cc0 fffff880`01219384 : nt!PspSystemThreadStartup+0x5a
    fffff880`034e8c40 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16
    
    
    STACK_COMMAND:  .bugcheck ; kb
    
    FOLLOWUP_IP: 
    nvlddmkm+1759c8
    fffff880`0e97c9c8 4883ec28        sub     rsp,28h
    
    SYMBOL_NAME:  nvlddmkm+1759c8
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: nvlddmkm
    
    IMAGE_NAME:  nvlddmkm.sys
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  4e99233b
    
    FAILURE_BUCKET_ID:  X64_0x116_IMAGE_nvlddmkm.sys
    
    BUCKET_ID:  X64_0x116_IMAGE_nvlddmkm.sys
    
    Followup: MachineOwner
    ---------
    There are a lot of methods for solving this. Start by closely following the first three posts of STOP 0x116: VIDEO_TDR_ERROR troubleshooting and proceed through each step. Let us know if you need further help.
      My Computer


  4. Posts : 5
    Windows 7 Professional K 64bit
    Thread Starter
       #4

    Thank you for the reply. I will go through the steps. Thanks again~
      My Computer


  5. Posts : 11,269
    Windows 7 Home Premium 64 Bit
       #5

    Alright, let us know if you need any help with the steps or after you are done. Also let us know if you determine the problem. Best wishes!



    Did the TDR explanation and troubleshooting steps help?
    Last edited by writhziden; 16 Feb 2012 at 00:55. Reason: TDR help?
      My Computer


  6. Posts : 5
    Windows 7 Professional K 64bit
    Thread Starter
       #6

    Yes I read through the troubleshooting steps and found out that my video card as well as the hard drive was faulty. I have now replaced them and now the computer is BSOD-free!

    Thank you for your help. This took a while for me because trying to save up for the replacements!
      My Computer


  7. Posts : 5
    Windows 7 Professional K 64bit
    Thread Starter
       #7

    New BSOD: (During computer use)


    I have experienced another BSOD, this time while I was using the computer.
    When I was using the computer like any other day, I noticed it was running slower that it used to and suddenly crashed and got a BSOD.
    After the crash the computer periodically pauses for a second.
    Also I have a caution notice under 'Current Pending Sector Count' when I ran CrystalDiskInfo. Does this have anything to do with the BSOD?
    Please help!
      My Computer


 

  Related Discussions
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 10:58.
Find Us