PC crash causing restart Solved

Page 2 of 4 FirstFirst 1234 LastLast

  1. Posts : 23,927
    windows 10 professional version 1607 build 14393.969 64 bit
       3 Weeks Ago #11

    1) Windows driver verifier can be turned on to find misbehaving drivers or malfunctioning hardware once you have:
    a) understood the methods to turn off and recover from using the tool
    b) made a backed up image using Macrium and saved the image to another drive
    c) made a brand new restore point

    2) After any BSOD:
    a) Run the BETA log collector and post a new zip into the thread
    b) Open file explorer > this PC > C: > in the right upper corner search for C:\windows\memory.dmp > if the file size is < 1.5 GB then zip and post a separate share link into the thread using one drive, drop box, or google drive
      My ComputerSystem Spec

  2.    2 Weeks Ago #12

    Hey @zbook I have followed all your steps and touch wood I've had no blue screens has of yet, what I'll do I'll mark as solved but I've turned mini dumps on and will post back if any issues arise again, you mentioned Ccleaner, would you advise uninstalling?
      My ComputerSystem Spec


  3. Posts : 23,927
    windows 10 professional version 1607 build 14393.969 64 bit
       2 Weeks Ago #13

    Windows driver verifier has customized settings for tests and drivers.
    The settings in this link had three simultaneous tests
    Enable and Disable Driver Verifier in Windows 10 | Tutorials

    This link has approximately 19 simultaneous tests:
    Driver Verifier-- tracking down a mis-behaving driver. - Microsoft Community

    Run Windows driver verifier for 48 hours with these settings.
    If there are no BSOD then that will conclude the troubleshooting.
    If there are BSOD then the misbehaving drivers can be replaced.
    Then the tool can be run for an additional 36 hours after the last BSOD.
    If there are no BSOD then that will conclude the troubleshooting.

    Ccleaner has settings which can clean files needed in the troubleshooting.
    For example it has a box to check for memory dumps.
    The memory dumps are often useful in the troubleshooting.
    So this setting is unchecked so that if needed the memory dumps are available.
      My ComputerSystem Spec

  4.    2 Weeks Ago #14

    Thank you buddy, I forgot to run that, I will run it, can I still use my computer whilst using it or not?
      My ComputerSystem Spec


  5. Posts : 23,927
    windows 10 professional version 1607 build 14393.969 64 bit
       2 Weeks Ago #15

    The computer can be used while using windows driver verifier.
    The computer may become sluggish or have a slow boot while using windows driver verifier.
    You can start with the 3 simultaneous tests in the first link and if there are no performance or boot issues increase by 3 -5 simultaneous tests every hour. This way all drivers will be tested with approximately 19 simultaneous tests.

    For any BSOD:
    a) use the steps in the first link to turn off or recover from using the tool
    b) when back on the desktop run the BETA log collector and post a new zip into the thread
    c) open file explorer > this PC > C: > in the right upper corner search for C:\windows\memory.dmp > if the file size is < 1.5 GB then zip and post a separate share link into this thread
      My ComputerSystem Spec

  6.    2 Weeks Ago #16

    So I ran Verifier no BSOD but just had one, I'll include everything in this post
    PC crash causing restart Attached Files
      My ComputerSystem Spec

  7.    2 Weeks Ago #17

    Here is the DMP link Desktop.rar - Google Drive
      My ComputerSystem Spec

  8.    2 Weeks Ago #18

    All I remember the BSOD error was something like "thread_handle" cant remember much more sorry.
      My ComputerSystem Spec


  9. Posts : 23,927
    windows 10 professional version 1607 build 14393.969 64 bit
       2 Weeks Ago #19

    The bugcheck for the mini dump was:
    SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)

    The bugcheck for the memory dump was:
    SYSTEM_THREAD_EXCEPTION_NOT_HANDLED (7e)

    There were no identifiable misbehaving drivers debugging the mini dump.
    For the memory dump debugging there were two drivers identified in the crash.
    The likely cause was the Nvidia GPU driver.
    Replace the Nvidia GPU and uninstall the Malwarebytes software and its drivers.

    1) uninstall the Nvidia GPU driver using DDU (display driver uninstaller)

    2) re-install the Nvidia GPU driver from the Nvidia website

    3) make sure that you check the clean install box and if available install the physx driver.


    Display Driver Uninstaller Download version 18.0.0.7 (or newer version if available)

    Display Driver Uninstaller: How to use - Windows 7 Help Forums

    NVIDIA

    Download Display Driver Uninstaller - MajorGeeks

    4) Uninstall Malwarebytes using the applicable uninstall tool:
    https://downloads.malwarebytes.com/file/mb_clean

    5) Malwarebytes can be reinstalled one week after the last BSOD.



    If there are any BSOD after the above steps:
    a) run the BETA log collector and post a new zip into this thread
    b) open file explorer > this PC > C: > in the right upper corner search or C:\windows\memory.dmp > if the file size is < 1.5 GB then zip and post a share link into this thread using one drive, drop box, or google drive



    Code:
    03/02/2019 03:14	Windows Error Reporting	Fault bucket , type 0
    Event Name: BlueScreen
    Response: Not available
    Cab Id: 0
    
    Problem signature:
    P1: 1000007e
    P2: ffffffffc0000005
    P3: fffff80118dd7b35
    P4: ffff870aee2a6fa8
    P5: ffff870aee2a67f0
    P6: 10_0_17763
    P7: 0_0
    P8: 256_1
    P9: 
    P10: 
    
    Attached files:
    \\?\C:\WINDOWS\Minidump\020319-10140-01.dmp
    \\?\C:\WINDOWS\TEMP\WER-29781-0.sysdata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER8B48.tmp.WERInternalMetadata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER8B58.tmp.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER8B67.tmp.csv
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER8BA7.tmp.txt
    
    These files may be available here:
    \\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_1000007e_ea40c44f46a346ede3d61c5950c46bf76d74ac3_00000000_cab_2b388c13
    
    Analysis symbol: 
    Rechecking for solution: 0
    Report Id: 6e2fd3e7-1e64-4fb9-9f5b-02c5d710054b
    Report Status: 2049
    Hashed bucket: 
    Cab Guid: 0
    03/02/2019 03:14	Windows Error Reporting	Fault bucket , type 0
    Event Name: BlueScreen
    Response: Not available
    Cab Id: 0
    
    Problem signature:
    P1: 1000007e
    P2: ffffffffc0000005
    P3: fffff80118dd7b35
    P4: ffff870aee2a6fa8
    P5: ffff870aee2a67f0
    P6: 10_0_17763
    P7: 0_0
    P8: 256_1
    P9: 
    P10: 
    
    Attached files:
    \\?\C:\WINDOWS\Minidump\020319-10140-01.dmp
    \\?\C:\WINDOWS\TEMP\WER-29781-0.sysdata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER8B48.tmp.WERInternalMetadata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER8B58.tmp.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER8B67.tmp.csv
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER8BA7.tmp.txt
    
    These files may be available here:
    \\?\C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_1000007e_ea40c44f46a346ede3d61c5950c46bf76d74ac3_00000000_03ec8ba6
    
    Analysis symbol: 
    Rechecking for solution: 0
    Report Id: 6e2fd3e7-1e64-4fb9-9f5b-02c5d710054b
    Report Status: 4
    Hashed bucket: 
    Cab Guid: 0
    03/02/2019 20:14	Windows Error Reporting	Fault bucket , type 0
    Event Name: BlueScreen
    Response: Not available
    Cab Id: 0
    
    Problem signature:
    P1: 1000007e
    P2: ffffffffc0000005
    P3: fffff802217804f4
    P4: fffffe021ad09908
    P5: fffffe021ad09150
    P6: 10_0_17763
    P7: 0_0
    P8: 256_1
    P9: 
    P10: 
    
    Attached files:
    \\?\C:\WINDOWS\Minidump\020319-11312-01.dmp
    \\?\C:\WINDOWS\TEMP\WER-22359-0.sysdata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER6B0E.tmp.WERInternalMetadata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER6B1E.tmp.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER6B2D.tmp.csv
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER6B7C.tmp.txt
    
    These files may be available here:
    \\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_1000007e_e7bc1a4c3fbaf361d733e64399ac3b87b98f90_00000000_cab_18946be9
    
    Analysis symbol: 
    Rechecking for solution: 0
    Report Id: 808489e7-f296-410b-ad30-70746f59ff08
    Report Status: 2049
    Hashed bucket: 
    Cab Guid: 0
    03/02/2019 20:14	Windows Error Reporting	Fault bucket , type 0
    Event Name: BlueScreen
    Response: Not available
    Cab Id: 0
    
    Problem signature:
    P1: 1000007e
    P2: ffffffffc0000005
    P3: fffff802217804f4
    P4: fffffe021ad09908
    P5: fffffe021ad09150
    P6: 10_0_17763
    P7: 0_0
    P8: 256_1
    P9: 
    P10: 
    
    Attached files:
    \\?\C:\WINDOWS\Minidump\020319-11312-01.dmp
    \\?\C:\WINDOWS\TEMP\WER-22359-0.sysdata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER6B0E.tmp.WERInternalMetadata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER6B1E.tmp.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER6B2D.tmp.csv
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER6B7C.tmp.txt
    
    These files may be available here:
    \\?\C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_1000007e_e7bc1a4c3fbaf361d733e64399ac3b87b98f90_00000000_00786b7b
    
    Analysis symbol: 
    Rechecking for solution: 0
    Report Id: 808489e7-f296-410b-ad30-70746f59ff08
    Report Status: 4
    Hashed bucket: 
    Cab Guid: 0
    Code:
    28/01/2019 21:25	Application Error	Faulting application name: bfv.exe, version: 1.0.68.64411, time stamp: 0x5c3644c4
    Faulting module name: bfv.exe, version: 1.0.68.64411, time stamp: 0x5c3644c4
    Exception code: 0xc0000005
    Fault offset: 0x00000000052d5a3e
    Faulting process ID: 0x810
    Faulting application start time: 0x01d4b74ddb4d62e0
    Faulting application path: E:\Origin\Battlefield V\bfv.exe
    Faulting module path: E:\Origin\Battlefield V\bfv.exe
    Report ID: eac67d5f-b5ed-42fd-b064-57a7059d58cc
    Faulting package full name: 
    Faulting package-relative application ID:
    20/01/2019 20:48	Application Error	Faulting application name: bfv.exe, version: 1.0.68.64411, time stamp: 0x5c3644c4
    Faulting module name: bfv.exe, version: 1.0.68.64411, time stamp: 0x5c3644c4
    Exception code: 0xc0000409
    Fault offset: 0x000000000998eb9c
    Faulting process ID: 0x184c
    Faulting application start time: 0x01d4b0f597f4c42a
    Faulting application path: E:\Origin\Battlefield V\bfv.exe
    Faulting module path: E:\Origin\Battlefield V\bfv.exe
    Report ID: e6a57db4-a648-4608-888f-e1c44ff5d317
    Faulting package full name: 
    Faulting package-relative application ID:
    28/01/2019 21:40	Application Error	Faulting application name: bfv.exe, version: 1.0.68.64411, time stamp: 0x5c3644c4
    Faulting module name: nvwgf2umx.dll, version: 25.21.14.1771, time stamp: 0x5c3862aa
    Exception code: 0xc0000005
    Fault offset: 0x0000000000c9fa6b
    Faulting process ID: 0x26d8
    Faulting application start time: 0x01d4b751f097bffd
    Faulting application path: E:\Origin\Battlefield V\bfv.exe
    Faulting module path: C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_5db32447b43ce666\nvwgf2umx.dll
    Report ID: bd5760fd-83a3-49d9-a708-00e802d980fa
    Faulting package full name: 
    Faulting package-relative application ID:
    28/01/2019 21:39	Application Error	Faulting application name: bfv.exe, version: 1.0.68.64411, time stamp: 0x5c3644c4
    Faulting module name: nvwgf2umx.dll, version: 25.21.14.1771, time stamp: 0x5c3862aa
    Exception code: 0xc000001d
    Fault offset: 0x0000000000be5b2a
    Faulting process ID: 0x514
    Faulting application start time: 0x01d4b75010532e8b
    Faulting application path: E:\Origin\Battlefield V\bfv.exe
    Faulting module path: C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_5db32447b43ce666\nvwgf2umx.dll
    Report ID: d63e5f9e-c9fd-4622-9697-e040c5d9b84d
    Faulting package full name: 
    Faulting package-relative application ID:

    Code:
    Name	NVIDIA GeForce GTX 1070
    PNP Device ID	PCI\VEN_10DE&DEV_1B81&SUBSYS_33011462&REV_A1\4&1C3D25BB&0&0019
    Adapter Type	GeForce GTX 1070, NVIDIA compatible
    Adapter Description	NVIDIA GeForce GTX 1070
    Adapter RAM	(1,048,576) bytes
    Installed Drivers	C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_5db32447b43ce666\nvldumdx.dll,C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_5db32447b43ce666\nvldumdx.dll,C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_5db32447b43ce666\nvldumdx.dll,C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_5db32447b43ce666\nvldumdx.dll
    Driver Version	25.21.14.1771
    INF File	oem52.inf (Section108 section)
    Colour Planes	Not Available
    Colour Table Entries	4294967296
    Resolution	1920 x 1080 x 144 hertz
    Bits/Pixel	32
    Memory Address	0xF6000000-0xF6FFFFFF
    Memory Address	0xE0000000-0xEFFFFFFF
    Memory Address	0xF0000000-0xF1FFFFFF
    I/O Port	0x0000E000-0x0000E07F
    IRQ Channel	IRQ 54
    I/O Port	0x000003B0-0x000003BB
    I/O Port	0x000003C0-0x000003DF
    Memory Address	0xA0000-0xBFFFF
    Driver	c:\windows\system32\driverstore\filerepository\nv_dispi.inf_amd64_5db32447b43ce666\nvlddmkm.sys (25.21.14.1771, 19.51 MB (20,461,984 bytes), 15/01/2019 20:10)

    Code:
    nvlddmkm	nvlddmkm	c:\windows\system32\driverstore\filerepository\nv_dispi.inf_amd64_5db32447b43ce666\nvlddmkm.sys	Kernel Driver	No	Manual	Stopped	OK	Ignore	No	No
    nvlddmkm.sys Fri Jan 11 03:16:04 2019 (5C385ED4)
    MbamChameleon.sys Thu Oct 11 11:29:30 2018 (5BBF7A6A)
      My ComputerSystem Spec

  10.    2 Weeks Ago #20

    Thank you so much Zbook for all your help, you're a star mate, I'll run DDU tomorrow and get rid of Malwarebytes and report back.

    Thanks again

    Adam
      My ComputerSystem Spec


 
