Constant reboots, different errors, old computer

Page 1 of 2 12 LastLast

  1. Posts : 16,325
    W10Prox64
       #1

    Constant reboots, different errors, old computer


    Hi.
    I have an old Dell XPS, originally came with Vista 32-bit, been running W10 Creators Update 32-bit on Insider Release Preview, but, as of yesterday running Fall Creators Update. This system constantly reboots for no reason; many reboots are not "complete" shutdowns.

    Until yesterday, it was running Creators Update in Release Preview. SFC /SCANNOW and all DISM commands ran without error. Tried several times to update to Fall Creators Update and it always failed. Tried UUP2ISO before Restart, and that failed with "Windows\WinSxS\x86_microsoft-windows-ie-memoryanalyzer_....MemoryAnalyzer.dll blob not found" in the UUP tool. So, figured I'd let it fail the update once again and try more tomorrow. Well, I hit Restart and it successfully updated to FCU. Then I tried to make the UUP ISO from the Windows.old folder, and it worked.

    Memtest was run for 19 hours with no errors.
    Hard drive is healthy.
    Fast Startup is off.
    BIOS has no updates available.
    Sometimes upon reboot, the fans will sound like a jet engine.
    I do know that some of the USB ports are acting up/failing (mostly on the front of the box).

    Hoping someone might see something in these logs, because I am out of ideas.

    TIA for any and all assistance!
    Last edited by simrick; 15 Nov 2017 at 23:25.
      My Computer


  2. Posts : 5,169
    64bit Win 10 Pro ver 21H2
       #2

    We are going to struggle to make any progress on debugging until Microsoft release the new symbol files for the FCU. I can see from the eventlog that the last startup repair failed.

    It did report the following: Windows successfully installed the following update: 2017-10 Cumulative Update for Windows 10 Version 1709 for x86-based Systems (KB4043961)
      My Computers


  3. Posts : 16,325
    W10Prox64
    Thread Starter
       #3

    philc43 said:
    We are going to struggle to make any progress on debugging until Microsoft release the new symbol files for the FCU. I can see from the eventlog that the last startup repair failed.

    It did report the following: Windows successfully installed the following update: 2017-10 Cumulative Update for Windows 10 Version 1709 for x86-based Systems (KB4043961)
    Yes, it took a cumulative update this morning.

    It just seems so very unstable.
    Sometimes the reboots are not true reboots - it doesn't completely shutdown, even though Fast Startup is turned off.
    Once it corrupted Teamviewer, which had to be reinstalled.
    Several times it will try to reboot and say boot files are corrupt; then reboot and all is fine, without fixing anything.
    The errors that turned up in Reliability History were all over the place - no rhyme or reason.
    It will constantly reboot numerous times, and then become stable and work well the rest of the day.
    Macrium images will complete, but many times the verification part fails.

    I understand you need the new symbol files to be able to do anything. Wondering if a memory controller is going?
    Thanks! :)
      My Computer


  4. Posts : 5,169
    64bit Win 10 Pro ver 21H2
       #4

    I did get this information from the earliest crashdump in the logs:

    ADDITIONAL_DEBUG_TEXT: Memory Manager detected corruption of a pagefile page while performing an in-page operation.
    The data read from storage does not match the original data written.
    This indicates the data was corrupted by the storage stack, or device hardware.

    The next crash dump showed this: ERROR_CODE: (NTSTATUS) 0xc0000420 - An assertion failure has occurred.

    It looks as if there may be some corruption with data being read to and from the disk.
      My Computers


  5. Posts : 16,325
    W10Prox64
    Thread Starter
       #5

    I did do this a few days ago:
    Open Start, right-click My Computer, and then click Properties.
    Click the Advanced System settings tab.
    Under Performance, click Settings.
    Click the Advanced tab.
    Under Virtual Memory, click Change.
    Click No paging file. Click OK, ok, ok and make sure to apply.
    Restart your computer.
    Open Start, right-click My Computer, and then click Properties.
    Click the Advanced System settings tab.
    Under Performance, click Settings.
    Click the Advanced tab.
    Under Virtual Memory, click Change.
    Click System managed sized. Click OK, ok, ok and make sure to apply.
    Restart your computer.

    Didn't make any difference.
      My Computer


  6. Posts : 16,325
    W10Prox64
    Thread Starter
       #6

    Hi. Just wondering if the symbol files are out yet, and if so, is there anything more to look at on this system, or should we just trash it? Thanks.
      My Computer


  7. Posts : 41,412
    windows 10 professional version 1607 build 14393.969 64 bit
       #7

    Hi simrick,

    There were 3 BSOD mini dumps debugged and there was 1 misbehaving hardware driver.
    These were from 10/16 and 10/17
    The event viewer was clean.

    In case this misbehaving driver was not yet fixed:

    The best way to fix the misbehaving Nvidia driver is to uninstall everything Nvidia using Display driver uninstaller and install new drivers from the computer manufacturer's website or from the Nvidia website.
    The computer manufacturer's web site is preferred. Enter the computer's serial or product number and the operating system to view available drivers.
    If you use the Nvidia web site be sure the "clean install" box is checked and only install the graphics driver and the physx driver.
    Official Display Driver Uninstaller DDU Download
    Display Driver Uninstaller Download version 17.0.7.2
    Display Driver Uninstaller: How to use - Windows 7 Help Forums
    NVIDIA

    Code:
    Name	NVIDIA GeForce 7900 GS
    PNP Device ID	PCI\VEN_10DE&DEV_0292&SUBSYS_037010DE&REV_A1\4&1C5347E9&0&0008
    Adapter Type	GeForce 7900 GS, NVIDIA compatible
    Adapter Description	NVIDIA GeForce 7900 GS
    Adapter RAM	256.00 MB (268,435,456 bytes)
    Installed Drivers	nvd3dum.dll
    Driver Version	9.18.13.908
    INF File	oem29.inf (Section002 section)
    Color Planes	Not Available
    Color Table Entries	4294967296
    Resolution	1024 x 768 x 60 hertz
    Bits/Pixel	32
    Memory Address	0xDD000000-0xDDFFFFFF
    Memory Address	0xC0000000-0xCFFFFFFF
    Memory Address	0xDE000000-0xDEFFFFFF
    I/O Port	0x0000DC80-0x0000DCFF
    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 (9.18.13.908, 10.46 MB (10,964,624 bytes), 7/21/2015 1:02 PM)
      My Computer


  8. Posts : 926
    Windows 10 Pro
       #8

    There are many different bugchecks in the dumpfiles.
    The cause for different error codes are usually hardware and lower level problems.

    Check RAM and HDD. U also have different RAM modules. Incompatibilty can cause that too.

    But first, like zbook wrote, u should update the nvidia graphics driver, your version is very old (dated 2015-01-31)
      My Computer


  9. Posts : 16,325
    W10Prox64
    Thread Starter
       #9

    Thanks guys. I will get back to this system in a few days, and let you know how it goes.
      My Computer


  10. Posts : 16,325
    W10Prox64
    Thread Starter
       #10

    Okay, I ran DDU in safe mode, then rebooted. Now it has the Windows Generic Driver. The screen resolution looks fine, so thought I'd leave it that way for a while and see what happens. There are no updates for this nVidia driver - it's an old video card.

    It started rebooting again on it's own; once when it cycled, the fans sounded like jet engines again.

    Just to recap:
    System originally had Vista 32-bit and was clean installed with W10 during initial Insider program.
    Memtest was run for 19 hours with no errors.
    Hard drive is healthy.
    Fast Startup is off.
    BIOS has no updates available.
    Sometimes (but not always) upon reboot, the fans will sound like a jet engine.
    I do know that some of the USB ports are acting up/failing (mostly on the front of the box).
    The RAM has been that way (2 different MFGs) for years without issue, and was added/purchased based on a scan at Crucial.com.

    Any other ideas? Thanks very much!

    EDIT:
    Owner has decided to junk it. Thanks again guys for your help.
    Last edited by simrick; 15 Nov 2017 at 23:23.
      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 10:01.
Find Us




Windows 10 Forums