Windows 10: Having 1 crash every time I start up just ONCE then not anymore daily

Discus and support Having 1 crash every time I start up just ONCE then not anymore daily in Windows 10 BSOD Crashes and Debugging to solve the problem; So the day I get home and the pc has been shut off for an entire day and I turn it on and it tells me which users I want to login with and then it... Discussion in 'Windows 10 BSOD Crashes and Debugging' started by Max Pen, May 30, 2017.

  1. Max Pen Win User

    Having 1 crash every time I start up just ONCE then not anymore daily


    So the day I get home and the pc has been shut off for an entire day and I turn it on and it tells me which users I want to login with and then it crashes. I restart and everything works normal again but don't want to get through this every day for the rest of my time I use this junk...


    I didn't have any bsod recently as you can see from the dump.... Just this month it seems

    Attachment 137519

    :)
     
    Max Pen, May 30, 2017
    #1

  2. Microsoft Jigsaw

    I cannot play the daily challenges anymore. Every time I try to start a challenge, an advert tries to load and after 5 to 10 seconds Jigsaw crashes. I did a reset of the store, checked time and zone, reinstalled Jigsaw, nothing helped. Any ideas??
     
    Math Gerards, May 30, 2017
    #2
  3. Boykin Win User
    Windows 10 File Explorer crash

    I have waited to report what was causing my crash because every time I thought I had it fixed and told someone, the problem would come back. It has been over a week since the last crash. It was crashing daily.

    My crash was caused by my eSATA external HD. I took the HD out of the enclosure and put it in a HD dock and I have not had anymore problems.
     
    Boykin, May 30, 2017
    #3
  4. zbook New Member

    Having 1 crash every time I start up just ONCE then not anymore daily

    BugCheck 50, {ffff80000fff0000, 0, ffff8880538cbcf1, 2}*** WARNING: Unable to verify timestamp for mbae64.sys*** ERROR: Module load completed but symbols could not be loaded for mbae64.sysCould not read faulting driver nameProbably caused by : mbae64.sys ( mbae64+759c )

    BugCheck 50, {ffff80002fff0000, 0, ffffaf8087e9dcf1, 2}*** WARNING: Unable to verify timestamp for mbae64.sys*** ERROR: Module load completed but symbols could not be loaded for mbae64.sysCould not read faulting driver nameProbably caused by : mbae64.sys ( mbae64+759c )


    BugCheck 50, {ffff80001fff0000, 0, ffffe081297a5cf1, 2}*** WARNING: Unable to verify timestamp for mbae64.sys*** ERROR: Module load completed but symbols could not be loaded for mbae64.sysCould not read faulting driver nameProbably caused by : mbae64.sys ( mbae64+759c )


    BugCheck 50, {ffff80001fff0000, 0, ffffde819a013cf1, 2}*** WARNING: Unable to verify timestamp for mbae64.sys*** ERROR: Module load completed but symbols could not be loaded for mbae64.sysCould not read faulting driver nameProbably caused by : mbae64.sys ( mbae64+759c )


    BugCheck 50, {ffff80000fff0000, 0, ffffe58087904cf1, 2}*** WARNING: Unable to verify timestamp for mbae64.sys*** ERROR: Module load completed but symbols could not be loaded for mbae64.sysCould not read faulting driver nameProbably caused by : mbae64.sys ( mbae64+759c )


    esprotectiondriver Malwarebytes Anti-Exploit \??\h:\program files (x86)\malwarebytes anti-exploit\mbae64.sys Kernel Driver Yes System Running OK Normal No Yes


    There were 5 bsod minidump files. All the debugging displayed mbae64.sys








    Event[11973]: Log Name: System Source: Microsoft-Windows-Ntfs Date: 2017-01-07T17:00:09.095 Event ID: 140 Task: N/A Level: Warning Opcode: Info Keyword: N/A User: S-1-5-18 User Name: NT AUTHORITY\SYSTEM Computer: Terra-PC Description: The system failed to flush data to the transaction log. Corruption may occur in VolumeId: D:, DeviceName: \Device\HarddiskVolume2.(The I/O device reported an I/O error.)


    Event[12014]: Log Name: System Source: Microsoft-Windows-Ntfs Date: 2017-01-07T17:17:19.123 Event ID: 140 Task: N/A Level: Warning Opcode: Info Keyword: N/A User: S-1-5-18 User Name: NT AUTHORITY\SYSTEM Computer: Terra-PC Description: The system failed to flush data to the transaction log. Corruption may occur in VolumeId: D:, DeviceName: \Device\HarddiskVolume2.(The I/O device reported an I/O error.)


    Event[12031]: Log Name: System Source: Microsoft-Windows-Ntfs Date: 2017-01-07T17:24:49.134 Event ID: 140 Task: N/A Level: Warning Opcode: Info Keyword: N/A User: S-1-5-18 User Name: NT AUTHORITY\SYSTEM Computer: Terra-PC Description: The system failed to flush data to the transaction log. Corruption may occur in VolumeId: D:, DeviceName: \Device\HarddiskVolume2.(The I/O device reported an I/O error.)


    Event[12077]: Log Name: System Source: Microsoft-Windows-Ntfs Date: 2017-01-07T17:45:19.156 Event ID: 140 Task: N/A Level: Warning Opcode: Info Keyword: N/A User: S-1-5-18 User Name: NT AUTHORITY\SYSTEM Computer: Terra-PC Description: The system failed to flush data to the transaction log. Corruption may occur in VolumeId: D:, DeviceName: \Device\HarddiskVolume2.(The I/O device reported an I/O error.)


    Event[12250]: Log Name: System Source: Microsoft-Windows-Ntfs Date: 2017-01-07T19:02:19.229 Event ID: 140 Task: N/A Level: Warning Opcode: Info Keyword: N/A User: S-1-5-18 User Name: NT AUTHORITY\SYSTEM Computer: Terra-PC Description: The system failed to flush data to the transaction log. Corruption may occur in VolumeId: D:, DeviceName: \Device\HarddiskVolume2.(The I/O device reported an I/O error.)


    Event[12303]: Log Name: System Source: Microsoft-Windows-Ntfs Date: 2017-01-07T19:26:29.243 Event ID: 140 Task: N/A Level: Warning Opcode: Info Keyword: N/A User: S-1-5-18 User Name: NT AUTHORITY\SYSTEM Computer: Terra-PC Description: The system failed to flush data to the transaction log. Corruption may occur in VolumeId: D:, DeviceName: \Device\HarddiskVolume2.(The I/O device reported an I/O error.)


    Event[12398]: Log Name: System Source: Microsoft-Windows-Ntfs Date: 2017-01-07T20:08:09.276 Event ID: 140 Task: N/A Level: Warning Opcode: Info Keyword: N/A User: S-1-5-18 User Name: NT AUTHORITY\SYSTEM Computer: Terra-PC Description: The system failed to flush data to the transaction log. Corruption may occur in VolumeId: D:, DeviceName: \Device\HarddiskVolume2.(The I/O device reported an I/O error.)


    Event[19808]: Log Name: System Source: Microsoft-Windows-Ntfs Date: 2017-02-01T16:13:39.899 Event ID: 140 Task: N/A Level: Warning Opcode: Info Keyword: N/A User: S-1-5-18 User Name: NT AUTHORITY\SYSTEM Computer: Terra-PC Description: The system failed to flush data to the transaction log. Corruption may occur in VolumeId: D:, DeviceName: \Device\HarddiskVolume2.(The I/O device reported an I/O error.)


    Event[27635]: Log Name: System Source: Microsoft-Windows-Kernel-General Date: 2017-03-09T21:44:24.322 Event ID: 5 Task: N/A Level: Error Opcode: Info Keyword: N/A User: S-1-5-18 User Name: NT AUTHORITY\SYSTEM Computer: Terra-PC Description: {Registry Hive Recovered} Registry hive (file): '\??\C:\Users\Slaver\AppData\Local\Microsoft\Windows\UsrClass.dat' was corrupted and it has been recovered. Some data might have been lost.


    Event[37573]: Log Name: System Source: Microsoft-Windows-Kernel-General Date: 2017-05-02T18:00:09.064 Event ID: 5 Task: N/A Level: Error Opcode: Info Keyword: N/A User: S-1-5-18 User Name: NT AUTHORITY\SYSTEM Computer: Terra-PC Description: {Registry Hive Recovered} Registry hive (file): '\??\C:\Users\Gamer\AppData\Local\Microsoft\Windows\UsrClass.dat' was corrupted and it has been recovered. Some data might have been lost.

    Event[40363]: Log Name: System Source: Microsoft-Windows-Kernel-General Date: 2017-05-15T12:57:58.698 Event ID: 5 Task: N/A Level: Error Opcode: Info Keyword: N/A User: S-1-5-18 User Name: NT AUTHORITY\SYSTEM Computer: Terra-PC Description: {Registry Hive Recovered} Registry hive (file): '\??\C:\Users\Gamer\AppData\Local\Microsoft\Windows\UsrClass.dat' was corrupted and it has been recovered. Some data might have been lost.


    Event[21447]: Log Name: System Source: Application Popup Date: 2017-02-08T18:27:39.785 Event ID: 26 Task: N/A Level: Information Opcode: Info Keyword: N/A User: S-1-5-18 User Name: NT AUTHORITY\SYSTEM Computer: Terra-PC Description: Application popup: WhoCrashedEx.exe - Ordinal Not Found : The ordinal 1002 could not be located in the dynamic link library C:\WINDOWS\SYSTEM32\dbgeng.dll.


    Service Name: Torch Crash HandlerService File Name: C:\Users\Gamer\AppData\Local\Torch\Update\TorchCrashHandler.exeService Type: user mode serviceService Start Type: auto startService Account: LocalSystem


    Event[26412]: Log Name: System Source: Service Control Manager Date: 2017-03-04T18:26:12.531 Event ID: 7030 Task: N/A Level: Error Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: Terra-PC Description: The Torch Crash Handler service is marked as an interactive service. However, the system is configured to not allow interactive services. This service may not function properly.

    Event[28572]: Log Name: System Source: Microsoft-Windows-NDIS Date: 2017-03-16T08:50:27.829 Event ID: 10400 Task: N/A Level: Warning Opcode: Info Keyword: N/A User: N/A User Name: N/A Computer: Terra-PC Description: The network interface "Intel(R) 82579V Gigabit Network Connection" has begun resetting. There will be a momentary disruption in network connectivity while the hardware resets.Reason: The network driver detected that its hardware has stopped responding to commands.


    Event[28587]: Log Name: System Source: Microsoft-Windows-NDIS Date: 2017-03-16T08:56:43.188 Event ID: 10400 Task: N/A Level: Warning Opcode: Info Keyword: N/A User: N/A User Name: N/A Computer: Terra-PC Description: The network interface "Intel(R) 82579V Gigabit Network Connection" has begun resetting. There will be a momentary disruption in network connectivity while the hardware resets.Reason: The network driver detected that its hardware has stopped responding to commands.


    Event[28596]: Log Name: System Source: Microsoft-Windows-NDIS Date: 2017-03-16T09:07:19.570 Event ID: 10400 Task: N/A Level: Warning Opcode: Info Keyword: N/A User: N/A User Name: N/A Computer: Terra-PC Description: The network interface "Intel(R) 82579V Gigabit Network Connection" has begun resetting. There will be a momentary disruption in network connectivity while the hardware resets.Reason: The network driver detected that its hardware has stopped responding to commands.


    Event[27635]: Log Name: System Source: Microsoft-Windows-Kernel-General Date: 2017-03-09T21:44:24.322 Event ID: 5 Task: N/A Level: Error Opcode: Info Keyword: N/A User: S-1-5-18 User Name: NT AUTHORITY\SYSTEM Computer: Terra-PC Description: {Registry Hive Recovered} Registry hive (file): '\??\C:\Users\Slaver\AppData\Local\Microsoft\Windows\UsrClass.dat' was corrupted and it has been recovered. Some data might have been lost.

    Your original HOSTS file was infected and it was replaced # by this file containing only clean default entries. # The original HOSTS file may be restored from the product's# quarantine feature.



    There were 5 minidump files collected and analyzed with Microsoft (R) Windows Debugger Version 10.0.15063.137 AMD64

    Perform the following steps:
    Open administrative command prompt and type or copy:

    1) sfc /scannow
    2) dism /online /cleanup-image /restorehealth
    3) chkdsk /scan

    Right click on the top of the administrative command prompt box > left click edit > left click select all > right click the top of the box again > left click edit > left click copy > paste into the forum

    4) Uninstall malwarebytes (The logs display Avast as your antivirus)
    5) reinstall malwarebytes and run a scan
    6) run Avast on all drives in full mode
    7) Check windows updates (computer current Version 10.0.14393 Build 14393; available Version 10.0.15063 Build 15063
    8) run chkdsk /x /f /r (this may take many hours so run overnight)
    9) type services.msc in the left lower corner search and scroll to find TorchCrashHandler, then click properties, under path to executable staartup type change to disable, apply, ok.
    10) reboot after the change to torchcrashhandler

    What is TorchCrashHandler.exe? - Helpdesk- Torch Media

    10) if the above steps do not fix the hangs/crashes place your computer in clean boot and monitor the performance:

    How to perform a Clean Boot in Windows 10 - TechNet Articles - United States (English) - TechNet Wiki

    https://support.microsoft.com/en-us/...oot-in-windows

    11) There were problems in the event viewer with Intel networking and you likely have fixed this long ago. In case there are any new problems you can often troubleshoot via the control panel windows troubleshooting or Microsoft easy fix: https://support.microsoft.com/en-us/...-fix-solutions
     
    zbook, May 31, 2017
    #4
