Computer Lockup and Restarts- Bad Video Card (Again?)

Page 3 of 6 FirstFirst 12345 ... LastLast

  1. Posts : 29
    Windows 10 Pro x64 v1809 build 17763.503
    Thread Starter
       #21

    I turned the computer on today, at like 19:25. It barely had time to load Steam and my mouse cursor froze up. Computer locked up. By like 19:28. Attaching dm and collector logs.

    1) Yes, I've made several posts. I've pointed you to a few already. I believe their Tech Support wants me to RMA the motherboard. I already RMAd a video card with them so I am hesitant to say the least. Long time ago: X99A Gaming Carbon BIOS Update Issue and more recently MSI X99 Gaming Pro Carbon NEW BIOS 7A20v14?? basically, when I upgrade to v.1.40 I lose functional parts of the BIOS like the m-flash option and Save Changes. I explain in the threads that I linked to. Point is this motherboard supports dual bios A and B. A is 1.30 and B is 1.40... but it doesn't look like it takes the update...maybe I should just send it in.

    2)Attachment 236934
    Attachment 236935
    Temps are ok. A little warm because it's between the video card and the power supply, but well within reason.

    3-4) Microsoft services found some other dumps recent files included in that folder too

    5, 7, not needed I'm probably going to end up reinstalling/reformatting once I figure this out

    6) will check it out

    9) will check it out soon

    10) my apologies, I couldn't find the chkdsk for C: drive in event viewer. So I cleared the application log and ran it. I haven't done anything else/any cleaning.

    Hope this helps! Hope you can discern something from one or more of those dmps!
      My Computer


  2. Posts : 41,412
    windows 10 professional version 1607 build 14393.969 64 bit
       #22

    What are the status of the files on the windows drive?
    Are all important files backed up?

    If yes, then windows driver can be started once you understand how to use the computer's windows advanced troubleshooting menu to run the command prompt commands to turn off the tool.

    If no, then backup important files to another disk drive or to the cloud.



    Plan to run the tool for approximately 48 hours. And then for an additional 36 hours after the last BSOD.
    Start with the three customized tests in the Ten Forums link:
    Enable and Disable Driver Verifier in Windows 10
    Always make a new restore point before using the tool.
      My Computer


  3. Posts : 29
    Windows 10 Pro x64 v1809 build 17763.503
    Thread Starter
       #23

    zbook said:
    What are the status of the files on the windows drive?
    Are all important files backed up?

    If yes, then windows driver can be started once you understand how to use the computer's windows advanced troubleshooting menu to run the command prompt commands to turn off the tool.

    If no, then backup important files to another disk drive or to the cloud.



    Plan to run the tool for approximately 48 hours. And then for an additional 36 hours after the last BSOD.
    Start with the three customized tests in the Ten Forums link:
    Enable and Disable Driver Verifier in Windows 10
    Always make a new restore point before using the tool.
    I read both threads about driver verifier. Totally understand what it does and why we're using it. Came home tonight, started computer... nothing. Had to leave after about five minutes.

    Came back turned it on, immediately it froze.

    Collect logs and reboot.

    Screw it, I'm turning on verifier.

    Turn it on, set the following settings:
    Custom settings
    All scenarios except Low Resources Simulation and DDI Compliance (did not select these and there were two each)
    All drivers tested that were not Microsoft - the ones at the top had no company, then Avast, Logitech, Nvidia. Microsoft drivers were un-checked.

    I did a reboot and nothing. Sat at the BIOS splash with the circles. Infinite loading.

    Turned the computer off. Waited a few minutes, turned it on and same thing. Infinite loading.

    Pop in the Windows 8.1 DVD I have sitting next to the computer figure ok better turn it off this is serious... Windows goes to Autorepair itself because it can't boot. I choose to do nothing, exit and continue loading Windows 10. I go to the bathroom and come back.

    It had bluescreened with a DRIVER_VERIFIER error. Turned the power off. Booted the computer to "Automatically trying to repair"... told it cancel, boot to Windows 10. Nothing at all now just a black screen.

    Am I testing too much with verifier? Should I cut down on some? Should I have gotten results this quickly? Does this indicate a driver/software issue or could it be hardware? What should I do now? Try to get more verifier crashes? Try and cut down on what it's testing at once? Or try and disable it now and retrieve the dump file I'm hoping it left?


    Let me know when you can, I'm typing this from my good ol MacBook Pro...

    Edit: I was able to pull a few dumps off and disable verifier, for now. Command Prompts won't do it you have to be in the Windows 10 OS environment. Easiest way to get there is through safe mode. Please check the MS shared folder for the verifier dumps and let me know if they contain anything meaningful to you. Thanks!!
    Last edited by nasch007; 13 Jun 2019 at 01:32.
      My Computer


  4. Posts : 41,412
    windows 10 professional version 1607 build 14393.969 64 bit
       #24

    Please see post #20 and #22

    Code:
    The plan is to use windows driver verifier to cause crashes by stressing drivers.
    There may be decreased performance and slow boots while using the tool.
    (do not use the tool until it is communicated in the thread)
    Code:
    Plan to run the tool for approximately 48 hours. And then for an additional 36 hours after the last BSOD.
    Start with the three customized tests in the Ten Forums link:
    Enable and Disable Driver Verifier in Windows 10
    Always make a new restore point before using the tool.



    The testing was to be performed with only three customized tests.

    Please restart testing using the customized settings in the Ten Forums link.

    When the tool is used there can be immediate and delayed BSOD.

    Start with the three customized tests. Test all non-Microsoft drivers simultaneously.
    If there are no major performance or delayed boot problems then increase the number of customized tests by two to four per hour. If there are problems with performance or boot then remove some of the customized tests. The goal is to expose all of the non-Microsoft drivers to all of the customized tests displayed in the Microsoft link.

    If you are able to identify a customized test that causes a major change in performance that test behavior may change as drivers are modified or uninstalled. Alternatively you can try running the tool wit only one customized test. Allow sufficient testing time for bot immediate and delayed BSOD.

    There is a lot of flexibility wile using the tool. Over 48 hours all of the non-Microsoft should be exposed to all or almost all of the 19 customized tests. Then the tool is run for additional 36 hours of typical computer use.

    After each BSOD you should use the computer's windows advanced troubleshooting menu to turn off the tool (safe mode with reset or command prompt with bootmode). When back to the desktop run V2 and post a share link for the memory dump if the file size is <1.5 GB.

    If there are problems turning off the tool you may be able to use system restore. Often though system restore can lead to a loss of the dump file. If there is no dump file then there is little progress in the troubleshooting. If you have available the windows advanced troubleshooting menu on a DVD or USB they can be used following the instructions in the Ten Forums link (command prompt bootmode and system restore)

    For the troubleshooting if possible uninstall software, otherwise uninstall and reinstall.

    https://answers.microsoft.com/en-us/...0-8d22254aa1c1

    Uninstall and reinstall: SteamStreamingMicrophone.sys

    Code:
    SteamStreami Steam Streaming Microp Steam Streaming Microp Kernel        Manual     Running    OK         TRUE        FALSE        8,192             8,192       0          07/28/17 08:33:15 AM   C:\Windows\system32\drivers\SteamStreamingMicrop 4,096
    Code:
    Name	Steam Streaming Microphone
    Manufacturer	Valve Corporation Audio DDK
    Status	OK
    PNP Device ID	ROOT\STEAMSTREAMINGMICROPHONE\0000
    Driver	c:\windows\system32\drivers\steamstreamingmicrophone.sys (, 39.78 KB (40,736 bytes), 04/30/19 08:30)
    Code:
    SteamStreamingMicrophone.sys Fri Jul 28 08:33:15 2017 (597B593B)
    Last edited by zbook; 13 Jun 2019 at 02:55.
      My Computer


  5. Posts : 29
    Windows 10 Pro x64 v1809 build 17763.503
    Thread Starter
       #25

    zbook said:
    snip
    I did not uninstall that driver. Those drivers are installed by Valve/Steam when you use the Steamlink hardware. It allows you to stream you computer's screen/contents to whereever the Steamlink is plugged in to, in this case the living room... If I remove them, then either a) streaming will not work properly, or b) they will just be automatically installed again when I go to stream. So it's sort of a moot point. I should also add, when my nvidia card was out for repairs, and I installed an AMD card in the system in its place, I had none of these symptoms, even while using the Steamlink and streaming features.

    It did jog my memory, though, and I remember for some reason I can't recall now, I did create a Scheduled Task to Launch Steam as an Admin, at user logon. I wonder if this did something to call the drivers or just create a duplicate process or something that could be fudging things up. I couldn't remember why so i just deleted the task and proceeded as usual.

    So I was able to get back to my normal desktop and then last night I turned on verifier using only the three tests, and testing all non-microsoft drivers. So far uptime is 13 hours with no restarts and no bluescreens.

    How often should I add a new test? And should I indefinitely avoid the DDI Compliance and Low resources tests? Or just maybe enable them last?

    Thank you again for your help!!
      My Computer


  6. Posts : 41,412
    windows 10 professional version 1607 build 14393.969 64 bit
       #26

    Increase the number of customized tests by 3 - 5 / hour.
    The more the dump files the better.
    Sometimes the newest build of Windows may become corrupt.
    Drivers can be affected in a similar fashion.
    So if possible uninstall and reinstall.
      My Computer


  7. Posts : 29
    Windows 10 Pro x64 v1809 build 17763.503
    Thread Starter
       #27

    zbook said:
    Increase the number of customized tests by 3 - 5 / hour.
    The more the dump files the better.
    Sometimes the newest build of Windows may become corrupt.
    Drivers can be affected in a similar fashion.
    So if possible uninstall and reinstall.
    I had 12 out of 19 tests enabled and it ran fine for about 12 hours. Then when I increased the test by 3 to about 15 out of the 19 total, it crashed.

    As soon as I made the change in verifier settings and rebooted, that reboot took a long time for the Windows loading (circling dots) to go away. As soon as it did, blue screen with the verifier error. Here were the settings before the reboot:

    Code:
    Standard Flags:
    
        [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.
        [ ] 0x00020000 DDI compliance checking.
    
      Additional Flags:
    
        [ ] 0x00000004 Randomized low resources simulation.
        [X] 0x00000200 Force pending I/O requests.
        [X] 0x00000400 IRP logging.
        [X] 0x00002000 Invariant MDL checking for stack.
        [X] 0x00004000 Invariant MDL checking for driver.
        [X] 0x00008000 Power framework delay fuzzing.
        [X] 0x00010000 Port/miniport interface checking.
        [ ] 0x00040000 Systematic low resources simulation.
        [ ] 0x00080000 DDI compliance checking (additional).
        [X] 0x00200000 NDIS/WIFI verification.
        [X] 0x00800000 Kernel synchronization delay fuzzing.
        [X] 0x01000000 VM switch verification.
        [X] 0x02000000 Code integrity checks.
    
      Internal Flags:
    
        [X] 0x00100000 Extended Verifier flags (internal).
    
        [X] Indicates flag is enabled.
    
      Boot Mode:
    
        Persistent
    
      Rules:
    
        All rules are using default settings
    
      Verified Drivers:
    
        aswelam.sys
        iarnvme.sys
        iastorb.sys
        aswvmm.sys
        aswrvrt.sys
        aswbuniv.sys
        aswblog.sys
        aswbidsh.sys
        aswardisk.sys
        aswsp.sys
        aswsnx.sys
        aswkbd.sys
        selow_x64.sys
        aswrdr2.sys
        aswbidsdriver.sys
        aswarpot.sys
        neo6_x64_vpn.sys
        nvlddmkm.sys
        teedriverw8x64.sys
        e1d65x64.sys
        xtuacpidriver.sys
        steamstreamingmicrophone.sys
        steamstreamingspeakers.sys
        nvhda64v.sys
        rtkvhd64.sys
        lhidfilt.sys
        lmoufilt.sys
        dump_dumpstorport.sys
        dump_stornvme.sys
        dump_dumpfve.sys
        aswmonflt.sys
        rtcore64.sys
        aswstm.sys
    I entered safemode, turned off verifier and collected the logs. I am willing to continue verifier enabling one tick at a time after the 12 mark to see which one tripped it. I can run everything but that one or only that one and see if we get more dumps. Everything relevant is posted here for sharing: Microsoft OneDrive - Access files anywhere. Create docs with free Office Online. Please let me know if the link doesn't work. Folder contains memory.dmp and v2/dm collector logs
      My Computer


  8. Posts : 41,412
    windows 10 professional version 1607 build 14393.969 64 bit
       #28

    Uninstall all software / hardware related to SteamStreamingMicrophone

    Do not reinstall the software.

    Restart windows driver verifier with the 19 customized tests.


    Code:
    Steam                                                          2.10.91.91     Valve Corporation
    Code:
    SteamStreamingMicrophone.sys Fri Jul 28 08:33:15 2017 (597B593B)
    Code:
    SteamStreami Steam Streaming Microp Steam Streaming Microp Kernel        Manual     Running    OK         TRUE        FALSE        8,192             8,192       0          07/28/17 08:33:15 AM   C:\Windows\system32\drivers\SteamStreamingMicrop 4,096

    Code:
    Name	Steam Streaming Microphone
    Manufacturer	Valve Corporation Audio DDK
    Status	OK
    PNP Device ID	ROOT\STEAMSTREAMINGMICROPHONE\0000
    Driver	c:\windows\system32\drivers\steamstreamingmicrophone.sys (, 39.78 KB (40,736 bytes), 04/30/19 08:30)
    Last edited by zbook; 16 Jun 2019 at 00:45.
      My Computer


  9. Posts : 29
    Windows 10 Pro x64 v1809 build 17763.503
    Thread Starter
       #29

    zbook said:
    Uninstall all software / hardware related to SteamStreamingMicrophone

    Do not reinstall the software.

    Restart windows driver verifier with the 19 customized tests.


    Code:
    Steam                                                          2.10.91.91     Valve Corporation
    Code:
    SteamStreamingMicrophone.sys Fri Jul 28 08:33:15 2017 (597B593B)
    Code:
    SteamStreami Steam Streaming Microp Steam Streaming Microp Kernel        Manual     Running    OK         TRUE        FALSE        8,192             8,192       0          07/28/17 08:33:15 AM   C:\Windows\system32\drivers\SteamStreamingMicrop 4,096

    Code:
    Name	Steam Streaming Microphone
    Manufacturer	Valve Corporation Audio DDK
    Status	OK
    PNP Device ID	ROOT\STEAMSTREAMINGMICROPHONE\0000
    Driver	c:\windows\system32\drivers\steamstreamingmicrophone.sys (, 39.78 KB (40,736 bytes), 04/30/19 08:30)
    I had to check in for Jury Duty today, so I'm afraid not much got done.

    I checked that driver in device manager and it says no problem and it's WHQL.. but I did get another blue screen today... so here are the logs, and I've attached the dump (it's only like 50 mb yeah). So I've uninstalled Steam, and uninstalled those drivers (also delete file) from device manager while I'm at it.

    Now you want me to enable all 19 tests and run for Blue Screens?
      My Computer


  10. Posts : 41,412
    windows 10 professional version 1607 build 14393.969 64 bit
       #30

    There were no links in the above post.

    For any BSOD:

    a) run the V2 log collector to collect new log files

    b) open file explorer> this PC > C: > in the right upper corner search for: C:\Windows\memory.dmp
    > if the file size is < 1.5 GB then zip > post a separate share link into the thread using one drive, drop box, or google drive

    Run windows driver verifier after uninstalling the misbehaving/software.

    If there are no BSOD for 48 hours then the tool can be turned off.

    Drivers / software can be reinstalled after one week of computer stability (no BSOD or unexpected shutdowns / restarts).
      My Computer


 

  Related Discussions
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 19:26.
Find Us




Windows 10 Forums