Page 1 of 6 123 ... LastLast
  1.    2 Weeks Ago #1
    Join Date : Sep 2015
    Sydney Oz
    Posts : 77
    Win Pro 10x64 1709 16299.19

    Blue screen at start-since up to 1703-KB4041676 won't load and more


    Hi,

    Firstly my machine..

    ASRock 880GM-LE FX Bios AM P1.70 07/23/2015
    AMD FX 6100 Six Core 3.30 Ghz
    8GB RAM 7.75 Stable
    ATI Radeon HD4250
    Monitors DEll 24"+Toshiba 19"
    Win 10 x64 1703 Build 15063.608

    Seems like since update to 1703 When I cold boot I get Blue screen
    VIDEO TDR FAILURE atikm pag.sys
    When I reboot, Win opens okay.

    When open everything seesm to work fine except Win system files for eg.
    When I right click on Start menu items
    These links will not open..
    File Explorer, Computer Management, Disk Management, Device Manager, Event Viewer all other links work.

    In Event mgr; Lots of Errors in Admin events

    Win Update problem. Fail to install since Oct 14 also (KB4040724) on Oct 28
    2017-10 Cumulative Update for Windows 10 Version 1703 for x64-based Systems (KB4041676) - Error 0x8007025d

    In case of Virus etc..
    I have Driver Booster says all updated, SuperAntiSpy, no probs, Defender no probs, Avast no probs,Malwarebytes no probs.

    Have attached Diag zip as requested as well as error panel which came up during diag install.

    I am not sure whether I need a new box or clean Win 10.

    Many thanks for the offer of help.

    oz
    Attached Thumbnails Attached Thumbnails Win 10 error panel1.jpg  
    Blue screen at start-since up to 1703-KB4041676 won't load and more Attached Files
      My ComputerSystem Spec
  2.    2 Weeks Ago #2
    Join Date : Apr 2014
    Space coast of Florida
    Posts : 5,343
    Windows 10 Pro X64 16299.19

    The zip file you uploaded is empty. Run dm_log_collector as described. Check the resulting zip file to make sure it's not empty before uploading.
      My ComputersSystem Spec
  3.    2 Weeks Ago #3
    Join Date : Sep 2015
    Sydney Oz
    Posts : 77
    Win Pro 10x64 1709 16299.19
    Thread Starter

    Hi,

    Not sure what happened then. That Error panel came up again when I clicked the diag prog.

    Hope this one is fine now.

    oz
    Blue screen at start-since up to 1703-KB4041676 won't load and more Attached Files
      My ComputerSystem Spec
  4.    2 Weeks Ago #4
    Join Date : Apr 2014
    Space coast of Florida
    Posts : 5,343
    Windows 10 Pro X64 16299.19

    That's better, thanks.

    Looks like a problem is with your video driver, atikmpag.sys for your ATI Radeon HD 4250.
    Code:
    BugCheck 116, {ffffe20252e3b010, fffff80ef5778efc, 0, d}
    *** ERROR: Symbol file could not be found.  Defaulted to export symbols for dxgmms1.sys - 
    Unable to load image \SystemRoot\system32\DRIVERS\atikmpag.sys, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for atikmpag.sys
    *** ERROR: Module load completed but symbols could not be loaded for atikmpag.sys
    *** WARNING: Unable to verify timestamp for win32k.sys
    *** ERROR: Module load completed but symbols could not be loaded for win32k.sys
    Probably caused by : atikmpag.sys ( atikmpag+8efc )

    Driver Description:
    ATI Video driver (remove the Catalyst Control Center and only install the Display Driver)
    Driver Update Site: http://support.amd.com/us/Pages/AMDSupportHub.aspx

    The one you have installed is dated: Tue Jan 13 11:20:43 2015

    ATI does not support the 4000 series on Windows 10 so there is not Windows 10 driver for it. All I can suggest is to do the following and see if it helps:

    Remove and install latest ATI drivers:

    I suggest completely uninstalling the ATI display drivers using Display Driver Uninstaller (DDU) from WagnardMobile (near bottom of page) then reinstall the current ATI driver you have. Install only the Display Driver. DO NOT install the Catalyst Control Center..

    See if that gets rid of the problem.

    If not, you could add a PCI-E video card and disable the on-board ATI chip, or you could use this as a good excuse to get a new computer
      My ComputersSystem Spec
  5.    2 Weeks Ago #5
    Join Date : Sep 2015
    Sydney Oz
    Posts : 77
    Win Pro 10x64 1709 16299.19
    Thread Starter

    Many thanks. I will try the uninstall the driver and see what happens.

    I do put in a Gigabiyte GT610 which I happend to have for another box before, but for some resaon when I cold booted I couldn't even get to the ASRock opening screen to enter bios and change it to this card. It was just black and stayed there.

    I will retry again too however also looking at the new box scenario too !

    Will post results and many thanks again.
      My ComputerSystem Spec
  6.    2 Weeks Ago #6
    Join Date : Apr 2017
    Posts : 8,670
    windows 10 professional version 1607 build 14393.969 64 bit

    The event logs displayed possible corruption or corruption on the drives.
    There were also hardware errors and retired blocks and paging errors.

    Open administrative command prompt and type or copy and paste:
    1) sfc /scannow
    2) dism /online /cleanup-image /restorehealth
    3) 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
    4) chkdsk /x /r (run this on every drive using the applicable drive letter)
    This may take many hours so plan to run overnight.
    To find the report in event.vwr use the information in this link and post the results into the thread:
    Read Chkdsk Log in Event Viewer in Windows 10 Performance Maintenance Tutorials

    5) Run HD Tune on each drive:
    http://www.hdtune.com/

    to check the health,
    scan for errors, no quick scan but full scan
    run a benchmark.


    It may take some time, but please take the time you need to perform it properly.
    When above is done please make screenshots of the following
    the health,
    the error scan,
    the benchmark incl. following
    transfer rate,
    access time,
    burst rate,
    cpu usage.
    Take Screenshot in Windows 10 General Tips Tutorials





    Code:
    Event[0]:  Log Name: System  Source: Microsoft-Windows-Ntfs  Date: 2017-07-09T17:03:12.605  Event ID: 140  Task: N/A  Level: Warning  Opcode: Info  Keyword: N/A  User: S-1-5-18  User Name: NT AUTHORITY\SYSTEM  Computer: WEBMAINx64  Description: The system failed to flush data to the transaction log. Corruption may occur in VolumeId: I:, DeviceName: \Device\HarddiskVolume2.(The I/O device reported an I/O error.)
    Code:
    Event[26]:  Log Name: System  Source: Microsoft-Windows-Ntfs  Date: 2017-07-09T17:03:31.655  Event ID: 140  Task: N/A  Level: Warning  Opcode: Info  Keyword: N/A  User: S-1-5-18  User Name: NT AUTHORITY\SYSTEM  Computer: WEBMAINx64  Description: The system failed to flush data to the transaction log. Corruption may occur in VolumeId: J:, DeviceName: \Device\HarddiskVolume3.
    Code:
    Event[69]:  Log Name: System  Source: Ntfs  Date: 2017-07-09T17:04:09.807  Event ID: 55  Task: N/A  Level: Error  Opcode: Info  Keyword: N/A  User: S-1-5-18  User Name: NT AUTHORITY\SYSTEM  Computer: WEBMAINx64  Description: A corruption was discovered in the file system structure on volume I:.The exact nature of the corruption is unknown.  The file system structures need to be scanned online.
    Code:
    Event[213]:  Log Name: System  Source: Ntfs  Date: 2017-07-09T17:06:24.168  Event ID: 55  Task: N/A  Level: Error  Opcode: Info  Keyword: N/A  User: S-1-5-18  User Name: NT AUTHORITY\SYSTEM  Computer: WEBMAINx64  Description: A corruption was discovered in the file system structure on volume H:.The exact nature of the corruption is unknown.  The file system structures need to be scanned online.
    Code:
    Event[308]:  Log Name: System  Source: Ntfs  Date: 2017-07-09T17:07:38.370  Event ID: 55  Task: N/A  Level: Error  Opcode: Info  Keyword: N/A  User: S-1-5-18  User Name: NT AUTHORITY\SYSTEM  Computer: WEBMAINx64  Description: A corruption was discovered in the file system structure on volume G:.The exact nature of the corruption is unknown.  The file system structures need to be scanned online.
    Code:
    Event[12428]:  Log Name: System
      Source: Microsoft-Windows-Ntfs
      Date: 2017-07-10T08:53:45.140
      Event ID: 98
      Task: N/A
      Level: Warning
      Opcode: Info
      Keyword: N/A
      User: S-1-5-18
      User Name: NT AUTHORITY\SYSTEM
      Computer: WEBMAINx64
      Description: 
    Volume J: (\Device\HarddiskVolume3) requires an Online Scan.  An Online Scan will automatically run as part of the next scheduled maintenance task.  Alternatively you may run "CHKDSK /SCAN" locally via the command line, or run "REPAIR-VOLUME <drive:> -SCAN" locally or remotely via PowerShell.
    Code:
    Event[15235]:  Log Name: System
      Source: Disk
      Date: 2017-07-10T16:59:53.929
      Event ID: 51
      Task: N/A
      Level: Warning
      Opcode: N/A
      Keyword: Classic
      User: N/A
      User Name: N/A
      Computer: WEBMAINx64
      Description: 
    An error was detected on device \Device\Harddisk3\DR7 during a paging operation.
    Code:
    Event[15331]:  Log Name: System
      Source: Disk
      Date: 2017-07-10T17:18:01.844
      Event ID: 51
      Task: N/A
      Level: Warning
      Opcode: N/A
      Keyword: Classic
      User: N/A
      User Name: N/A
      Computer: WEBMAINx64
      Description: 
    An error was detected on device \Device\Harddisk3\DR18 during a paging operation.
    Code:
    Event[17096]:  Log Name: System
      Source: Disk
      Date: 2017-07-17T07:25:53.299
      Event ID: 51
      Task: N/A
      Level: Warning
      Opcode: N/A
      Keyword: Classic
      User: N/A
      User Name: N/A
      Computer: WEBMAINx64
      Description: 
    An error was detected on device \Device\Harddisk5\DR7 during a paging operation.

    Code:
    Event[6917]:  Log Name: System
      Source: atapi
      Date: 2017-07-10T07:11:44.510
      Event ID: 11
      Task: N/A
      Level: Error
      Opcode: N/A
      Keyword: Classic
      User: N/A
      User Name: N/A
      Computer: WEBMAINx64
      Description: 
    The driver detected a controller error on \Device\Ide\IdePort0.
    Code:
    Event[77]:  Log Name: System
      Source: Disk
      Date: 2017-07-09T17:04:15.688
      Event ID: 153
      Task: N/A
      Level: Warning
      Opcode: N/A
      Keyword: Classic
      User: N/A
      User Name: N/A
      Computer: WEBMAINx64
      Description: 
    The IO operation at logical block address 0x7339dd30 for Disk 0 (PDO name: \Device\Ide\IdeDeviceP0T0L0-0) was retried.
    Code:
    Event[37567]:  Log Name: System
      Source: Disk
      Date: 2017-09-12T11:17:59.483
      Event ID: 154
      Task: N/A
      Level: Error
      Opcode: N/A
      Keyword: Classic
      User: N/A
      User Name: N/A
      Computer: WEBMAINx64
      Description: 
    The IO operation at logical block address 0x0 for Disk 6 (PDO name: \Device\000000ab) failed due to a hardware error.
    Code:
    Event[37554]:  Log Name: System
      Source: Disk
      Date: 2017-09-12T11:17:58.888
      Event ID: 154
      Task: N/A
      Level: Error
      Opcode: N/A
      Keyword: Classic
      User: N/A
      User Name: N/A
      Computer: WEBMAINx64
      Description: 
    The IO operation at logical block address 0x0 for Disk 6 (PDO name: \Device\000000ab) failed due to a hardware error.
    
    
    Event[37555]:
      Log Name: System
      Source: Disk
      Date: 2017-09-12T11:17:58.889
      Event ID: 154
      Task: N/A
      Level: Error
      Opcode: N/A
      Keyword: Classic
      User: N/A
      User Name: N/A
      Computer: WEBMAINx64
      Description: 
    The IO operation at logical block address 0x0 for Disk 6 (PDO name: \Device\000000ab) failed due to a hardware error.
    
    
    Event[37556]:
      Log Name: System
      Source: Disk
      Date: 2017-09-12T11:17:58.890
      Event ID: 154
      Task: N/A
      Level: Error
      Opcode: N/A
      Keyword: Classic
      User: N/A
      User Name: N/A
      Computer: WEBMAINx64
      Description: 
    The IO operation at logical block address 0x0 for Disk 6 (PDO name: \Device\000000ab) failed due to a hardware error.
    
    
    Event[37557]:
      Log Name: System
      Source: Disk
      Date: 2017-09-12T11:17:58.891
      Event ID: 154
      Task: N/A
      Level: Error
      Opcode: N/A
      Keyword: Classic
      User: N/A
      User Name: N/A
      Computer: WEBMAINx64
      Description: 
    The IO operation at logical block address 0x0 for Disk 6 (PDO name: \Device\000000ab) failed due to a hardware error.
    
    
    Event[37558]:
      Log Name: System
      Source: Disk
      Date: 2017-09-12T11:17:58.891
      Event ID: 154
      Task: N/A
      Level: Error
      Opcode: N/A
      Keyword: Classic
      User: N/A
      User Name: N/A
      Computer: WEBMAINx64
      Description: 
    The IO operation at logical block address 0x0 for Disk 6 (PDO name: \Device\000000ab) failed due to a hardware error.
    
    
    Event[37559]:
      Log Name: System
      Source: Disk
      Date: 2017-09-12T11:17:58.892
      Event ID: 154
      Task: N/A
      Level: Error
      Opcode: N/A
      Keyword: Classic
      User: N/A
      User Name: N/A
      Computer: WEBMAINx64
      Description: 
    The IO operation at logical block address 0x0 for Disk 6 (PDO name: \Device\000000ab) failed due to a hardware error.
    
    
    Event[37560]:
      Log Name: System
      Source: Disk
      Date: 2017-09-12T11:17:58.911
      Event ID: 154
      Task: N/A
      Level: Error
      Opcode: N/A
      Keyword: Classic
      User: N/A
      User Name: N/A
      Computer: WEBMAINx64
      Description: 
    The IO operation at logical block address 0x0 for Disk 6 (PDO name: \Device\000000ab) failed due to a hardware error.
    
    
    Event[37561]:
      Log Name: System
      Source: Disk
      Date: 2017-09-12T11:17:58.913
      Event ID: 154
      Task: N/A
      Level: Error
      Opcode: N/A
      Keyword: Classic
      User: N/A
      User Name: N/A
      Computer: WEBMAINx64
      Description: 
    The IO operation at logical block address 0x0 for Disk 6 (PDO name: \Device\000000ab) failed due to a hardware error.
    
    
    Event[37562]:
      Log Name: System
      Source: Disk
      Date: 2017-09-12T11:17:58.914
      Event ID: 154
      Task: N/A
      Level: Error
      Opcode: N/A
      Keyword: Classic
      User: N/A
      User Name: N/A
      Computer: WEBMAINx64
      Description: 
    The IO operation at logical block address 0x0 for Disk 6 (PDO name: \Device\000000ab) failed due to a hardware error.
    
    
    Event[37563]:
      Log Name: System
      Source: Disk
      Date: 2017-09-12T11:17:58.916
      Event ID: 154
      Task: N/A
      Level: Error
      Opcode: N/A
      Keyword: Classic
      User: N/A
      User Name: N/A
      Computer: WEBMAINx64
      Description: 
    The IO operation at logical block address 0x0 for Disk 6 (PDO name: \Device\000000ab) failed due to a hardware error.
    
    
    Event[37564]:
      Log Name: System
      Source: Disk
      Date: 2017-09-12T11:17:59.476
      Event ID: 154
      Task: N/A
      Level: Error
      Opcode: N/A
      Keyword: Classic
      User: N/A
      User Name: N/A
      Computer: WEBMAINx64
      Description: 
    The IO operation at logical block address 0x0 for Disk 6 (PDO name: \Device\000000ab) failed due to a hardware error.
    
    
    Event[37565]:
      Log Name: System
      Source: Disk
      Date: 2017-09-12T11:17:59.478
      Event ID: 154
      Task: N/A
      Level: Error
      Opcode: N/A
      Keyword: Classic
      User: N/A
      User Name: N/A
      Computer: WEBMAINx64
      Description: 
    The IO operation at logical block address 0x0 for Disk 6 (PDO name: \Device\000000ab) failed due to a hardware error.
    
    
    Event[37566]:
      Log Name: System
      Source: Disk
      Date: 2017-09-12T11:17:59.480
      Event ID: 154
      Task: N/A
      Level: Error
      Opcode: N/A
      Keyword: Classic
      User: N/A
      User Name: N/A
      Computer: WEBMAINx64
      Description: 
    The IO operation at logical block address 0x0 for Disk 6 (PDO name: \Device\000000ab) failed due to a hardware error.
    
    
    Event[37567]:
      Log Name: System
      Source: Disk
      Date: 2017-09-12T11:17:59.483
      Event ID: 154
      Task: N/A
      Level: Error
      Opcode: N/A
      Keyword: Classic
      User: N/A
      User Name: N/A
      Computer: WEBMAINx64
      Description: 
    The IO operation at logical block address 0x0 for Disk 6 (PDO name: \Device\000000ab) failed due to a hardware error.
    
    
    Event[37568]:
      Log Name: System
      Source: Disk
      Date: 2017-09-12T11:24:06.183
      Event ID: 154
      Task: N/A
      Level: Error
      Opcode: N/A
      Keyword: Classic
      User: N/A
      User Name: N/A
      Computer: WEBMAINx64
      Description: 
    The IO operation at logical block address 0x3f00c000 for Disk 6 (PDO name: \Device\000000ab) failed due to a hardware error.
    
    
    Event[37569]:
      Log Name: System
      Source: Disk
      Date: 2017-09-12T11:24:06.185
      Event ID: 154
      Task: N/A
      Level: Error
      Opcode: N/A
      Keyword: Classic
      User: N/A
      User Name: N/A
      Computer: WEBMAINx64
      Description: 
    The IO operation at logical block address 0x0 for Disk 6 (PDO name: \Device\000000ab) failed due to a hardware error.
      My ComputerSystem Spec
  7.    2 Weeks Ago #7
    Join Date : Sep 2015
    Sydney Oz
    Posts : 77
    Win Pro 10x64 1709 16299.19
    Thread Starter

    Many thanks .. Unfortunately got this in admin/cmd..

    Code:
    C:\WINDOWS\system32>sfc /scannow
    Beginning system scan.  This process will take some time.
    Beginning verification phase of system scan.
    Verification 17% complete.
    Windows Resource Protection could not perform the requested operation.
    C:\WINDOWS\system32>
    I then started Trustedinstaller and Windows Module Installer but got exactly the same result.
      My ComputerSystem Spec
  8.    2 Weeks Ago #8
    Join Date : Apr 2017
    Posts : 8,670
    windows 10 professional version 1607 build 14393.969 64 bit

    Using administrative command prompt run these dism commands:

    dism /online /cleanup-image /checkhealth
    dism /online /cleanup-image /scanhealth
    dism /online /cleanup-image /restorehealth

    Use step #3 in post #6 to copy and paste the results into the thread.
      My ComputerSystem Spec
  9.    2 Weeks Ago #9
    Join Date : Sep 2015
    Sydney Oz
    Posts : 77
    Win Pro 10x64 1709 16299.19
    Thread Starter

    Microsoft Windows [Version 10.0.15063]
    (c) 2017 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 17% complete.
    Windows Resource Protection could not perform the requested operation.

    C:\WINDOWS\system32>services.msc

    C:\WINDOWS\system32>sfc /scannow
    Beginning system scan. This process will take some time.
    Beginning verification phase of system scan.
    Verification 17% complete.
    Windows Resource Protection could not perform the requested operation.

    C:\WINDOWS\system32>net start trustedinstaller
    The Windows Modules Installer service is starting.
    The Windows Modules Installer service was started successfully.


    C:\WINDOWS\system32>sfc /scannow
    Beginning system scan. This process will take some time.
    Beginning verification phase of system scan.
    Verification 17% complete.
    Windows Resource Protection could not perform the requested operation.

    C:\WINDOWS\system32>findstr /c:"[SR]" %windir%\logs\cbs\cbs.log >sfcdetails.txt

    C:\WINDOWS\system32>dism /online /cleanup-image /checkhealth
    Deployment Image Servicing and Management tool
    Version: 10.0.15063.0
    Image Version: 10.0.15063.0

    The component store is repairable.
    The operation completed successfully.

    C:\WINDOWS\system32>dism /online /cleanup-image /scanhealth
    Deployment Image Servicing and Management tool
    Version: 10.0.15063.0
    Image Version: 10.0.15063.0
    [=== 6.1% ]
    Error: 1392
    The file or directory is corrupted and unreadable.
    The DISM log file can be found at C:\WINDOWS\Logs\DISM\dism.log

    C:\WINDOWS\system32>dism /online /cleanup-image /restorehealth
    Deployment Image Servicing and Management tool
    Version: 10.0.15063.0
    Image Version: 10.0.15063.0
    [== 5.1% ]
    Error: 1392
    The file or directory is corrupted and unreadable.
    The DISM log file can be found at C:\WINDOWS\Logs\DISM\dism.log

    C:\WINDOWS\system32>
      My ComputerSystem Spec
  10.    2 Weeks Ago #10
    Join Date : Apr 2017
    Posts : 8,670
    windows 10 professional version 1607 build 14393.969 64 bit

    Please perform an in place upgrade repair:
    Repair Install Windows 10 with an In-place Upgrade Installation Upgrade Tutorials

    1) Create a bootable windows 10 iso:
    Download Windows 10
    2) Insert the windows 10 iso into any USB port.
    3) Open file explorer
    4) Look for the drive with the windows 10 iso
    5) click on this drive and look for setup or setup.exe and launch it
    6) choose language, time, currency, and keyboard
    7) follow the text and images in this link to complete the in place upgrade repair:
    Repair Install Windows 10 with an In-place Upgrade Installation Upgrade Tutorials

    Make sure that you do not click install on the windows 10 iso as this is the method to perform a clean install.
    Instead look in the left lower corner and click on "repair your computer"
      My ComputerSystem Spec

 