Page 2 of 4 FirstFirst 1234 LastLast

Related Threads
My computer was crashed this morning, and I see the following from Reliability: Source Windows Summary Hardware error Date ‎4/‎29/‎2018 8:35 AM
Wireless Adapter is causing my pc to crash in BSOD Crashes and Debugging
I Have a Tp-Link TL-WN822N wireless adapter that randomly disconnects from the internet even though the internet in the house is still on. usually to fix it, i unplug the adapter then replug it and it'll reconnect to the internet. Im not sure how to...
ntoskrnl.exe Causing My PC to crash in BSOD Crashes and Debugging
I recently bought a new GPU because I thought my GPU was causing crashes while playing. Then I ran WInCrashReport and it told me that ntoskrnl.exe is causing my PC to crash and I do not know how to fix it
What is causing my pc to crash in BSOD Crashes and Debugging
https://mymdc-my.sharepoint.com/personal/anthony_pena008_mymdc_net/_layouts/15/guestaccess.aspx?guestaccesstoken=LL%2fjLL4EW3nFJI3cEGXdA9F08FOs3UAXNY5PTq2sxIM%3d&docid=1f69967b704d0469d9e4b1be6b9db2006&rev=1 ^ Dump file
I hope I am posting this in the right place. I just did the GWX thing and most things work as expected. They say old dogs like me can't learn new tricks. That's not true, we just don't want to. I tell you that because I am still using MS Office...
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 06:45.
Find Us