BSOD while playing games

Page 1 of 7 123 ... LastLast

  1. Posts : 32
    Windows 10
       #1

    BSOD while playing games


    Hi, I'm new here and I discover this forum from the HP support. I have BSOD from the half of May when I play some games. The weird thing is that I have the blue screen only on some games not all. Like GTA V or the forest while with other games I'm fine. I'm sure this is not an hardware problem because I've replaced my pc through the Amazon support and I still have BSOD. I've got a laptop, HP - Gaming Pavilion 15-cx0013nl
    My hardware is:
    OS Windows 10 build 2004 ver. 19041.329
    Motherboard HP 8478 (U3E1)
    CPU Intel Core i5-8300H
    GPU Intel UHD Graphics 630 and NVIDIA GeForce GTX 1050 4 GB
    RAM 16 GB (2 sticks of 8GB)
    SSD and HDD

    I've added the V2 Log collector for all info and file dump (both have the same errors)
    Hope you can help me, I've installed windows 5 times

    EDIT: I don't know if this can help or not, but the first blue screen was with the background blue and the second was with the background orange (I don't know the differences with the colours)
      My Computer


  2. Posts : 158
    windows 10 pro build 2004
       #2

    Fabiushow said:
    Hope you can help me, I've installed windows 5 times
    how exactly did you install windows? did you do factory reset or did you format and clean install windows? you shouldn't do factory reset because if the windows that came with the laptop has issues then those issues will come back when you do factory reset. you need to install a fresh copy of windows by using windows setup flash usb\dvd. try installing fresh copy 2004 and then try installing fresh copy of 1909 if there still are issues. you can do that the other way round if you want

    Fabiushow said:
    I have BSOD from the half of May when I play some games. The weird thing is that I have the blue screen only on some games not all. Like GTA V or the forest while with other games I'm fine
    are you only getting a bsod when you play some games and you are not getting bsod when you are not playing a game? if yes then i think that the graphics in some games are causing bsod and not all games cause bsod because games have different graphics. try these things:-
    1) completely wipe the nvidia files by using DDU in windows safe mode, restart and install nvidia driver. if you still got bsod then again wipe by using DDU and install an older nvidia driver. download DDU from Official Display Driver Uninstaller DDU Download and you can download old nvidia drivers by finding your graphics card in Advanced Driver Search | NVIDIA. How to do a Clean Graphics Card Driver Installation - DDU Tutorial - GPU Driver Uninstall tells you how to use DDU (AMD drivers is wiped in the youtube video. you have to select nvidia as your gpu in DDU)
    2) it could be that your nvidia card has issues. stress test your graphics card and check if something happens. there are tutorials that teach you how to stress test

    another thing is that you have to force the game to use the nvidia card by following How To Force An App To Use The Dedicated GPU On Windows. you can force it in windows graphics settings or in nvidia control panel. if you don't force it then some games may try to use intel card and issues could happen because the game has to run on nvidia card and not intel card. also don't play games when the laptop is running on battery and always play games when the laptop is plugged to electricity because the laptop could try to force the game to use the intel card to save power when it's running on battery
      My Computer

  3. axe0's Avatar
    Posts : 14,855
    Windows 10 Pro
       #3

    This is a peculiar case. A 0x124 with arg 1 = 10. This is an undocumented hardware crash.
    With 0x124 we usually know immediately who reported the crash, note that this is different from who caused the crash. Since this is unknown territory, we'll need to find out who reported the crash.
    Code:
    WHEA_UNCORRECTABLE_ERROR (124)
    A fatal hardware error has occurred. Parameter 1 identifies the type of error
    source that reported the error. Parameter 2 holds the address of the
    WHEA_ERROR_RECORD structure that describes the error conditon.
    Arguments:
    Arg1: 0000000000000010, Error Source Type
    Arg2: ffffd08957035028
    Arg3: ffffd08941b10aac
    Arg4: ffffd08941b1b1a0
    
    3: kd> dt _WHEA_ERROR_RECORD ffffd08957035028
    PSHED!_WHEA_ERROR_RECORD
       +0x000 Header           : _WHEA_ERROR_RECORD_HEADER
       +0x080 SectionDescriptor : [1] _WHEA_ERROR_RECORD_SECTION_DESCRIPTOR
    
    3: kd> dt _WHEA_ERROR_RECORD_HEADER ffffd08957035028
    PSHED!_WHEA_ERROR_RECORD_HEADER
       +0x000 Signature        : 0x52455043
       +0x004 Revision         : _WHEA_REVISION
       +0x006 SignatureEnd     : 0xffffffff
       +0x00a SectionCount     : 1
       +0x00c Severity         : 1 ( WheaErrSevFatal )
       +0x010 ValidBits        : _WHEA_ERROR_RECORD_HEADER_VALIDBITS
       +0x014 Length           : 0x12a
       +0x018 Timestamp        : _WHEA_TIMESTAMP
       +0x020 PlatformId       : _GUID {83c1603c-1552-48a7-87d1-14d9467d7765}
       +0x030 PartitionId      : _GUID {00000000-0000-0000-0000-000000000000}
       +0x040 CreatorId        : _GUID {57217c8d-5e66-44fb-8033-9b74cacedf5b}
       +0x050 NotifyType       : _GUID {0033f803-2e70-4e88-992c-6f26daf3db7a}
       +0x060 RecordId         : 0x01d65181abd2e0e7
       +0x068 Flags            : _WHEA_ERROR_RECORD_HEADER_FLAGS
       +0x06c PersistenceInfo  : _WHEA_PERSISTENCE_INFO
       +0x074 Reserved         : [12]  ""
    
    3: kd> dt _WHEA_ERROR_RECORD_HEADER_FLAGS 0xffffd08957035028+0x068
    PSHED!_WHEA_ERROR_RECORD_HEADER_FLAGS
       +0x000 Recovered        : 0y0
       +0x000 PreviousError    : 0y0
       +0x000 Simulated        : 0y0
       +0x000 DeviceDriver     : 0y1
       +0x000 CriticalEvent    : 0y0
       +0x000 PersistPfn       : 0y0
       +0x000 Reserved         : 0y00000000000000000000000000 (0)
       +0x000 AsULONG          : 8
    Great, we know a device driver reported the error.

    Let's look at the stack.
    Code:
    3: kd> !dpx
    Start memory scan  : 0xffff91898799a388 ($csp)
    End memory scan    : 0xffff91898799b000 (Kernel Stack Base)
    
                   rsp : 0xffff91898799a388 : 0xfffff80267dc3acc : nt!WheaReportHwError+0x3ec
                   r12 : 0xfffff8026b069700 :  !du ""ms, 4ms, 16ms, 64ms, 128ms, 256ms, 2000ms, 6000ms, 10000ms, 20000ms, 20000+ms""
    0xffff91898799a388 : 0xfffff80267dc3acc : nt!WheaReportHwError+0x3ec
    0xffff91898799a418 : 0xfffff80264fb10a4 : PSHED!PshedRetrieveErrorInfo+0x94
    0xffff91898799a428 : 0xfffff80267ac6179 : nt!EtwWriteEx+0x119
    0xffff91898799a438 : 0xfffff80267dc4509 : nt!WheaHwErrorReportSetSeverityDeviceDriver+0x9
    0xffff91898799a460 : 0xfffff8026b0778f0 : storport!WheaErrorData
    0xffff91898799a468 : 0xfffff80267dc4629 : nt!WheaHwErrorReportSubmitDeviceDriver+0xe9
    0xffff91898799a498 : 0xfffff80267dc4745 : nt!WheaReportFatalHwErrorDeviceDriverEx+0xf5
    0xffff91898799a4f8 : 0xfffff8026b050f45 : storport!StorpWheaReportError+0x9d
    0xffff91898799a548 : 0xfffff8026b06fb60 : storport!g_StorpSourceGuid
    0xffff91898799a558 : 0xfffff8026b050df4 : storport!StorpPopulateErrorData+0x120
    0xffff91898799a588 : 0xfffff8026b04a3b0 : storport!StorpMarkDeviceFailed+0x358
    0xffff91898799a618 : 0xfffff80267ad3220 : nt!KiQuantumEnd+0x120
    0xffff91898799a658 : 0xfffff8026afff9f0 :  !du ""Controller Reset failed due to surprise remove""
    0xffff91898799a690 : 0xffffd08941b40238 :  !du "stornvme"
    0xffff91898799a6f0 : 0xffff91898799a700 :  !du ""s is set is set""
    0xffff91898799a700 : 0x0073006900200073 :  !du ""s is set is set""
    0xffff91898799a708 : 0x0074006500730020 :  !du "" set is set""
    0xffff91898799a710 : 0x0020007300690020 :  !du "" is set""
    0xffff91898799a7c0 : 0xffff91898799a700 :  !du ""s is set is set""
    0xffff91898799a7c8 : 0xfffff8026afff210 :  !du ""Controller Fatal Status is set""
    0xffff91898799a7e0 : 0xfffff80268524440 : nt!ExNode0
    0xffff91898799a840 : 0xfffff8026afff9f0 :  !du ""Controller Reset failed due to surprise remove""
    0xffff91898799a848 : 0xfffff8026b010000 : "storport!StorpTelemetryLogUnitSmartAttributesMeasures <PERF> (storport+0x0)"
    0xffff91898799a898 : 0xfffff8026afef477 : stornvme!NVMeRequestComplete+0x27
    0xffff91898799a8a8 : 0xfffff80268524440 : nt!ExNode0
    0xffff91898799a8e8 : 0xfffff8026afea01d : stornvme!ControllerReset+0x1a1
    0xffff91898799a918 : 0xfffff8026afff9f0 :  !du ""Controller Reset failed due to surprise remove""
    0xffff91898799a968 : 0xfffff8026afed20a : stornvme!NVMeControllerReset+0x10a
    0xffff91898799a998 : 0xfffff8026afec11f : stornvme!NVMeControllerAsyncResetWorker+0x3f
    0xffff91898799a9c8 : 0xfffff8026b047b01 : storport!StorPortWorkItemRoutine+0x41
    0xffff91898799a9f0 : 0xfffff8026b047ac0 : storport!StorPortWorkItemRoutine
    0xffff91898799a9f8 : 0xfffff80267ada7a5 : nt!IopProcessWorkItem+0x135
    0xffff91898799aa18 : 0xfffff8027fda5d20 : usbaudio!USBCaptureRequeueWorker
    0xffff91898799aa28 : 0xfffff80267ada670 : nt!IopProcessWorkItem
    0xffff91898799aa68 : 0xfffff80267a33f25 : nt!ExpWorkerThread+0x105
    0xffff91898799aa80 : 0xfffff80267ada670 : nt!IopProcessWorkItem
    0xffff91898799aa90 : 0x0038006500350036 :  !du "65e8773d"
    0xffff91898799aaa8 : 0xffffd0893e883060 : 0xffffd0893e8cd500 : 0xfffff80268450ac0 : nt!MiSystemPartition
    0xffff91898799aaf0 : 0xfffff80267a33e20 : nt!ExpWorkerThread
    0xffff91898799ab08 : 0xfffff80267b46715 : nt!PspSystemThreadStartup+0x55
    0xffff91898799ab28 : 0x0037003800650035 :  !du "5e8773d-8f56-11d"
    0xffff91898799ab30 : 0x002d006400330037 :  !du "73d-8f56-11d"
    0xffff91898799ab38 : 0x0036003500660038 :  !du "8f56-11d"
    0xffff91898799ab58 : 0xfffff80267be5078 : nt!KiStartSystemThread+0x28
    0xffff91898799ab70 : 0xfffff80267b466c0 : nt!PspSystemThreadStartup
    0xffff91898799ab98 : 0xffff918987994000 :  !du "412&0&0001#{6994ad04-93ef-11d0-a3cc-00a0c9223196}\frontlineingreytopo"
    'Controller reset failed due to surprise remove' involving the stornvme and storport drivers.

    I checked your logs and noticed the Daemon tools virtual SCSI driver is present. Daemon tools drivers have a history of causing trouble. Although I haven't seen Daemon tools much lately, I am cautious around it and therefore I suggest that you remove Daemon Tools.
    Code:
    3: kd> lmvm dtlitescsibus
    Browse full module list
    start             end                 module name
    fffff802`85dc0000 fffff802`85dcb000   dtlitescsibus   (deferred)             
        Image path: \SystemRoot\System32\drivers\dtlitescsibus.sys
        Image name: dtlitescsibus.sys
        Browse all global symbols  functions  data
        Timestamp:        Tue Nov 13 04:11:07 2018 (5BEA40CB)
        CheckSum:         00019B23
        ImageSize:        0000B000
        Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
        Information from resource tables:
    Let us know how things go after the removal of Daemon tools. If new crashes occur after the removal of Daemon tools, run the log collector tool again and upload a new zip.
    Last edited by axe0; 04 Jul 2020 at 04:57.
      My Computers


  4. Posts : 32
    Windows 10
    Thread Starter
       #4

    cns00 said:
    how exactly did you install windows? did you do factory reset or did you format and clean install windows? you shouldn't do factory reset because if the windows that came with the laptop has issues then those issues will come back when you do factory reset. you need to install a fresh copy of windows by using windows setup flash usb\dvd. try installing fresh copy 2004 and then try installing fresh copy of 1909 if there still are issues. you can do that the other way round if you want


    are you only getting a bsod when you play some games and you are not getting bsod when you are not playing a game? if yes then i think that the graphics in some games are causing bsod and not all games cause bsod because games have different graphics. try these things:-
    1) completely wipe the nvidia files by using DDU in windows safe mode, restart and install nvidia driver. if you still got bsod then again wipe by using DDU and install an older nvidia driver. download DDU from Official Display Driver Uninstaller DDU Download and you can download old nvidia drivers by finding your graphics card in Advanced Driver Search | NVIDIA. How to do a Clean Graphics Card Driver Installation - DDU Tutorial - GPU Driver Uninstall tells you how to use DDU (AMD drivers is wiped in the youtube video. you have to select nvidia as your gpu in DDU)
    2) it could be that your nvidia card has issues. stress test your graphics card and check if something happens. there are tutorials that teach you how to stress test

    another thing is that you have to force the game to use the nvidia card by following How To Force An App To Use The Dedicated GPU On Windows. you can force it in windows graphics settings or in nvidia control panel. if you don't force it then some games may try to use intel card and issues could happen because the game has to run on nvidia card and not intel card. also don't play games when the laptop is running on battery and always play games when the laptop is plugged to electricity because the laptop could try to force the game to use the intel card to save power when it's running on battery

    Thanks for reply!
    Already installed all windows 10 versions, I've tried the 1903 too. All installed through bios with usb.
    And already tried the DDU method, after the amazon support suggest it. Now I tried to force the game with GPU Nvidia but still BSOD

    - - - Updated - - -

    axe0 said:
    This is a peculiar case. A 0x124 with arg 1 = 10. This is an undocumented hardware crash.
    With 0x124 we usually know immediately who reported the crash, note that this is different from who caused the crash. Since this is unknown territory, we'll need to find out who reported the crash.
    Code:
    WHEA_UNCORRECTABLE_ERROR (124)
    A fatal hardware error has occurred. Parameter 1 identifies the type of error
    source that reported the error. Parameter 2 holds the address of the
    WHEA_ERROR_RECORD structure that describes the error conditon.
    Arguments:
    Arg1: 0000000000000010, Error Source Type
    Arg2: ffffd08957035028
    Arg3: ffffd08941b10aac
    Arg4: ffffd08941b1b1a0
    
    3: kd> dt _WHEA_ERROR_RECORD ffffd08957035028
    PSHED!_WHEA_ERROR_RECORD
       +0x000 Header           : _WHEA_ERROR_RECORD_HEADER
       +0x080 SectionDescriptor : [1] _WHEA_ERROR_RECORD_SECTION_DESCRIPTOR
    
    3: kd> dt _WHEA_ERROR_RECORD_HEADER ffffd08957035028
    PSHED!_WHEA_ERROR_RECORD_HEADER
       +0x000 Signature        : 0x52455043
       +0x004 Revision         : _WHEA_REVISION
       +0x006 SignatureEnd     : 0xffffffff
       +0x00a SectionCount     : 1
       +0x00c Severity         : 1 ( WheaErrSevFatal )
       +0x010 ValidBits        : _WHEA_ERROR_RECORD_HEADER_VALIDBITS
       +0x014 Length           : 0x12a
       +0x018 Timestamp        : _WHEA_TIMESTAMP
       +0x020 PlatformId       : _GUID {83c1603c-1552-48a7-87d1-14d9467d7765}
       +0x030 PartitionId      : _GUID {00000000-0000-0000-0000-000000000000}
       +0x040 CreatorId        : _GUID {57217c8d-5e66-44fb-8033-9b74cacedf5b}
       +0x050 NotifyType       : _GUID {0033f803-2e70-4e88-992c-6f26daf3db7a}
       +0x060 RecordId         : 0x01d65181abd2e0e7
       +0x068 Flags            : _WHEA_ERROR_RECORD_HEADER_FLAGS
       +0x06c PersistenceInfo  : _WHEA_PERSISTENCE_INFO
       +0x074 Reserved         : [12]  ""
    
    3: kd> dt _WHEA_ERROR_RECORD_HEADER_FLAGS 0xffffd08957035028+0x068
    PSHED!_WHEA_ERROR_RECORD_HEADER_FLAGS
       +0x000 Recovered        : 0y0
       +0x000 PreviousError    : 0y0
       +0x000 Simulated        : 0y0
       +0x000 DeviceDriver     : 0y1
       +0x000 CriticalEvent    : 0y0
       +0x000 PersistPfn       : 0y0
       +0x000 Reserved         : 0y00000000000000000000000000 (0)
       +0x000 AsULONG          : 8
    Great, we know a device driver reported the error.

    Let's look at the stack.
    Code:
    3: kd> !dpx
    Start memory scan  : 0xffff91898799a388 ($csp)
    End memory scan    : 0xffff91898799b000 (Kernel Stack Base)
    
                   rsp : 0xffff91898799a388 : 0xfffff80267dc3acc : nt!WheaReportHwError+0x3ec
                   r12 : 0xfffff8026b069700 :  !du ""ms, 4ms, 16ms, 64ms, 128ms, 256ms, 2000ms, 6000ms, 10000ms, 20000ms, 20000+ms""
    0xffff91898799a388 : 0xfffff80267dc3acc : nt!WheaReportHwError+0x3ec
    0xffff91898799a418 : 0xfffff80264fb10a4 : PSHED!PshedRetrieveErrorInfo+0x94
    0xffff91898799a428 : 0xfffff80267ac6179 : nt!EtwWriteEx+0x119
    0xffff91898799a438 : 0xfffff80267dc4509 : nt!WheaHwErrorReportSetSeverityDeviceDriver+0x9
    0xffff91898799a460 : 0xfffff8026b0778f0 : storport!WheaErrorData
    0xffff91898799a468 : 0xfffff80267dc4629 : nt!WheaHwErrorReportSubmitDeviceDriver+0xe9
    0xffff91898799a498 : 0xfffff80267dc4745 : nt!WheaReportFatalHwErrorDeviceDriverEx+0xf5
    0xffff91898799a4f8 : 0xfffff8026b050f45 : storport!StorpWheaReportError+0x9d
    0xffff91898799a548 : 0xfffff8026b06fb60 : storport!g_StorpSourceGuid
    0xffff91898799a558 : 0xfffff8026b050df4 : storport!StorpPopulateErrorData+0x120
    0xffff91898799a588 : 0xfffff8026b04a3b0 : storport!StorpMarkDeviceFailed+0x358
    0xffff91898799a618 : 0xfffff80267ad3220 : nt!KiQuantumEnd+0x120
    0xffff91898799a658 : 0xfffff8026afff9f0 :  !du ""Controller Reset failed due to surprise remove""
    0xffff91898799a690 : 0xffffd08941b40238 :  !du "stornvme"
    0xffff91898799a6f0 : 0xffff91898799a700 :  !du ""s is set is set""
    0xffff91898799a700 : 0x0073006900200073 :  !du ""s is set is set""
    0xffff91898799a708 : 0x0074006500730020 :  !du "" set is set""
    0xffff91898799a710 : 0x0020007300690020 :  !du "" is set""
    0xffff91898799a7c0 : 0xffff91898799a700 :  !du ""s is set is set""
    0xffff91898799a7c8 : 0xfffff8026afff210 :  !du ""Controller Fatal Status is set""
    0xffff91898799a7e0 : 0xfffff80268524440 : nt!ExNode0
    0xffff91898799a840 : 0xfffff8026afff9f0 :  !du ""Controller Reset failed due to surprise remove""
    0xffff91898799a848 : 0xfffff8026b010000 : "storport!StorpTelemetryLogUnitSmartAttributesMeasures <PERF> (storport+0x0)"
    0xffff91898799a898 : 0xfffff8026afef477 : stornvme!NVMeRequestComplete+0x27
    0xffff91898799a8a8 : 0xfffff80268524440 : nt!ExNode0
    0xffff91898799a8e8 : 0xfffff8026afea01d : stornvme!ControllerReset+0x1a1
    0xffff91898799a918 : 0xfffff8026afff9f0 :  !du ""Controller Reset failed due to surprise remove""
    0xffff91898799a968 : 0xfffff8026afed20a : stornvme!NVMeControllerReset+0x10a
    0xffff91898799a998 : 0xfffff8026afec11f : stornvme!NVMeControllerAsyncResetWorker+0x3f
    0xffff91898799a9c8 : 0xfffff8026b047b01 : storport!StorPortWorkItemRoutine+0x41
    0xffff91898799a9f0 : 0xfffff8026b047ac0 : storport!StorPortWorkItemRoutine
    0xffff91898799a9f8 : 0xfffff80267ada7a5 : nt!IopProcessWorkItem+0x135
    0xffff91898799aa18 : 0xfffff8027fda5d20 : usbaudio!USBCaptureRequeueWorker
    0xffff91898799aa28 : 0xfffff80267ada670 : nt!IopProcessWorkItem
    0xffff91898799aa68 : 0xfffff80267a33f25 : nt!ExpWorkerThread+0x105
    0xffff91898799aa80 : 0xfffff80267ada670 : nt!IopProcessWorkItem
    0xffff91898799aa90 : 0x0038006500350036 :  !du "65e8773d"
    0xffff91898799aaa8 : 0xffffd0893e883060 : 0xffffd0893e8cd500 : 0xfffff80268450ac0 : nt!MiSystemPartition
    0xffff91898799aaf0 : 0xfffff80267a33e20 : nt!ExpWorkerThread
    0xffff91898799ab08 : 0xfffff80267b46715 : nt!PspSystemThreadStartup+0x55
    0xffff91898799ab28 : 0x0037003800650035 :  !du "5e8773d-8f56-11d"
    0xffff91898799ab30 : 0x002d006400330037 :  !du "73d-8f56-11d"
    0xffff91898799ab38 : 0x0036003500660038 :  !du "8f56-11d"
    0xffff91898799ab58 : 0xfffff80267be5078 : nt!KiStartSystemThread+0x28
    0xffff91898799ab70 : 0xfffff80267b466c0 : nt!PspSystemThreadStartup
    0xffff91898799ab98 : 0xffff918987994000 :  !du "412&0&0001#{6994ad04-93ef-11d0-a3cc-00a0c9223196}\frontlineingreytopo"
    'Controller reset failed due to surprise remove' involving the stornvme and storport drivers.

    I checked your logs and noticed the Daemon tools virtual SCSI driver is present. Daemon tools drivers have a history of causing trouble. Although I haven't seen Daemon tools much lately, I am cautious around it and therefore I suggest that you remove Daemon Tools.
    Code:
    3: kd> lmvm dtlitescsibus
    Browse full module list
    start             end                 module name
    fffff802`85dc0000 fffff802`85dcb000   dtlitescsibus   (deferred)             
        Image path: \SystemRoot\System32\drivers\dtlitescsibus.sys
        Image name: dtlitescsibus.sys
        Browse all global symbols  functions  data
        Timestamp:        Tue Nov 13 04:11:07 2018 (5BEA40CB)
        CheckSum:         00019B23
        ImageSize:        0000B000
        Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
        Information from resource tables:
    Let us know how things go after the removal of Daemon tools. If new crashes occur after the removal of Daemon tools, run the log collector tool again and upload a new zip.
    I've unistalled daemon tools but still got BSOD after 40 min of game. I'm gonna update the new logs. Thanks for the help!
    Can't edit the thread for update the logs so if it's ok I'm gonna update it on my dropbox: Dropbox - FABIO-PC-(2020-07-04_12-39-10).zip - Simplify your life
      My Computer


  5. Posts : 158
    windows 10 pro build 2004
       #5

    try stress testing your nvidia card. if you got a bsod during stress testing then it could mean that your nvidia card is damaged

    i want to ask you did you get a proper warranty when you bought the laptop from amazon? if yes then go the nearest service center which is an authorized hp service center and ask them to check your laptop and they will do any needed repairs for free. if you don't have a warranty then go to any repair shop and pay for repairs
      My Computer


  6. Posts : 32
    Windows 10
    Thread Starter
       #6

    cns00 said:
    try stress testing your nvidia card. if you got a bsod during stress testing then it could mean that your nvidia card is damaged

    i want to ask you did you get a proper warranty when you bought the laptop from amazon? if yes then go the nearest service center which is an authorized hp service center and ask them to check your laptop and they will do any needed repairs for free. if you don't have a warranty then go to any repair shop and pay for repairs
    I've got the standard italian warrancy (2 years, but I already replaced the laptop (for the BSOD)) so maybe I've got 1 years remaining of warrancy
      My Computer

  7. axe0's Avatar
    Posts : 14,855
    Windows 10 Pro
       #7

    It appears the Daemon tools device is still present, probably because the removal process didn't properly remove the traces.

    This won't do anything besides prevent confusion, please go to device manager (right click Windows logo > device manager), go to Storage controllers and remove the Daemon tools device.


    Please check HP for chipset driver updates.
      My Computers


  8. Posts : 32
    Windows 10
    Thread Starter
       #8

    axe0 said:
    It appears the Daemon tools device is still present, probably because the removal process didn't properly remove the traces.

    This won't do anything besides prevent confusion, please go to device manager (right click Windows logo > device manager), go to Storage controllers and remove the Daemon tools device.


    Please check HP for chipset driver updates.
    Yeah, you are right. There was still Daemon tools with the yellow triangle. Anyway, I've unistalled it and I'm gonna play the same games.
    Already update all drivers (the first thing I do after install windows)

    - - - Updated - - -

    axe0 said:
    It appears the Daemon tools device is still present, probably because the removal process didn't properly remove the traces.

    This won't do anything besides prevent confusion, please go to device manager (right click Windows logo > device manager), go to Storage controllers and remove the Daemon tools device.


    Please check HP for chipset driver updates.
    Still got BSOD. Here the new log: Dropbox - FABIO-PC-(2020-07-04_14-20-27).zip - Simplify your life
      My Computer

  9. axe0's Avatar
    Posts : 14,855
    Windows 10 Pro
       #9

    Please run driver verifier using the following settings for 48 hours.
    • Special Pool
    • Force IRQL checking
    • Pool Tracking
    • Security Checks
    • Miscellaneous Checks
    • DDI compliance checking
    • I/O verification



    Warning: driver verifier could cause boot issues and/or performance issues.



    Resetting driver verifier options (recommended in this order)
    1. In normal mode open an administrator command prompt and enter the below command
    2. In safe mode open an administrator command prompt and enter the below command
    3. On 3 boot failures, you'll boot automatically to the recovery options,
      • click Troubleshoot
      • go to the advanced options
      • choose command prompt
      • enter the below command

    4. Boot with the recovery media, see above 4 steps in option 3.
    5. Via the recovery options or recovery media, select a restore point prior enabling driver verifier

    Code:
    verifier /reset


    Crashed when running driver verifier
    1. Reset driver verifier
    2. Boot in normal mode if necessary
    3. Follow Blue Screen of Death (BSOD) Posting Instructions to provide the requested logs




    Extra information about driver verifier
    When you run driver verifier, there are two things you're looking out for
    1. Driver verifier won't find any driver violating something and thus in the time you need to run it there won't be a crash
    2. Driver verifier will find a driver violating something and thus the system will crash.

    The end result of driver verifier is either of the two, but when driver verifier finds something your system will BSOD.


    Driver verifier essentially validates selected drivers on selected actions, this validation adds some delay to actions performed in the background which results in a performance decrease that many people notice. This is called stress testing drivers and depending on quite a few factors this performance decrease is worse for some than for others, and some won't even notice a difference.

    Depending on the drivers selected, it is possible that some of the selected drivers are so-called 'boot' drivers, meaning they load when your system is booting. If these drivers don't pass a validation check, your system will crash, but since the drivers are loading at boot, your system will basically be in a boot loop. That is one of the risks involved and the most important one. Of course, there are various methods to recover from it.

    If you want visual confirmation that driver verifier is actually running, copy/paste the following command in powershell or command prompt
    Code:
    verifier /query
    If the command gives a result similar to this, it means driver verifier is running.
      My Computers


  10. Posts : 32
    Windows 10
    Thread Starter
       #10

    axe0 said:
    Please run driver verifier using the following settings for 48 hours.
    • Special Pool
    • Force IRQL checking
    • Pool Tracking
    • Security Checks
    • Miscellaneous Checks
    • DDI compliance checking
    • I/O verification



    Warning: driver verifier could cause boot issues and/or performance issues.



    Resetting driver verifier options (recommended in this order)
    1. In normal mode open an administrator command prompt and enter the below command
    2. In safe mode open an administrator command prompt and enter the below command
    3. On 3 boot failures, you'll boot automatically to the recovery options,
      • click Troubleshoot
      • go to the advanced options
      • choose command prompt
      • enter the below command

    4. Boot with the recovery media, see above 4 steps in option 3.
    5. Via the recovery options or recovery media, select a restore point prior enabling driver verifier

    Code:
    verifier /reset


    Crashed when running driver verifier
    1. Reset driver verifier
    2. Boot in normal mode if necessary
    3. Follow Blue Screen of Death (BSOD) Posting Instructions to provide the requested logs




    Extra information about driver verifier
    When you run driver verifier, there are two things you're looking out for
    1. Driver verifier won't find any driver violating something and thus in the time you need to run it there won't be a crash
    2. Driver verifier will find a driver violating something and thus the system will crash.

    The end result of driver verifier is either of the two, but when driver verifier finds something your system will BSOD.


    Driver verifier essentially validates selected drivers on selected actions, this validation adds some delay to actions performed in the background which results in a performance decrease that many people notice. This is called stress testing drivers and depending on quite a few factors this performance decrease is worse for some than for others, and some won't even notice a difference.

    Depending on the drivers selected, it is possible that some of the selected drivers are so-called 'boot' drivers, meaning they load when your system is booting. If these drivers don't pass a validation check, your system will crash, but since the drivers are loading at boot, your system will basically be in a boot loop. That is one of the risks involved and the most important one. Of course, there are various methods to recover from it.

    If you want visual confirmation that driver verifier is actually running, copy/paste the following command in powershell or command prompt
    Code:
    verifier /query
    If the command gives a result similar to this, it means driver verifier is running.
    Thanks again for all. So now I will activate the driver verifier, when the system crash can I turn it off and send you the dump log? Or should I wait 48 hours?
      My Computer


 
Page 1 of 7 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 00:49.
Find Us




Windows 10 Forums