Page 1 of 6 123 ... LastLast


Similar Threads
Thread Forum
Windows couldn't load correctly blue screen on startup
Almost every time I start my computer I get the "windows couldn't load properly" blue screen message. I have the option to repair, continue, or to restart. When i restart the computer loads up fine. The computer is a dell xps 15, which is brand...
General Support
The following boot-start or system-start driver(s) did not load: dam
So I frequently get the event viewer message "The following boot-start or system-start driver(s) did not load: dam" Well, DAM I say! What is dam, and does anyone care? By the way, in other Windows, I like to keep my desktop quiet and calm. I...
Performance & Maintenance
Blue screen on start, normal on restart-any solutions?
Hi, I recently installed Win10 on a new computer. Everything runs fine except for when I start the computer. When I start it "cold" it automatically goes to the blue screen/repair screen. However if I immediately restart the computer from the...
BSOD Crashes and Debugging
Solved Working Windows 10 suddenly won't load (four blue squares then reboot)
I've had some fun and games with Windows 10 so far (Solved Windows 10 upgrade - random freezes and PC becomes unresponsive - Windows 10 Forums), and this forum has helped me get back on my feet. Now something else seems to have gone wrong. I was...
General Support
Computer won't load past start up screen
Hello, I'm new here. Sorry for posing another thread but I couldn't find one similar enough to my question. Anyway, my laptop began moving incredibly slow last night, like the cursor would hardly move and it sounded like it was running extra hard. I...
General Support
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 18:01.
Find Us
Twitter Facebook Google+ Ten Forums iOS App Ten Forums Android App



Windows 10 Forums