Random BSOD while working

  1.    #1

    Random BSOD while working


    Edition Windows 10 Pro
    Version 20H2
    Installed on ‎5/‎27/‎2020
    OS build 19042.685
    Experience Windows Feature Experience Pack 120.2212.551.0

    I experienced this strange issue while working yesterday. I was on the phone with a client via VOIP, using RingCentral, when my computer just froze and then restarted after a few seconds. I didn't see any BSOD or anything, just restarted right away. I got bluescreenviewer and found a minidump. Something about watchdog.sys and dxgmms1.sys.

    Any ideas?
      My Computer


  2. Posts : 14,046
    Windows 11 Pro X64 22H2 22621.1848
       #2

    Definite Video problem.

    Code:
    VIDEO_MEMORY_MANAGEMENT_INTERNAL (10e)
    The video memory manager encountered a condition that it can't recover from. By crashing,
    the video memory manager is attempting to get enough information into the minidump such that
    somebody can pinpoint what lead to this condition.
    Arguments:
    Arg1: 0000000000000026, The subtype of the bugcheck:
    Arg2: ffffb80fbaeaa8e0
    Arg3: 0000000000000000
    Arg4: 0000000000000000
    Code:
    STACK_TEXT:  
    ffffd08c`8c9be1c8 fffff804`2e053ad0 : 00000000`0000010e 00000000`00000026 ffffb80f`baeaa8e0 00000000`00000000 : nt!KeBugCheckEx
    ffffd08c`8c9be1d0 fffff804`2f7bf629 : ffffb80f`baeaa8e0 00000000`00000000 ffffe28c`67789080 ffffe28c`67106410 : watchdog!WdLogEvent5_WdCriticalError+0xe0
    ffffd08c`8c9be210 fffff804`2f7be781 : 00000000`00000000 ffffe28c`60203160 ffffe28c`5b284000 ffffe28c`60203178 : dxgmms1!VIDMM_GLOBAL::CloseLocalAllocation+0x159
    ffffd08c`8c9be290 fffff804`2f7ceea1 : ffffb80f`e18bc5d0 ffffb80f`c0002f40 00000288`9b040000 00000000`80003b40 : dxgmms1!VIDMM_GLOBAL::CloseOneAllocation+0x131
    ffffd08c`8c9be470 fffff804`2f794d55 : 00000000`00000000 ffffd08c`8c9be600 ffffb80f`bae86800 00000000`00000001 : dxgmms1!VIDMM_GLOBAL::CloseAllocation+0xa1
    ffffd08c`8c9be4c0 fffff804`2dd8e849 : 00000000`00000000 ffffd08c`8c9be600 ffffb80f`bae86800 fffff804`2dd9af75 : dxgmms1!VidMmCloseAllocation+0x15
    ffffd08c`8c9be500 fffff804`2dd8e34e : 00000000`00000000 ffffb80f`a659d820 00000000`00000000 fffff804`00000000 : dxgkrnl!DXGDEVICE::DestroyAllocations+0x4c5
    ffffd08c`8c9be6a0 fffff804`2dd7ad01 : ffffb80f`a659d820 ffffd08c`8c9be7f0 ffffb80f`a659da01 fffff804`2dca43c9 : dxgkrnl!DXGDEVICE::DestroyResource+0x5e
    ffffd08c`8c9be6e0 fffff804`2dd79f60 : ffffb80f`a659d820 ffffb80f`a659da01 ffffd08c`8c9be7f0 ffffb80f`a659da00 : dxgkrnl!DXGDEVICE::DrainResources+0x71
    ffffd08c`8c9be730 fffff804`2dd7979c : ffffb80f`a659d820 ffffb80f`a4d059b0 ffffd08c`00000000 00000000`00000000 : dxgkrnl!DXGDEVICE::DestroyAllDeviceState+0x140
    ffffd08c`8c9be770 fffff804`2dd79443 : ffffb80f`a659d820 ffffe28c`5b2095c0 ffffb80f`a659d820 fffff804`23b411e0 : dxgkrnl!ADAPTER_RENDER::DestroyDevice+0xd8
    ffffd08c`8c9be7a0 fffff804`2dd793ab : ffffb80f`a659d820 ffffd08c`00000005 ffffb80f`a659d820 ffffb80f`a659d820 : dxgkrnl!ADAPTER_RENDER::DestroyDeviceNoLocksInternal+0x83
    ffffd08c`8c9be8b0 fffff804`2deef935 : ffffb80f`a659d820 ffffd08c`8c9be9e0 ffffe28c`67807000 ffffb80f`a21e4820 : dxgkrnl!ADAPTER_RENDER::DestroyDeviceNoLocks+0x15b
    ffffd08c`8c9be8e0 fffff804`2de842f8 : ffffb80f`a21e4820 ffffe28c`67807000 ffffb80f`a21e4820 00000000`00000000 : dxgkrnl!DxgkReleaseVidPnSourceOwnerAndRestartCdds+0x445
    ffffd08c`8c9bec90 fffff804`2df21813 : ffffb80f`a14eddb0 ffffffff`ffffffff ffffffff`ffffffff 00000000`00000000 : dxgkrnl!DXGPROCESS::ReleaseVidPnSourceOwners+0x90f70
    ffffd08c`8c9beda0 ffffc964`d1b5837e : 1b3856d2`00000002 00000000`00000000 ffff98a6`8f9fe054 ffffd08c`8c9bedc0 : dxgkrnl!DxgkReleaseProcessVidPnSourceOwners+0x103
    MODULE_NAME: dxgmms1
    IMAGE_NAME: dxgmms1.sys

    dxgmms1.sys


    Name dxgmms1.sys
    Info DirectX Graphics MMS
    Not sure which adapter is causing the problem though.

    Microsoft Remote Display Adapter or NVIDIA GeForce 8400GS

    Since you were connected to a remote client I'm thinking it's the Microsoft Remote Display Adapter.
    You have the latest version available: 10.0.19041.662 dated 6/20/2006 5:00:00 PM

    Is there a rollback version available in Device Manager?

    You also have the latest Nvidia driver available, 342.01. You could try this:

    Remove and install latest Nvidia drivers:

    Get the latest driver for your Nvidia card here: NVIDIA Driver Downloads
    Completely uninstall the current Nvidia display drivers using Display Driver Uninstaller (DDU) from WagnardMobile here: Official Download Here. Do this in Safe Mode.

    Then do a custom install of only the Nvidia Graphics and PhysX driver.

    See if that gets rid of the problem.

    One last thing, check the voltages in BIOS/UEFI setup. Post results here if you can.
      My Computers


  3. Posts : 4
    W10
       #3

    Ztruker said:
    a
    Thanks for the quick response!

    The rollback option for Microsoft Remote Display Adapter is grayed out unfortunately.

    I actually had everything in my gaming rig but decided to take some older hardware and swap it out. (mainly wanted to separate gaming and office/plex) So I took 1 SSD, 3 HDD and also USB adapters for bluetooth headset, wireless m/kb then put into an old mini atx build w/ 2500k and 8gb of ram. I got brand new 550w PSU for it. Corsair. O/S is on the SSD. I also ran DDU in safe mode when moving over. (nvidia drivers)

    I also had this issue while it was in the gaming PC but never got any dump files as I believe I had incorrect settings but fixed them once moving into this one. The worst part is it already happened once on my 5 day old brand new gaming rig, but no dump file. New O/S on M2 drive so I forgot dump file settings, but put them in now and will make new thread for that rig if it happens again. New rig has everything new except I re-used RTX 3080 and CPU cooler + case fans. Also a brand new Corsair PSU.

    I think the only thing linking these two builds is Corsair brand PSU... maybe Corsair PSUs aren't great but I would think this would be a much more widespread issue. Another thing I'm thinking of is that it might be my battery backup but everything else plugged in seems fine, including PS5 and C9 TV. APC BR1500MS Back-UPS Pro Tower UPS. Also I'm pretty sure I unplugged my old gaming rig from UPS a few months back and it still happened.

    One last little thing is that these random freeze/reboots never happened during gaming. It was usually idle, when I was asleep, or a few minutes after starting to use the computer after a long idle. This mini build is the first time that it's happened while actually working with an average/small load.

    Sorry for the wall of text, I just thought I should mention all this in-case some sort of link between these systems stands out.

    I am planning on moving the SSD/3 HDD and the MB/ram of my old gaming rig and putting it into a new case that should arrive later today. The only reason I didn't do this from the beginning was because my existing case is a mini atx one and I needed something for work/plex server.

    Do you think any of this info makes sense at all? Maybe I should just avoid Corsair PSU from now on? lol

    EDIT: Also which voltage info did you need? Should I just screenshot everything and post here?

    p.s. Sorry for posting with a new acc - had some account issues but Brink helped me out!
      My Computer


  4. Posts : 14,046
    Windows 11 Pro X64 22H2 22621.1848
       #4

    Pics of all voltages in BIOS/UEFI setup would be good.

    How to fill out System Specs for tenforums.

    See here: System Specs - Fill in at Ten Forums

    Fill out as much as you can, look at mine for an example of what can be included. The more information the better.
    Full PSU info also please.

    You could try uninstalling Microsoft Remote Display Adapter in Device Manager then reboot and let Windows detect and reinstall it, see if that makes any difference.
      My Computers


  5. Posts : 41,481
    windows 10 professional version 1607 build 14393.969 64 bit
       #5

    The logs displayed drive problems.


    Computer: DESKTOP-P7CMON6
    Computer: KayOffice
    Was the computer name recently changed?


    Some of the drives are very large.

    Please test all drives and run the tests overnight as needed.


    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


    Run Sea Tools for Windows
    long generic test
    Post an image of the test result into the thread
    SeaTools for Windows |
    Seagate

    How to use SeaTools for Windows | Seagate Support US




    Open administrative command prompt and type or copy and paste:
    chkdsk /r /v
    This may take hours to run so plan to run overnight.
    Run on all drives using the syntax: chkdsk /b /v C: or chkdsk /b /v D: changing the drive letter to the applicable drive.

    C:\Windows\system32>chkdsk /b /v
    The type of the file system is NTFS.
    Cannot lock current drive.

    Chkdsk cannot run because the volume is in use by another
    process. Would you like to schedule this volume to be
    checked the next time the system restarts? (Y/N)

    Type: Y
    reboot


    Use the information in this link to find the chkdsk report in the event viewer.
    Copy and paste into notepad > save to desktop > post into the thread using a one drive, drop box, or google drive share link:
    Read Chkdsk Log in Event Viewer in Windows 10 Windows 10 Performance Maintenance Tutorials
    Read Chkdsk Log in Event Viewer in Windows 10



    Code:
    Event[4494]:
      Log Name: System
      Source: disk
      Date: 2020-12-11T07:34:45.4240000Z
      Event ID: 7
      Task: N/A
      Level: Error
      Opcode: N/A
      Keyword: Classic
      User: N/A
      User Name: N/A
      Computer: KayOffice
      Description: 
    The device, \Device\Harddisk2\DR2, has a bad block.
    Code:
    Event[1684]:
      Log Name: System
      Source: disk
      Date: 2020-11-27T02:51:22.9010000Z
      Event ID: 7
      Task: N/A
      Level: Error
      Opcode: N/A
      Keyword: Classic
      User: N/A
      User Name: N/A
      Computer: DESKTOP-P7CMON6
      Description: 
    The device, \Device\Harddisk1\DR1, has a bad block.
    Code:
    Description	Disk drive
    Manufacturer	(Standard disk drives)
    Model	WDC WD80EFZX-68UW8N0
    Bytes/Sector	512
    Media Loaded	Yes
    Media Type	Fixed hard disk
    Partitions	1
    SCSI Bus	1
    SCSI Logical Unit	0
    SCSI Port	0
    SCSI Target ID	0
    Sectors/Track	63
    Size	7.28 TB (8,001,560,609,280 bytes)
    Total Cylinders	972,801
    Total Sectors	15,628,048,065
    Total Tracks	248,064,255
    Tracks/Cylinder	255
    Partition	Disk #1, Partition #0
    Partition Size	7.28 TB (8,001,560,772,608 bytes)
    Partition Starting Offset	1,048,576 bytes
    	
    Description	Disk drive
    Manufacturer	(Standard disk drives)
    Model	Samsung SSD 850 EVO 500GB
    Bytes/Sector	512
    Media Loaded	Yes
    Media Type	Fixed hard disk
    Partitions	3
    SCSI Bus	0
    SCSI Logical Unit	0
    SCSI Port	0
    SCSI Target ID	0
    Sectors/Track	63
    Size	465.76 GB (500,105,249,280 bytes)
    Total Cylinders	60,801
    Total Sectors	976,768,065
    Total Tracks	15,504,255
    Tracks/Cylinder	255
    Partition	Disk #0, Partition #0
    Partition Size	529.00 MB (554,696,704 bytes)
    Partition Starting Offset	135,266,304 bytes
    Partition	Disk #0, Partition #1
    Partition Size	100.00 MB (104,857,600 bytes)
    Partition Starting Offset	689,963,008 bytes
    Partition	Disk #0, Partition #2
    Partition Size	465.02 GB (499,313,016,832 bytes)
    Partition Starting Offset	794,820,608 bytes
    	
    Description	Disk drive
    Manufacturer	(Standard disk drives)
    Model	WDC WD30EZRZ-00WN9B0
    Bytes/Sector	512
    Media Loaded	Yes
    Media Type	Fixed hard disk
    Partitions	1
    SCSI Bus	4
    SCSI Logical Unit	0
    SCSI Port	0
    SCSI Target ID	0
    Sectors/Track	63
    Size	2.73 TB (3,000,590,369,280 bytes)
    Total Cylinders	364,801
    Total Sectors	5,860,528,065
    Total Tracks	93,024,255
    Tracks/Cylinder	255
    Partition	Disk #2, Partition #0
    Partition Size	2.73 TB (3,000,457,232,384 bytes)
    Partition Starting Offset	135,266,304 bytes
    	
    Description	Disk drive
    Manufacturer	(Standard disk drives)
    Model	WDC WD80EMAZ-00WJTA0
    Bytes/Sector	512
    Media Loaded	Yes
    Media Type	Fixed hard disk
    Partitions	1
    SCSI Bus	5
    SCSI Logical Unit	0
    SCSI Port	0
    SCSI Target ID	0
    Sectors/Track	63
    Size	7.28 TB (8,001,560,609,280 bytes)
    Total Cylinders	972,801
    Total Sectors	15,628,048,065
    Total Tracks	248,064,255
    Tracks/Cylinder	255
    Partition	Disk #3, Partition #0
    Partition Size	7.28 TB (8,001,527,218,176 bytes)
    Partition Starting Offset	1,048,576 bytes
      My Computer


  6. Posts : 18,044
    Win 10 Pro 64-bit v1909 - Build 18363 Custom ISO Install
       #6

    Hello @Ztruker,

    Ztruker said:
    Completely uninstall the current Nvidia display drivers using Display Driver Uninstaller (DDU) from WagnardMobile here: Official Download Here. Do this in Safe Mode.

    I don't know if you use a file to keep the most used information for a reply in a post, and then just Copy & Paste it into a reply, but if you do, you might want to update the above to . . .

    Wagnardsoft Website => Display Driver Uninstaller (DDU) V18.0.3.5
    Direct DDU Download => Official Download Here

    I hope this helps.
      My Computer


  7. Posts : 14,046
    Windows 11 Pro X64 22H2 22621.1848
       #7

    Absolutely, thanks Paul. Earning that new gold star I see

    I keep a lot of my responses in the Manage Post templates section.

    Attachment 311802 Attachment 311803

    Just updated my NVIDIA one to the new info you provided.
      My Computers


  8. Posts : 18,044
    Win 10 Pro 64-bit v1909 - Build 18363 Custom ISO Install
       #8

    Ztruker said:
    Absolutely, thanks Paul.

    Just updated my NVIDIA one to the new info you provided.
    You are VERY welcome Rich.
      My Computer


 

  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 20:47.
Find Us




Windows 10 Forums