Windows 10: BSODs trying to update graphics driver

Page 2 of 3 FirstFirst 123 LastLast

  1. Posts : 5,012
    Windows 10 Pro X64 15063.138
       11 Jul 2016 #11

    I have a Realtek HD Audio device to, so I installed the latest WHQL driver.
    The first time I ran setup.exe it went through some of the install then had to restart, I believe what it did was uninstall the current driver.
    After the reboot, it did the install again without me doing anything and this time did the full install. One more reboot and all is well. Sounds works and I'm now at the 6.0.1.7874 7/6/2016 version.
      My ComputersSystem Spec


  2. Posts : 11
    Windows 10 Pro 10.0.10586 Build 10586
    Thread Starter
       11 Jul 2016 #12

    Ztruker said: View Post
    I have a Realtek HD Audio device to, so I installed the latest WHQL driver.
    The first time I ran setup.exe it went through some of the install then had to restart, I believe what it did was uninstall the current driver.
    After the reboot, it did the install again without me doing anything and this time did the full install. One more reboot and all is well. Sounds works and I'm now at the 6.0.1.7874 7/6/2016 version.
    Thanks. I manually uninstalled my audio driver successfully, then downloaded the new driver and ran the setup. It asked me to reboot, and while loading windows, I got a BSOD for Driver Corrupted Expool. Rebooted again, got into windows fine, no audio driver installed.
      My ComputerSystem Spec


  3. Posts : 5,012
    Windows 10 Pro X64 15063.138
       11 Jul 2016 #13

    That's a different failure:

    Code:
    BugCheck C5, {8, 2, 0, fffff801b5e4ff48}
    
    *** WARNING: Unable to verify timestamp for WinVDEdrv.sys
    *** ERROR: Module load completed but symbols could not be loaded for WinVDEdrv.sys
    Probably caused by : Pool_Corruption ( nt!ExDeferredFreePool+798 )
    
    Followup: Pool_corruption
    ---------
    
    0: kd> lmvm WinVDEdrv
    start             end                 module name
    fffff800`18a80000 fffff800`18ac0000   WinVDEdrv T (no symbols)           
        Loaded symbol image file: WinVDEdrv.sys
        Image path: \??\C:\Windows\SysWow64\WinVDEdrv.sys
        Image name: WinVDEdrv.sys
        Timestamp:        Fri Jul 15 07:24:05 2011 (4E202355)
        CheckSum:         00041B9A
        ImageSize:        00040000
        Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
    winvdedrv.sys is part of Folder Lock and developed by NewSoftwares.net, Inc. according to the winvdedrv.sys version information.

    winvdedrv.sys's description is "Virtual Encryption Driver"

    winvdedrv.sys is digitally signed by NewSoftwares.net Inc. SDN. BHD..

    winvdedrv.sys is usually located in the 'c:\windows\syswow64\' folder.
    The date on the driver is very old, 2011. Either uninstall Folder Lock or update it to a later level.
      My ComputersSystem Spec


  4. Posts : 11
    Windows 10 Pro 10.0.10586 Build 10586
    Thread Starter
       11 Jul 2016 #14

    Ztruker said: View Post
    That's a different failure:

    Code:
    BugCheck C5, {8, 2, 0, fffff801b5e4ff48}
    
    *** WARNING: Unable to verify timestamp for WinVDEdrv.sys
    *** ERROR: Module load completed but symbols could not be loaded for WinVDEdrv.sys
    Probably caused by : Pool_Corruption ( nt!ExDeferredFreePool+798 )
    
    Followup: Pool_corruption
    ---------
    
    0: kd> lmvm WinVDEdrv
    start             end                 module name
    fffff800`18a80000 fffff800`18ac0000   WinVDEdrv T (no symbols)           
        Loaded symbol image file: WinVDEdrv.sys
        Image path: \??\C:\Windows\SysWow64\WinVDEdrv.sys
        Image name: WinVDEdrv.sys
        Timestamp:        Fri Jul 15 07:24:05 2011 (4E202355)
        CheckSum:         00041B9A
        ImageSize:        00040000
        Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4


    The date on the driver is very old, 2011. Either uninstall Folder Lock or update it to a later level.
    I think this did it. Uninstalled folder lock, then was able to install the latest audio drivers, no problems. Thank you for your help and your patience!

    On a side note, because of all this, I decided to look into how to read dmp files with windows sdk, hopefully I can get to the point where I can help others!
      My ComputerSystem Spec


  5. Posts : 5,012
    Windows 10 Pro X64 15063.138
       12 Jul 2016 #15

    I started about 6 months ago or so. I did a lot of dump reading back when I worked for IBM so was very familiar with the concept.
    It just takes time and a willingness to do a lot of reading and looking at dumps handled by others. I've looked at lots and lots of threads handled by axe0, Arc and Essenbe.

    It's fun most of the time though it gets a bit tedious when the dump doesn't contain anything useful for figuring out what is happening.
      My ComputersSystem Spec


  6. Posts : 11,546
    Windows 10 Pro
       13 Jul 2016 #16

    chopstxnrice said: View Post
    On a side note, because of all this, I decided to look into how to read dmp files with windows sdk, hopefully I can get to the point where I can help others!
    It is the same with many others, started to analyze dumps because they wanted to help others with their BSOD issues
    Though I didn't wait with helping someone until I was at a certain level, I started immediately after I had the setup proper. Learning throughout the practice is a good method
      My ComputersSystem Spec


  7. Posts : 11
    Windows 10 Pro 10.0.10586 Build 10586
    Thread Starter
       14 Jul 2016 #17

    Sorry to revive this, but I just got a new BSOD randomly, not doing anything out of the ordinary. Never had this BSOD before with this hardware (~5 years). Tried to look at dmp - is it suggesting it's caused by RAM errors? I don't remember exactly, but I'm pretty sure I ran memtest when I first got these sticks years ago and it was fine.

    edit: after getting this BSOD a second time in the same day, decided to run memtest, immediately getting lots of errors. Never had memory problems until today.

    BugCheck C1, {ffffcf8043262fb0, ffffcf804326239b, 330050, 32}
    Probably caused by : memory_corruption ( nt!MiCheckSpecialPoolSlop+8a )
    Followup: MachineOwner
    ---------
    3: kd> !analyze -v
    *******************************************************************************
    Bugcheck Analysis
    *******************************************************************************

    SPECIAL_POOL_DETECTED_MEMORY_CORRUPTION (c1)
    Special pool has detected memory corruption. Typically the current thread's
    stack backtrace will reveal the guilty party.
    Arguments:
    Arg1: ffffcf8043262fb0, address trying to free
    Arg2: ffffcf804326239b, address where one bit is corrupted
    Arg3: 0000000000330050, (reserved)
    Arg4: 0000000000000032, caller is freeing an address where nearby bytes within the same page have a single bit error
    Last edited by chopstxnrice; 14 Jul 2016 at 23:39.
      My ComputerSystem Spec


  8. Posts : 11,546
    Windows 10 Pro
       15 Jul 2016 #18

    That it is a hardware error is clear and good to know that you've found the cause, but why did you enable driver verifier?
    Code:
      STANDARD FLAGS:
        [X] (0x00000000) Automatic Checks
        [X] (0x00000001) Special pool
        [X] (0x00000002) Force IRQL checking
        [X] (0x00000008) Pool tracking
        [X] (0x00000010) I/O verification
        [X] (0x00000020) Deadlock detection
        [X] (0x00000080) DMA checking
        [X] (0x00000100) Security checks
        [X] (0x00000800) Miscellaneous checks
        [X] (0x00020000) DDI compliance checking
    
      ADDITIONAL FLAGS:
        [ ] (0x00000004) Randomized low resources simulation
        [ ] (0x00000200) Force pending I/O requests
        [ ] (0x00000400) IRP logging
        [ ] (0x00002000) Invariant MDL checking for stack
        [ ] (0x00004000) Invariant MDL checking for driver
        [ ] (0x00008000) Power framework delay fuzzing
        [ ] (0x00010000) Port/miniport interface checking
        [ ] (0x00040000) Systematic low resources simulation
        [ ] (0x00080000) DDI compliance checking (additional)
        [ ] (0x00200000) NDIS/WIFI verification
        [ ] (0x00800000) Kernel synchronization delay fuzzing
        [ ] (0x01000000) VM switch verification
        [ ] (0x02000000) Code integrity checks
    
        [X] Indicates flag is enabled
    is it suggesting it's caused by RAM errors?
    Nope, it is saying something caused memory corruption. Memory corruption isn't specific RAM:
    Memory corruption is a thing that is the most coming back in the dumps, because the memory mechanism of Windows is extremely large and complicated. When memory corruption is shown the first step is to rule out the memory as best as possible. The next step is to rule out the drivers what can be done with driver verifier if none is flagged. If drivers are also not causing any problems then we (or at least myself) usually check for the hard drives. Hard drives can also cause memory corruption, as it is the non-volatile version of memory, but there are usually signs about hard drive problems when we suggest something for the hard drive. Another memory corruption is the VRAM, but when that happens there are also signs about it.
    From BSOD to Windows Crash
      My ComputersSystem Spec


  9. Posts : 11
    Windows 10 Pro 10.0.10586 Build 10586
    Thread Starter
       15 Jul 2016 #19

    axe0 said: View Post
    That it is a hardware error is clear and good to know that you've found the cause, but why did you enable driver verifier?
    Code:
      STANDARD FLAGS:
        [X] (0x00000000) Automatic Checks
        [X] (0x00000001) Special pool
        [X] (0x00000002) Force IRQL checking
        [X] (0x00000008) Pool tracking
        [X] (0x00000010) I/O verification
        [X] (0x00000020) Deadlock detection
        [X] (0x00000080) DMA checking
        [X] (0x00000100) Security checks
        [X] (0x00000800) Miscellaneous checks
        [X] (0x00020000) DDI compliance checking
    
      ADDITIONAL FLAGS:
        [ ] (0x00000004) Randomized low resources simulation
        [ ] (0x00000200) Force pending I/O requests
        [ ] (0x00000400) IRP logging
        [ ] (0x00002000) Invariant MDL checking for stack
        [ ] (0x00004000) Invariant MDL checking for driver
        [ ] (0x00008000) Power framework delay fuzzing
        [ ] (0x00010000) Port/miniport interface checking
        [ ] (0x00040000) Systematic low resources simulation
        [ ] (0x00080000) DDI compliance checking (additional)
        [ ] (0x00200000) NDIS/WIFI verification
        [ ] (0x00800000) Kernel synchronization delay fuzzing
        [ ] (0x01000000) VM switch verification
        [ ] (0x02000000) Code integrity checks
    
        [X] Indicates flag is enabled

    Nope, it is saying something caused memory corruption. Memory corruption isn't specific RAM:

    From BSOD to Windows Crash
    Thanks. I initially enabled driver verifier when I was having driver issues in the beginning of this thread. Didn't know what I was doing with it. Should I do anything with it now?

    Can ram sticks "go bad" over time? I.e. I've never had problems with them until yesterday. I guess my next step is to isolate the sticks and figure out which of the sticks is bad, and try to contact manufacturer (lifetime guarantee) for new hardware?
      My ComputerSystem Spec


  10. Posts : 11,546
    Windows 10 Pro
       15 Jul 2016 #20

    All hardware go bad in a matter of time, it is why you can replace them
      My ComputersSystem Spec


 
Page 2 of 3 FirstFirst 123 LastLast

Related Threads
HP Supports Assistant shows that I need Intel High-Definition (HD) Graphics Driver - sp72370 driver for my Envy 360. Before I install this driver I can see that things are a bit laggy, ofcourse I dont have graphics driver. So I install this driver...
can anyone tell me how to fix this. i followed this https://www.youtube.com/watch?v=sYj3xNh8QNk video and i cant find intelGfx.NTamd64.6.3 in the inf file.
Well! That was a jarring experience! Just got a update via WU for Intel HD Graphics 4600. During install, it went absolutely bonkers on the display. Kaleidoscope wacky! Just let it be for a minute or so to finish install, then power button...
Hey everyone! I've been having a lot of problems playing online games with my integrated graphics. I get really low fps if I try to play using my dedicated graphics card. It gets to the point where the games are unplayable which is why I switched...
I'm getting an array of different BSODs, hopefully all contained in the crash report. They occur at seemingly random intervals. Please let me know what I should do, and if I should provide any further info. 47545 Thanks in advance! Hans
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd
All times are GMT -5. The time now is 10:31.
Find Us