Thema:

Having 1 crash every time I start up just ONCE then not anymore daily

Loading...
  1. Having 1 crash every time I start up just ONCE then not anymore daily - Similar Threads - Having crash every

  2. REALLY TIRED OF HAVING TO CLICK THE SIGN iN BUTON EVERY TIME I START MY COMPUTER BACK UP

    in AntiVirus, Firewalls and System Security
    REALLY TIRED OF HAVING TO CLICK THE SIGN iN BUTON EVERY TIME I START MY COMPUTER BACK UP: What exactly must I do to eliminate having to press the Sign In button every time my computer goes to sleep ? It happens all day long and I am really so tired of it. I have tried doing the thing where you tick the box saying that you dont have to put in a password but that...
  3. Every time I start up the computer I recieve an alert card cage fan failure and have to...

    in Windows 10 BSOD Crashes and Debugging
    Every time I start up the computer I recieve an alert card cage fan failure and have to...: Dell Precision T3500 running Windows 10 Version 10.0.17763 Build 17763 I've had this problem on and off for about a year. I have not replaced the fan, it simply runs at full speed, I assume because the operating system does not detect the hardware and therefore defaults...
  4. Strange blue screen every time I start up PC

    in Windows 10 Customization
    Strange blue screen every time I start up PC: Every time I start windows up I am faced with the blue screen in the picture provided. All I have to do is right click then choose personalise and it goes back to normal but I want to know what is causing this. I have attached a screenshot of my general spec too. Any help...
  5. BSOD crash every time I watch Youtube.

    in Windows 10 BSOD Crashes and Debugging
    BSOD crash every time I watch Youtube.: Every time I load a video on Youtube it will give me an BSOD Crash. It was at first only for Youtube but now it can happen for random websites. The last error code it gave me was: PAGE FAULT IN NONPAGED AREA. Twitch however is not affected. Has had about 5 or so BSOD crashes...
  6. I have to type " explorer.exe " every time i start windows

    in Windows 10 BSOD Crashes and Debugging
    I have to type " explorer.exe " every time i start windows: When i start my windows my screen is black and only thing showing is CMD windows with " C:/Windows/System32/ "written on it and i have to type " explorer.exe " every time for windows to work properly. This did not work for me:...
  7. Why do I have VMMS Checkpoint Errors at every start-up?

    in Windows 10 Virtualization
    Why do I have VMMS Checkpoint Errors at every start-up?: On every startup I see 7 errors associated with the 7 checkpoints I have for the various VMs installed on my PC. I have shown one of the errors below. These happen even though I do not start any of the VMs during the boot process. I can open and run all my VMs normally so...
  8. Crashing every time after startup

    in Windows 10 BSOD Crashes and Debugging
    Crashing every time after startup: Hello Tenforums. Every time I start my computer its crashes 10 minutes afterwards, and it also did it back when i was using windows 7. I have uploaded my debug zip file to this thread. Attachment 30608 - Morten Abrahamsen 15444
  9. BSOD every time I start a game (not overheating)

    in Windows 10 BSOD Crashes and Debugging
    BSOD every time I start a game (not overheating): Attachment 61603 I hope this is the right file, I cannot find anything else. Please help. I have tried everything. 39165
  10. BSOD on start up every time - CRITICAL_PROCESS_DIED

    in Windows 10 BSOD Crashes and Debugging
    BSOD on start up every time - CRITICAL_PROCESS_DIED: Every time I startup my computer, I get a blue screen of death with the message "CRITICAL_PROCESS_DIED". This happens after the windows 10 logo appears, but before I reach the login screen or desktop. The computer then restarts automatically and attempts an "Automatic...

Users found this page by searching for:

  1. application popup: whocrashedex.exe - ordinal not found : the ordinal 1003 could not be located in the dynamic link library c:\windows\system32\dbgeng.dll.