Windows 10: looking to have Memory dump file looked at Solved

Page 1 of 2 12 LastLast
  1.    03 Jul 2018 #1

    looking to have Memory dump file looked at


    hi,
    i would like to have someone read the memory dump and tell me what they see as the error.
    my guess being a ryzen machine it's ether ram or a device driver.

    thanks,
    Nathan Saunders
    looking to have Memory dump file looked at Attached Files
      My ComputerSystem Spec

  2. Ztruker's Avatar
    Posts : 6,424
    Windows 10 Pro X64 17134.191
       03 Jul 2018 #2

    Looks like you've only had one BSOD,
    Code:
    BugCheck 139, {3, ffff860f124addb0, ffff860f124add08, 0}
    
    *** ERROR: Module load completed but symbols could not be loaded for Wdf01000.sys
    *** WARNING: Unable to verify timestamp for USBXHCI.SYS
    *** ERROR: Module load completed but symbols could not be loaded for USBXHCI.SYS
    Probably caused by : USBXHCI.SYS ( USBXHCI+27c73 )
    Those are both Windows Operating system files, neither the cause of the failure.

    Your specs say you have 8GB DDR3 but the dump and supporting files say 4GB. Since you've only had this single BSOD, try reseating ( removing then reinstalling) the memory DIMM as sometimes a contact can become slightly corroded. If you get another then I suggest testing your memory for the full 8 passes as described below.

    ===================================================
    Follow this tutorial: MemTest86+ - Test RAM - Windows 10 Forums

    MemTest86+ is a diagnostic tool designed to test Random Access Memory (RAM) for faults. MemTest86+ 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


    Memtest86+ runs from bootable media to isolate the RAM from the system, no other components are taken into account during the test.

    warning   Warning
    MemTest86+ needs to run for at least 8 passes to be anywhere near conclusive, anything less will not give a complete analysis of the RAM.


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

    Note   Note
    MemTest86+ 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+ is a long and drawn out exercise and the more RAM you have the longer it will take. It's recommended to run MemTest86+ just before you go to bed and leave it overnight.

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

  3.    03 Jul 2018 #3

    so the specs in my signature is a different machine,
    the specs for the machine with the issues is
    ryzen 7 1700x with 16 GB of ddr4 win 10 64 bit

    --

    and it sounds like i should reinstall the usb driver right?

    also i have disabled the reboot on BSOD and disabed USB selective suspend based on this:
    BSOD issue with USBXHCI.SYS - Windows 10 Forums

    thanks,
    Nathan Saunders

    Ztruker said: View Post
    Looks like you've only had one BSOD,
    Code:
    BugCheck 139, {3, ffff860f124addb0, ffff860f124add08, 0}
    
    *** ERROR: Module load completed but symbols could not be loaded for Wdf01000.sys
    *** WARNING: Unable to verify timestamp for USBXHCI.SYS
    *** ERROR: Module load completed but symbols could not be loaded for USBXHCI.SYS
    Probably caused by : USBXHCI.SYS ( USBXHCI+27c73 )
    Those are both Windows Operating system files, neither the cause of the failure.

    Your specs say you have 8GB DDR3 but the dump and supporting files say 4GB. Since you've only had this single BSOD, try reseating ( removing then reinstalling) the memory DIMM as sometimes a contact can become slightly corroded. If you get another then I suggest testing your memory for the full 8 passes as described below.

    ===================================================
    Follow this tutorial: MemTest86+ - Test RAM - Windows 10 Forums

    MemTest86+ is a diagnostic tool designed to test Random Access Memory (RAM) for faults. MemTest86+ 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


    Memtest86+ runs from bootable media to isolate the RAM from the system, no other components are taken into account during the test.

    warning   Warning
    MemTest86+ needs to run for at least 8 passes to be anywhere near conclusive, anything less will not give a complete analysis of the RAM.


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

    Note   Note
    MemTest86+ 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+ is a long and drawn out exercise and the more RAM you have the longer it will take. It's recommended to run MemTest86+ just before you go to bed and leave it overnight.

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

  4. Ztruker's Avatar
    Posts : 6,424
    Windows 10 Pro X64 17134.191
       03 Jul 2018 #4

    Yes, 16GB in DIMM1, sorry, I misread the dump BIOS data.
    Reinstalling the USB drivers wouldn't hurt but testing the ram would also be a good idea.

    16GB is going to take a long time, so running over night is the best way to go. I would expect it to take 12 hours or more to get 8 full passes.

    If that doesn't show any problems then I would suggest enabling Driver Verifier to see if it can shake out any driver problems, as follows:
    ===================================================
    Driver Verifier
    is a diagnostic tool built into Windows 10, it is designed to verify both native Microsoft drivers and third party drivers. Driver Verifier's verification process involves putting heavy stress on drivers with the intention of making bad, outdated, incompatible or misbehaving drivers fail. The required result is a BSOD (Blue Screen of Death) which will generate a crash dump for debugging purposes.
    Machines exposed to Driver Verifier will run very sluggishly due to the stress being applied to the drivers.

    Driver Verifier - Enable and Disable in Windows 10

    Pay close attention to PART TWO and make sure the correct boxes are checked.

    Warning:
    It is not advised to run Driver Verifier for more than 48 hours at a time. Disable Driver Verifier after 48 hours or after receiving a BSOD, whichever happens soonest.

    Always create a Restore Point prior to enabling Driver Verifier.

    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 dm_log_collector and upload the resulting zip file.
      My ComputersSystem Spec

  5.    03 Jul 2018 #5

    Hi,
    o.k.
    Does memtest 86+ run under uefi or will i have to go to comparability mode for boot?

    I will I’ll do the mem test tonight then set the driver verfier tomorrow.

    also note that I find ryzen’s ram controller to be sensitive to say the least.
    Thanks, Nathan Saunders

    Ztruker said: View Post
    Yes, 16GB in DIMM1, sorry, I misread the dump BIOS data.
    Reinstalling the USB drivers wouldn't hurt but testing the ram would also be a good idea.

    16GB is going to take a long time, so running over night is the best way to go. I would expect it to take 12 hours or more to get 8 full passes.

    If that doesn't show any problems then I would suggest enabling Driver Verifier to see if it can shake out any driver problems, as follows:
    ===================================================
    Driver Verifier
    is a diagnostic tool built into Windows 10, it is designed to verify both native Microsoft drivers and third party drivers. Driver Verifier's verification process involves putting heavy stress on drivers with the intention of making bad, outdated, incompatible or misbehaving drivers fail. The required result is a BSOD (Blue Screen of Death) which will generate a crash dump for debugging purposes.
    Machines exposed to Driver Verifier will run very sluggishly due to the stress being applied to the drivers.

    Driver Verifier - Enable and Disable in Windows 10

    Pay close attention to PART TWO and make sure the correct boxes are checked.

    Warning:
    It is not advised to run Driver Verifier for more than 48 hours at a time. Disable Driver Verifier after 48 hours or after receiving a BSOD, whichever happens soonest.

    Always create a Restore Point prior to enabling Driver Verifier.

    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 dm_log_collector and upload the resulting zip file.
      My ComputerSystem Spec

  6. Ztruker's Avatar
    Posts : 6,424
    Windows 10 Pro X64 17134.191
       03 Jul 2018 #6

    Not sure about memtest86+. I'll try it on my Lenovo K450 (EFI/GPT) and let you know.
      My ComputersSystem Spec

  7.    03 Jul 2018 #7

    Ztruker said: View Post
    Not sure about memtest86+. I'll try it on my Lenovo K450 (EFI/GPT) and let you know.
    Thanks
      My ComputerSystem Spec

  8. Ztruker's Avatar
    Posts : 6,424
    Windows 10 Pro X64 17134.191
       03 Jul 2018 #8

    Rats, can't test right now. Not able to boot into EFI setup for some reason. Seems to be a comon problem for Lenovo computers sooner or later. I'll see if I can fix it and test then. Meanwhile, give it a shot. If you look at the flash drive memtest86+ creates, it has a EFI folder on it so I believe it will boot in EFI mode okay.
      My ComputersSystem Spec

  9.    03 Jul 2018 #9

    i could not boot memtest 86+ on that computer ether in uefi mode or legacy ether from USB or C.D.
    the system really did not like it.

    thanks,
    Nathan Saunders

    Ztruker said: View Post
    Rats, can't test right now. Not able to boot into EFI setup for some reason. Seems to be a comon problem for Lenovo computers sooner or later. I'll see if I can fix it and test then. Meanwhile, give it a shot. If you look at the flash drive memtest86+ creates, it has a EFI folder on it so I believe it will boot in EFI mode okay.
      My ComputerSystem Spec

  10. Ztruker's Avatar
    Posts : 6,424
    Windows 10 Pro X64 17134.191
       03 Jul 2018 #10

    I could not boot in EFI, Had to set CSM and legacy mode to boot it, then it booted okay.
      My ComputersSystem Spec


 
