BSOD after new windows installation. nvlddmkm.sys and ntoskrnl.exe

Page 1 of 2 12 LastLast

  1. Posts : 33
    Windows 7 x64
       #1

    BSOD after new windows installation. nvlddmkm.sys and ntoskrnl.exe


    Installed windows yesterday and today I got 4 BSODs. I run whocrashed and three of them say ntoskrnl.exe and one nvlddmkm.sys but I couldn't find the solution googling. I'm attaching the minidumps. Thank you
      My Computer


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


  3. Posts : 33
    Windows 7 x64
    Thread Starter
       #3

    Uploaded. Sorry for that.
      My Computer


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

    You need to uninstall AVG.
    Code:
    fffff880`033852b8  fffff880`041ae545Unable to load image \SystemRoot\system32\DRIVERS\avgtdia.sys, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for avgtdia.sys
    *** ERROR: Module load completed but symbols could not be loaded for avgtdia.sys
     avgtdia+0x2d545
    Uninstall AVG. Use Microsoft Security Essentials as your antivirus with windows inbuilt firewall, and free MBAM as the on demand scanner.
    Download, install and update those, and then run full system scans with both of them, one by one.

    Well, you need to perform deeper scans for virus. Atatprt.sys is most vulnerable to rootkits.
    Code:
    fffff880`033851e0  fffff880`0114f1a0 ataport!WPP_MAIN_CB
    Scan the system for possible virus infection with the following programs.


    Update the network driver from Realtek ..... get the Win7 and WinServer 2008 R2 Auto Installation Program dated 2013/9/24.

    Let us know the results.

    If the crashes continue to occur, we will search for AVG leftovers in the system, as AVG leftovers are as harmful as AVG itself.
      My Computer


  5. Posts : 33
    Windows 7 x64
    Thread Starter
       #5

    Thank you. Will let you know if I get a bsod.
      My Computer


  6. Posts : 33
    Windows 7 x64
    Thread Starter
       #6

    Thank you. Will let you know if I get a bsod.
      My Computer


  7. Posts : 33
    Windows 7 x64
    Thread Starter
       #7

    No bsod yet but today the computer froze completely without getting a BSOD and I had to manually reset. What do I do?
      My Computer


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

    If you get any further BSOD , let us know.
      My Computer


  9. Posts : 33
    Windows 7 x64
    Thread Starter
       #9

    Got another bsod today after 3 days.
      My Computer


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

    It is a different BSOD. A stop 0x116, a display/graphics issue.

    Install the NVIDIA DRIVERS 314.22WHQL only.

    • Uninstall All nvidia items in Control Panel > Programs and features
      • 3D Vision Control Driver
      • 3D Vision Driver
      • Graphics Driver
      • HD Audio Driver
      • PhysX
      • nvidia Update

      (Are you using nvidia chipset drivers? If so, dont uninstall anything other than those are listed).
    • Now follow Drivers - Clean Left over Files after Uninstalling
    • Download 314.22 WHQL. While installing, Select Custom (Advanced) install. In the next page, follow this settings:


    Are you overclocking?
    Code:
    CPUID:        "Intel(R) Core(TM) i7 CPU       K 875  @ 2.93GHz"
    MaxSpeed:     2930
    CurrentSpeed: 2942
    As you are getting BSODs, you should stop overclocking and run all the hardware components like CPU, GPU and RAM to their default settings.

    Stress test the Graphics Card using Furmark.
    Video Card - Stress Test with Furmark

    Check if the Power Supply Unit (PSU) supplying adequate power to the computer or not.
    eXtreme Power Supply Calculator

    Is the computer hot? Report us the heat of the computer after a couple of hours of your normal usage. Upload a screenshot of the summery tab of Speccy.

    Let us know the results.
    Code:
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 116, {fffffa800a875010, fffff8800f1be084, ffffffffc00000b5, a}
    
    *** 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+153084 )
    
    Followup: MachineOwner
    ---------
    
    4: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    VIDEO_TDR_FAILURE (116)
    Attempt to reset the display driver and recover from timeout failed.
    Arguments:
    Arg1: fffffa800a875010, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
    Arg2: fffff8800f1be084, The pointer into responsible device driver module (e.g. owner tag).
    Arg3: ffffffffc00000b5, Optional error code (NTSTATUS) of the last failed operation.
    Arg4: 000000000000000a, Optional internal context dependent data.
    
    Debugging Details:
    ------------------
    
    
    FAULTING_IP: 
    nvlddmkm+153084
    fffff880`0f1be084 803d5ec4720000  cmp     byte ptr [nvlddmkm+0x87f4e9 (fffff880`0f8ea4e9)],0
    
    DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_TDR_FAULT
    
    CUSTOMER_CRASH_COUNT:  1
    
    BUGCHECK_STR:  0x116
    
    PROCESS_NAME:  System
    
    CURRENT_IRQL:  0
    
    STACK_TEXT:  
    fffff880`0539c9c8 fffff880`0fcf5140 : 00000000`00000116 fffffa80`0a875010 fffff880`0f1be084 ffffffff`c00000b5 : nt!KeBugCheckEx
    fffff880`0539c9d0 fffff880`0fcf4f1b : fffff880`0f1be084 fffffa80`0a875010 00000000`00000000 fffffa80`09a0e410 : dxgkrnl!TdrBugcheckOnTimeout+0xec
    fffff880`0539ca10 fffff880`0fd9bf13 : fffffa80`0a875010 00000000`c00000b5 00000000`00000000 fffffa80`09a0e410 : dxgkrnl!TdrIsRecoveryRequired+0x273
    fffff880`0539ca40 fffff880`0fdc5d50 : fffffa80`00000000 00000000`0002d252 00000000`00000000 00000000`00000002 : dxgmms1!VidSchiReportHwHang+0x40b
    fffff880`0539cb20 fffff880`0fdc4437 : 00000000`00000102 00000000`00000000 00000000`0002d252 00000000`00000000 : dxgmms1!VidSchiCheckHwProgress+0xd0
    fffff880`0539cb50 fffff880`0fd972d2 : ffffffff`ff676980 fffffa80`09a0e410 00000000`00000000 00000000`00000000 : dxgmms1!VidSchiWaitForSchedulerEvents+0x1fb
    fffff880`0539cbf0 fffff880`0fdc3ff6 : 00000000`00000000 fffffa80`0a203d50 00000000`00000080 fffffa80`09a0e410 : dxgmms1!VidSchiScheduleCommandToRun+0x1da
    fffff880`0539cd00 fffff800`02f7a2ea : 00000000`03c1316d fffffa80`097318b0 fffffa80`06707990 fffffa80`097318b0 : dxgmms1!VidSchiWorkerThread+0xba
    fffff880`0539cd40 fffff800`02cce8e6 : fffff800`02e58e80 fffffa80`097318b0 fffff800`02e66cc0 fffff800`02ce9454 : nt!PspSystemThreadStartup+0x5a
    fffff880`0539cd80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16
    
    
    STACK_COMMAND:  .bugcheck ; kb
    
    FOLLOWUP_IP: 
    nvlddmkm+153084
    fffff880`0f1be084 803d5ec4720000  cmp     byte ptr [nvlddmkm+0x87f4e9 (fffff880`0f8ea4e9)],0
    
    SYMBOL_NAME:  nvlddmkm+153084
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: nvlddmkm
    
    IMAGE_NAME:  nvlddmkm.sys
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  525da526
    
    FAILURE_BUCKET_ID:  X64_0x116_IMAGE_nvlddmkm.sys
    
    BUCKET_ID:  X64_0x116_IMAGE_nvlddmkm.sys
    
    Followup: MachineOwner
    ---------
    
    4: kd> lmvm nvlddmkm
    start             end                 module name
    fffff880`0f06b000 fffff880`0fc98000   nvlddmkm T (no symbols)           
        Loaded symbol image file: nvlddmkm.sys
        Image path: \SystemRoot\system32\DRIVERS\nvlddmkm.sys
        Image name: nvlddmkm.sys
        Timestamp:        Wed Oct 16 01:57:18 2013 (525DA526)
        CheckSum:         00C04839
        ImageSize:        00C2D000
        Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
      My Computer


 
Page 1 of 2 12 LastLast

  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 04:31.
Find Us