1. #1

    [W10StdV1703b15063 x64] BC 0x5c HAL_INITIALIZATION_FAILED.

    Since I formated my pc and installed Windows 10 pro from scratch, every time I start my pc after been powered down for at least 15 minutes, it restarts after reaching the blue Windows logo.
    Checking BlueScreenView shows that I get a BSOD every time that happens (I never get to even see it). The error is called HAL_INITIALIZATION_FAILED involving hal.dll and ntoskrnl.exe.
    I've reinstalled Win10, done a chkdsk /r but none of them worked. In the cmd of the repair tools (the one you access via holding down shift and clicking restart) I entered the commands:
    bootrec /RebuildBcd
    bootrec /FixMbr
    bootrec /FixBoot
    and it fixed the problem! But 4 days later I was having the same issue again.
    I had x2 Hyper Blue 4GB and x2 Corsair 4GB
    RAM's adding a total of 16 GB. I removed the Hyper Blue's and the issue was fixed but three weeks later I'm getting the same error again.

    ╖ OS: Windows 10 Pro x64 (upgraded from 8.1, then installed from scratch)
    ╖ CPU: AMD FX-6300 six core
    ╖ Video Card: MSI GTX 960
    ╖ RAM: CORSAIR VENGANCE Pro Series DDR3 2x4GB 2400MHZ
    ╖ MotherBoard: ASRock
    980DE3/U3S3
    ╖ Power Supply: Purepower ATX 12v 2.0

    SysnativeFileCollectionApp.rar: SysnativeFileCollectionApp.rar - Google Drive
    Thanks.


    • Ad Bot

      advertising
      Beep.

        
       

  2. #2
    Sysnative Staff
    BSOD Kernel Dump Analyst
    Contributor
    axe0's Avatar
    Join Date
    May 2015
    Location
    The Netherlands
    Age
    22
    Posts
    666
    • specs System Specs
      • Manufacturer:
        Custom build
      • Motherboard:
        Gigabyte B150-HD3P-CF
      • CPU:
        Intel(R) Core(TM) i5-6500 CPU @ 3.20GHz
      • Memory:
        16GB DDR4 Crucial Ballistix Sport LT BLS8G4D240F
      • Graphics:
        Intel(R) HD Graphics 530
      • Sound Card:
        (1) Intel(R) Display Audio (2) Realtek HD Audio
      • Hard Drives:
        Crucial MX200 500GB & 2x Toshiba DT01ACA300
      • Power Supply:
        Corsair RM550x
      • Case:
        Fractal Design Define S
      • Cooling:
        Cooler Master TX3 i
      • Display:
        24" Liyama ProLite XB2483HSU-B2 & 24" Dell Ultrasharp U2414H
      • Operating System:
        Windows 10 Pro

    Re: HAL_INITIALIZATION_FAILED Windows 10

    Please run in an admin command prompt following command
    Code:
    slmgr /dlv
    a pop-up will show within a few moments, make a screenshot of it and post it.

  3. #3
    Moderator
    BSOD Kernel Dump Analyst
    Windows Update Instructor
    softwaremaniac's Avatar
    Join Date
    Oct 2014
    Location
    Croatia
    Age
    23
    Posts
    13,185
    • specs System Specs
      • Motherboard:
        ASUS MAXIMUS ROG HERO X
      • CPU:
        Intel Core i7-8700K 3.7GHz
      • Memory:
        Crucial 2x8GB DDR4 2666 MHz
      • Graphics:
        Gigabyte GTX 1080 G1 Gaming 8 GB
      • Sound Card:
        Asus Xonar DSX
      • Hard Drives:
        WD Caviar Black 1TB SATA III 7200rpm, WD Caviar Black 6TB SATA III 7200rpm
      • Disk Drives:
        Samsung 960 Evo 256GB NVME PCIe
      • Power Supply:
        Corsair HX 750W 80+ Platinum
      • Case:
        Fractal Design Define R6
      • Cooling:
        Noctua NH-D14
      • Display:
        Philips Brilliance BDM4065UC 4K 3840x2160
      • Operating System:
        Windows 10 Pro 1803 x64

    Re: HAL_INITIALIZATION_FAILED Windows 10

    Hello and welcome, I'd like you to upodate your Realtek PCIe Adapter driver, and run hardware tests:

    Initial Hardware Diagnostics

    Also, please note that your PSU is very old, and it may be causing the BSODs.



    Code:
    Rt630x64.sys Tue Jun 12 15:37:53 2012  (4FD74631) 
    Realtek PCI/PCIe Adapters  http://www.realtek.com.tw/downloads/downloadsView.aspx?Langid=1&PNid=7&PFid=10&Level=3&Conn=2  
    http://www.carrona.org/drivers/driver.php?id=Rt630x64.sys 
    
    MpKsl6b41d987.sys Wed May 20 03:50:37 2015 (555BE86D)  
    
    MpKsl6b41d987.sys - this  driver hasn't been added to the DRT as of this run. Please search Google/Bing  for the driver if additional information is needed. 
    
    MpKsleaca8b98.sys Wed May 20 03:50:37 2015 (555BE86D)  
    
    MpKsleaca8b98.sys - this  driver hasn't been added to the DRT as of this run. Please search Google/Bing  for the driver if additional information is needed. 
    
    MpKslc43d3673.sys Wed May 20 03:50:37 2015 (555BE86D)  
    
    MpKslc43d3673.sys - this  driver hasn't been added to the DRT as of this run. Please search Google/Bing  for the driver if additional information is needed. 
    
    MpKslfd40722d.sys Wed May 20 03:50:37 2015 (555BE86D)  
    
    MpKslfd40722d.sys - this  driver hasn't been added to the DRT as of this run. Please search Google/Bing  for the driver if additional information is needed. 
    
    MpKsl545ca187.sys Wed May 20 03:50:37 2015 (555BE86D)  
    
    MpKsl545ca187.sys - this  driver hasn't been added to the DRT as of this run. Please search Google/Bing  for the driver if additional information is needed. 
    
    MpKsl566e23cb.sys Wed May 20 03:50:37 2015 (555BE86D)  
    
    MpKsl566e23cb.sys - this  driver hasn't been added to the DRT as of this run. Please search Google/Bing  for the driver if additional information is needed. 
    
    MpKsl32b30be4.sys Wed May 20 03:50:37 2015 (555BE86D)  
    
    MpKsl32b30be4.sys - this  driver hasn't been added to the DRT as of this run. Please search Google/Bing  for the driver if additional information is needed. 
    
    MpKslc4cea991.sys Wed May 20 03:50:37 2015 (555BE86D)  
    
    MpKslc4cea991.sys - this  driver hasn't been added to the DRT as of this run. Please search Google/Bing  for the driver if additional information is needed. 
    
    ALSysIO64.sys  Wed Jul 6 18:47:33 2016 (577D3625) 
    Core Temp - CPU temperature monitor  Core Temp 
    http://www.carrona.org/drivers/driver.php?id=ALSysIO64.sys 
    
    rt640x64.sys Wed Oct 5 15:32:55  2016 (57F50107) 
    Realtek NICDRV 8169 PCIe GBE Family Controller driver [br]  Realtek  
    http://www.carrona.org/drivers/driver.php?id=rt640x64.sys 
    
    nvhda64v.sys Tue May 16 15:02:27  2017 (591AF863) 
    nVidia HDMI Audio Device (nForce chipset driver)  http://www.nvidia.com/Download/index.aspx 
    http://www.carrona.org/drivers/driver.php?id=nvhda64v.sys 
    
    nvvad64v.sys Mon May 29 01:04:45  2017 (592B578D) 
    NVIDIA Virtual Audio Driver  http://www.nvidia.com/Download/index.aspx?lang=en-us 
    http://www.carrona.org/drivers/driver.php?id=nvvad64v.sys 
    
    VBoxNetLwf.sys Thu Jul 27  13:33:48 2017 (5979CF9C) 
    Oracle VirtualBox NDIS 6.0 Lightweight Filter  Driver http://www.virtualbox.org/wiki/Downloads 
    http://www.carrona.org/drivers/driver.php?id=VBoxNetLwf.sys 
    
    VBoxUSBMon.sys Thu Jul 27  13:33:48 2017 (5979CF9C) 
    VirtualBox USB driver  http://www.virtualbox.org/wiki/Downloads 
    http://www.carrona.org/drivers/driver.php?id=VBoxUSBMon.sys 
    
    VBoxDrv.sys Thu Jul 27 13:33:49  2017 (5979CF9D) 
    VirtualBox http://www.virtualbox.org/wiki/Downloads 
    http://www.carrona.org/drivers/driver.php?id=VBoxDrv.sys 
    
    nvlddmkm.sys Sat Sep 16 18:54:01  2017 (59BD5729) 
    nVidia Video drivers  http://www.nvidia.com/Download/index.aspx[br]Get from OEM for laptops 
    http://www.carrona.org/drivers/driver.php?id=nvlddmkm.sys 
    
    xusb22.sys  ***** Invalid 1986 Invalid 1986 Invalid 
    Xbox 360 Wireless  Receiver driver  http://www.microsoft.com/hardware/en...indows#support  
    http://www.carrona.org/drivers/driver.php?id=xusb22.sys 
    
    
    Code:
    
    Debug session time: Sat Sep 23 15:26:42.898 2017 (UTC + 2:00)
    
    Loading Dump File [D:\SysnativeBSODApps\092317-29218-01.dmp]
    
    Built by: 15063.0.amd64fre.rs2_release.170317-1834
    
    System Uptime: 0 days 12:59:52.604
    
    Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )
    
    BugCheck 5C, {110, fffff79740001000, 2a, 2614d0}
    
    BugCheck Info: HAL_INITIALIZATION_FAILED (5c)
    
    Bugcheck code 0000005C
    
    Arguments: 
    
    Arg1: 0000000000000110
    
    Arg2: fffff79740001000
    
    Arg3: 000000000000002a
    
    Arg4: 00000000002614d0
    
    BUGCHECK_STR:  0x5C
    
    DEFAULT_BUCKET_ID:  ZEROED_STACK_0x5C
    
    PROCESS_NAME:  System
    
    FAILURE_BUCKET_ID:  ZEROED_STACK_0x5C
    
    BiosVersion = P2.00
    
    BiosReleaseDate = 09/04/2015
    
    SystemManufacturer = To Be Filled By O.E.M.
    
    BaseBoardManufacturer = ASRock
    
    SystemProductName = To Be Filled By O.E.M.
    
    BaseBoardProduct = 980DE3/U3S3
    
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    
    Debug session time: Tue Sep 12 14:29:16.727 2017 (UTC + 2:00)
    
    Loading Dump File [D:\SysnativeBSODApps\091217-21828-01.dmp]
    
    Built by: 15063.0.amd64fre.rs2_release.170317-1834
    
    System Uptime: 1 days 3:20:42.457
    
    Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )
    
    BugCheck 5C, {110, fffff7b900001000, 2a, 155818}
    
    BugCheck Info: HAL_INITIALIZATION_FAILED (5c)
    
    Bugcheck code 0000005C
    
    Arguments: 
    
    Arg1: 0000000000000110
    
    Arg2: fffff7b900001000
    
    Arg3: 000000000000002a
    
    Arg4: 0000000000155818
    
    BUGCHECK_STR:  0x5C
    
    DEFAULT_BUCKET_ID:  ZEROED_STACK_0x5C
    
    PROCESS_NAME:  System
    
    FAILURE_BUCKET_ID:  ZEROED_STACK_0x5C
    
    BiosVersion = P2.00
    
    BiosReleaseDate = 09/04/2015
    
    SystemManufacturer = To Be Filled By O.E.M.
    
    BaseBoardManufacturer = ASRock
    
    SystemProductName = To Be Filled By O.E.M.
    
    BaseBoardProduct = 980DE3/U3S3
    
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    
    Debug session time: Mon Sep 11 11:07:48.554 2017 (UTC + 2:00)
    
    Loading Dump File [D:\SysnativeBSODApps\091117-22546-01.dmp]
    
    Built by: 15063.0.amd64fre.rs2_release.170317-1834
    
    System Uptime: 0 days 15:22:38.285
    
    Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )
    
    BugCheck 5C, {110, fffff7bdc0001000, 2a, 2a94ce}
    
    BugCheck Info: HAL_INITIALIZATION_FAILED (5c)
    
    Bugcheck code 0000005C
    
    Arguments: 
    
    Arg1: 0000000000000110
    
    Arg2: fffff7bdc0001000
    
    Arg3: 000000000000002a
    
    Arg4: 00000000002a94ce
    
    BUGCHECK_STR:  0x5C
    
    DEFAULT_BUCKET_ID:  ZEROED_STACK_0x5C
    
    PROCESS_NAME:  System
    
    FAILURE_BUCKET_ID:  ZEROED_STACK_0x5C
    
    BiosVersion = P2.00
    
    BiosReleaseDate = 09/04/2015
    
    SystemManufacturer = To Be Filled By O.E.M.
    
    BaseBoardManufacturer = ASRock
    
    SystemProductName = To Be Filled By O.E.M.
    
    BaseBoardProduct = 980DE3/U3S3
    
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    
    Debug session time: Sun Sep 10 16:14:10.083 2017 (UTC + 2:00)
    
    Loading Dump File [D:\SysnativeBSODApps\091017-23000-01.dmp]
    
    Built by: 15063.0.amd64fre.rs2_release.170317-1834
    
    System Uptime: 0 days 15:29:24.809
    
    Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )
    
    BugCheck 5C, {110, fffff7edc0001000, 2a, 25b8f7}
    
    BugCheck Info: HAL_INITIALIZATION_FAILED (5c)
    
    Bugcheck code 0000005C
    
    Arguments: 
    
    Arg1: 0000000000000110
    
    Arg2: fffff7edc0001000
    
    Arg3: 000000000000002a
    
    Arg4: 000000000025b8f7
    
    BUGCHECK_STR:  0x5C
    
    DEFAULT_BUCKET_ID:  ZEROED_STACK_0x5C
    
    PROCESS_NAME:  System
    
    FAILURE_BUCKET_ID:  ZEROED_STACK_0x5C
    
    BiosVersion = P2.00
    
    BiosReleaseDate = 09/04/2015
    
    SystemManufacturer = To Be Filled By O.E.M.
    
    BaseBoardManufacturer = ASRock
    
    SystemProductName = To Be Filled By O.E.M.
    
    BaseBoardProduct = 980DE3/U3S3
    
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    
    Debug session time: Thu Sep  7 05:02:30.128 2017 (UTC + 2:00)
    
    Loading Dump File [D:\SysnativeBSODApps\090717-24859-01.dmp]
    
    Built by: 15063.0.amd64fre.rs2_release.170317-1834
    
    System Uptime: 0 days 13:20:12.858
    
    Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )
    
    BugCheck 12B, {ffffffffc00002c4, 20e, bc87f0, ffffe0015d6f7000}
    
    BugCheck Info: FAULTY_HARDWARE_CORRUPTED_PAGE (12b)
    
    Bugcheck code 0000012B
    
    Arguments: 
    
    Arg1: ffffffffc00002c4, virtual address mapping the corrupted page
    
    Arg2: 000000000000020e, physical page number
    
    Arg3: 0000000000bc87f0, zero
    
    Arg4: ffffe0015d6f7000, zero
    
    BUGCHECK_STR:  0x12B_c00002c4_StCtDecompressFailed
    
    PROCESS_NAME:  MemCompression
    
    FAILURE_BUCKET_ID:  ZEROED_STACK_0x12B_c00002c4_StCtDecompressFailed
    
    BiosVersion = P2.00
    
    BiosReleaseDate = 09/04/2015
    
    SystemManufacturer = To Be Filled By O.E.M.
    
    BaseBoardManufacturer = ASRock
    
    SystemProductName = To Be Filled By O.E.M.
    
    BaseBoardProduct = 980DE3/U3S3
    
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    
    Debug session time: Wed Sep  6 15:41:27.018 2017 (UTC + 2:00)
    
    Loading Dump File [D:\SysnativeBSODApps\090617-36812-01.dmp]
    
    Built by: 15063.0.amd64fre.rs2_release.170317-1834
    
    System Uptime: 0 days 23:58:10.441
    
    Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )
    
    BugCheck 5C, {110, fffff7dc00001000, 2a, 25e701}
    
    BugCheck Info: HAL_INITIALIZATION_FAILED (5c)
    
    Bugcheck code 0000005C
    
    Arguments: 
    
    Arg1: 0000000000000110
    
    Arg2: fffff7dc00001000
    
    Arg3: 000000000000002a
    
    Arg4: 000000000025e701
    
    BUGCHECK_STR:  0x5C
    
    DEFAULT_BUCKET_ID:  ZEROED_STACK_0x5C
    
    PROCESS_NAME:  System
    
    FAILURE_BUCKET_ID:  ZEROED_STACK_0x5C
    
    BiosVersion = P2.00
    
    BiosReleaseDate = 09/04/2015
    
    SystemManufacturer = To Be Filled By O.E.M.
    
    BaseBoardManufacturer = ASRock
    
    SystemProductName = To Be Filled By O.E.M.
    
    BaseBoardProduct = 980DE3/U3S3
    
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    
    Debug session time: Tue Sep  5 15:42:37.483 2017 (UTC + 2:00)
    
    Loading Dump File [D:\SysnativeBSODApps\090517-25281-01.dmp]
    
    Built by: 15063.0.amd64fre.rs2_release.170317-1834
    
    System Uptime: 0 days 15:26:50.212
    
    Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )
    
    BugCheck 5C, {110, fffff7c080001000, 2a, 258d0e}
    
    BugCheck Info: HAL_INITIALIZATION_FAILED (5c)
    
    Bugcheck code 0000005C
    
    Arguments: 
    
    Arg1: 0000000000000110
    
    Arg2: fffff7c080001000
    
    Arg3: 000000000000002a
    
    Arg4: 0000000000258d0e
    
    BUGCHECK_STR:  0x5C
    
    DEFAULT_BUCKET_ID:  ZEROED_STACK_0x5C
    
    PROCESS_NAME:  System
    
    FAILURE_BUCKET_ID:  ZEROED_STACK_0x5C
    
    BiosVersion = P2.00
    
    BiosReleaseDate = 09/04/2015
    
    SystemManufacturer = To Be Filled By O.E.M.
    
    BaseBoardManufacturer = ASRock
    
    SystemProductName = To Be Filled By O.E.M.
    
    BaseBoardProduct = 980DE3/U3S3
    
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    
    Debug session time: Mon Sep  4 15:50:46.826 2017 (UTC + 2:00)
    
    Loading Dump File [D:\SysnativeBSODApps\090417-26109-01.dmp]
    
    Built by: 15063.0.amd64fre.rs2_release.170317-1834
    
    System Uptime: 0 days 18:05:37.229
    
    Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )
    
    BugCheck 5C, {110, fffff7f300001000, 2a, 260529}
    
    BugCheck Info: HAL_INITIALIZATION_FAILED (5c)
    
    Bugcheck code 0000005C
    
    Arguments: 
    
    Arg1: 0000000000000110
    
    Arg2: fffff7f300001000
    
    Arg3: 000000000000002a
    
    Arg4: 0000000000260529
    
    BUGCHECK_STR:  0x5C
    
    DEFAULT_BUCKET_ID:  ZEROED_STACK_0x5C
    
    PROCESS_NAME:  System
    
    FAILURE_BUCKET_ID:  ZEROED_STACK_0x5C
    
    BiosVersion = P2.00
    
    BiosReleaseDate = 09/04/2015
    
    SystemManufacturer = To Be Filled By O.E.M.
    
    BaseBoardManufacturer = ASRock
    
    SystemProductName = To Be Filled By O.E.M.
    
    BaseBoardProduct = 980DE3/U3S3
    
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    
    Debug session time: Sun Sep  3 16:48:35.046 2017 (UTC + 2:00)
    
    Loading Dump File [D:\SysnativeBSODApps\090317-21171-01.dmp]
    
    Built by: 15063.0.amd64fre.rs2_release.170317-1834
    
    System Uptime: 0 days 16:06:43.773
    
    *** WARNING: Unable to verify timestamp for win32k.sys
    
    *** ERROR: Module load completed but symbols could not be loaded for win32k.sys
    
    Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )
    
    BugCheck 5C, {110, fffff7c0c0001000, 2a, 2a3562}
    
    BugCheck Info: HAL_INITIALIZATION_FAILED (5c)
    
    Bugcheck code 0000005C
    
    Arguments: 
    
    Arg1: 0000000000000110
    
    Arg2: fffff7c0c0001000
    
    Arg3: 000000000000002a
    
    Arg4: 00000000002a3562
    
    BUGCHECK_STR:  0x5C
    
    DEFAULT_BUCKET_ID:  ZEROED_STACK_0x5C
    
    PROCESS_NAME:  System
    
    FAILURE_BUCKET_ID:  ZEROED_STACK_0x5C
    
    BiosVersion = P2.00
    
    BiosReleaseDate = 09/04/2015
    
    SystemManufacturer = To Be Filled By O.E.M.
    
    BaseBoardManufacturer = ASRock
    
    SystemProductName = To Be Filled By O.E.M.
    
    BaseBoardProduct = 980DE3/U3S3
    
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    
    Debug session time: Sun Sep  3 00:39:56.773 2017 (UTC + 2:00)
    
    Loading Dump File [D:\SysnativeBSODApps\090217-26343-01.dmp]
    
    Built by: 15063.0.amd64fre.rs2_release.170317-1834
    
    System Uptime: 0 days 2:55:51.501
    
    Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )
    
    BugCheck 5C, {110, fffff7bc80001000, 2a, 2ac5ab}
    
    BugCheck Info: HAL_INITIALIZATION_FAILED (5c)
    
    Bugcheck code 0000005C
    
    Arguments: 
    
    Arg1: 0000000000000110
    
    Arg2: fffff7bc80001000
    
    Arg3: 000000000000002a
    
    Arg4: 00000000002ac5ab
    
    BUGCHECK_STR:  0x5C
    
    DEFAULT_BUCKET_ID:  ZEROED_STACK_0x5C
    
    PROCESS_NAME:  System
    
    FAILURE_BUCKET_ID:  ZEROED_STACK_0x5C
    
    BiosVersion = P2.00
    
    BiosReleaseDate = 09/04/2015
    
    SystemManufacturer = To Be Filled By O.E.M.
    
    BaseBoardManufacturer = ASRock
    
    SystemProductName = To Be Filled By O.E.M.
    
    BaseBoardProduct = 980DE3/U3S3
    
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    
    
    
    
    
    --- E O J --- 2017 Sep 23 18:20:16 PM _88-dbug  Copyright 2017 Sysnative Forums 
    --- E O J --- 2017 Sep 23 18:20:16 PM  _88-dbug Copyright 2017 Sysnative Forums 
    --- E O J --- 2017 Sep 23 18:20:16  PM _88-dbug Copyright 2017 Sysnative Forums

  4. #4

    Re: HAL_INITIALIZATION_FAILED Windows 10

    Quote Originally Posted by axe0 View Post
    Please run in an admin command prompt following command
    Code:
    slmgr /dlv
    a pop-up will show within a few moments, make a screenshot of it and post it.
    [W10StdV1703b15063 x64] BC 0x5c HAL_INITIALIZATION_FAILED.-sin-t-tulo-jpg

  5. #5
    xilolee's Avatar
    Join Date
    Dec 2013
    Location
    World, Europe, Italy
    Posts
    2,260
    • specs System Specs
      • Manufacturer:
        XILOLEE.com
      • Model Number:
        XILO
      • Motherboard:
        ASROCK FM2A88M Pro3+ chipset A88X Bolton-D4
      • CPU:
        A10-7800, 4 CPU, 4 thr, 65/45W, FM2+, 28nm, Steamroller/Kaveri
      • Memory:
        10GB (Nanya and kingston ddr3-1333 9-9-9-24)
      • Graphics:
        Radeon R7 720MHz (8 GPU cores, integrated in CPU)
      • Sound Card:
        RealTek ALC662 (integrated in MB)
      • Hard Drives:
        Seagate ST500DM002-1BD142 500GB 7200RPM
      • Power Supply:
        SuperFlower 450W 80+ Platinum (SF-450P14PE)
      • Case:
        Sharkoon VG4-S
      • Cooling:
        Realtek RTL8111GR (NIC integrated in MB)
      • Display:
        Samsung SyncMaster SA100 LS22A100NS-EN
      • Operating System:
        Windows 10 Home/Standard x64

    Re: HAL_INITIALIZATION_FAILED Windows 10

    Hi spikedmace.

    Reading specs:
    - AMD FX 6-Core Black Edition - FX6300 Max Memory Speed: 1866 MHz.
    - ASROCK 980DE3/U3S3 motherboard supports DDR3 1866(OC)/1600(OC)/1333/1066/800 non-ECC, un-buffered memory.
    - ASROCK 980DE3/U3S3 motherboard supports up to windows 8 (but in the same page it says it supports Win10, in a picture).
    - RAM sticks should be seated in slots DDR3_A1 & DDR3_B1 (or DDR3_A2 & DDR3_B2), i.e.2nd & 4th slots (or 1st & 3rd) starting from the cpu.
    - RAM model is not present in asrock QVL (possible incompatibility?)
    - QVL 1st note: the mainboard supports DDR3-2100 MHz DIMMs only when you install a AM3+ cpu to the mainboard (but in QVL there aren't modules with that frequency).
    - QVL 2nd note: AMD FX series CPU on this motherboard support up to DDR3 1866 MHz as its standard memory frequency.
    - QVL 3rd note: When overclocking, some AMD CPU models may not support DDR3 1600 MHz or higher frequency DIMMs.
    - the dump shows Current Memory Type 0140h - ECC DIMM, but I think ECC modules of this type/model don't exist.
    - Microsoft support opinion about Bug Check 0x5C HAL_INITIALIZATION_FAILED: "This indicates that the HAL initialization failed". Very useful!

    A possible fix suggested by an user in answers.microsoft.com (click):
    Code:
    bcdedit /set useplatformclock true
    But I was starting to think there could be incompatibilities with RAM and/or GPU.
    Could you reveal us the other RAM (exact) model?

    Other strange information found in the dump:
    [Memory Controller Information (Type 5) - Length 24 - Handle 0008h]
    Error Detecting Method 06h - 64-bit ECC
    Error Correcting Capability 04h - None
    Supported Interleave 03h - One Way Interleave
    Current Interleave 03h - One Way Interleave
    Maximum Memory Module Size 0bh - 2048MB
    Supported Speeds 000ch - 70ns 60ns
    Supported Memory Types 0500h - DIMM SDRAM
    Memory Module Voltage 3.3V
    Number of Memory Slots 4
    Memory Slot Handle 0009h
    Memory Slot Handle 000ah
    Memory Slot Handle 000bh
    Memory Slot Handle 000ch
    Enabled Err Correcting Caps 04h - None

    [Physical Memory Array (Type 16) - Length 15 - Handle 0013h]
    Location 03h - SystemBoard/Motherboard
    Use 03h - System Memory
    Memory Error Correction 03h - None
    Maximum Capacity 8388608KB <---- This is 8GB!!!
    Memory Error Inf Handle [Not Provided]
    Number of Memory Devices 4
    I'm not sure why it shows those data.
    Your MB should support non-ECC/un-buffered memory, up to 32GB, therefore 8GB per slot.
    Last edited by xilolee; 09-23-2017 at 04:01 PM.

  6. #6

    Re: HAL_INITIALIZATION_FAILED Windows 10

    Quote Originally Posted by xilolee View Post
    Hi spikedmace.

    Reading specs:
    - AMD FX 6-Core Black Edition - FX6300 Max Memory Speed: 1866 MHz.
    - ASROCK 980DE3/U3S3 motherboard supports DDR3 1866(OC)/1600(OC)/1333/1066/800 non-ECC, un-buffered memory.
    - ASROCK 980DE3/U3S3 motherboard supports up to windows 8 (but in the same page it says it supports Win10, in a picture).
    - RAM sticks should be seated in slots DDR3_A1 & DDR3_B1 (or DDR3_A2 & DDR3_B2), i.e.2nd & 4th slots (or 1st & 3rd) starting from the cpu.
    - RAM model is not present in asrock QVL (possible incompatibility?)
    - QVL 1st note: the mainboard supports DDR3-2100 MHz DIMMs only when you install a AM3+ cpu to the mainboard (but in QVL there aren't modules with that frequency).
    - QVL 2nd note: AMD FX series CPU on this motherboard support up to DDR3 1866 MHz as its standard memory frequency.
    - QVL 3rd note: When overclocking, some AMD CPU models may not support DDR3 1600 MHz or higher frequency DIMMs.
    - the dump shows Current Memory Type 0140h - ECC DIMM, but I think ECC modules of this type/model don't exist.
    - Microsoft support opinion about Bug Check 0x5C HAL_INITIALIZATION_FAILED: "This indicates that the HAL initialization failed". Very useful!

    But I was starting to think there could be incompatibilities with RAM and/or GPU.
    Could you reveal us the other RAM (exact) model?
    I'm not sure why it shows those data.
    Your MB should support non-ECC/un-buffered memory, up to 32GB, therefore 8GB per slot.[/QUOTE]

    Right now I'm using the 2nd and 4th slots of RAM with the two Corsair.
    The other two Kingston Hyper Blu that I took away are:
    [W10StdV1703b15063 x64] BC 0x5c HAL_INITIALIZATION_FAILED.-whatsapp-image-2017-09-23-17-28-26-jpeg
    I was told to remove these RAM because of different frecuencies and different manufacturer.
    Thanks for the reply. I've done the CMD command, I'll let you know if it helps.

  7. #7
    xilolee's Avatar
    Join Date
    Dec 2013
    Location
    World, Europe, Italy
    Posts
    2,260
    • specs System Specs
      • Manufacturer:
        XILOLEE.com
      • Model Number:
        XILO
      • Motherboard:
        ASROCK FM2A88M Pro3+ chipset A88X Bolton-D4
      • CPU:
        A10-7800, 4 CPU, 4 thr, 65/45W, FM2+, 28nm, Steamroller/Kaveri
      • Memory:
        10GB (Nanya and kingston ddr3-1333 9-9-9-24)
      • Graphics:
        Radeon R7 720MHz (8 GPU cores, integrated in CPU)
      • Sound Card:
        RealTek ALC662 (integrated in MB)
      • Hard Drives:
        Seagate ST500DM002-1BD142 500GB 7200RPM
      • Power Supply:
        SuperFlower 450W 80+ Platinum (SF-450P14PE)
      • Case:
        Sharkoon VG4-S
      • Cooling:
        Realtek RTL8111GR (NIC integrated in MB)
      • Display:
        Samsung SyncMaster SA100 LS22A100NS-EN
      • Operating System:
        Windows 10 Home/Standard x64

    Re: HAL_INITIALIZATION_FAILED Windows 10

    It doesn't appear in QVL, but it could be more compatible.
    There's a similar model: KHX1600C9D3K2/8G.

  8. #8
    Sysnative Staff
    BSOD Kernel Dump Analyst
    Contributor
    axe0's Avatar
    Join Date
    May 2015
    Location
    The Netherlands
    Age
    22
    Posts
    666
    • specs System Specs
      • Manufacturer:
        Custom build
      • Motherboard:
        Gigabyte B150-HD3P-CF
      • CPU:
        Intel(R) Core(TM) i5-6500 CPU @ 3.20GHz
      • Memory:
        16GB DDR4 Crucial Ballistix Sport LT BLS8G4D240F
      • Graphics:
        Intel(R) HD Graphics 530
      • Sound Card:
        (1) Intel(R) Display Audio (2) Realtek HD Audio
      • Hard Drives:
        Crucial MX200 500GB &amp; 2x Toshiba DT01ACA300
      • Power Supply:
        Corsair RM550x
      • Case:
        Fractal Design Define S
      • Cooling:
        Cooler Master TX3 i
      • Display:
        24&quot; Liyama ProLite XB2483HSU-B2 &amp; 24&quot; Dell Ultrasharp U2414H
      • Operating System:
        Windows 10 Pro

    Re: HAL_INITIALIZATION_FAILED Windows 10

    Quote Originally Posted by spikedmace View Post
    Quote Originally Posted by axe0 View Post
    Please run in an admin command prompt following command
    Code:
    slmgr /dlv
    a pop-up will show within a few moments, make a screenshot of it and post it.
    [W10StdV1703b15063 x64] BC 0x5c HAL_INITIALIZATION_FAILED.-sin-t-tulo-jpg
    No KMS info, looks like a counterfeit Windows as Windows with proper KMS activation show details where you have none.

    Please install a genuine copy of Windows before moving on.

  9. #9
    xilolee's Avatar
    Join Date
    Dec 2013
    Location
    World, Europe, Italy
    Posts
    2,260
    • specs System Specs
      • Manufacturer:
        XILOLEE.com
      • Model Number:
        XILO
      • Motherboard:
        ASROCK FM2A88M Pro3+ chipset A88X Bolton-D4
      • CPU:
        A10-7800, 4 CPU, 4 thr, 65/45W, FM2+, 28nm, Steamroller/Kaveri
      • Memory:
        10GB (Nanya and kingston ddr3-1333 9-9-9-24)
      • Graphics:
        Radeon R7 720MHz (8 GPU cores, integrated in CPU)
      • Sound Card:
        RealTek ALC662 (integrated in MB)
      • Hard Drives:
        Seagate ST500DM002-1BD142 500GB 7200RPM
      • Power Supply:
        SuperFlower 450W 80+ Platinum (SF-450P14PE)
      • Case:
        Sharkoon VG4-S
      • Cooling:
        Realtek RTL8111GR (NIC integrated in MB)
      • Display:
        Samsung SyncMaster SA100 LS22A100NS-EN
      • Operating System:
        Windows 10 Home/Standard x64

    Re: HAL_INITIALIZATION_FAILED Windows 10

    This thread was in windows update forum marked as solved.

    How was this solved?

Similar Threads

  1. Replies: 7
    Last Post: 01-17-2018, 03:56 PM
  2. [W10StdV1703b15063 x64] Another BSOD Crash 0x7f
    By kvizerad in forum BSOD, Crashes, Kernel Debugging
    Replies: 20
    Last Post: 10-04-2017, 02:10 PM
  3. [SOLVED] [W10StdV1703b15063 x64] PC reboots during gaming; no minidumps. FIX: NEW PSU.
    By Mikedabike in forum BSOD, Crashes, Kernel Debugging
    Replies: 72
    Last Post: 09-19-2017, 03:05 PM
  4. Replies: 12
    Last Post: 09-16-2017, 12:19 PM
  5. BSOD Code 0x5C
    By IRFAN in forum BSOD, Crashes, Kernel Debugging
    Replies: 6
    Last Post: 10-03-2012, 10:00 AM

Log in

Log in