Windows 10: BSOD on new Laptop

  1.    23 Jan 2016 #1

    BSOD on new Laptop


    Hello - I just bought a new laptop, which came with a preinstalled windows 8.1.
    I immediately updated the computer to windows 10 without any issues.

    I have been using it for some days now, but upon during a movie playback I got my first BSOD (kernel security check failure).
    I thought little of it at first, but a day after I got the same error trying to load a pc-game. Everytime the game loads, I get a BSOD. I suspect its a driver which is only compatible for windows 8.1.

    I have run verifier and if i have done it correctly, the latest dump file should be of that. Apparently its a driver starting upon startup, as I wasnt allowed access to windows when running the verifier.
    I hope you guys can shed some light upon the problem, as I dont want to "build on a flawed machine". Id much rather have it fixed immediately.

    Thanks.
      My ComputerSystem Spec

  2.    24 Jan 2016 #2

    The driver verifier dumpfile flagged
    Code:
      BugCheck C9, {23e, fffff80060f11324, ffffcf8058f96e50, 0}
    *** WARNING: Unable to verify timestamp for dtsoftbus01.sys
    *** ERROR: Module load completed but symbols could not be loaded for dtsoftbus01.sys
    Probably caused by : dtsoftbus01.sys ( dtsoftbus01+1324 )

    Daemon tools, Alcohol 120% and Power Archiver Pro uses SCSI Pass ThroughDirect (SPTD), which is a well known cause for BSOD's.
    Please remove Daemon Tools and run the SPTD pass through remover.


    1. UninstallDaemon Tools

    2. Download the SPTD standalone installer and followthese steps:

    Double click the executable to open it
    Click on the button shown below

    If the Uninstall button is grayedout there is no more SPTD installation on your system, and you can close the window.
    (thanks to: ax0)



      My ComputerSystem Spec

  3.    24 Jan 2016 #3

    lifetec said: View Post
    The driver verifier dumpfile flagged
    Code:
      BugCheck C9, {23e, fffff80060f11324, ffffcf8058f96e50, 0}
    *** WARNING: Unable to verify timestamp for dtsoftbus01.sys
    *** ERROR: Module load completed but symbols could not be loaded for dtsoftbus01.sys
    Probably caused by : dtsoftbus01.sys ( dtsoftbus01+1324 )

    Daemon tools, Alcohol 120% and Power Archiver Pro uses SCSI Pass ThroughDirect (SPTD), which is a well known cause for BSOD's.
    Please remove Daemon Tools and run the SPTD pass through remover.


    1. UninstallDaemon Tools

    2. Download the SPTD standalone installer and followthese steps:

    Double click the executable to open it
    Click on the button shown below

    If the Uninstall button is grayedout there is no more SPTD installation on your system, and you can close the window.
    (thanks to: ax0)



    Hi. Thanks, that did solve the booting error. I was not aware that Daemon Tools would cause BSOD like that.

    However the original BSOD is still present. I managed to make a new log of this incident with verifier. I have attached an updated DM Log
      My ComputerSystem Spec

  4.    24 Jan 2016 #4

    The driver verifier dumpfile blames your Nvdia GPU driver.
    Code:
     *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    Use !analyze -v to get detailed debugging information.
    BugCheck C4, {d2, ffffe0002d62c3c0, ffffe0002d62c000, b30}
    *** WARNING: Unable to verify timestamp for nvlddmkm.sys
    *** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
    Probably caused by : nvlddmkm.sys ( nvlddmkm+3b908 )
    Followup: MachineOwner
    ---------
    2: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    DRIVER_VERIFIER_DETECTED_VIOLATION (c4)
    A device driver attempting to corrupt the system has been caught.  This is
    because the driver was specified in the registry as being suspect (by the
    administrator) and the kernel has enabled substantial checking of this driver.
    If the driver attempts to corrupt the system, bugchecks 0xC4, 0xC1 and 0xA will
    be among the most commonly seen crashes.
    Arguments:
    Arg1: 00000000000000d2, Freeing pool allocation that contains active ERESOURCE.
    Arg2: ffffe0002d62c3c0, ERESOURCE address.
    Arg3: ffffe0002d62c000, Pool allocation start address.
    Arg4: 0000000000000b30, Pool allocation size.
    Debugging Details:
    ------------------
    
    BUGCHECK_STR:  0xc4_d2
    CUSTOMER_CRASH_COUNT:  1
    DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
    PROCESS_NAME:  witcher3.exe
    CURRENT_IRQL:  2
    ANALYSIS_VERSION: 6.3.9600.17336 (debuggers(dbg).150226-1500) x86fre
    LAST_CONTROL_TRANSFER:  from fffff802b56c02c8 to fffff802b5143770
    STACK_TEXT:  
    ffffd000`28c8d0d8 fffff802`b56c02c8 : 00000000`000000c4 00000000`000000d2 ffffe000`2d62c3c0 ffffe000`2d62c000 : nt!KeBugCheckEx
    ffffd000`28c8d0e0 fffff802`b56c9869 : ffffe000`2d62c000 00000000`00000000 00000000`00000001 ffffe000`2d3b6a50 : nt!VerifierBugCheckIfAppropriate+0x3c
    ffffd000`28c8d120 fffff802`b520fb3f : ffffe000`2d62c000 00000000`00000b30 00000000`00000000 fffff802`b5210461 : nt!VfCheckForResource+0x99
    ffffd000`28c8d170 fffff802`b5232d32 : ffffe000`2d62c000 00000000`00000b30 00000000`00000000 00000000`00000000 : nt!ExpCheckForResource+0x3b
    ffffd000`28c8d1c0 fffff802`b53d3150 : 00000000`00000000 ffffe000`2d62c030 00000000`00000000 00000000`00010286 : nt!ExFreePool+0x212
    ffffd000`28c8d2a0 fffff802`b5051d2f : 00000000`00000000 00000000`00000000 ffffd000`28c8d3c0 ffffe000`2d62c080 : nt!ObpRemoveObjectRoutine+0x80
    ffffd000`28c8d300 fffff802`b50e98da : 00000000`00000000 ffffe000`30823a60 00000000`00001c00 00000000`00000000 : nt!ObfDereferenceObjectWithTag+0xbf
    ffffd000`28c8d340 fffff802`b50e977c : 00000000`00000000 ffffd000`28c8d500 ffffe000`2d62c080 00000000`c0000910 : nt!IopCompleteUnloadOrDelete+0xa6
    ffffd000`28c8d400 fffff800`61b1b908 : ffffe000`2d62c260 ffffd000`28c8d530 ffffe000`2d62c330 ffffe000`2d62c2c8 : nt!IoDeleteDevice+0x9c
    ffffd000`28c8d430 ffffe000`2d62c260 : ffffd000`28c8d530 ffffe000`2d62c330 ffffe000`2d62c2c8 00000000`00000000 : nvlddmkm+0x3b908
    ffffd000`28c8d438 ffffd000`28c8d530 : ffffe000`2d62c330 ffffe000`2d62c2c8 00000000`00000000 00000000`00000000 : 0xffffe000`2d62c260
    ffffd000`28c8d440 ffffe000`2d62c330 : ffffe000`2d62c2c8 00000000`00000000 00000000`00000000 fffff800`62161f00 : 0xffffd000`28c8d530
    ffffd000`28c8d448 ffffe000`2d62c2c8 : 00000000`00000000 00000000`00000000 fffff800`62161f00 00000000`00000000 : 0xffffe000`2d62c330
    ffffd000`28c8d450 00000000`00000000 : 00000000`00000000 fffff800`62161f00 00000000`00000000 ffffe000`2d62c080 : 0xffffe000`2d62c2c8
    
    STACK_COMMAND:  kb
    FOLLOWUP_IP: 
    nvlddmkm+3b908
    fffff800`61b1b908 488d0dd15fa100  lea     rcx,[nvlddmkm+0xa518e0 (fffff800`625318e0)]
    SYMBOL_STACK_INDEX:  9
    SYMBOL_NAME:  nvlddmkm+3b908
    FOLLOWUP_NAME:  MachineOwner
    MODULE_NAME: nvlddmkm
    IMAGE_NAME:  nvlddmkm.sys
    DEBUG_FLR_IMAGE_TIMESTAMP:  56716f32
    FAILURE_BUCKET_ID:  0xc4_d2_VRF_nvlddmkm+3b908
    BUCKET_ID:  0xc4_d2_VRF_nvlddmkm+3b908
    ANALYSIS_SOURCE:  KM
    FAILURE_ID_HASH_STRING:  km:0xc4_d2_vrf_nvlddmkm+3b908
    FAILURE_ID_HASH:  {f6025b94-f6f1-05e3-20d8-c9f2f4037a1d}
    Followup: MachineOwner
    ---------
    2: kd> lmvm nvlddmkm
    start             end                 module name
    fffff800`61ae0000 fffff800`626fb000   nvlddmkm T (no symbols)           
        Loaded symbol image file: nvlddmkm.sys
        Image path: nvlddmkm.sys
        Image name: nvlddmkm.sys
        Timestamp:        Wed Dec 16 15:03:30 2015 (56716F32)
        CheckSum:         00BE13AE
        ImageSize:        00C1B000
        Tran
    It could be that the driver is corrupted.

    This is thedriver of your Nvdia GPU.. The driver might be corrupted uninstall withDDU http://www.guru3d.com/files-tags/download-ddu.html and reinstall the latest version.

    You have Asus laptop check for other windows 10 updates/drivers from supportpage of your manufacturer https://www.asus.com/support/Downloa...OINWJ0zTH3/45/.


    Please
      My ComputerSystem Spec

  5.    24 Jan 2016 #5

    lifetec said: View Post
    The driver verifier dumpfile blames your Nvdia GPU driver.
    Code:
     *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    Use !analyze -v to get detailed debugging information.
    BugCheck C4, {d2, ffffe0002d62c3c0, ffffe0002d62c000, b30}
    *** WARNING: Unable to verify timestamp for nvlddmkm.sys
    *** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
    Probably caused by : nvlddmkm.sys ( nvlddmkm+3b908 )
    Followup: MachineOwner
    ---------
    2: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    DRIVER_VERIFIER_DETECTED_VIOLATION (c4)
    A device driver attempting to corrupt the system has been caught.  This is
    because the driver was specified in the registry as being suspect (by the
    administrator) and the kernel has enabled substantial checking of this driver.
    If the driver attempts to corrupt the system, bugchecks 0xC4, 0xC1 and 0xA will
    be among the most commonly seen crashes.
    Arguments:
    Arg1: 00000000000000d2, Freeing pool allocation that contains active ERESOURCE.
    Arg2: ffffe0002d62c3c0, ERESOURCE address.
    Arg3: ffffe0002d62c000, Pool allocation start address.
    Arg4: 0000000000000b30, Pool allocation size.
    Debugging Details:
    ------------------
    
    BUGCHECK_STR:  0xc4_d2
    CUSTOMER_CRASH_COUNT:  1
    DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
    PROCESS_NAME:  witcher3.exe
    CURRENT_IRQL:  2
    ANALYSIS_VERSION: 6.3.9600.17336 (debuggers(dbg).150226-1500) x86fre
    LAST_CONTROL_TRANSFER:  from fffff802b56c02c8 to fffff802b5143770
    STACK_TEXT:  
    ffffd000`28c8d0d8 fffff802`b56c02c8 : 00000000`000000c4 00000000`000000d2 ffffe000`2d62c3c0 ffffe000`2d62c000 : nt!KeBugCheckEx
    ffffd000`28c8d0e0 fffff802`b56c9869 : ffffe000`2d62c000 00000000`00000000 00000000`00000001 ffffe000`2d3b6a50 : nt!VerifierBugCheckIfAppropriate+0x3c
    ffffd000`28c8d120 fffff802`b520fb3f : ffffe000`2d62c000 00000000`00000b30 00000000`00000000 fffff802`b5210461 : nt!VfCheckForResource+0x99
    ffffd000`28c8d170 fffff802`b5232d32 : ffffe000`2d62c000 00000000`00000b30 00000000`00000000 00000000`00000000 : nt!ExpCheckForResource+0x3b
    ffffd000`28c8d1c0 fffff802`b53d3150 : 00000000`00000000 ffffe000`2d62c030 00000000`00000000 00000000`00010286 : nt!ExFreePool+0x212
    ffffd000`28c8d2a0 fffff802`b5051d2f : 00000000`00000000 00000000`00000000 ffffd000`28c8d3c0 ffffe000`2d62c080 : nt!ObpRemoveObjectRoutine+0x80
    ffffd000`28c8d300 fffff802`b50e98da : 00000000`00000000 ffffe000`30823a60 00000000`00001c00 00000000`00000000 : nt!ObfDereferenceObjectWithTag+0xbf
    ffffd000`28c8d340 fffff802`b50e977c : 00000000`00000000 ffffd000`28c8d500 ffffe000`2d62c080 00000000`c0000910 : nt!IopCompleteUnloadOrDelete+0xa6
    ffffd000`28c8d400 fffff800`61b1b908 : ffffe000`2d62c260 ffffd000`28c8d530 ffffe000`2d62c330 ffffe000`2d62c2c8 : nt!IoDeleteDevice+0x9c
    ffffd000`28c8d430 ffffe000`2d62c260 : ffffd000`28c8d530 ffffe000`2d62c330 ffffe000`2d62c2c8 00000000`00000000 : nvlddmkm+0x3b908
    ffffd000`28c8d438 ffffd000`28c8d530 : ffffe000`2d62c330 ffffe000`2d62c2c8 00000000`00000000 00000000`00000000 : 0xffffe000`2d62c260
    ffffd000`28c8d440 ffffe000`2d62c330 : ffffe000`2d62c2c8 00000000`00000000 00000000`00000000 fffff800`62161f00 : 0xffffd000`28c8d530
    ffffd000`28c8d448 ffffe000`2d62c2c8 : 00000000`00000000 00000000`00000000 fffff800`62161f00 00000000`00000000 : 0xffffe000`2d62c330
    ffffd000`28c8d450 00000000`00000000 : 00000000`00000000 fffff800`62161f00 00000000`00000000 ffffe000`2d62c080 : 0xffffe000`2d62c2c8
    
    STACK_COMMAND:  kb
    FOLLOWUP_IP: 
    nvlddmkm+3b908
    fffff800`61b1b908 488d0dd15fa100  lea     rcx,[nvlddmkm+0xa518e0 (fffff800`625318e0)]
    SYMBOL_STACK_INDEX:  9
    SYMBOL_NAME:  nvlddmkm+3b908
    FOLLOWUP_NAME:  MachineOwner
    MODULE_NAME: nvlddmkm
    IMAGE_NAME:  nvlddmkm.sys
    DEBUG_FLR_IMAGE_TIMESTAMP:  56716f32
    FAILURE_BUCKET_ID:  0xc4_d2_VRF_nvlddmkm+3b908
    BUCKET_ID:  0xc4_d2_VRF_nvlddmkm+3b908
    ANALYSIS_SOURCE:  KM
    FAILURE_ID_HASH_STRING:  km:0xc4_d2_vrf_nvlddmkm+3b908
    FAILURE_ID_HASH:  {f6025b94-f6f1-05e3-20d8-c9f2f4037a1d}
    Followup: MachineOwner
    ---------
    2: kd> lmvm nvlddmkm
    start             end                 module name
    fffff800`61ae0000 fffff800`626fb000   nvlddmkm T (no symbols)           
        Loaded symbol image file: nvlddmkm.sys
        Image path: nvlddmkm.sys
        Image name: nvlddmkm.sys
        Timestamp:        Wed Dec 16 15:03:30 2015 (56716F32)
        CheckSum:         00BE13AE
        ImageSize:        00C1B000
        Tran
    It could be that the driver is corrupted.

    This is thedriver of your Nvdia GPU.. The driver might be corrupted uninstall withDDU http://www.guru3d.com/files-tags/download-ddu.html and reinstall the latest version.

    You have Asus laptop check for other windows 10 updates/drivers from supportpage of your manufacturer https://www.asus.com/support/Downloa...OINWJ0zTH3/45/.


    Please
    Thank you so much, this worked! Reinstalling the Geforce Drivers did the job. Must have been a corrupted driver as you pointed out.

    A final thing:
    I can only see updates to the BIOS on the asus page - Is this useful and in this case should I only install the latest or are they all single-updates which all need to be installed?

    Again - Thanks, I am grateful !
      My ComputerSystem Spec


 

Related Threads
1st BSOD on new Laptop in BSOD Crashes and Debugging
Hi Everyone, so I just bought this laptop a few weeks ago, but earlier I did a clean windows reset, and then install all my files again, I have like installed almost 15+ programs and after I have installed my programs, my windows just crashed :(...
I have an Asus laptop and since I upgraded to windows 10, I've been getting periodical shutdowns. I've received two Bsod's but most of the time, my laptop would fall asleep while I was using it. I ran chkdsk and everything checked out ok so I...
Machine_Check_Exception BSOD on new laptop in BSOD Crashes and Debugging
So far I've gotten it twice. Before I go through the work of returning and getting a new one I'm hoping it's an easy fix. 51968
Hi there, I upgraded to Windows 10 a couple of days ago. And when I shutdown and turned it on the next morning or after few hours, I straight away had BSOD after passing the bios right just after the windows logo. This has happened twice (since I...
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 18:33.
Find Us