BSOD issue WIN10

Discussion in 'Windows 10 Blue Screen of Death (BSOD)' started by OlivierM, Sep 8, 2015.

  1. OlivierM

    OlivierM New Member

    Joined:
    Sep 8, 2015
    Messages:
    17
    Likes Received:
    1
    hello,

    I have a new BSOD MEMORY_MANAGEMENT. (find dump file enclosed)
    And Something Strange about graphic card:
    upload_2015-9-13_19-1-17.

    upload_2015-9-13_19-1-17.
     

    Attached Files:

  2. kemical

    kemical Windows Forum Admin
    Staff Member Premium Supporter Microsoft MVP

    Joined:
    Aug 28, 2007
    Messages:
    31,852
    Likes Received:
    1,569
    Code:
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 1A, {403, fffff6800d867070, c9d0000032d10867, fffff6800d867050}
    
    Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+10dce )
    
    Followup: MachineOwner
    ---------
    
    1: kd> !analyze -v;r;kv;lmtsmn;.bugcheck;!peb;!sysinfo cpuinfo;!sysinfo machineid; !sysinfo cpuspeed; !sysinfo smbios
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    MEMORY_MANAGEMENT (1a)
        # Any other values for parameter 1 must be individually examined.
    Arguments:
    Arg1: 0000000000000403, The subtype of the bugcheck.
    
    Hi,
    if you remember I did say that it might be down to a RAM issue and the above Bugcheck means a fatal memory management error occurred. The 'sub-type' of the Bugcheck also means it's possibly a hardware error.
    Windows does have a memory testing app but it can miss errors and the best app for the job is Memtest86.
    If you open the link below you'll see you can run Memtest86 in two ways. You can either burn it to disk or install it onto a USB drive it's entirely up to you. You'll then need to enter the bios to change the boot order so you can boot from either the Disk or USB stick you have Memtest86 on.
    You must test for at least 12 hours unless it becomes obvious there is a problem straight away (you'll see errors outlined in red.
    Memtest86+ - Advanced Memory Diagnostic Tool

    As for your gpu drivers, it's possible that this error may be connected in some way but testing will prove either way. Code 43 is written in Device manager which can mean the driver is reporting the device has failed. Try installing or re-installing the drivers found on your support page.
    Code 43: Windows has stopped this device because it has reported problems
     
    #22 kemical, Sep 13, 2015
    Last edited: Sep 13, 2015
  3. OlivierM

    OlivierM New Member

    Joined:
    Sep 8, 2015
    Messages:
    17
    Likes Received:
    1
    Hi Kemical,

    I give you some news:

    - I have run memtest86 during 24h and no errors. :(
    - i have re-installed drivers for Intel HD 4000 and now, no issue is indicated on this Card.
    - I have desactivated the ATI card at the moment.

    Olivier
     
  4. kemical

    kemical Windows Forum Admin
    Staff Member Premium Supporter Microsoft MVP

    Joined:
    Aug 28, 2007
    Messages:
    31,852
    Likes Received:
    1,569
    Ok Oliver, thanks for updating. Sometimes Memtest86 won't find any errors even when the RAM is bad. Let's leave the RAM a moment and try something else. As this issue was present in the previous os and due to the clues we've seen so far I'd hazard that it's either a RAM issue or an issue with a gpu (possibly faulty).
    See how you run with the ATI card disabled. If all seems well after a certain period of time say 48-36hrs then try enabling the ATI card again. If a bsod should occur after you do this then chances are it's the ATI card which is at fault (probably).

    Post any new dump files.
     
  5. OlivierM

    OlivierM New Member

    Joined:
    Sep 8, 2015
    Messages:
    17
    Likes Received:
    1
    Hello,
    One day Nothing, and today ... new BSOD.:(
    Find enclosed minidump.
     

    Attached Files:

  6. kemical

    kemical Windows Forum Admin
    Staff Member Premium Supporter Microsoft MVP

    Joined:
    Aug 28, 2007
    Messages:
    31,852
    Likes Received:
    1,569
    Code:
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 4E, {2, 32d10, 15f5ff, 1}
    
    Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+1ec74 )
    
    Followup: MachineOwner
    
    Hi,
    the above error can be caused by a bug in a device driver, bios or a hardware problem. The only drivers left on the system which date 2012 are:
    Accelerometer.sys Mon Sep 24 16:31:45 2012: HP Mobile Data Protection System Accelerometer
    WirelessButtonDriver64.sys Thu Aug 30 04:11:29 2012: HP wireless driver - 1st seen in Windows 8 Apparently related to various keyboard functions and FN key.

    There are later versions for these drivers but you must look under the Windows 8 section of the driver support page.

    If you change the above drivers and the bsod repeats then please remove one stick of RAM (I'm assuming you have two sticks) run on one stick for a while and see if the machine bsod's. If it does swap sticks and again just run on that one stick. The aim is to find a stick which doesn't bsod. I've found this method successful in cases where memtest86 wasn't reporting errors but all the signs pointed to bad ram. Memtest probably would error out eventually but only after many hours. This is just a way round that.
     
  7. OlivierM

    OlivierM New Member

    Joined:
    Sep 8, 2015
    Messages:
    17
    Likes Received:
    1
    Hello,

    i haven't succeeded to update these 2 drivers. I have then disabled these 2 functions and rename the drivers, i suppose that's enough.
    But i have had a new BSOD. find enclosed the dmp file.
    As the hard drive have been already changed. i suppose it is a ram issue.
     

    Attached Files:

  8. kemical

    kemical Windows Forum Admin
    Staff Member Premium Supporter Microsoft MVP

    Joined:
    Aug 28, 2007
    Messages:
    31,852
    Likes Received:
    1,569
    Code:
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck F7, {2a80a1d0d470, 55891dc984f4, ffffaa76e2367b0b, 0}
    
    Probably caused by : ntkrnlmp.exe ( nt!_report_gsfailure+25 )
    
    Followup: MachineOwner
    
    Hi,
    the above bugcheck we've seen before and can sometimes be related to security applications. Please remove Avast (sometimes known for causing issues).

    Also how did the running on one stick of RAM go? No results?

    Also may I ask why was this issue never attended to when you were running Windows 8.1?

    Is your laptop still under warranty?

    dtlitescsibus.sys Fri Mar 27 02:05:54 2015: Daemon Tools a well known cause of BSOD's.

    ScpVBus.sys Sun May 05 22:31:26 2013: XInput Wrapper for DS3 and Play.com USB Dual DS2 Controller please remove.

    eubakup.sys Sun Dec 14 16:46:37 2014: Easus Total Backup remove to test.

    Please run a chkdsk:
    The How-To Geek Guide to Using Check Disk in Windows 7, 8, or 10
     
  9. OlivierM

    OlivierM New Member

    Joined:
    Sep 8, 2015
    Messages:
    17
    Likes Received:
    1
    Hi,

    I have only one stick of RAM (4Go)
    This PC was to my mother before, when it was Under warranty, they have changed the Harddrive disk.
    But BSOD was still here. and she has not used the warranty again. that's the reason why.
    i will remove all the soft you tell me, and run a check disk. but as said before the disk has already been changed.
    i keep you informed. thanks

    Olivier
     
  10. kemical

    kemical Windows Forum Admin
    Staff Member Premium Supporter Microsoft MVP

    Joined:
    Aug 28, 2007
    Messages:
    31,852
    Likes Received:
    1,569
    Ok Olivier, thanks for updating. I'll await your next post.
     
  11. OlivierM

    OlivierM New Member

    Joined:
    Sep 8, 2015
    Messages:
    17
    Likes Received:
    1
    Hello,
    Good news, no more BSOD
    I have found compatible RAM to test, and yesss. no more BSOD.
    thanks a lot for your time. :up:

    Olivier
     
  12. kemical

    kemical Windows Forum Admin
    Staff Member Premium Supporter Microsoft MVP

    Joined:
    Aug 28, 2007
    Messages:
    31,852
    Likes Received:
    1,569
    Hey Olivier!
    That's great news... :) Thank you for posting back too. Best of luck with the new hardware..
     

Share This Page

Loading...