Page 1 of 2 12 LastLast

Related Threads
Weekly system error memory dump files in Performance & Maintenance
Every week (or so) I get a system error memory dump file around 800 mb in size. If I notice a drop in disk space for no reason I do a disk cleanup and it is there. No BSODs, no lock ups, no system lagging, in other words the computer runs...
Windows didnt create memory dump after crashes in BSOD Crashes and Debugging
I ran into 2 BSODS in space of 10 mins, I couldn't find any memory.dmp file in root directory, and Windows restarted very quickly after the blue screen so I didn't get to spot the error message. How do I make sure Windows logs the crash next it...
Hello I'm trying to configure my PC to dump memory after a PC crash. I'm receiving an error telling the the exchange file is not set or the allocated size is lower than 800 GB. How do I do that? Martin 107567
Debugging a hanging system with no memory dump in BSOD Crashes and Debugging
Hi, I'm having troubles with my Windows 10 laptop freezing when it comes out of sleep mode. I get the login screen and can move the mouse but I cannot click any buttons or type into the login box. The time also remains static and there are no...
First memory dump from Win10 in BSOD Crashes and Debugging
I generated this using NotMyFault with a High IRQL error..... 5429 EDIT: It appears that the Symbol Server hasn't uploaded the symbols for this build :(
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 00:59.
Find Us