Is it a hardware problem which has nothing to do with Windows?

Page 12 of 14 FirstFirst ... 21011121314 LastLast

  1. Posts : 38,349
    windows 10 professional version 1607 build 14393.969 64 bit
       #111

    The logs displayed no BSOD.

    These were seen in the logs:
    Code:
    The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.


    Were the RAM modules tested yet?
    If yes then please post an image of the results.
    If no then test both RAM modules with Memtest86+ version 5.01 with 8 or more passes.
    Memtest86+ - Advanced Memory Diagnostic Tool
    Testing is not done by time but by passes.
    The more the passes the better the testing conditions.
    The approximate testing time is 1 -2 hours / GB RAM
    Testing must be continuous.
    A substantial portion of the testing can be performed overnight.
    Just 1 error is a fail and testing can be aborted.
    Then test one RAM module at a time in the same DIMM for 8 or more passes to differentiate good from malfunctioning RAM.
    Use a camera or smartphone camera to take a pictures of each result and post images into the thread.

    Memory problems. - Microsoft Community
    MemTest86+ - Test RAM | Tutorials



    Also check each RAM module to make sure that they are approved by the motherboard manufacturer.



    Code:
    Name	Intel(R) HD Graphics 4400
    PNP Device ID	PCI\VEN_8086&DEV_041E&SUBSYS_D0001458&REV_06\3&11583659&0&10
    Adapter Type	Intel(R) HD Graphics Family, Intel Corporation compatible
    Adapter Description	Intel(R) HD Graphics 4400
    Adapter RAM	1.00 GB (1,073,741,824 bytes)
    Installed Drivers	igdumdim64.dll,igd10iumd64.dll,igd10iumd64.dll,igd12umd64.dll
    Driver Version	20.19.15.5058
    INF File	oem11.inf (iHSWD_w10 section)
    Color Planes	Not Available
    Color Table Entries	4294967296
    Resolution	1366 x 768 x 60 hertz
    Bits/Pixel	32
    Memory Address	0xF7800000-0xF7BFFFFF
    Memory Address	0xE0000000-0xEFFFFFFF
    I/O Port	0x0000F000-0x0000F03F
    IRQ Channel	IRQ 4294967293
    I/O Port	0x000003B0-0x000003BB
    I/O Port	0x000003C0-0x000003DF
    Memory Address	0xA0000-0xBFFFF
    Driver	c:\windows\system32\drivers\igdkmd64.sys (20.19.15.5058, 7.59 MB (7,963,576 bytes), 12/14/2018 20:13)
    Code:
    igfx	igfx	c:\windows\system32\drivers\igdkmd64.sys	Kernel Driver	No	Manual	Stopped	OK	Ignore	No	No

    Code:
    Name              : Intel(R) Core(TM) i3-4130 CPU @ 3.40GHz
    Description       : Intel64 Family 6 Model 60 Stepping 3
    Manufacturer      : GenuineIntel
    DeviceID          : CPU0
    SocketDesignation : SOCKET 0
    CurrentClockSpeed : 3400
    CPUStatus         : 1
    LastErrorCode     : 
    ErrorDescription  : 
    PartNumber        : Fill By OEM
    Revision          : 15363
    SerialNumber      : 
    ProcessorId       : BFEBFBFF000306C3
    Status            : OK
    StatusInfo        : 3
    Stepping          : 
    CurrentVoltage    : 11
    VoltageCaps       :
      My Computer

  2. Matthew Wai's Avatar
    Posts : 5,033
    Windows 10 Home 20H2
    Thread Starter
       #112

    I have just clean installed Windows 10 version 1607 in Chinese. Let's see whether the malfunction will happen.

    Is it a hardware problem which has nothing to do with Windows?-ram-test.jpg
      My Computer

  3. spapakons's Avatar
    Posts : 2,891
    Windows 10 Pro 64-bit 202H (Nov 2020 build 19042.867)
       #113

    Download and run Passmark Burnin test. It will tell you which part of hardware is faulty.
      My Computer

  4. Matthew Wai's Avatar
    Posts : 5,033
    Windows 10 Home 20H2
    Thread Starter
       #114

    On December 19, after replacing the CPU, the same malfunction still happened.
    On December 20, I clean installed Windows 10 version 1607. Since then, Windows has been run for eight and a half hours, and no malfunction has happened so far.
      My Computer

  5. spapakons's Avatar
    Posts : 2,891
    Windows 10 Pro 64-bit 202H (Nov 2020 build 19042.867)
       #115

    So it was indeed a driver issue solver by the clean installation. Elementary Watson...
      My Computer

  6. Matthew Wai's Avatar
    Posts : 5,033
    Windows 10 Home 20H2
    Thread Starter
       #116

    After I clean installed version 1809, the malfunction happened repeatedly.
    See Is it a hardware problem which has nothing to do with Windows? - Page 8 - Windows 10 Forums

    I am now running version 1607. No malfunction has happened so far.
      My Computer

  7. Kbird's Avatar
    Posts : 2,196
    Win10 202H
       #117

    Matthew Wai said:
    After I clean installed version 1809, the malfunction happened repeatedly.
    See Is it a hardware problem which has nothing to do with Windows? - Page 8 - Windows 10 Forums

    I am now running version 1607. No malfunction has happened so far.
    Perhaps try 1709 or even 1803 too then , personally there a few quirks in 1809 and I rather still be on 1803 myself.
      My Computers

  8. spapakons's Avatar
    Posts : 2,891
    Windows 10 Pro 64-bit 202H (Nov 2020 build 19042.867)
       #118

    Matthew Wai said:
    After I clean installed version 1809, the malfunction happened repeatedly. See Is it a hardware problem which has nothing to do with Windows? - Page 8 - Windows 10 ForumsI am now running version 1607. No malfunction has happened so far.
    Again this indicated a driver issue. Try changing the driver after v1809 installation.
      My Computer

  9. Matthew Wai's Avatar
    Posts : 5,033
    Windows 10 Home 20H2
    Thread Starter
       #119

    spapakons said:
    Again this indicated a driver issue. Try changing the driver after v1809 installation.
    I tried five drivers on version 1809, and the malfunction happened repeatedly.
      My Computer

  10. Matthew Wai's Avatar
    Posts : 5,033
    Windows 10 Home 20H2
    Thread Starter
       #120

    Kbird said:
    Perhaps try 1709 or even 1803 too then , personally there a few quirks in 1809 and I rather still be on 1803 myself.
    1803 crashed my PC occasionally.
    1809 crashed my PC frequently.
    I have not tried 1703 and 1709.
    I am now running 1607, which has not yet crashed my PC but may do so later.
    Let's wait and see.
      My Computer


 
Page 12 of 14 FirstFirst ... 21011121314 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 06:00.
Find Us




Windows 10 Forums