BSOD Random Crash, Possibly Memory Corruption?

Page 2 of 2 FirstFirst 12

  1. Posts : 14,046
    Windows 11 Pro X64 22H2 22621.1848
       #11

    I can't do anything with the newer dumps as Microsoft has not placed the symbols for the 14393.447 build on the symbol server. Makes it impossible for me to even look at anything useful, sorry.

    I don't know what we are going to do as this completely wipes out the BSOD support, unless someone has another way to get the symbols.
      My Computers


  2. Posts : 12
    Windows 10
    Thread Starter
       #12

    Thanks for the effort Ztruker That's why my debugger wont work! This is really wired for them to do that. Hopefully they are just uploading it late :P
      My Computer


  3. Posts : 14,046
    Windows 11 Pro X64 22H2 22621.1848
       #13

    I think I just fixed the symbol problem, but not sure yet. I changed the server part of my symbol path from

    Code:
    http://msdl.microsoft.com/download/symbols
    to

    Code:
    https://msdl.microsoft.com/download/symbols
    (*http to *https) and so far it's working.

    Can you control the overclocking of your CPU or RAM. I see this:
    Code:
    2: kd> !sysinfo cpuspeed
    CPUID:        "Intel(R) Core(TM) i5-4200U CPU @ 1.60GHz"
    MaxSpeed:     1600
    CurrentSpeed: 2295
    I see looking at the specs the CPU speed can range from 1600Mhz to 3800Mhz so it's probably automatic and not under your control.

    The latest dump still indicates a single bit memory error. It's possible this is caused by a device driver. The only suggestion I have is to try running with Driver Verifier enabled and see if that shows anything.

    ===================================================
    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 BSOD with a mini dump that will tell us what driver caused it.
      My Computers


  4. Posts : 12
    Windows 10
    Thread Starter
       #14

    Great you find a solution!

    Oh crap.... still single bit error? I have already remove the extra RAM! But u said driver issue, is that mean the hardware is fine?
    No I didn't overclock anything. It's automatic.
    I have tried out the verifier. The gd thing is it didn't take long to bsod. Actually it bsod right away after reboot.... And it bsod multiple times (weirdly without crash dump. The code is something "multiple ISP request") before I can reboot it to safe mode to disable the verifier. I have attached the crash dump here.
      My Computer


  5. Posts : 14,046
    Windows 11 Pro X64 22H2 22621.1848
       #15

    Verifier found a problem with the Nvidia driver:
    Code:
    BUGCHECK_P1: 219
    BUGCHECK_P2: fffff8026d44fb0d
    BUGCHECK_P3: ffff800a27500ca0
    BUGCHECK_P4: 0
    BUGCHECK_STR:  0xc9_219
    
    DRIVER_VERIFIER_IO_VIOLATION_TYPE:  219
    
    FAULTING_IP: 
    dxgkrnl!DpiFdoHandleDevicePower+1cd
    fffff802`6d44fb0d 4533c9          xor     r9d,r9d
    
    FOLLOWUP_IP: 
    dxgkrnl!DpiFdoHandleDevicePower+1cd
    fffff802`6d44fb0d 4533c9          xor     r9d,r9d
    
    IRP_ADDRESS: ffff800a27500ca0
    DEVICE_OBJECT: ffff800a254c0030
    DRIVER_OBJECT: ffff800a251c0cd0
    IMAGE_NAME:  nvlddmkm.sys
    DEBUG_FLR_IMAGE_TIMESTAMP:  5782ca2f
    MODULE_NAME: nvlddmkm
    FAULTING_MODULE: fffff80270430000 nvlddmkm
    You have Nvidia driver version 368.81 dated Sun Jul 10 18:20:31 2016
    The latest on the Nvidia web site is version 375.95 dated 2016.11.18.

    Try it using DDU as described in this tutorial:

    Remove and install latest Nvidia drivers:

    I suggest completely uninstalling the Nvidia display drivers using Display Driver Uninstaller (DDU) from WagnardMobile (near bottom of page) then get the latest driver for you Nvidia card here: NVIDIA Driver Downloads

    Then do a custom install of only the NVidia graphics driver and the PhysX driver.

    See if that gets rid of the problem.
      My Computers


  6. Posts : 12
    Windows 10
    Thread Starter
       #16

    Hi Ztruker, I have reinstall the whole computer, update all drivers, remove extra RAM but the problem still persist.... I even remove the ssd cache drive which was failed and replaced before. I guess the only option left is to send it to repair. I hate dealing with ASUS support, they are rude and rubbish..... Anyway thanks for the help all along! You have been very supportive
    Last edited by kurkyThomas; 25 Nov 2016 at 06:47.
      My Computer


  7. Posts : 14,046
    Windows 11 Pro X64 22H2 22621.1848
       #17

    Make sure you have your data backed up before sending to ASUS as I'm sure they will wipe it and do a Clean Install again, just like you did.

    Please let me know what ASUS tells you.
      My Computers


  8. Posts : 12
    Windows 10
    Thread Starter
       #18

    Sure thing. I will post an update once it's done
      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 02:38.
Find Us




Windows 10 Forums