4-5 BSOD in 2 days after changing my GPU and RAM

Page 2 of 3 FirstFirst 123 LastLast
  1. Ztruker's Avatar
    Posts : 13,703
    Windows 10 Pro X64 21H1 19043.1266
       #11

    The 05 and 06 dumps (2 each) are all identical and show this:
    Code:
    SYSTEM_SERVICE_EXCEPTION (3b)
    An exception happened while executing a system service routine.
    Arguments:
    Arg1: 00000000c0000005, Exception code that caused the bugcheck
    Arg2: fffff8055a695674, Address of the instruction which caused the bugcheck
    Arg3: fffff9041b18d810, Address of the context record for the exception that caused the bugcheck
    Arg4: 0000000000000000, zero.

    *** WARNING: Unable to verify timestamp for MAudioMTrack.sys


    This is a very old driver:
    Code:
    1: kd> lmvm MAudioMTrack
    Browse full module list
    start             end                 module name
    fffff805`5a690000 fffff805`5a707000   MAudioMTrack T (no symbols)           
        Loaded symbol image file: MAudioMTrack.sys
        Image path: MAudioMTrack.sys
        Image name: MAudioMTrack.sys
        Browse all global symbols  functions  data
        Timestamp:        Wed Apr 24 10:31:02 2013 (5177ECA6)
        CheckSum:         00082150
        ImageSize:        00077000
        Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
    M-audio Mtrack plus audio driver
    M-Audio

    Attachment 287458

    Looks to be some kind of USB device. Remove it unless you can find an updated driver for it.
      My Computers

  2. Ztruker's Avatar
    Posts : 13,703
    Windows 10 Pro X64 21H1 19043.1266
       #12

    Did you install all new RAM? If so, do you have the old RAM? If yes, remove the new RAM and reinstall the old RAM, just for testing.
      My Computers


  3. Posts : 9
    Win 10
    Thread Starter
       #13

    Computer just restarted again, I haven't seen the crash this time. Do you guys want the log collector scan again?

    I don't know what to do at this point, my computer seems to crash twice or three times a day~~
      My Computer

  4. Ztruker's Avatar
    Posts : 13,703
    Windows 10 Pro X64 21H1 19043.1266
       #14

    Did you read my dump analysis? Follow directions, see what happens.

    .... yes, new V2 please.
      My Computers


  5. Posts : 1,867
    Windows 10 Pro 2004 20H1
       #15

    Ztruker said:
    I think John prefers uploading the zips to a file sharing site to reduce space usage on our server. Uploading here is acceptable but not preferred.
    It should probably say that in the instructions -

    9. In your BSOD post, either...
    Upload the created zip file to a reputable file sharing service such as OneDrive, Google Drive, Dropbox or Amazon Cloud Drive (US) (UK) and post a share link.
    Upload the zip file directly into your post.
      My Computer


  6. Posts : 1,867
    Windows 10 Pro 2004 20H1
       #16

    Ztruker said:
    Looks to be some kind of USB device. Remove it unless you can find an updated driver for it.
    John Carrona's site (excellent resource) lists it -

    Driver Reference Table (DRT) | MAudioMTrack.sys

    It links to the M-Audio site with the latest version of the driver 6.1.3.
      My Computer



  7. Posts : 9
    Win 10
    Thread Starter
       #17

    Thank you both for your support. I am waiting for my friend to lend me back my GPU. Do you suggest me to try putting back the old GPU first, or the old RAM first? Which one I should test first.

    As for the driver Ztruker suggested me, I am actually uninstalling the old version, cause the driver doesn't want to install without that, and I'm not sure I have the good version actually.

    As for the third V2 report here it is guys. Thanks again for the support

    YUVA01L-(2020-07-10_19-54-50).zip - Google Drive


    PS: I will try my old GPU tomorrow night, my friend will lend it back to me, and i'll try to switch the RAM too, in too separate times! ~~

    Edit 1: I haven't seen there was a second page, I will change the ram as soon has possible

    Edit 2: For the M-track audio, I receive the error: Another version of this product is already installed.. and after that a run time error

    I've tried to uninstall the program from the list of Programs and Features. (M-track audio & M-Track Plus)

    Then I've uninstalled a couple of drivers in Device Manager, there was a few of them, but every time I restart the PC, they are back into the Device Manager list.

    This is an external audio card, so when I uninstall it, my sound should not work anymore..


    Last edit: I've taken my driver here : M-Audio

    In the legacy section M-Track (I don't have the MkII) with win10 64bit.

    and the only driver available is this one "1.0.6 (PC) 05-02-2013 M-Track 1.0.6"

    This suggested by another user doesn't seems to work for me, i've tried to uninstall "everything" but it still wouldn't work.

    - - - Updated - - -

    Here's my last crash: YUVA01L-(2020-07-10_22-14-13).zip - Google Drive

    I will switch the RAM and GPU tomorrow.

    But about the driver for my external audio card i'm in a mess...~~ My guitars and micro phone are plugged in this.

    I can't "throw" this away... and I couldn't installed the driver suggested :

    "John Carrona's site (excellent resource) lists it -

    Driver Reference Table (DRT) | MAudioMTrack.sys"

    Again, thanks for your time..


    Edit 10 min later: Here's a crash 10 min later : YUVA01L-(2020-07-10_22-31-45).zip - Google Drive

    I've tried to change the plug where the m-track audio is plugged in, I know it won't help much ...

    - - - Updated - - -

    This time "kernel security check failure"

    I am actually making an sfc/scannow like suggested somewhere in a thread about that error; I received the following feedback : Windows Resource Protection did not find any integrity violations.

    and here's the last V2 log : YUVA01L-(2020-07-10_23-11-05).zip - Google Drive

    I am also doing this one : chkdsk /f c: (I will do it on each of my hard drive)
    Last edited by WeConnected; 10 Jul 2020 at 23:19.
      My Computer


  8. Posts : 1,867
    Windows 10 Pro 2004 20H1
       #18

    You would need to manually install the drivers -

    Download the drivers from M-Track.

    In Device Manager, right-click on the device and select Properties

    Click on the Driver tab and select Update Driver

    Click Browse my computer for driver software

    Click Let me pick from an available list of drivers on my computer

    Click Have Disk and then Browse to the path where you saved the M-Track drivers.
      My Computer


  9. Posts : 9
    Win 10
    Thread Starter
       #19

    At OldNavyGuy; Thanks alot, I was able to install it, it rebooted my computer :)

    Thanks again! I'll give more feedback after switch the RAM and GPU tomorrow evening!

    - - - Updated - - -

    can't modify last post

    Another one for the road : YUVA01L-(2020-07-11_02-15-23).zip - Google Drive
      My Computer

  10. Ztruker's Avatar
    Posts : 13,703
    Windows 10 Pro X64 21H1 19043.1266
       #20

    Four of the dumps show single bit memory failure so put the old memory back if you can and test for awhile. I all runs okay then remove the old memory and install half of the new memory and test. If okay remove the new memory and install the other half then test.

    If at any point you start having problems (BSODs) then the memory currently installed is the cause. Remove half of it leaving 8GB and test. If problem then what is installed is the cause. If no problem, swap installed with the other 8GB DIMMs which should be the one that causes the problem. Test to verify. Once you know which one is causing the problem, RMA it for a new one.

    Doing it this way should be faster than using memtest86+ to test 32GB of ram, that could takes many days. If you prefer to test it, here is the procedure:

    ===================================================
    Up through DDR3, follow this tutorial: MemTest86+ - Test RAM - Windows 10 Forums
    DDR4, follow this tutorial: MemTest86 v8.1 Free Memory Testing Tool Review

    Both of these are diagnostic tools designed to test Random Access Memory (RAM) for faults. They will verify that:
    • RAM will accept and keep random patterns of data sent to it
    • There are no errors when different parts of memory try to interact
    • There are no conflicts between memory addresses

    They run from bootable media to isolate the RAM from the system, no other components are taken into account during the test.

    warning   Warning
    MemTest86+ and Memtest86 need to run for at least 8 passes to be anywhere near conclusive, anything less will not give a complete analysis of the RAM. The new version of Memtest86 only allows 4 passes for the free version so run it twice, back to back.

    If you are asked to run MemTest86+ or Memtest86 by a Ten Forums member make sure you run the full 8 (or 4+4) passes for conclusive results. If you run less than 8 passes you will be asked to run it again.

    Note   Note
    Both of these diagnostics has been known to discover errors in RAM in later passes than the eighth pass. This is for information only; if you feel there is a definite problem with the RAM and 8 passes have shown no errors feel free to continue for longer.

    Running 8 passes of MemTest86+ or 4+4 passes of Memtest86 is a long and drawn out exercise and the more RAM you have the longer it will take. It's recommended to run it overnight, starting just before you go to bed and leave it overnight.

    Take a picture when done and post in the forum please.

    Code:
    IRQL_NOT_LESS_OR_EQUAL (a)
    
    MODULE_NAME: memory_corruption
    IMAGE_NAME:  memory_corruption
    FOLLOWUP_NAME:  memory_corruption
    DEBUG_FLR_IMAGE_TIMESTAMP:  0
    MEMORY_CORRUPTOR:  ONE_BIT
    STACK_COMMAND:  .thread ; .cxr ; kb
    FAILURE_BUCKET_ID:  MEMORY_CORRUPTION_ONE_BIT
    BUCKET_ID:  MEMORY_CORRUPTION_ONE_BIT
    PRIMARY_PROBLEM_CLASS:  MEMORY_CORRUPTION_ONE_BIT
    
    FAILURE_ID_HASH_STRING:  km:memory_corruption_one_bit
    Code:
    fffff803`77467248  fffff803`82087798Unable to load image MAudioMTrack.sys, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for MAudioMTrack.sys
     MAudioMTrack+0x7798
    The only driver I see is this: M-Audio.

    You may need to replace the M-Track. I don't know what they cost but that may be the only solution.

    For now, uninstall the driver and unplug it and test for awhile and see if that resolves the problem. If yes then you know for sure that is the cause of the problem. If you still get BSODs then something else is the cause. Leave it unplugged and the driver uninstalled then run Driver Verifier and see if that finds anything for us.

    Run Driver Verifier

    Driver Verifier-- tracking down a mis-behaving driver.

    Following the instructions in the above link will check for problems in all non-Microsoft drivers.

    What we're looking for is a verifier generated BSOD with a mini dump that will tell us what driver caused it. If you get a BSOD, rerun the V2 log collector as soon as possible and upload the resulting zip file. Also see if there is a new C:\Windows \MEMORY.DMP file. If there is, copy it to another location then zip it an upload to a file sharing site like OneDrive and post a link to it here.

    To check if verifier is active, open a Command Prompt and enter:

    verifier /query

    If not active it will respond with

    No drivers are currently verified.

    If you have questions, see this additional tutorial which may help to clear things up.

    Enable and Disable Driver Verifier in Windows 10
      My Computers


 
Page 2 of 3 FirstFirst 123 LastLast

  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 05:33.
Find Us




Windows 10 Forums