1.    25 Apr 2015 #1
    Join Date : Sep 2014
    DFW Area
    Posts : 439
    Windows 8&10

    Need Help with setting up Windbg


    I seem to be suffering from a severe lack of knowledge and experience in this area. I am trying to read dump file created by Windows 10 but keep seeing errors about ntoskrnl.exe and symbol errors.

    I have gone through the tutorial by Golden. I notice the Executable search path seems to be a problem.

    ************* Symbol Path validation summary **************
    Response Time (ms) Location
    Deferred SRV*H:\Symbols*http://msdl.microsoft.com/download/symbols
    Symbol search path is: SRV*H:\Symbols*http://msdl.microsoft.com/download/symbols
    Executable search path is:
    Unable to load image \SystemRoot\system32\ntoskrnl.exe, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for ntoskrnl.exe
    *** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
    Windows 8 Kernel Version 10049 MP (12 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 10049.0.amd64fre.fbl_impressive.150325-1700
    Machine Name:
    Kernel base = 0xfffff802`35872000 PsLoadedModuleList = 0xfffff802`35b814b0
    Debug session time: Tue Apr 14 14:39:30.073 2015 (UTC - 5:00)
    System Uptime: 0 days 0:04:28.787
    Unable to load image \SystemRoot\system32\ntoskrnl.exe, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for ntoskrnl.exe
    *** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
    Loading Kernel Symbols
    The version of Windgb is 6.3.9600.17298 AMD64. The test dump file in the tutorial will not extract or run.

    I tried downloading a version of Windbg from the link in the other thread but all I seem to get is Visual Studio and Phone development tools.

    If anyone wants to check, these dump files are from an X99 system running 2 GTX 980s in SLI surround mode. I don't seem to have a problem playing my games, but it appears interaction with the Desktop is generating the problems, such as clicking on the Start button. I have received many Video Driver has stopped responding and recovered type messages.

    I did have a heck of a time getting 10061 into Surround mode.

    I am providing the dump files, but I am really more interested in getting Windbg to work correctly. So the additional info regarding system configuration should not be necessary. I am not sure if Windows 10 is responsible for my problems or if I am using the wrong version of something...

    Thanks, this is not essential just interesting since I assume Microsoft has already gotten the 6 Dump files already generated.
    Last edited by Saltgrass; 25 Apr 2015 at 11:38.
      My ComputerSystem Spec
  2.    25 Apr 2015 #2
    Join Date : Oct 2013
    Wolves, England
    Posts : 1,634
    W7 Pro x64 | W10 IP x64 | Linux Mint VM
      My ComputerSystem Spec
  3.    26 Apr 2015 #3
    Join Date : Oct 2014
    Posts : 230
    10

    Do not worry about the symbol errors in Win10 - it's most likely due to new builds and lag time in uploading the new build's symbols to the Microsoft symbol server.

    Go over to Eight Forums and pick a few dumps from there and see if you get the same errors.
    If you do, post back with a link to them and we'll try to run them and see if we get the same errors.
      My ComputerSystem Spec
  4.    26 Apr 2015 #4
    Join Date : Oct 2013
    Wolves, England
    Posts : 1,634
    W7 Pro x64 | W10 IP x64 | Linux Mint VM

    I've really got to stop posting after a bellyful of beer. Apologies to the OP, I obvously completely misread your post.
      My ComputerSystem Spec
  5.    27 Apr 2015 #5
    Join Date : Oct 2014
    Posts : 230
    10

    The link for Visual Studio is a prerequisite to installing the other tools - among which is WinDbg.
    I used it in my VM and had no problems with it. I haven't updated to them in my current Win10, but will likely do so soon.

    I have never had issues installing WinDbg, and the only thing that I've ever configured is the path for the symbols. I don't associate the .dmp extension with anything (as I mostly use kd.exe as my debugger, and use WinDbg for those times that I need a bit more info from a dump file.

    Video driver has stopped responding and has recovered are often signs of a STOP 0x117 error. You won't actually see a BSOD for these in most OS's - although I haven't had any experience with them in Win10. Here's a link for troubleshooting them that I use frequently: Please follow these troubleshooting suggestions: Video TDR Timeout - 0x116 + 0x117 - Sysnative Forums
    Also, please monitor your temps with this free utility: HWMONITOR | Softwares | CPUID

    In running these dumps the script that I use had to access the Microsoft Symbol Server for symbols. This indicates that the symbols weren't present on my system - which likely means that I've never run memory dumps from that build. It's also possible that some of the components (such as ntoskrnl.exe) have been updated since I last ran that build - but we'll see what the dump analysis has to show.......

    The dump analysis shows the wrong symbols also - so, as this copy of the debuggers (kd and windbg) have worked well with Win7, 8, and 8.1 dumps without symbol issues, I'd have to figure that these symbols haven't been uploaded to the symbol server.

    Out of 8 memory dumps there were 4 different BSOD error codes. The differing error codes are usually symptomatic of a lower level problem within the system. They are usually caused by one of these things (the list is not in any sort of order):
    - borked (broken) hardware (several different procedures used to isolate the problem device)
    - BIOS issues (check for updates at the motherboard manufacturer's website)
    - overclocking/overheating - You'll know if you're overclocking or not. If uncertain we can suggest things to check.
    - dirt/dust/hair/fur/crud inside the case. Blow out the case/vents with canned air (DO NOT use an air compressor or vacuum as they can cause damage to the system)
    - missing Windows Updates
    - compatibility issues (3rd party hardware/drivers), older systems, or even pirated systems
    - low-level driver problems
    - or even malware (scanned for when we ask for hardware diagnostics from Initial Hardware Diagnostics or Hardware Diagnostics ).

    Please note that most of the memory dumps were related to video, so we should concentrate on video issues first.

    Please get a head start on the hardware diagnostics - they are located here: Hardware Diagnostics

    I'd also run Driver Verifier according to these instructions, just in case there's a low-level driver causing the problems: Driver Verifier Settings

    Analysis:
    The following is for informational purposes only.
    Code:
    **************************Sat Apr 25 12:14:45.784 2015 (UTC - 4:00)**************************
    Loading Dump File [C:\Users\John\SysnativeBSODApps\042515-27109-01.dmp]
    *** WARNING: Unable to verify timestamp for ntoskrnl.exe
    *** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
    Windows 8 Kernel Version 10061 MP (12 procs) Free x64
    Built by: 10061.0.amd64fre.fbl_impressive.150410-2039
    System Uptime:0 days 0:03:56.496
    *** WARNING: Unable to verify timestamp for ntoskrnl.exe
    *** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
    *** WARNING: Unable to verify timestamp for dxgkrnl.sys
    *** ERROR: Module load completed but symbols could not be loaded for dxgkrnl.sys
    Probably caused by :dxgkrnl.sys ( dxgkrnl+ab159 )
    BugCheck 3B, {c0000005, fffff801bec9b159, ffffd000286ccf80, 0}
    BugCheck Info: SYSTEM_SERVICE_EXCEPTION (3b)
    Arguments: 
    Arg1: 00000000c0000005, Exception code that caused the bugcheck
    Arg2: fffff801bec9b159, Address of the instruction which caused the bugcheck
    Arg3: ffffd000286ccf80, Address of the context record for the exception that caused the bugcheck
    Arg4: 0000000000000000, zero.
    BUGCHECK_STR:  0x3B
    DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
    FAILURE_BUCKET_ID: WRONG_SYMBOLS
    CPUID:        "Intel(R) Core(TM) i7-5930K CPU @ 3.50GHz"
    MaxSpeed:     3500
    CurrentSpeed: 3498
      BIOS Version                  1501
      BIOS Release Date             02/25/2015
      Manufacturer                  ASUS
      Baseboard Manufacturer        ASUSTeK COMPUTER INC.
      Product Name                  All Series
      Baseboard Product             X99-PRO
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Sat Apr 25 12:10:08.391 2015 (UTC - 4:00)**************************
    Loading Dump File [C:\Users\John\SysnativeBSODApps\042515-28125-01.dmp]
    *** WARNING: Unable to verify timestamp for ntoskrnl.exe
    *** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
    Windows 8 Kernel Version 10061 MP (12 procs) Free x64
    Built by: 10061.0.amd64fre.fbl_impressive.150410-2039
    System Uptime:0 days 0:03:58.103
    *** WARNING: Unable to verify timestamp for ntoskrnl.exe
    *** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
    *** WARNING: Unable to verify timestamp for dxgkrnl.sys
    *** ERROR: Module load completed but symbols could not be loaded for dxgkrnl.sys
    Probably caused by :dxgkrnl.sys ( dxgkrnl+ab149 )
    BugCheck 3B, {c0000005, fffff8005225b149, ffffd00028a9af80, 0}
    BugCheck Info: SYSTEM_SERVICE_EXCEPTION (3b)
    Arguments: 
    Arg1: 00000000c0000005, Exception code that caused the bugcheck
    Arg2: fffff8005225b149, Address of the instruction which caused the bugcheck
    Arg3: ffffd00028a9af80, Address of the context record for the exception that caused the bugcheck
    Arg4: 0000000000000000, zero.
    BUGCHECK_STR:  0x3B
    DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
    FAILURE_BUCKET_ID: WRONG_SYMBOLS
    CPUID:        "Intel(R) Core(TM) i7-5930K CPU @ 3.50GHz"
    MaxSpeed:     3500
    CurrentSpeed: 3498
      BIOS Version                  1501
      BIOS Release Date             02/25/2015
      Manufacturer                  ASUS
      Baseboard Manufacturer        ASUSTeK COMPUTER INC.
      Product Name                  All Series
      Baseboard Product             X99-PRO
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Sat Apr 25 12:05:28.096 2015 (UTC - 4:00)**************************
    Loading Dump File [C:\Users\John\SysnativeBSODApps\042515-28703-01.dmp]
    *** WARNING: Unable to verify timestamp for ntoskrnl.exe
    *** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
    Windows 8 Kernel Version 10061 MP (12 procs) Free x64
    Built by: 10061.0.amd64fre.fbl_impressive.150410-2039
    System Uptime:0 days 0:03:57.808
    *** WARNING: Unable to verify timestamp for ntoskrnl.exe
    *** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
    *** WARNING: Unable to verify timestamp for dxgkrnl.sys
    *** ERROR: Module load completed but symbols could not be loaded for dxgkrnl.sys
    Probably caused by :dxgkrnl.sys ( dxgkrnl+ab149 )
    BugCheck 3B, {c0000005, fffff80177ddb149, ffffd000267e0f80, 0}
    BugCheck Info: SYSTEM_SERVICE_EXCEPTION (3b)
    Arguments: 
    Arg1: 00000000c0000005, Exception code that caused the bugcheck
    Arg2: fffff80177ddb149, Address of the instruction which caused the bugcheck
    Arg3: ffffd000267e0f80, Address of the context record for the exception that caused the bugcheck
    Arg4: 0000000000000000, zero.
    BUGCHECK_STR:  0x3B
    DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
    FAILURE_BUCKET_ID: WRONG_SYMBOLS
    CPUID:        "Intel(R) Core(TM) i7-5930K CPU @ 3.50GHz"
    MaxSpeed:     3500
    CurrentSpeed: 3498
      BIOS Version                  1501
      BIOS Release Date             02/25/2015
      Manufacturer                  ASUS
      Baseboard Manufacturer        ASUSTeK COMPUTER INC.
      Product Name                  All Series
      Baseboard Product             X99-PRO
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Fri Apr 24 09:24:36.760 2015 (UTC - 4:00)**************************
    Loading Dump File [C:\Users\John\SysnativeBSODApps\042415-21218-01.dmp]
    *** WARNING: Unable to verify timestamp for ntoskrnl.exe
    *** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
    Windows 8 Kernel Version 10061 MP (12 procs) Free x64
    Built by: 10061.0.amd64fre.fbl_impressive.150410-2039
    System Uptime:0 days 0:07:03.472
    *** WARNING: Unable to verify timestamp for ntoskrnl.exe
    *** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
    Probably caused by :ntoskrnl.exe ( nt+1360f0 )
    BugCheck 133, {1, 1e00, 0, 0}
    BugCheck Info: DPC_WATCHDOG_VIOLATION (133)
    Arguments: 
    Arg1: 0000000000000001, The system cumulatively spent an extended period of time at
        DISPATCH_LEVEL or above. The offending component can usually be
        identified with a stack trace.
    Arg2: 0000000000001e00, The watchdog period.
    Arg3: 0000000000000000
    Arg4: 0000000000000000
    BUGCHECK_STR:  0x133
    DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
    FAILURE_BUCKET_ID: WRONG_SYMBOLS
    CPUID:        "Intel(R) Core(TM) i7-5930K CPU @ 3.50GHz"
    MaxSpeed:     3500
    CurrentSpeed: 3498
      BIOS Version                  1501
      BIOS Release Date             02/25/2015
      Manufacturer                  ASUS
      Baseboard Manufacturer        ASUSTeK COMPUTER INC.
      Product Name                  All Series
      Baseboard Product             X99-PRO
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Fri Apr 24 09:16:53.989 2015 (UTC - 4:00)**************************
    Loading Dump File [C:\Users\John\SysnativeBSODApps\042415-22812-01.dmp]
    *** WARNING: Unable to verify timestamp for ntoskrnl.exe
    *** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
    Windows 8 Kernel Version 10061 MP (12 procs) Free x64
    Built by: 10061.0.amd64fre.fbl_impressive.150410-2039
    System Uptime:0 days 7:46:40.703
    *** WARNING: Unable to verify timestamp for ntoskrnl.exe
    *** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
    *** 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+eb0ef )
    BugCheck 1000007E, {ffffffffc0000005, fffff800c846b0ef, ffffd0016b2b40d8, ffffd0016b2b38f0}
    BugCheck Info: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
    Arguments: 
    Arg1: ffffffffc0000005, The exception code that was not handled
    Arg2: fffff800c846b0ef, The address that the exception occurred at
    Arg3: ffffd0016b2b40d8, Exception Record Address
    Arg4: ffffd0016b2b38f0, Context Record Address
    BUGCHECK_STR:  AV
    DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
    FAILURE_BUCKET_ID: WRONG_SYMBOLS
    CPUID:        "Intel(R) Core(TM) i7-5930K CPU @ 3.50GHz"
    MaxSpeed:     3500
    CurrentSpeed: 3498
      BIOS Version                  1501
      BIOS Release Date             02/25/2015
      Manufacturer                  ASUS
      Baseboard Manufacturer        ASUSTeK COMPUTER INC.
      Product Name                  All Series
      Baseboard Product             X99-PRO
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Thu Apr 23 13:16:25.543 2015 (UTC - 4:00)**************************
    Loading Dump File [C:\Users\John\SysnativeBSODApps\042315-21390-01.dmp]
    *** WARNING: Unable to verify timestamp for ntoskrnl.exe
    *** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
    Windows 8 Kernel Version 10061 MP (12 procs) Free x64
    Built by: 10061.0.amd64fre.fbl_impressive.150410-2039
    System Uptime:0 days 1:03:33.257
    *** WARNING: Unable to verify timestamp for ntoskrnl.exe
    *** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
    Probably caused by :ntoskrnl.exe ( nt+1360f0 )
    BugCheck 133, {1, 1e00, 0, 0}
    BugCheck Info: DPC_WATCHDOG_VIOLATION (133)
    Arguments: 
    Arg1: 0000000000000001, The system cumulatively spent an extended period of time at
        DISPATCH_LEVEL or above. The offending component can usually be
        identified with a stack trace.
    Arg2: 0000000000001e00, The watchdog period.
    Arg3: 0000000000000000
    Arg4: 0000000000000000
    BUGCHECK_STR:  0x133
    DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
    FAILURE_BUCKET_ID: WRONG_SYMBOLS
    CPUID:        "Intel(R) Core(TM) i7-5930K CPU @ 3.50GHz"
    MaxSpeed:     3500
    CurrentSpeed: 3498
      BIOS Version                  1501
      BIOS Release Date             02/25/2015
      Manufacturer                  ASUS
      Baseboard Manufacturer        ASUSTeK COMPUTER INC.
      Product Name                  All Series
      Baseboard Product             X99-PRO
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Thu Apr 23 12:12:02.743 2015 (UTC - 4:00)**************************
    Loading Dump File [C:\Users\John\SysnativeBSODApps\042315-21812-01.dmp]
    *** WARNING: Unable to verify timestamp for ntoskrnl.exe
    *** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
    Windows 8 Kernel Version 10061 MP (12 procs) Free x64
    Built by: 10061.0.amd64fre.fbl_impressive.150410-2039
    System Uptime:0 days 2:10:28.454
    *** WARNING: Unable to verify timestamp for ntoskrnl.exe
    *** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
    Probably caused by :ntoskrnl.exe ( nt+1360f0 )
    BugCheck 133, {1, 1e00, 0, 0}
    BugCheck Info: DPC_WATCHDOG_VIOLATION (133)
    Arguments: 
    Arg1: 0000000000000001, The system cumulatively spent an extended period of time at
        DISPATCH_LEVEL or above. The offending component can usually be
        identified with a stack trace.
    Arg2: 0000000000001e00, The watchdog period.
    Arg3: 0000000000000000
    Arg4: 0000000000000000
    BUGCHECK_STR:  0x133
    DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
    FAILURE_BUCKET_ID: WRONG_SYMBOLS
    CPUID:        "Intel(R) Core(TM) i7-5930K CPU @ 3.50GHz"
    MaxSpeed:     3500
    CurrentSpeed: 3498
      BIOS Version                  1501
      BIOS Release Date             02/25/2015
      Manufacturer                  ASUS
      Baseboard Manufacturer        ASUSTeK COMPUTER INC.
      Product Name                  All Series
      Baseboard Product             X99-PRO
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Thu Apr 23 00:57:49.902 2015 (UTC - 4:00)**************************
    Loading Dump File [C:\Users\John\SysnativeBSODApps\042315-29218-01.dmp]
    *** WARNING: Unable to verify timestamp for ntoskrnl.exe
    *** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
    Windows 8 Kernel Version 10061 MP (12 procs) Free x64
    Built by: 10061.0.amd64fre.fbl_impressive.150410-2039
    System Uptime:0 days 0:13:13.615
    *** WARNING: Unable to verify timestamp for ntoskrnl.exe
    *** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
    *** WARNING: Unable to verify timestamp for mssmbios.sys
    *** ERROR: Module load completed but symbols could not be loaded for mssmbios.sys
    *** 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+2157f2 )
    BugCheck D1, {ffffe001d8413a84, e, 0, fffff801138f57f2}
    BugCheck Info: DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
    Arguments: 
    Arg1: ffffe001d8413a84, memory referenced
    Arg2: 000000000000000e, IRQL
    Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
    Arg4: fffff801138f57f2, address which referenced memory
    BUGCHECK_STR:  AV
    DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
    FAILURE_BUCKET_ID: WRONG_SYMBOLS
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    
    3rd Party Drivers:
    The following is for information purposes only.
    Any drivers in red should be updated or removed from your system. And should have been discussed in the body of my post.
    Code:
    **************************Sat Apr 25 12:14:45.784 2015 (UTC - 4:00)**************************
    AsIO.sys                    Wed Aug 22 05:54:47 2012 (5034AC67)
    iqvw64e.sys                 Thu Nov 14 10:22:43 2013 (5284EAC3)
    rzpmgrk.sys                 Thu Apr 17 15:36:12 2014 (53502D2C)
    mbam.sys                    Wed Sep  3 13:50:25 2014 (540754E1)
    bcmwl63a.sys                Thu Sep  4 09:02:16 2014 (540862D8)
    TeeDriverx64.sys            Tue Sep 23 16:01:14 2014 (5421D18A)
    nvhda64v.sys                Thu Oct  9 13:02:27 2014 (5436BFA3)
    rzpnk.sys                   Fri Oct 17 15:38:10 2014 (54417022)
    rzendpt.sys                 Tue Dec 30 04:32:47 2014 (54A2713F)
    rzudd.sys                   Tue Dec 30 04:32:50 2014 (54A27142)
    RTKVHD64.sys                Mon Mar  2 04:57:24 2015 (54F43404)
    nvlddmkm.sys                Wed Mar 11 15:48:01 2015 (55009BF1)
    bcbtums.sys                 Mon Mar 23 17:31:26 2015 (5510862E)
    e1i63x64.sys                Thu Mar 26 16:24:57 2015 (55146B19)
    intelppm.sys                Sat Apr 11 01:48:19 2015 (5528B5A3)
    WindowsTrustedRTProxy.sys   Sat Apr 11 01:49:50 2015 (5528B5FE)
    WindowsTrustedRT.sys        Sat Apr 11 01:49:52 2015 (5528B600)
    filecrypt.sys               Sat Apr 11 01:53:19 2015 (5528B6CF)
    mirahid.sys                 Sat Apr 11 01:58:43 2015 (5528B813)
    storqosflt.sys              Sat Apr 11 02:00:42 2015 (5528B88A)
    
    http://www.carrona.org/drivers/driver.php?id=AsIO.sys
    http://www.carrona.org/drivers/driver.php?id=iqvw64e.sys
    http://www.carrona.org/drivers/driver.php?id=rzpmgrk.sys
    http://www.carrona.org/drivers/driver.php?id=mbam.sys
    http://www.carrona.org/drivers/driver.php?id=bcmwl63a.sys
    http://www.carrona.org/drivers/driver.php?id=TeeDriverx64.sys
    http://www.carrona.org/drivers/driver.php?id=nvhda64v.sys
    http://www.carrona.org/drivers/driver.php?id=rzpnk.sys
    http://www.carrona.org/drivers/driver.php?id=rzendpt.sys
    http://www.carrona.org/drivers/driver.php?id=rzudd.sys
    http://www.carrona.org/drivers/driver.php?id=RTKVHD64.sys
    http://www.carrona.org/drivers/driver.php?id=nvlddmkm.sys
    http://www.carrona.org/drivers/driver.php?id=bcbtums.sys
    http://www.carrona.org/drivers/driver.php?id=e1i63x64.sys
    http://www.carrona.org/drivers/driver.php?id=intelppm.sys
    WindowsTrustedRTProxy.sys - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed.
    WindowsTrustedRT.sys - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed.
    filecrypt.sys - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed.
    mirahid.sys - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed.
    storqosflt.sys - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed.
      My ComputerSystem Spec
  6.    04 May 2015 #6
    Join Date : Sep 2014
    DFW Area
    Posts : 439
    Windows 8&10
    Thread Starter

    Thanks usasma, I will go over you comments. My installs are clean installs, so any drivers have probably been added during or after the install.

    They seem to be related to SLI and have been happening through most of the builds.

    Anyway, when someone shows they have version 10 of Windbg and the only Windows 10 symbols I can find are for 9926, I figure I must be missing something.

    Yesterday, using 10074, I got 3 Blue Screens when the system was just sitting on the Desktop. Between dxgkrnl and nvlddmkm.sys there always seem to be dump files for Microsoft to check.... It is strange to me, I can play my games fine, it is the Desktop and interaction with it what problems are happening...

    Thanks again.
      My ComputerSystem Spec
  7.    04 May 2015 #7
    Join Date : Oct 2013
    Shasta County
    Posts : 1,073
    Win 10 Pro x64

    Just an FYI on this from your first post,

    Quote Originally Posted by Saltgrass
    The test dump file in the tutorial will not extract or run.
    That was zipped with 7-zip, so you need 7-zip to extract it.
      My ComputerSystem Spec
  8.    07 May 2015 #8
    Join Date : Oct 2014
    Posts : 230
    10

    Video drivers are complicated critters and they span far more of the OS's functions than most drivers.

    The Microsoft Symbol Server has symbols for the builds if they are provided by the developers.
    I wouldn't be surprised if there were difficulties with this as there are many different teams working on this project.
    It's once it's time to release the build that the symbols need to be supplied - and I wonder how important it is to the developers. They have access to the private symbols, and the telemetry supplies them with the information that they need.

    Upload the current minidumps and I'll see if I get the same errors with kd.exe. If so, then we have to presume that the symbol server doesn't have the necessary symbols. If this is the case, a concerted effort by us to provide feedback on this may see some results (if enough of us report it).
      My ComputerSystem Spec

 


Similar Threads
Thread Forum
BSOD WinDBG - The Basics for Debugging Crash Dumps in Windows 10
WinDBG - The Basics for Debugging Crash Dumps in Windows 10 WinDBG (Windows DeBuGger) is an analytic tool used for analysing and debugging Windows crash dumps, also known as BSODs (Blue Screens of Death). It is part of the Windows Developer Kit...
Tutorials
BSOD Install and Configure WinDBG for BSOD Analysis
How to Install and Configure WinDBG for BSOD Analysis WinDBG (Windows DeBuGger) is a Microsoft software tool that is needed to load and analyse the .dmp files that are created when a system BSOD's. The latest version of WinDBG allows debugging of...
Tutorials
Solved DPC_WATCHDOG_VIOLATION BSOD, Windbg unable to load symbols
Windows 10 Insider Preview Build 10130 WIN-A82HE7DTDIP-Fri_06_05_2015_172808_86.zip attached PC Specs are in profile :P So I have windbg, I followed the how to install guide (Using both the win8.1 and win10 SDK, both give the same errors,...
BSOD Crashes and Debugging
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 03:20.
Find Us
Twitter Facebook Google+ Ten Forums iOS App Ten Forums Android App



Windows 10 Forums