BSOD Error: Faulty driver on the kernal stack

Page 1 of 3 123 LastLast

  1. Posts : 12
    Windows 7 Home Premium x64
       #1

    BSOD Error: Faulty driver on the kernal stack


    Hi guys,

    First post here, as I've looked on the internet for a couple of weeks now and not found a definitive solution to my problem. About a month ago I was having problems with my drivers whereby I was crashing in games and sometimes even browsing the internet with a couple of tabs. The game would freeze up and then the graphics card would restore itself, but crash the game. This was usually followed by the blue screen error I am getting now soon afterwards. I have done a fresh reinstall of Windows 7 and it has been working fine up until two weeks ago whereby I get sporadic blue screens that occur whether I am on a game, have Chrome open or if I'm literally just sitting on my desktop doing nothing. So far I have tried disabling and deleting the currents settings for the Driver Verifier, but has done nothing. I am open to any suggestions or ways around this.

    As a side note, sometimes when I blue screen my computer will reboot but the monitor will not load up properly. I am forced to manually switch off the computer, unplug the cable and hold the power button down for a while before plugging it back in and booting it up again, however this only happens half of the time. I have no idea what causes this.

    Thanks!

    -As a side note, if there are any files that I need to attach, I should be able to provide them. I have attempted to attach one of my crash dumps to this post but cannot get permission to access it (even after changing the permissions under its properties). Please note that I am by no means an expert with computers, so if any technical jargon could be put into simplified terms that would be very much appreciated. Thanks again!
    Last edited by Jmainsley; 20 May 2013 at 12:48. Reason: Included a new version of my crash dump.zip
      My Computer


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


  3. Posts : 12
    Windows 7 Home Premium x64
    Thread Starter
       #3

    Sorry for that, was unaware of the formatting. I've added my .zip into the post.
      My Computer


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

    The zip you uploaded does not contain any crash dump. There are no event log files, too. First check in C:\Windows\Minidump. Is there anything in the folder? If so, copy them to desktop, zip them and upload in the next post.

    Follow it: Dump Files - Configure Windows to Create on BSOD
    Go to Option Two, Point 2. Download the .reg file and merge it in registry by double clicking it.

    Now wait for another BSOD. When it occurred, search the .dmp files manually in the default path: C:\Windows\Minidump or %SystemRoot%\Minidump. See if the crash dump is recorded or not (hopefully it will be recorded).Post it following the Blue Screen of Death (BSOD) Posting Instructions.

    Dont run any disc cleanup program before you upload another zip, as those programs clean up the minidump folder.
      My Computer


  5. Posts : 12
    Windows 7 Home Premium x64
    Thread Starter
       #5

    Sorry to pain you, but as mentioned before I cannot add them to the .zip or attach them as I don't have sufficient permission despite having set my account to the owner of the dump file and having full permissions. If I unzip the file I submitted, add them in and try to zip it again it comes up with an error stating that "File not found or no read permission"
      My Computer


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

    Can you copy them dump files to desktop?

    When those files are on desktop, zip them.
      My Computer


  7. Posts : 12
    Windows 7 Home Premium x64
    Thread Starter
       #7

    I can copy the files to the desktop with admin permission (myself). When I try to zip them I get the "File not found or no read permission" error
      My Computer


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

    Run the SF diag tools once again, and run it as administrator. It should gram all the files.

    Also try the files on the desktop . Right click on them > properties .... see at the attributes. If the "read only" is checked, uncheck it, apply, ok. Then try to zip those again.
      My Computer


  9. Posts : 12
    Windows 7 Home Premium x64
    Thread Starter
       #9

    Ok, running the SF Diag tool in Admin mode worked fine. The DMP files should be included now. Sorry for the hassle.
      My Computer


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

    It's a driver bug. That version of display driver you have installed is bad.

    The BSOD indicates , as the computer things, it is driver verifier enabled.
    Code:
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck C4, {91, 2, fffffa8008f00b50, 0}
    
    *** 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+1b775d )
    
    Followup: MachineOwner
    ---------
    Whereas Driver verifier is not enabled actually. See it:
    Code:
    DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
    If driver verifier is enabled, the value would have been : Verifier_ Enabled_Vista_Minidump.

    Let us see what is said there in the parameters ....
    Code:
    Arguments:
    Arg1: 0000000000000091, A driver switched stacks using a method that is not supported by
        the operating system. The only supported way to extend a kernel
        mode stack is by using KeExpandKernelStackAndCallout.
    Arg2: 0000000000000002
    Arg3: fffffa8008f00b50
    Arg4: 0000000000000000
    And which is the misbehaving driver? It is the display driver.
    Code:
    Probably caused by : nvlddmkm.sys ( nvlddmkm+1b775d )
    In such a situation let us try to remove the display driver totally from the system, and try another one. At first, let us go with the latest WHQL driver.

    • 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
    • Boot normally now. Go to Drivers - Download NVIDIA Drivers, Download 314.22 WHQL. While installing, Select Custom (Advanced) install. In the next page, follow this settings:


    When done, observe the situation. Observe how it is running. Let us know the results.
      My Computer


 
Page 1 of 3 123 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 12:41.
Find Us