Assistance With a Couple Recent BSODs Since Upgrading

Page 1 of 2 12 LastLast

  1. Posts : 65
    Windows 10
       #1

    Assistance With a Couple Recent BSODs Since Upgrading


    I've gotten a couple of crashes in the week or two that I've been running win10. The first was a typical looking one, but the 2nd was a new-look windows 10 style and it said "critical process died". Very descriptive, huh.

    So I ran the V2 collector to gather some of the dump info & attached it here which hopefully will be a good starting point.

    When I upgraded my system from win 7, I did it as a clean install so everything got blown out. I have re-installed some applications but my system is far leaner than it was before. I should mention that I was having some BSODs under windows 7 which never really got a definitive solution to...the only possibility was to replace the RAM which I didn't do. But, as part of the extensive diagnosis that went on at the end when my system would not upgrade a couple weeks ago, I ran Memtest 5.01 for 10 passes and there were no memory errors.

    I am running window 10 version 1909 build 18363.592
      My Computers


  2. Posts : 38,422
    windows 10 professional version 1607 build 14393.969 64 bit
       #2

    Hi Brucex64,


    In the prior thread there were drive problems displayed in the test results.
    Drive problems can cause BSOD.

    The tests can be ran again with the new operating system.
    If the tests again report abnormal results > replace the drive

    1) Open administrative command prompt and type or copy and paste:
    2) sfc /scannow
    3) dism /online /cleanup-image /scanhealth
    4) dism /online /cleanup-image /restorehealth
    5) sfc /scannow
    6) chkdsk /scan
    7) wmic recoveros set autoreboot = false
    8) wmic recoveros set DebugInfoType = 7
    9) wmic recoveros get autoreboot
    10) wmic recoveros get DebugInfoType
    11) Powercfg -h off
    12) bcdedit /enum {badmemory}

    13) When these have completed > right click on the top bar or title bar of the administrative command prompt box > left click on edit then select all > right click on the top bar again > left click on edit then copy > paste into the thread

    14) Make sure that there is no over clocking while troubleshooting

    15) Make a backup image using Macrium and save the image to another disk drive or the cloud:
    Macrium Software | Macrium Reflect Free:
    Macrium Software | Macrium Reflect Free

    16) In the left lower corner search type: system or system control > open system control panel > on the left pane click advanced system settings

    a) > on the advanced tab under startup and recovery > click settings > post an image of the startup and recovery window into the thread

    b) > on the advanced tab under performance > click on settings > on the performance options window > click on the advanced tab > under virtual memory > click on change > post an image of the virtual memory window into the thread

    17) Run HD Tune (free version) (all drives)
    HD Tune website
    Post images into the thread for results on these tabs:
    a) Health
    b) Benchmark
    c) Full error scan


    18) Run Sea Tools for Windows
    long generic test
    Post an image of the test result into the thread
    Seagate US
    How to use SeaTools for Windows | Seagate Support US

    19) Run HD Sentinel: (free or trial edition)
    Hard Disk Sentinel - HDD health and temperature monitoring
    Hard Disk Sentinel - HDD health and temperature monitoring
    Post images of each of these tabs into the thread:
    Overview tab
    Temperature
    SMART
    Disk performance

    20) Crystal Disk standard edition:
    CrystalDiskInfo Crystal Dew World

    21) Open disk management > by default some columns are compressed > widen each Status and Volume > make sure the contents within the parenthesis are in full view and that none of the characters are cutoff > view disk 0 > widen this row as needed so that all of the characters are in full view > post an image into the thread
    Disk Management - How to Post a Screenshot of

    22) For any BSOD:

    a) run the V2 log collector to collect new log files

    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 > post a separate share link into the thread using one drive, drop box, or google drive
    Last edited by zbook; 28 Jan 2020 at 17:33.
      My Computer


  3. Posts : 65
    Windows 10
    Thread Starter
       #3

    I don't recall any drive errors. We did drive scans on both and there were no issues. I'll work down your list above. Here is the command prompt results:

    Microsoft Windows [Version 10.0.18363.592]
    (c) 2019 Microsoft Corporation. All rights reserved.

    C:\Windows\system32>sfc /scannow

    Beginning system scan. This process will take some time.

    Beginning verification phase of system scan.
    Verification 100% complete.

    Windows Resource Protection did not find any integrity violations.

    C:\Windows\system32>dism /online /cleanup-image /scanhealth

    Deployment Image Servicing and Management tool
    Version: 10.0.18362.1

    Image Version: 10.0.18363.592

    [==========================100.0%==========================] No component store corruption detected.
    The operation completed successfully.

    C:\Windows\system32>dism /online /cleanup-image /restorehealth

    Deployment Image Servicing and Management tool
    Version: 10.0.18362.1

    Image Version: 10.0.18363.592

    [==========================100.0%==========================] The restore operation completed successfully.
    The operation completed successfully.

    C:\Windows\system32>sfc /scannow

    Beginning system scan. This process will take some time.

    Beginning verification phase of system scan.
    Verification 100% complete.

    Windows Resource Protection did not find any integrity violations.

    C:\Windows\system32>chkdsk /scan
    The type of the file system is NTFS.

    Stage 1: Examining basic file system structure ...
    461824 file records processed.
    File verification completed.
    4810 large file records processed.
    0 bad file records processed.

    Stage 2: Examining file name linkage ...
    1497 reparse records processed.
    567482 index entries processed.
    Index verification completed.
    0 unindexed files scanned.
    0 unindexed files recovered to lost and found.
    1497 reparse records processed.

    Stage 3: Examining security descriptors ...
    Security descriptor verification completed.
    52830 data files processed.
    CHKDSK is verifying Usn Journal...
    34598200 USN bytes processed.
    Usn Journal verification completed.

    Windows has scanned the file system and found no problems.
    No further action is required.

    117115903 KB total disk space.
    49207092 KB in 193708 files.
    130940 KB in 52831 indexes.
    0 KB in bad sectors.
    573987 KB in use by the system.
    65536 KB occupied by the log file.
    67203884 KB available on disk.

    4096 bytes in each allocation unit.
    29278975 total allocation units on disk.
    16800971 allocation units available on disk.

    C:\Windows\system32>wmic recoveros set autoreboot = false
    Updating property(s) of '\\BRUCE-1\ROOT\CIMV2:Win32_OSRecoveryConfiguration.Name="Microsoft Windows 10 Pro|C:\\Windows|\\Device\\Harddisk0\\Partition2"'
    Property(s) update successful.

    C:\Windows\system32>wmic recoveros set DebugInfoType = 7
    Updating property(s) of '\\BRUCE-1\ROOT\CIMV2:Win32_OSRecoveryConfiguration.Name="Microsoft Windows 10 Pro|C:\\Windows|\\Device\\Harddisk0\\Partition2"'
    Property(s) update successful.

    C:\Windows\system32>wmic recoveros get autoreboot
    AutoReboot
    FALSE


    C:\Windows\system32>wmic recoveros get DebugInfoType
    DebugInfoType
    7


    C:\Windows\system32>Powercfg -h off

    C:\Windows\system32>bcdedit /enum {badmemory}

    RAM Defects
    -----------
    identifier {badmemory}

    C:\Windows\system32>

    - - - Updated - - -

    16. Startup & Recovery: Attachment 265060

    Virtual Memory tab: Attachment 265061

    17. HDTune - SSD Health: Attachment 265062
    SSD Benchmark: Attachment 265063
    SSD Errors: Attachment 265064

    D drive health: Attachment 265065
    D drive benchmark: Attachment 265066
    D drive errors: Attachment 265067

    18. Seatools long generic test - D drive only is Seagate: Attachment 265068

    19. HDSentinel SSD Overview: Attachment 265069
    SSD Temp.: Attachment 265070
    SSD S.M.A.R.T. Attachment 265071
    SSD Performance: Attachment 265072
    D Drive Overview: Attachment 265073
    D Drive Temp.: Attachment 265074
    D Drive S.M.A.R.T. Attachment 265075
    D Drive Performance: Attachment 265076

    20. Crystal Disk Info - SSD: Attachment 265077
    D Drive: Attachment 265078

    21: Disk Management screenshot: Attachment 265079

    22: I think there was one more BSOD since the ones I posted above so I ran V2 and attached the resulting zip here.
      My Computers


  4. Posts : 38,422
    windows 10 professional version 1607 build 14393.969 64 bit
       #4

    1) Post a share link for: C:\Windows\MEMORY.DMP

    Code:
    LastWriteTime        Size (MB) FullName             
    -------------        --------- --------             
    1/28/2020 7:19:24 PM     820.9 C:\Windows\MEMORY.DMP


    2) Make a new restore point:
    Create System Restore Point in Windows 10


    3) Make a backup image using Macrium and save the image to another disk drive or the cloud.

    Macrium Software | Your Image is Everything
    Backup and Restore with Macrium Reflect

    4) Detach the non- Windows drive

    5) For any BSOD:

    a) run the V2 log collector to collect new log files

    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 > post a separate share link into the thread using one drive, drop box, or google drive
      My Computer


  5. Posts : 65
    Windows 10
    Thread Starter
       #5

    Here's a link to the dmp file on Google Drive: MEMORY.DMP - Google Drive

    I can't detach the D drive because everything I work with is on it so the computer is pretty much useless without it.

    There haven't been any more blue screens since the most recent V2 package I uploaded in my last post. This BSOD tends to happen if I go into sleep mode with applications still open (and then not even every single time), so I've tried to close all the programs before sleep mode. Interestingly...after I first installed windows 10 I did not realize the default setting was to turn off after a certain period of time...I would notice that it was off (or in sleep?) after a few hours away and everything came back up normally, and I had a bunch of things open. So I disabled that by selecting "never" for turn computer off. When I want to put the computer in sleep mode, I do it manually via a button on my keyboard. My keyboard is quite old but still in good condition so I never got a new one. I think it may be from 2005. (Its a Microsoft Multi-Media Keyboard 1.0A). I wonder if the keyboard command may somehow be messing up. Its a long shot though. I don't have a new one to test. Its using a generic driver; I can't find a specific win10 driver for this model.

    - - - Updated - - -

    Since my last post there was another crash but it didn't cause a blue screen. Based on the time stamp it seems to have happened while the computer was in sleep mode. When I tried to wake it later it was just frozen so I had to restart and it did generate a minidump file. From what I see it was caused by a driver called farflt.sys+11fed which I think is part of Malwarebytes? I did a scan with Malwarebytes and it did not find anything. I collected data using V2 and attached here.
      My Computers


  6. Posts : 38,422
    windows 10 professional version 1607 build 14393.969 64 bit
       #6

    Please perform the following steps:

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

    2) uninstall the Nvidia GPU driver using DDU (display driver uninstaller)
    3) re-install the Nvidia GPU driver from the Nvidia website
    4) make sure that you check the clean install box and if available install the physx driver.

    Display Driver Uninstaller Download version 18.0.2.2 (or newer version if available)
    Official Display Driver Uninstaller DDU Download

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

    Download Drivers | NVIDIA
    Download Drivers | NVIDIA



    Code:
    Name	NVIDIA GeForce GT 640
    PNP Device ID	PCI\VEN_10DE&DEV_0FC1&SUBSYS_26433842&REV_A1\4&1286464&0&0008
    Adapter Type	GeForce GT 640, NVIDIA compatible
    Adapter Description	NVIDIA GeForce GT 640
    Adapter RAM	(2,147,483,648) bytes
    Installed Drivers	nvd3dumx.dll,nvwgf2umx.dll,nvwgf2umx.dll,nvwgf2umx.dll
    Driver Version	10.18.13.5330
    INF File	oem16.inf (Section009 section)
    Color Planes	Not Available
    Color Table Entries	4294967296
    Resolution	1920 x 1080 x 60 hertz
    Bits/Pixel	32
    Memory Address	0xF6000000-0xF70FFFFF
    Memory Address	0xE0000000-0xF1FFFFFF
    Memory Address	0xF0000000-0xF1FFFFFF
    I/O Port	0x0000E000-0x0000EFFF
    IRQ Channel	IRQ 16
    I/O Port	0x000003B0-0x000003BB
    I/O Port	0x000003C0-0x000003DF
    Memory Address	0xA0000-0xBFFFF
    Driver	C:\WINDOWS\SYSTEM32\DRIVERS\NVLDDMKM.SYS (10.18.13.5330, 10.58 MB (11,095,696 bytes), 1/20/2020 7:56 PM)

    Code:
    farflt.sys   Wed Dec 18 07:11:55 2019 (5DFA41BB)
    Code:
    nvlddmkm.sys Tue Jun 16 22:28:00 2015 (55810560)
      My Computer


  7. Posts : 65
    Windows 10
    Thread Starter
       #7

    Ok. Malware Bytes is uninstalled & cleaned off. Display drivers were cleaned off and a new set installed. I will see if I get a BSOD.

    A related question....after doing the clean install of the Nvidia drivers, there is a folder c:\program files\Nvidia Corporation\Installer2 which is over 200mb. is this a temporary install folder and can I delete it?
      My Computers

  8. Ztruker's Avatar
    Posts : 13,512
    Windows 10 Pro X64 20H4 19042.746
       #8

    Mine is 1.2GB. I leave it alone. 200MB is peanuts, as is 1.2GB (for me at least, I have a 1TB SSD).

    Attachment 265371
      My Computers


  9. Posts : 65
    Windows 10
    Thread Starter
       #9

    Sigh. Another wakeup crash. The computer was in sleep mode all day, and when I pressed a button on the kbd it just was black. So I hit the power button and it shut off, then hit it again and it started up and into windows. I see from my Bluescreenview that it had a "page fault in non paged area" error code with a time stamp that corresponded to when I hit the button to wake it. So it appears that waking it caused whatever it is...

    I ran another V2 Collector and attached the results.
      My Computers


  10. Posts : 38,422
    windows 10 professional version 1607 build 14393.969 64 bit
       #10

    Please post a share link for C:\windows\memory.dmp

    Code:
    LastWriteTime        Size (MB) FullName             
    -------------        --------- --------             
    2/1/2020 11:54:40 PM    584.41 C:\Windows\MEMORY.DMP


    Read these links on Windows driver verifier: (do not use the tool until it is communicated in the thread) (learn how to run the reset and bootmode commands in Windows Recovery Environment (RE)

    Enable and Disable Driver Verifier in Windows 10
    https://answers.microsoft.com/en-us/...3-c48669e4c983
      My Computer


 
Page 1 of 2 12 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 04:38.
Find Us




Windows 10 Forums