Windows 10: BSOD, many errors, sending data

Discus and support BSOD, many errors, sending data in Windows 10 BSOD Crashes and Debugging to solve the problem; Hi there Not much to say, sudden crashes with BSOD and reboot. (It's probably relevant to mention that before this bsod's i had a different thing... Discussion in 'Windows 10 BSOD Crashes and Debugging' started by marcosdipaolo, Feb 26, 2017.

  1. BSOD, many errors, sending data


    Hi there
    Not much to say, sudden crashes with BSOD and reboot.

    (It's probably relevant to mention that before this bsod's i had a different thing that stopped happening due to something i might have changed, what i'm talking about is like a "hang" of the system but then it was coming back like 5 minutes later, no rebooting or resetting needed.)

    here I send the data of the dm log collector.

    I warn you that the programs never reaches the end of the process, don't know why but had to create the zip myself. I waited for it about 5 to 10 min every time, it gets stuck at "generating msinfo report".
    In addition I added to the zip file 3 xml files with the Event information about the three crashes corresponding to the 3 dump files contained in the zip.

    :)
     
    marcosdipaolo, Feb 26, 2017
    #1

  2. New 2520 multiple lockups BSD and reboot

    more errors BSOD

    DPC_WATCHDOG_VIOLATION



    going to send it back
     
    ramseyjack---01, Feb 26, 2017
    #2
  3. SgtCiege Win User
    Win10 BSOD with many (driver) errors

    Ok I got a hold of the minidump and msinfo files
    here
     
    SgtCiege, Feb 26, 2017
    #3
  4. Ztruker Win User

    BSOD, many errors, sending data

    Missing a lot of files from the zip, bummer.

    Please enter the following in a Command Prompt window:

    licensingdiag.exe -report "Genuine.txt"
    zip Genuine.txt and upload please.
    Delete Genuine.txt if you no longer want it.
    Delete the files shown in the line after what you typed: Diagnostics file created at C:\Users\?????????????????????????

    The latest dump indicates a problem with atikmpag.sys.
    Code: BugCheck 1000007E, {ffffffffc0000005, fffff807d850b745, ffff9b81af5f5658, ffff9b81af5f4e80} Probably caused by : atikmpag.sys ( atikmpag+b745 )[/quote] Driver Description: ATI Video driver (remove the Catalyst Control Center and only install the Display Driver)

    Driver Update Site: Support & Drivers
    Get from OEM for laptops

    The driver you have is fairly old: Driver Date/Size: 02/08/2015 09:00:00 p.m., 1466744 bytes

    There is a much newer version on the AMD site: Radeon Software Crimson Edition ReLive Graphics Driver Installer for Windows 10 64-Bi

    Attachment 123050

    I suggest completely uninstalling the AMD display drivers using Display Driver Uninstaller (DDU) from WagnardMobile (near bottom of page) then get the latest driver from the link above.

    Then do a custom install of only the graphics driver, leave out the Catalyst Control Center.

    See if that gets rid of the problem.
     
    Ztruker, Feb 27, 2017
    #4
  5. Hi Ztruker!
    well, I tried to do the "Genuine.txt" but it didn't create any txt file, it created a cab file in C:\Users\MyUser\AppData\Local\Temp which i cannot upload since it's not a supported file type.
    The driver you are pointing in your screenshot doesn't correspond to my model, which is ATI Radeon HD 5770, a legacy product. This is the page where the driver is:
    Attachment 123061

    Anyways, I uninstalled all AMD drivers (the AMD uninstaller was enough to leave me completely driverless) and use the AMD auto-installer, which installed the drivers i just showed you at the images, same drivers as before I think.

    Regarding the genuine.txt i think I need some extra help because it's generating something else, I also wonder why the DM Log Collector isn't working properly.
     
    marcosdipaolo, Feb 27, 2017
    #5
  6. Ztruker Win User
    The driver page I pointed to is the latest Crimson driver. Should work but lets see how things are for now.

    Code: licensingdiag.exe -report "Genuine.txt" zip Genuine.txt and upload please. Delete Genuine.txt if you no longer want it. Delete the files shown in the line after what you typed: Diagnostics file created at C:\Users\?????????????????????????[/quote] Try running the above from a Elevated Command Prompt (Windows key + X, Command Prompt (Admin)).
     
    Ztruker, Feb 27, 2017
    #6
  7. Try running the above from a Elevated Command Prompt (Windows key + X, Command Prompt (Admin)).[/quote] I did with both, elevated and non elevated. Same result. What I'm doing now is to put the cab file into a zip and uploading it with this post.
    As long as i understand latest AMD driver won't support an HD5770, if you run the driver wizard you end up installing v.15.7.1, there is a beta as well as you can see in the picture.

    I'll report if I have a new crash.

    thanks a lot!!
     
    marcosdipaolo, Feb 27, 2017
    #7
  8. BSOD, many errors, sending data

    Here I am again sending new bug data.
    This time DM log collector got to finish but still couldn't create the zip file. Anyways I guess this time more data is on the zip than before. That is from yesterday and I attach the zip together with this event viewer data:

    Code: - <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"> - <System> <Provider Name="Microsoft-Windows-Kernel-Power" Guid="{331C3B3A-2005-44C2-AC5E-77220C37D6B4}" /> <EventID>41</EventID> <Version>4</Version> <Level>1</Level> <Task>63</Task> <Opcode>0</Opcode> <Keywords>0x8000400000000002</Keywords> <TimeCreated SystemTime="2017-03-01T17:36:38.660115000Z" /> <EventRecordID>10891</EventRecordID> <Correlation /> <Execution ProcessID="4" ThreadID="8" /> <Channel>System</Channel> <Computer>Marcos-PC</Computer> <Security UserID="S-1-5-18" /> </System> - <EventData> <Data Name="BugcheckCode">299</Data> <Data Name="BugcheckParameter1">0xffffffffc00002c4</Data> <Data Name="BugcheckParameter2">0x3ba</Data> <Data Name="BugcheckParameter3">0x58d5b20</Data> <Data Name="BugcheckParameter4">0xffffdb0103b3c000</Data> <Data Name="SleepInProgress">1</Data> <Data Name="PowerButtonTimestamp">0</Data> <Data Name="BootAppStatus">0</Data> <Data Name="Checkpoint">0</Data> <Data Name="ConnectedStandbyInProgress">false</Data> <Data Name="SystemSleepTransitionsToOn">1</Data> <Data Name="CsEntryScenarioInstanceId">0</Data> </EventData> </Event>[/quote]
    I want to mention that today I had again this strange behavior of the computer hanging and coming back after a while, this time was like 10 min at least. Here the Event Viewer info:
    Code: - <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"> - <System> <Provider Name="Microsoft-Windows-DistributedCOM" Guid="{1B562E86-B7AA-4131-BADC-B6F3A001407E}" EventSourceName="DCOM" /> <EventID Qualifiers="0">10010</EventID> <Version>0</Version> <Level>2</Level> <Task>0</Task> <Opcode>0</Opcode> <Keywords>0x8080000000000000</Keywords> <TimeCreated SystemTime="2017-03-02T18:18:29.060368600Z" /> <EventRecordID>11024</EventRecordID> <Correlation /> <Execution ProcessID="964" ThreadID="6656" /> <Channel>System</Channel> <Computer>Marcos-PC</Computer> <Security UserID="S-1-5-21-2019790605-585455450-2503125053-1000" /> </System> - <EventData> <Data Name="param1">App.AppXwdz8g2fxr36xz0tdtagygnvemf85s7gg.mca</Data> </EventData> </Event>[/quote]
    Here the Event viewer details of all critical errors registered since last year:
    Code: Log Name: System Source: Microsoft-Windows-Kernel-Power Date: 23/02/2017 10:32:55 p.m. Event ID: 41 Task Category: (63) Level: Critical Keywords: (70368744177664),(2) User: SYSTEM Computer: Marcos-PC Description: The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly. Event Xml: <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"> <System> <Provider Name="Microsoft-Windows-Kernel-Power" Guid="{331C3B3A-2005-44C2-AC5E-77220C37D6B4}" /> <EventID>41</EventID> <Version>4</Version> <Level>1</Level> <Task>63</Task> <Opcode>0</Opcode> <Keywords>0x8000400000000002</Keywords> <TimeCreated SystemTime="2017-02-24T01:32:55.314037000Z" /> <EventRecordID>9864</EventRecordID> <Correlation /> <Execution ProcessID="4" ThreadID="8" /> <Channel>System</Channel> <Computer>Marcos-PC</Computer> <Security UserID="S-1-5-18" /> </System> <EventData> <Data Name="BugcheckCode">59</Data> <Data Name="BugcheckParameter1">0xc0000005</Data> <Data Name="BugcheckParameter2">0xfffff802a4eef789</Data> <Data Name="BugcheckParameter3">0xffffdb8139245f50</Data> <Data Name="BugcheckParameter4">0x0</Data> <Data Name="SleepInProgress">0</Data> <Data Name="PowerButtonTimestamp">0</Data> <Data Name="BootAppStatus">0</Data> <Data Name="Checkpoint">0</Data> <Data Name="ConnectedStandbyInProgress">false</Data> <Data Name="SystemSleepTransitionsToOn">3</Data> <Data Name="CsEntryScenarioInstanceId">0</Data> </EventData> </Event> Log Name: System Source: Microsoft-Windows-Kernel-Power Date: 31/12/2016 07:44:12 p.m. Event ID: 41 Task Category: (63) Level: Critical Keywords: (70368744177664),(2) User: SYSTEM Computer: Marcos-PC Description: The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly. Event Xml: <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"> <System> <Provider Name="Microsoft-Windows-Kernel-Power" Guid="{331C3B3A-2005-44C2-AC5E-77220C37D6B4}" /> <EventID>41</EventID> <Version>4</Version> <Level>1</Level> <Task>63</Task> <Opcode>0</Opcode> <Keywords>0x8000400000000002</Keywords> <TimeCreated SystemTime="2016-12-31T22:44:12.603472000Z" /> <EventRecordID>5372</EventRecordID> <Correlation /> <Execution ProcessID="4" ThreadID="8" /> <Channel>System</Channel> <Computer>Marcos-PC</Computer> <Security UserID="S-1-5-18" /> </System> <EventData> <Data Name="BugcheckCode">268435583</Data> <Data Name="BugcheckParameter1">0x8</Data> <Data Name="BugcheckParameter2">0xffff8401cf04ba30</Data> <Data Name="BugcheckParameter3">0x7bff8401d6786e60</Data> <Data Name="BugcheckParameter4">0xfffff80347557abf</Data> <Data Name="SleepInProgress">0</Data> <Data Name="PowerButtonTimestamp">0</Data> <Data Name="BootAppStatus">0</Data> <Data Name="Checkpoint">0</Data> <Data Name="ConnectedStandbyInProgress">false</Data> <Data Name="SystemSleepTransitionsToOn">0</Data> <Data Name="CsEntryScenarioInstanceId">0</Data> </EventData> </Event> Log Name: System Source: Microsoft-Windows-Kernel-Power Date: 30/11/2016 04:55:42 p.m. Event ID: 41 Task Category: (63) Level: Critical Keywords: (70368744177664),(2) User: SYSTEM Computer: Marcos-PC Description: The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly. Event Xml: <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"> <System> <Provider Name="Microsoft-Windows-Kernel-Power" Guid="{331C3B3A-2005-44C2-AC5E-77220C37D6B4}" /> <EventID>41</EventID> <Version>4</Version> <Level>1</Level> <Task>63</Task> <Opcode>0</Opcode> <Keywords>0x8000400000000002</Keywords> <TimeCreated SystemTime="2016-11-30T19:55:42.540473300Z" /> <EventRecordID>3584</EventRecordID> <Correlation /> <Execution ProcessID="4" ThreadID="8" /> <Channel>System</Channel> <Computer>Marcos-PC</Computer> <Security UserID="S-1-5-18" /> </System> <EventData> <Data Name="BugcheckCode">268435583</Data> <Data Name="BugcheckParameter1">0x8</Data> <Data Name="BugcheckParameter2">0xffffa4802b0c1a30</Data> <Data Name="BugcheckParameter3">0x7affa480353e29b0</Data> <Data Name="BugcheckParameter4">0xfffff8029edd38df</Data> <Data Name="SleepInProgress">0</Data> <Data Name="PowerButtonTimestamp">0</Data> <Data Name="BootAppStatus">0</Data> <Data Name="Checkpoint">0</Data> <Data Name="ConnectedStandbyInProgress">false</Data> <Data Name="SystemSleepTransitionsToOn">0</Data> <Data Name="CsEntryScenarioInstanceId">0</Data> </EventData> </Event> Log Name: System Source: Microsoft-Windows-Kernel-Power Date: 29/12/2016 03:39:53 p.m. Event ID: 41 Task Category: (63) Level: Critical Keywords: (70368744177664),(2) User: SYSTEM Computer: Marcos-PC Description: The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly. Event Xml: <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"> <System> <Provider Name="Microsoft-Windows-Kernel-Power" Guid="{331C3B3A-2005-44C2-AC5E-77220C37D6B4}" /> <EventID>41</EventID> <Version>4</Version> <Level>1</Level> <Task>63</Task> <Opcode>0</Opcode> <Keywords>0x8000400000000002</Keywords> <TimeCreated SystemTime="2016-12-29T18:39:53.930988600Z" /> <EventRecordID>5171</EventRecordID> <Correlation /> <Execution ProcessID="4" ThreadID="8" /> <Channel>System</Channel> <Computer>Marcos-PC</Computer> <Security UserID="S-1-5-18" /> </System> <EventData> <Data Name="BugcheckCode">268435583</Data> <Data Name="BugcheckParameter1">0x8</Data> <Data Name="BugcheckParameter2">0xffffa6015f3f7a30</Data> <Data Name="BugcheckParameter3">0xfdffa601611fd560</Data> <Data Name="BugcheckParameter4">0xfffff80115fceabf</Data> <Data Name="SleepInProgress">0</Data> <Data Name="PowerButtonTimestamp">0</Data> <Data Name="BootAppStatus">0</Data> <Data Name="Checkpoint">0</Data> <Data Name="ConnectedStandbyInProgress">false</Data> <Data Name="SystemSleepTransitionsToOn">7</Data> <Data Name="CsEntryScenarioInstanceId">0</Data> </EventData> </Event> Log Name: System Source: Microsoft-Windows-Kernel-Power Date: 01/01/2017 09:57:49 p.m. Event ID: 41 Task Category: (63) Level: Critical Keywords: (70368744177664),(2) User: SYSTEM Computer: Marcos-PC Description: The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly. Event Xml: <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"> <System> <Provider Name="Microsoft-Windows-Kernel-Power" Guid="{331C3B3A-2005-44C2-AC5E-77220C37D6B4}" /> <EventID>41</EventID> <Version>4</Version> <Level>1</Level> <Task>63</Task> <Opcode>0</Opcode> <Keywords>0x8000400000000002</Keywords> <TimeCreated SystemTime="2017-01-02T00:57:49.226597100Z" /> <EventRecordID>5448</EventRecordID> <Correlation /> <Execution ProcessID="4" ThreadID="8" /> <Channel>System</Channel> <Computer>Marcos-PC</Computer> <Security UserID="S-1-5-18" /> </System> <EventData> <Data Name="BugcheckCode">268435582</Data> <Data Name="BugcheckParameter1">0xffffffffc0000005</Data> <Data Name="BugcheckParameter2">0xfffff803f332a300</Data> <Data Name="BugcheckParameter3">0xffffd9000ad06568</Data> <Data Name="BugcheckParameter4">0xffffd9000ad05d90</Data> <Data Name="SleepInProgress">0</Data> <Data Name="PowerButtonTimestamp">0</Data> <Data Name="BootAppStatus">0</Data> <Data Name="Checkpoint">0</Data> <Data Name="ConnectedStandbyInProgress">false</Data> <Data Name="SystemSleepTransitionsToOn">1</Data> <Data Name="CsEntryScenarioInstanceId">0</Data> </EventData> </Event> Log Name: System Source: Microsoft-Windows-Kernel-Power Date: 12/01/2017 09:30:09 p.m. Event ID: 41 Task Category: (63) Level: Critical Keywords: (70368744177664),(2) User: SYSTEM Computer: Marcos-PC Description: The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly. Event Xml: <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"> <System> <Provider Name="Microsoft-Windows-Kernel-Power" Guid="{331C3B3A-2005-44C2-AC5E-77220C37D6B4}" /> <EventID>41</EventID> <Version>4</Version> <Level>1</Level> <Task>63</Task> <Opcode>0</Opcode> <Keywords>0x8000400000000002</Keywords> <TimeCreated SystemTime="2017-01-13T00:30:09.176735900Z" /> <EventRecordID>7144</EventRecordID> <Correlation /> <Execution ProcessID="4" ThreadID="8" /> <Channel>System</Channel> <Computer>Marcos-PC</Computer> <Security UserID="S-1-5-18" /> </System> <EventData> <Data Name="BugcheckCode">0</Data> <Data Name="BugcheckParameter1">0x0</Data> <Data Name="BugcheckParameter2">0x0</Data> <Data Name="BugcheckParameter3">0x0</Data> <Data Name="BugcheckParameter4">0x0</Data> <Data Name="SleepInProgress">0</Data> <Data Name="PowerButtonTimestamp">0</Data> <Data Name="BootAppStatus">0</Data> <Data Name="Checkpoint">0</Data> <Data Name="ConnectedStandbyInProgress">false</Data> <Data Name="SystemSleepTransitionsToOn">0</Data> <Data Name="CsEntryScenarioInstanceId">0</Data> </EventData> </Event> Log Name: System Source: Microsoft-Windows-Kernel-Power Date: 06/01/2017 07:00:01 p.m. Event ID: 41 Task Category: (63) Level: Critical Keywords: (70368744177664),(2) User: SYSTEM Computer: Marcos-PC Description: The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly. Event Xml: <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"> <System> <Provider Name="Microsoft-Windows-Kernel-Power" Guid="{331C3B3A-2005-44C2-AC5E-77220C37D6B4}" /> <EventID>41</EventID> <Version>4</Version> <Level>1</Level> <Task>63</Task> <Opcode>0</Opcode> <Keywords>0x8000400000000002</Keywords> <TimeCreated SystemTime="2017-01-06T22:00:01.620408700Z" /> <EventRecordID>6261</EventRecordID> <Correlation /> <Execution ProcessID="4" ThreadID="8" /> <Channel>System</Channel> <Computer>Marcos-PC</Computer> <Security UserID="S-1-5-18" /> </System> <EventData> <Data Name="BugcheckCode">160</Data> <Data Name="BugcheckParameter1">0x10e</Data> <Data Name="BugcheckParameter2">0xa</Data> <Data Name="BugcheckParameter3">0x8d7b</Data> <Data Name="BugcheckParameter4">0x55</Data> <Data Name="SleepInProgress">6</Data> <Data Name="PowerButtonTimestamp">0</Data> <Data Name="BootAppStatus">3221225473</Data> <Data Name="Checkpoint">0</Data> <Data Name="ConnectedStandbyInProgress">false</Data> <Data Name="SystemSleepTransitionsToOn">1</Data> <Data Name="CsEntryScenarioInstanceId">0</Data> </EventData> </Event> Log Name: System Source: Microsoft-Windows-Kernel-Power Date: 24/12/2016 06:01:44 p.m. Event ID: 41 Task Category: (63) Level: Critical Keywords: (70368744177664),(2) User: SYSTEM Computer: Marcos-PC Description: The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly. Event Xml: <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"> <System> <Provider Name="Microsoft-Windows-Kernel-Power" Guid="{331C3B3A-2005-44C2-AC5E-77220C37D6B4}" /> <EventID>41</EventID> <Version>4</Version> <Level>1</Level> <Task>63</Task> <Opcode>0</Opcode> <Keywords>0x8000400000000002</Keywords> <TimeCreated SystemTime="2016-12-24T21:01:44.491523500Z" /> <EventRecordID>4744</EventRecordID> <Correlation /> <Execution ProcessID="4" ThreadID="8" /> <Channel>System</Channel> <Computer>Marcos-PC</Computer> <Security UserID="S-1-5-18" /> </System> <EventData> <Data Name="BugcheckCode">268435583</Data> <Data Name="BugcheckParameter1">0x8</Data> <Data Name="BugcheckParameter2">0xffffe7818faa4a30</Data> <Data Name="BugcheckParameter3">0xfbffe78194a600b0</Data> <Data Name="BugcheckParameter4">0xfffff8018456babf</Data> <Data Name="SleepInProgress">0</Data> <Data Name="PowerButtonTimestamp">0</Data> <Data Name="BootAppStatus">0</Data> <Data Name="Checkpoint">0</Data> <Data Name="ConnectedStandbyInProgress">false</Data> <Data Name="SystemSleepTransitionsToOn">13</Data> <Data Name="CsEntryScenarioInstanceId">0</Data> </EventData> </Event> Log Name: System Source: Microsoft-Windows-Kernel-Power Date: 24/01/2017 06:51:14 p.m. Event ID: 41 Task Category: (63) Level: Critical Keywords: (70368744177664),(2) User: SYSTEM Computer: Marcos-PC Description: The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly. Event Xml: <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"> <System> <Provider Name="Microsoft-Windows-Kernel-Power" Guid="{331C3B3A-2005-44C2-AC5E-77220C37D6B4}" /> <EventID>41</EventID> <Version>4</Version> <Level>1</Level> <Task>63</Task> <Opcode>0</Opcode> <Keywords>0x8000400000000002</Keywords> <TimeCreated SystemTime="2017-01-24T21:51:14.559628800Z" /> <EventRecordID>7669</EventRecordID> <Correlation /> <Execution ProcessID="4" ThreadID="8" /> <Channel>System</Channel> <Computer>Marcos-PC</Computer> <Security UserID="S-1-5-18" /> </System> <EventData> <Data Name="BugcheckCode">10</Data> <Data Name="BugcheckParameter1">0xffff85c2c0000000</Data> <Data Name="BugcheckParameter2">0x2</Data> <Data Name="BugcheckParameter3">0x0</Data> <Data Name="BugcheckParameter4">0xfffff8037d680ce4</Data> <Data Name="SleepInProgress">4</Data> <Data Name="PowerButtonTimestamp">0</Data> <Data Name="BootAppStatus">3221225473</Data> <Data Name="Checkpoint">0</Data> <Data Name="ConnectedStandbyInProgress">false</Data> <Data Name="SystemSleepTransitionsToOn">27</Data> <Data Name="CsEntryScenarioInstanceId">0</Data> </EventData> </Event> Log Name: System Source: Microsoft-Windows-Kernel-Power Date: 27/02/2017 11:14:09 p.m. Event ID: 41 Task Category: (63) Level: Critical Keywords: (70368744177664),(2) User: SYSTEM Computer: Marcos-PC Description: The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly. Event Xml: <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"> <System> <Provider Name="Microsoft-Windows-Kernel-Power" Guid="{331C3B3A-2005-44C2-AC5E-77220C37D6B4}" /> <EventID>41</EventID> <Version>4</Version> <Level>1</Level> <Task>63</Task> <Opcode>0</Opcode> <Keywords>0x8000400000000002</Keywords> <TimeCreated SystemTime="2017-02-28T02:14:09.885867000Z" /> <EventRecordID>10464</EventRecordID> <Correlation /> <Execution ProcessID="4" ThreadID="8" /> <Channel>System</Channel> <Computer>Marcos-PC</Computer> <Security UserID="S-1-5-18" /> </System> <EventData> <Data Name="BugcheckCode">30</Data> <Data Name="BugcheckParameter1">0xffffffffc0000005</Data> <Data Name="BugcheckParameter2">0xfffff801aeaf5b75</Data> <Data Name="BugcheckParameter3">0x0</Data> <Data Name="BugcheckParameter4">0xffffffffffffffff</Data> <Data Name="SleepInProgress">0</Data> <Data Name="PowerButtonTimestamp">0</Data> <Data Name="BootAppStatus">0</Data> <Data Name="Checkpoint">0</Data> <Data Name="ConnectedStandbyInProgress">false</Data> <Data Name="SystemSleepTransitionsToOn">1</Data> <Data Name="CsEntryScenarioInstanceId">0</Data> </EventData> </Event> Log Name: System Source: Microsoft-Windows-Kernel-Power Date: 25/02/2017 05:57:34 p.m. Event ID: 41 Task Category: (63) Level: Critical Keywords: (70368744177664),(2) User: SYSTEM Computer: Marcos-PC Description: The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly. Event Xml: <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"> <System> <Provider Name="Microsoft-Windows-Kernel-Power" Guid="{331C3B3A-2005-44C2-AC5E-77220C37D6B4}" /> <EventID>41</EventID> <Version>4</Version> <Level>1</Level> <Task>63</Task> <Opcode>0</Opcode> <Keywords>0x8000400000000002</Keywords> <TimeCreated SystemTime="2017-02-25T20:57:34.659111600Z" /> <EventRecordID>10067</EventRecordID> <Correlation /> <Execution ProcessID="4" ThreadID="8" /> <Channel>System</Channel> <Computer>Marcos-PC</Computer> <Security UserID="S-1-5-18" /> </System> <EventData> <Data Name="BugcheckCode">59</Data> <Data Name="BugcheckParameter1">0xc0000005</Data> <Data Name="BugcheckParameter2">0xfffff801e0aeef76</Data> <Data Name="BugcheckParameter3">0xffff8c01d51de750</Data> <Data Name="BugcheckParameter4">0x0</Data> <Data Name="SleepInProgress">0</Data> <Data Name="PowerButtonTimestamp">0</Data> <Data Name="BootAppStatus">0</Data> <Data Name="Checkpoint">0</Data> <Data Name="ConnectedStandbyInProgress">false</Data> <Data Name="SystemSleepTransitionsToOn">2</Data> <Data Name="CsEntryScenarioInstanceId">0</Data> </EventData> </Event> Log Name: System Source: Microsoft-Windows-Kernel-Power Date: 26/02/2017 06:12:59 p.m. Event ID: 41 Task Category: (63) Level: Critical Keywords: (70368744177664),(2) User: SYSTEM Computer: Marcos-PC Description: The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly. Event Xml: <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"> <System> <Provider Name="Microsoft-Windows-Kernel-Power" Guid="{331C3B3A-2005-44C2-AC5E-77220C37D6B4}" /> <EventID>41</EventID> <Version>4</Version> <Level>1</Level> <Task>63</Task> <Opcode>0</Opcode> <Keywords>0x8000400000000002</Keywords> <TimeCreated SystemTime="2017-02-26T21:12:59.772012300Z" /> <EventRecordID>10194</EventRecordID> <Correlation /> <Execution ProcessID="4" ThreadID="8" /> <Channel>System</Channel> <Computer>Marcos-PC</Computer> <Security UserID="S-1-5-18" /> </System> <EventData> <Data Name="BugcheckCode">268435582</Data> <Data Name="BugcheckParameter1">0xffffffffc0000005</Data> <Data Name="BugcheckParameter2">0xfffff807d850b745</Data> <Data Name="BugcheckParameter3">0xffff9b81af5f5658</Data> <Data Name="BugcheckParameter4">0xffff9b81af5f4e80</Data> <Data Name="SleepInProgress">0</Data> <Data Name="PowerButtonTimestamp">0</Data> <Data Name="BootAppStatus">0</Data> <Data Name="Checkpoint">0</Data> <Data Name="ConnectedStandbyInProgress">false</Data> <Data Name="SystemSleepTransitionsToOn">0</Data> <Data Name="CsEntryScenarioInstanceId">0</Data> </EventData> </Event> Log Name: System Source: Microsoft-Windows-Kernel-Power Date: 24/12/2016 08:45:08 p.m. Event ID: 41 Task Category: (63) Level: Critical Keywords: (70368744177664),(2) User: SYSTEM Computer: Marcos-PC Description: The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly. Event Xml: <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"> <System> <Provider Name="Microsoft-Windows-Kernel-Power" Guid="{331C3B3A-2005-44C2-AC5E-77220C37D6B4}" /> <EventID>41</EventID> <Version>4</Version> <Level>1</Level> <Task>63</Task> <Opcode>0</Opcode> <Keywords>0x8000400000000002</Keywords> <TimeCreated SystemTime="2016-12-24T23:45:08.081425000Z" /> <EventRecordID>4806</EventRecordID> <Correlation /> <Execution ProcessID="4" ThreadID="8" /> <Channel>System</Channel> <Computer>Marcos-PC</Computer> <Security UserID="S-1-5-18" /> </System> <EventData> <Data Name="BugcheckCode">0</Data> <Data Name="BugcheckParameter1">0x0</Data> <Data Name="BugcheckParameter2">0x0</Data> <Data Name="BugcheckParameter3">0x0</Data> <Data Name="BugcheckParameter4">0x0</Data> <Data Name="SleepInProgress">0</Data> <Data Name="PowerButtonTimestamp">0</Data> <Data Name="BootAppStatus">0</Data> <Data Name="Checkpoint">0</Data> <Data Name="ConnectedStandbyInProgress">false</Data> <Data Name="SystemSleepTransitionsToOn">0</Data> <Data Name="CsEntryScenarioInstanceId">0</Data> </EventData> </Event> Log Name: System Source: Microsoft-Windows-Kernel-Power Date: 06/12/2016 04:11:09 p.m. Event ID: 41 Task Category: (63) Level: Critical Keywords: (70368744177664),(2) User: SYSTEM Computer: Marcos-PC Description: The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly. Event Xml: <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"> <System> <Provider Name="Microsoft-Windows-Kernel-Power" Guid="{331C3B3A-2005-44C2-AC5E-77220C37D6B4}" /> <EventID>41</EventID> <Version>4</Version> <Level>1</Level> <Task>63</Task> <Opcode>0</Opcode> <Keywords>0x8000400000000002</Keywords> <TimeCreated SystemTime="2016-12-06T19:11:09.295444900Z" /> <EventRecordID>3750</EventRecordID> <Correlation /> <Execution ProcessID="4" ThreadID="8" /> <Channel>System</Channel> <Computer>Marcos-PC</Computer> <Security UserID="S-1-5-18" /> </System> <EventData> <Data Name="BugcheckCode">268435583</Data> <Data Name="BugcheckParameter1">0x8</Data> <Data Name="BugcheckParameter2">0xffff820019ac1a30</Data> <Data Name="BugcheckParameter3">0xfbff820022b659b0</Data> <Data Name="BugcheckParameter4">0xfffff8012a3c98df</Data> <Data Name="SleepInProgress">0</Data> <Data Name="PowerButtonTimestamp">0</Data> <Data Name="BootAppStatus">0</Data> <Data Name="Checkpoint">0</Data> <Data Name="ConnectedStandbyInProgress">false</Data> <Data Name="SystemSleepTransitionsToOn">4</Data> <Data Name="CsEntryScenarioInstanceId">0</Data> </EventData> </Event> Log Name: System Source: Microsoft-Windows-Kernel-Power Date: 03/01/2017 01:03:52 a.m. Event ID: 41 Task Category: (63) Level: Critical Keywords: (70368744177664),(2) User: SYSTEM Computer: Marcos-PC Description: The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly. Event Xml: <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"> <System> <Provider Name="Microsoft-Windows-Kernel-Power" Guid="{331C3B3A-2005-44C2-AC5E-77220C37D6B4}" /> <EventID>41</EventID> <Version>4</Version> <Level>1</Level> <Task>63</Task> <Opcode>0</Opcode> <Keywords>0x8000400000000002</Keywords> <TimeCreated SystemTime="2017-01-03T04:03:52.313459400Z" /> <EventRecordID>5906</EventRecordID> <Correlation /> <Execution ProcessID="4" ThreadID="8" /> <Channel>System</Channel> <Computer>Marcos-PC</Computer> <Security UserID="S-1-5-18" /> </System> <EventData> <Data Name="BugcheckCode">268435583</Data> <Data Name="BugcheckParameter1">0x8</Data> <Data Name="BugcheckParameter2">0xfffff800e815be70</Data> <Data Name="BugcheckParameter3">0x7bffb480de6e96c0</Data> <Data Name="BugcheckParameter4">0xfffff800e656dabf</Data> <Data Name="SleepInProgress">0</Data> <Data Name="PowerButtonTimestamp">0</Data> <Data Name="BootAppStatus">0</Data> <Data Name="Checkpoint">0</Data> <Data Name="ConnectedStandbyInProgress">false</Data> <Data Name="SystemSleepTransitionsToOn">0</Data> <Data Name="CsEntryScenarioInstanceId">0</Data> </EventData> </Event> Log Name: System Source: Microsoft-Windows-Kernel-Power Date: 01/03/2017 02:36:38 p.m. Event ID: 41 Task Category: (63) Level: Critical Keywords: (70368744177664),(2) User: SYSTEM Computer: Marcos-PC Description: The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly. Event Xml: <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"> <System> <Provider Name="Microsoft-Windows-Kernel-Power" Guid="{331C3B3A-2005-44C2-AC5E-77220C37D6B4}" /> <EventID>41</EventID> <Version>4</Version> <Level>1</Level> <Task>63</Task> <Opcode>0</Opcode> <Keywords>0x8000400000000002</Keywords> <TimeCreated SystemTime="2017-03-01T17:36:38.660115000Z" /> <EventRecordID>10891</EventRecordID> <Correlation /> <Execution ProcessID="4" ThreadID="8" /> <Channel>System</Channel> <Computer>Marcos-PC</Computer> <Security UserID="S-1-5-18" /> </System> <EventData> <Data Name="BugcheckCode">299</Data> <Data Name="BugcheckParameter1">0xffffffffc00002c4</Data> <Data Name="BugcheckParameter2">0x3ba</Data> <Data Name="BugcheckParameter3">0x58d5b20</Data> <Data Name="BugcheckParameter4">0xffffdb0103b3c000</Data> <Data Name="SleepInProgress">1</Data> <Data Name="PowerButtonTimestamp">0</Data> <Data Name="BootAppStatus">0</Data> <Data Name="Checkpoint">0</Data> <Data Name="ConnectedStandbyInProgress">false</Data> <Data Name="SystemSleepTransitionsToOn">1</Data> <Data Name="CsEntryScenarioInstanceId">0</Data> </EventData> </Event> Log Name: System Source: Microsoft-Windows-Kernel-Power Date: 31/12/2016 06:58:38 p.m. Event ID: 41 Task Category: (63) Level: Critical Keywords: (70368744177664),(2) User: SYSTEM Computer: Marcos-PC Description: The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly. Event Xml: <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"> <System> <Provider Name="Microsoft-Windows-Kernel-Power" Guid="{331C3B3A-2005-44C2-AC5E-77220C37D6B4}" /> <EventID>41</EventID> <Version>4</Version> <Level>1</Level> <Task>63</Task> <Opcode>0</Opcode> <Keywords>0x8000400000000002</Keywords> <TimeCreated SystemTime="2016-12-31T21:58:38.726921200Z" /> <EventRecordID>5314</EventRecordID> <Correlation /> <Execution ProcessID="4" ThreadID="8" /> <Channel>System</Channel> <Computer>Marcos-PC</Computer> <Security UserID="S-1-5-18" /> </System> <EventData> <Data Name="BugcheckCode">268435583</Data> <Data Name="BugcheckParameter1">0x8</Data> <Data Name="BugcheckParameter2">0xfffff8012754ae70</Data> <Data Name="BugcheckParameter3">0x7fff8380ef24c9b0</Data> <Data Name="BugcheckParameter4">0xfffff80125766abf</Data> <Data Name="SleepInProgress">0</Data> <Data Name="PowerButtonTimestamp">0</Data> <Data Name="BootAppStatus">0</Data> <Data Name="Checkpoint">0</Data> <Data Name="ConnectedStandbyInProgress">false</Data> <Data Name="SystemSleepTransitionsToOn">4</Data> <Data Name="CsEntryScenarioInstanceId">0</Data> </EventData> </Event> Log Name: System Source: Microsoft-Windows-Kernel-Power Date: 20/02/2017 12:57:22 p.m. Event ID: 41 Task Category: (63) Level: Critical Keywords: (70368744177664),(2) User: SYSTEM Computer: Marcos-PC Description: The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly. Event Xml: <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"> <System> <Provider Name="Microsoft-Windows-Kernel-Power" Guid="{331C3B3A-2005-44C2-AC5E-77220C37D6B4}" /> <EventID>41</EventID> <Version>4</Version> <Level>1</Level> <Task>63</Task> <Opcode>0</Opcode> <Keywords>0x8000400000000002</Keywords> <TimeCreated SystemTime="2017-02-20T15:57:22.380010200Z" /> <EventRecordID>9442</EventRecordID> <Correlation /> <Execution ProcessID="4" ThreadID="8" /> <Channel>System</Channel> <Computer>Marcos-PC</Computer> <Security UserID="S-1-5-18" /> </System> <EventData> <Data Name="BugcheckCode">160</Data> <Data Name="BugcheckParameter1">0x10e</Data> <Data Name="BugcheckParameter2">0xa</Data> <Data Name="BugcheckParameter3">0xca45</Data> <Data Name="BugcheckParameter4">0x4ae3</Data> <Data Name="SleepInProgress">6</Data> <Data Name="PowerButtonTimestamp">0</Data> <Data Name="BootAppStatus">3221225473</Data> <Data Name="Checkpoint">0</Data> <Data Name="ConnectedStandbyInProgress">false</Data> <Data Name="SystemSleepTransitionsToOn">6</Data> <Data Name="CsEntryScenarioInstanceId">0</Data> </EventData> </Event> Log Name: System Source: Microsoft-Windows-Kernel-Power Date: 30/11/2016 03:12:04 p.m. Event ID: 41 Task Category: (63) Level: Critical Keywords: (70368744177664),(2) User: SYSTEM Computer: Marcos-PC Description: The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly. Event Xml: <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"> <System> <Provider Name="Microsoft-Windows-Kernel-Power" Guid="{331C3B3A-2005-44C2-AC5E-77220C37D6B4}" /> <EventID>41</EventID> <Version>4</Version> <Level>1</Level> <Task>63</Task> <Opcode>0</Opcode> <Keywords>0x8000400000000002</Keywords> <TimeCreated SystemTime="2016-11-30T18:12:04.899456800Z" /> <EventRecordID>3483</EventRecordID> <Correlation /> <Execution ProcessID="4" ThreadID="8" /> <Channel>System</Channel> <Computer>Marcos-PC</Computer> <Security UserID="S-1-5-18" /> </System> <EventData> <Data Name="BugcheckCode">0</Data> <Data Name="BugcheckParameter1">0x0</Data> <Data Name="BugcheckParameter2">0x0</Data> <Data Name="BugcheckParameter3">0x0</Data> <Data Name="BugcheckParameter4">0x0</Data> <Data Name="SleepInProgress">6</Data> <Data Name="PowerButtonTimestamp">0</Data> <Data Name="BootAppStatus">3221226513</Data> <Data Name="Checkpoint">0</Data> <Data Name="ConnectedStandbyInProgress">false</Data> <Data Name="SystemSleepTransitionsToOn">6</Data> <Data Name="CsEntryScenarioInstanceId">0</Data> </EventData> </Event> Log Name: System Source: Microsoft-Windows-Kernel-Power Date: 30/01/2017 07:46:27 p.m. Event ID: 41 Task Category: (63) Level: Critical Keywords: (70368744177664),(2) User: SYSTEM Computer: Marcos-PC Description: The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly. Event Xml: <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"> <System> <Provider Name="Microsoft-Windows-Kernel-Power" Guid="{331C3B3A-2005-44C2-AC5E-77220C37D6B4}" /> <EventID>41</EventID> <Version>4</Version> <Level>1</Level> <Task>63</Task> <Opcode>0</Opcode> <Keywords>0x8000400000000002</Keywords> <TimeCreated SystemTime="2017-01-30T22:46:27.475172400Z" /> <EventRecordID>8456</EventRecordID> <Correlation /> <Execution ProcessID="4" ThreadID="8" /> <Channel>System</Channel> <Computer>Marcos-PC</Computer> <Security UserID="S-1-5-18" /> </System> <EventData> <Data Name="BugcheckCode">0</Data> <Data Name="BugcheckParameter1">0x0</Data> <Data Name="BugcheckParameter2">0x0</Data> <Data Name="BugcheckParameter3">0x0</Data> <Data Name="BugcheckParameter4">0x0</Data> <Data Name="SleepInProgress">0</Data> <Data Name="PowerButtonTimestamp">0</Data> <Data Name="BootAppStatus">0</Data> <Data Name="Checkpoint">0</Data> <Data Name="ConnectedStandbyInProgress">false</Data> <Data Name="SystemSleepTransitionsToOn">1</Data> <Data Name="CsEntryScenarioInstanceId">0</Data> </EventData> </Event> Log Name: System Source: Microsoft-Windows-Kernel-Power Date: 26/02/2017 09:46:56 p.m. Event ID: 41 Task Category: (63) Level: Critical Keywords: (70368744177664),(2) User: SYSTEM Computer: Marcos-PC Description: The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly. Event Xml: <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"> <System> <Provider Name="Microsoft-Windows-Kernel-Power" Guid="{331C3B3A-2005-44C2-AC5E-77220C37D6B4}" /> <EventID>41</EventID> <Version>4</Version> <Level>1</Level> <Task>63</Task> <Opcode>0</Opcode> <Keywords>0x8000400000000002</Keywords> <TimeCreated SystemTime="2017-02-27T00:46:56.730673200Z" /> <EventRecordID>10261</EventRecordID> <Correlation /> <Execution ProcessID="4" ThreadID="8" /> <Channel>System</Channel> <Computer>Marcos-PC</Computer> <Security UserID="S-1-5-18" /> </System> <EventData> <Data Name="BugcheckCode">0</Data> <Data Name="BugcheckParameter1">0x0</Data> <Data Name="BugcheckParameter2">0x0</Data> <Data Name="BugcheckParameter3">0x0</Data> <Data Name="BugcheckParameter4">0x0</Data> <Data Name="SleepInProgress">0</Data> <Data Name="PowerButtonTimestamp">0</Data> <Data Name="BootAppStatus">0</Data> <Data Name="Checkpoint">0</Data> <Data Name="ConnectedStandbyInProgress">false</Data> <Data Name="SystemSleepTransitionsToOn">1</Data> <Data Name="CsEntryScenarioInstanceId">0</Data> </EventData> </Event> Log Name: System Source: Microsoft-Windows-Kernel-Power Date: 26/01/2017 08:28:23 p.m. Event ID: 41 Task Category: (63) Level: Critical Keywords: (70368744177664),(2) User: SYSTEM Computer: Marcos-PC Description: The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly. Event Xml: <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"> <System> <Provider Name="Microsoft-Windows-Kernel-Power" Guid="{331C3B3A-2005-44C2-AC5E-77220C37D6B4}" /> <EventID>41</EventID> <Version>4</Version> <Level>1</Level> <Task>63</Task> <Opcode>0</Opcode> <Keywords>0x8000400000000002</Keywords> <TimeCreated SystemTime="2017-01-26T23:28:23.975330000Z" /> <EventRecordID>7808</EventRecordID> <Correlation /> <Execution ProcessID="4" ThreadID="8" /> <Channel>System</Channel> <Computer>Marcos-PC</Computer> <Security UserID="S-1-5-18" /> </System> <EventData> <Data Name="BugcheckCode">265</Data> <Data Name="BugcheckParameter1">0xa39fffe363328634</Data> <Data Name="BugcheckParameter2">0xb3b70c69b5b3a4ee</Data> <Data Name="BugcheckParameter3">0xffffd101fe2a7108</Data> <Data Name="BugcheckParameter4">0x0</Data> <Data Name="SleepInProgress">0</Data> <Data Name="PowerButtonTimestamp">0</Data> <Data Name="BootAppStatus">0</Data> <Data Name="Checkpoint">0</Data> <Data Name="ConnectedStandbyInProgress">false</Data> <Data Name="SystemSleepTransitionsToOn">3</Data> <Data Name="CsEntryScenarioInstanceId">0</Data> </EventData> </Event> Log Name: System Source: Microsoft-Windows-Kernel-Power Date: 06/01/2017 05:01:21 p.m. Event ID: 41 Task Category: (63) Level: Critical Keywords: (70368744177664),(2) User: SYSTEM Computer: Marcos-PC Description: The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly. Event Xml: <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"> <System> <Provider Name="Microsoft-Windows-Kernel-Power" Guid="{331C3B3A-2005-44C2-AC5E-77220C37D6B4}" /> <EventID>41</EventID> <Version>4</Version> <Level>1</Level> <Task>63</Task> <Opcode>0</Opcode> <Keywords>0x8000400000000002</Keywords> <TimeCreated SystemTime="2017-01-06T20:01:21.317327400Z" /> <EventRecordID>6206</EventRecordID> <Correlation /> <Execution ProcessID="4" ThreadID="8" /> <Channel>System</Channel> <Computer>Marcos-PC</Computer> <Security UserID="S-1-5-18" /> </System> <EventData> <Data Name="BugcheckCode">159</Data> <Data Name="BugcheckParameter1">0x3</Data> <Data Name="BugcheckParameter2">0xffffa085cc620060</Data> <Data Name="BugcheckParameter3">0xfffff8027cb4baa0</Data> <Data Name="BugcheckParameter4">0xffffa085d0fc5310</Data> <Data Name="SleepInProgress">4</Data> <Data Name="PowerButtonTimestamp">0</Data> <Data Name="BootAppStatus">3221225473</Data> <Data Name="Checkpoint">0</Data> <Data Name="ConnectedStandbyInProgress">false</Data> <Data Name="SystemSleepTransitionsToOn">1</Data> <Data Name="CsEntryScenarioInstanceId">0</Data> </EventData> </Event> Log Name: System Source: Microsoft-Windows-Kernel-Power Date: 05/01/2017 12:30:40 p.m. Event ID: 41 Task Category: (63) Level: Critical Keywords: (70368744177664),(2) User: SYSTEM Computer: Marcos-PC Description: The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly. Event Xml: <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"> <System> <Provider Name="Microsoft-Windows-Kernel-Power" Guid="{331C3B3A-2005-44C2-AC5E-77220C37D6B4}" /> <EventID>41</EventID> <Version>4</Version> <Level>1</Level> <Task>63</Task> <Opcode>0</Opcode> <Keywords>0x8000400000000002</Keywords> <TimeCreated SystemTime="2017-01-05T15:30:40.095745000Z" /> <EventRecordID>6054</EventRecordID> <Correlation /> <Execution ProcessID="4" ThreadID="8" /> <Channel>System</Channel> <Computer>Marcos-PC</Computer> <Security UserID="S-1-5-18" /> </System> <EventData> <Data Name="BugcheckCode">268435583</Data> <Data Name="BugcheckParameter1">0x8</Data> <Data Name="BugcheckParameter2">0xffffb30001a4ba30</Data> <Data Name="BugcheckParameter3">0x7bffb3000b5779b0</Data> <Data Name="BugcheckParameter4">0xfffff800b4566abf</Data> <Data Name="SleepInProgress">0</Data> <Data Name="PowerButtonTimestamp">0</Data> <Data Name="BootAppStatus">0</Data> <Data Name="Checkpoint">0</Data> <Data Name="ConnectedStandbyInProgress">false</Data> <Data Name="SystemSleepTransitionsToOn">4</Data> <Data Name="CsEntryScenarioInstanceId">0</Data> </EventData> </Event> Log Name: System Source: Microsoft-Windows-Kernel-Power Date: 02/01/2017 02:55:24 p.m. Event ID: 41 Task Category: (63) Level: Critical Keywords: (70368744177664),(2) User: SYSTEM Computer: Marcos-PC Description: The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly. Event Xml: <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"> <System> <Provider Name="Microsoft-Windows-Kernel-Power" Guid="{331C3B3A-2005-44C2-AC5E-77220C37D6B4}" /> <EventID>41</EventID> <Version>4</Version> <Level>1</Level> <Task>63</Task> <Opcode>0</Opcode> <Keywords>0x8000400000000002</Keywords> <TimeCreated SystemTime="2017-01-02T17:55:24.032156400Z" /> <EventRecordID>5554</EventRecordID> <Correlation /> <Execution ProcessID="4" ThreadID="8" /> <Channel>System</Channel> <Computer>Marcos-PC</Computer> <Security UserID="S-1-5-18" /> </System> <EventData> <Data Name="BugcheckCode">268435583</Data> <Data Name="BugcheckParameter1">0x8</Data> <Data Name="BugcheckParameter2">0xfffff803c955be70</Data> <Data Name="BugcheckParameter3">0xfbffe2009430d9b0</Data> <Data Name="BugcheckParameter4">0xfffff803c79ccabf</Data> <Data Name="SleepInProgress">0</Data> <Data Name="PowerButtonTimestamp">0</Data> <Data Name="BootAppStatus">0</Data> <Data Name="Checkpoint">0</Data> <Data Name="ConnectedStandbyInProgress">false</Data> <Data Name="SystemSleepTransitionsToOn">0</Data> <Data Name="CsEntryScenarioInstanceId">0</Data> </EventData> </Event> Log Name: System Source: Microsoft-Windows-Kernel-Power Date: 23/11/2016 04:38:47 a.m. Event ID: 41 Task Category: (63) Level: Critical Keywords: (70368744177664),(2) User: SYSTEM Computer: Marcos-PC Description: The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly. Event Xml: <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"> <System> <Provider Name="Microsoft-Windows-Kernel-Power" Guid="{331C3B3A-2005-44C2-AC5E-77220C37D6B4}" /> <EventID>41</EventID> <Version>4</Version> <Level>1</Level> <Task>63</Task> <Opcode>0</Opcode> <Keywords>0x8000400000000002</Keywords> <TimeCreated SystemTime="2016-11-23T07:38:47.010954500Z" /> <EventRecordID>3190</EventRecordID> <Correlation /> <Execution ProcessID="4" ThreadID="8" /> <Channel>System</Channel> <Computer>Marcos-PC</Computer> <Security UserID="S-1-5-18" /> </System> <EventData> <Data Name="BugcheckCode">268435582</Data> <Data Name="BugcheckParameter1">0xffffffffc0000005</Data> <Data Name="BugcheckParameter2">0xfffff805bd0defa4</Data> <Data Name="BugcheckParameter3">0xffffcd0186e95a38</Data> <Data Name="BugcheckParameter4">0xffffcd0186e95260</Data> <Data Name="SleepInProgress">0</Data> <Data Name="PowerButtonTimestamp">0</Data> <Data Name="BootAppStatus">0</Data> <Data Name="Checkpoint">0</Data> <Data Name="ConnectedStandbyInProgress">false</Data> <Data Name="SystemSleepTransitionsToOn">18</Data> <Data Name="CsEntryScenarioInstanceId">0</Data> </EventData> </Event> Log Name: System Source: Microsoft-Windows-Kernel-Power Date: 09/01/2017 01:13:05 p.m. Event ID: 41 Task Category: (63) Level: Critical Keywords: (70368744177664),(2) User: SYSTEM Computer: Marcos-PC Description: The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly. Event Xml: <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"> <System> <Provider Name="Microsoft-Windows-Kernel-Power" Guid="{331C3B3A-2005-44C2-AC5E-77220C37D6B4}" /> <EventID>41</EventID> <Version>4</Version> <Level>1</Level> <Task>63</Task> <Opcode>0</Opcode> <Keywords>0x8000400000000002</Keywords> <TimeCreated SystemTime="2017-01-09T16:13:05.730647500Z" /> <EventRecordID>6474</EventRecordID> <Correlation /> <Execution ProcessID="4" ThreadID="8" /> <Channel>System</Channel> <Computer>Marcos-PC</Computer> <Security UserID="S-1-5-18" /> </System> <EventData> <Data Name="BugcheckCode">59</Data> <Data Name="BugcheckParameter1">0xc0000005</Data> <Data Name="BugcheckParameter2">0xfffff8015c7038fd</Data> <Data Name="BugcheckParameter3">0xffffb180851fcfe0</Data> <Data Name="BugcheckParameter4">0x0</Data> <Data Name="SleepInProgress">0</Data> <Data Name="PowerButtonTimestamp">0</Data> <Data Name="BootAppStatus">0</Data> <Data Name="Checkpoint">0</Data> <Data Name="ConnectedStandbyInProgress">false</Data> <Data Name="SystemSleepTransitionsToOn">0</Data> <Data Name="CsEntryScenarioInstanceId">0</Data> </EventData> </Event> Log Name: System Source: Microsoft-Windows-Kernel-Power Date: 10/12/2016 01:32:00 a.m. Event ID: 41 Task Category: (63) Level: Critical Keywords: (70368744177664),(2) User: SYSTEM Computer: Marcos-PC Description: The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly. Event Xml: <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"> <System> <Provider Name="Microsoft-Windows-Kernel-Power" Guid="{331C3B3A-2005-44C2-AC5E-77220C37D6B4}" /> <EventID>41</EventID> <Version>4</Version> <Level>1</Level> <Task>63</Task> <Opcode>0</Opcode> <Keywords>0x8000400000000002</Keywords> <TimeCreated SystemTime="2016-12-10T04:32:00.043829900Z" /> <EventRecordID>4008</EventRecordID> <Correlation /> <Execution ProcessID="4" ThreadID="8" /> <Channel>System</Channel> <Computer>Marcos-PC</Computer> <Security UserID="S-1-5-18" /> </System> <EventData> <Data Name="BugcheckCode">268435583</Data> <Data Name="BugcheckParameter1">0x8</Data> <Data Name="BugcheckParameter2">0xffffc800378c1a30</Data> <Data Name="BugcheckParameter3">0xfdffc8003c1e1880</Data> <Data Name="BugcheckParameter4">0xfffff8006e5d28df</Data> <Data Name="SleepInProgress">0</Data> <Data Name="PowerButtonTimestamp">0</Data> <Data Name="BootAppStatus">0</Data> <Data Name="Checkpoint">0</Data> <Data Name="ConnectedStandbyInProgress">false</Data> <Data Name="SystemSleepTransitionsToOn">5</Data> <Data Name="CsEntryScenarioInstanceId">0</Data> </EventData> </Event> Log Name: System Source: Microsoft-Windows-Kernel-Power Date: 20/02/2017 02:59:07 p.m. Event ID: 41 Task Category: (63) Level: Critical Keywords: (70368744177664),(2) User: SYSTEM Computer: Marcos-PC Description: The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly. Event Xml: <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"> <System> <Provider Name="Microsoft-Windows-Kernel-Power" Guid="{331C3B3A-2005-44C2-AC5E-77220C37D6B4}" /> <EventID>41</EventID> <Version>4</Version> <Level>1</Level> <Task>63</Task> <Opcode>0</Opcode> <Keywords>0x8000400000000002</Keywords> <TimeCreated SystemTime="2017-02-20T17:59:07.813730300Z" /> <EventRecordID>9496</EventRecordID> <Correlation /> <Execution ProcessID="4" ThreadID="8" /> <Channel>System</Channel> <Computer>Marcos-PC</Computer> <Security UserID="S-1-5-18" /> </System> <EventData> <Data Name="BugcheckCode">0</Data> <Data Name="BugcheckParameter1">0x0</Data> <Data Name="BugcheckParameter2">0x0</Data> <Data Name="BugcheckParameter3">0x0</Data> <Data Name="BugcheckParameter4">0x0</Data> <Data Name="SleepInProgress">0</Data> <Data Name="PowerButtonTimestamp">131320871128646505</Data> <Data Name="BootAppStatus">0</Data> <Data Name="Checkpoint">0</Data> <Data Name="ConnectedStandbyInProgress">false</Data> <Data Name="SystemSleepTransitionsToOn">0</Data> <Data Name="CsEntryScenarioInstanceId">0</Data> </EventData> </Event> Log Name: System Source: Microsoft-Windows-Kernel-Power Date: 26/01/2017 10:21:13 p.m. Event ID: 41 Task Category: (63) Level: Critical Keywords: (70368744177664),(2) User: SYSTEM Computer: Marcos-PC Description: The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly. Event Xml: <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"> <System> <Provider Name="Microsoft-Windows-Kernel-Power" Guid="{331C3B3A-2005-44C2-AC5E-77220C37D6B4}" /> <EventID>41</EventID> <Version>4</Version> <Level>1</Level> <Task>63</Task> <Opcode>0</Opcode> <Keywords>0x8000400000000002</Keywords> <TimeCreated SystemTime="2017-01-27T01:21:13.525557300Z" /> <EventRecordID>7856</EventRecordID> <Correlation /> <Execution ProcessID="4" ThreadID="8" /> <Channel>System</Channel> <Computer>Marcos-PC</Computer> <Security UserID="S-1-5-18" /> </System> <EventData> <Data Name="BugcheckCode">30</Data> <Data Name="BugcheckParameter1">0xffffffffc0000005</Data> <Data Name="BugcheckParameter2">0xfffff8030e47ab7f</Data> <Data Name="BugcheckParameter3">0x0</Data> <Data Name="BugcheckParameter4">0xffffffffffffffff</Data> <Data Name="SleepInProgress">0</Data> <Data Name="PowerButtonTimestamp">0</Data> <Data Name="BootAppStatus">0</Data> <Data Name="Checkpoint">0</Data> <Data Name="ConnectedStandbyInProgress">false</Data> <Data Name="SystemSleepTransitionsToOn">0</Data> <Data Name="CsEntryScenarioInstanceId">0</Data> </EventData> </Event>[/quote]
     
    marcosdipaolo, Mar 1, 2017
    #8
  9. Ztruker Win User
    No new dumps in the zip file. The latest is from 2/26. No event viewer log either, Please run the following from a Elevated Command Prompt:

    wevtutil qe System /f:text > "%USERPROFILE%\Desktop\eventlog.txt"

    Zip eventlog.txt on your Desktop and upload please. This is one of the commands dm_log_collector is supposed to run.
     
    Ztruker, Mar 2, 2017
    #9
  10. Hello Ztruker
    yes, i see a new dump there, from march 1st, i just downloaded myself the zip to check it. Just in case i attach it too.
    Attaching here the eventlog.txt

    Edit:
    The eventlog.txt is also in the zip file i sent last post
     
    marcosdipaolo, Mar 2, 2017
    #10
  11. Ztruker Win User
    Nothing useful in the dump nor in the eventlog.txt file.

    Have you considered not using sleep or hibernate? Instead use the Screen Saver function to turn off the display and hard drive after a set period on idle time. See if that makes any difference.
     
    Ztruker, Mar 3, 2017
    #11
  12. Done, but i doubt it'll change anything since I've had this problem with different hibernation and sleep settings and nothing has changed.
    I'll report back anyways. Thanks for your help Ztrucker as always.
     
    marcosdipaolo, Mar 4, 2017
    #12
  13. Ztruker Win User

    BSOD, many errors, sending data

    Also noticed you have a couple really old drivers installed:

    2005/08/11 08:07:32 PM \??\C:\Windows\system32\Drivers\SSPORT.sys
    Driver Description: Samsung printer driver
    Driver Update Site: Access Denied

    2006/09/05 04:10:02 AM \??\C:\Windows\GVTDrv64.sys
    Driver Description: Gigabyte Easy Tune 6 driver (known BSOD issues w/Win7)
    Driver Update Site: Utility - GIGABYTE - Motherboard , Graphics Card , Laptop , Mini-PC , Server , PC Peripherals and more

    2009/02/24 07:34:07 AM C:\WINDOWS\system32\DRIVERS\mcdbus.sysDriver Description: MagicISO SCSI Host Controller driver

    Driver Update Site: MagicISO - Convert BIN to ISO, Create, Edit, Burn, Extract ISO file, ISO/BIN converter/extractor/editor


    2009/03/13 12:22:29 AM \??\C:\Windows\gdrv.sys
    Driver Description: Gigabyte Easy Saver - mobo power utility driver

    Driver Update Site: Gigabyte Motherboard Support


    2009/03/19 11:59:06 PM \??\C:\Windows\etdrv.sys
    May be part of Gigabyte Tools Easy Tune 6.

    I'd say uninstall any of the Gigsabyte and NMagiciso software and if you still use a Samsung printer then update the driver.

    None of these indicate a problem in any dump but are still suspect.
     
    Ztruker, Mar 4, 2017
    #13
  14. ON IT
    I'll report back
    thanks a lot Ztrucker!!
     
    marcosdipaolo, Apr 5, 2018
    #14
Thema:

BSOD, many errors, sending data

Loading...
  1. BSOD, many errors, sending data - Similar Threads - BSOD many errors

  2. use so many data hotspot

    in Windows 10 Network and Sharing
    use so many data hotspot: I have download a movie about 800mb but my laptop use my data about 2gb..help meeeeeee https://answers.microsoft.com/en-us/windows/forum/all/use-so-many-data-hotspot/8b684b52-f940-4f8d-b1cb-793a9825dd9f
  3. send error

    in Windows 10 Customization
    send error: I have sent this same presentation numerous times before without any problems We weren't able to send this message, so we've put it in your Drafts folder. Before you try sending it again, you can check to see if the address is correct and that no attachments are too large....
  4. So. Many. errors.

    in Windows 10 BSOD Crashes and Debugging
    So. Many. errors.: alright. I built a computer recently (using windows so assume this is where to post) and i have oh so many errors. Ill list these out. Tell me if there's anything in common but the only common thing i can find is driver issues and well ive been going through all of my...
  5. System sending data to unknown IP.

    in Windows 10 Network and Sharing
    System sending data to unknown IP.: Hey, recently I had problem that I still did not fix, my system has got weird lag spikes, that happen in random intervals (whenever I ping google.pl, latency is ~20ms, but sometimes it's 400ms). I installed wireshark to check if there is something being sent in background....
  6. Send error

    in Windows 10 Network and Sharing
    Send error: I'm using Windows10 and keep getting a message giving "Send error" the offending e-mail gets put into Drafts. Whats strange is if i open the draft and forward the message on to the original addressee it sends it no problem. Any ideas? not got a clue and it doesn't do it every...
  7. Suddenly many BSODs

    in Windows 10 BSOD Crashes and Debugging
    Suddenly many BSODs: I was watching a stream for a while, when i closed firefox it caused a BSOD. After i turned the pc back on it started to constantly BSOD, sometimes right after getting into windows. There are various stop codes: System_thread_exception_not_handled...
  8. Many BSODs when at stress

    in Windows 10 BSOD Crashes and Debugging
    Many BSODs when at stress: Hi, I'm getting random BSODs like PAGE_FAULT_IN_NONPAGED_AREA ; SYSTEM_SERVICE_EXCEPTION or KMODE_EXCEPTION_NOT_HANDLED when playing games. Last time after restarting PC (BSOD) win10 run a disc repair, its going insane. I've tried: -Turning off, on ,and system managed...
  9. External USB HDD - Many Event Errors - Is my Data in Danger ?

    in Windows 10 Drivers and Hardware
    External USB HDD - Many Event Errors - Is my Data in Danger ?: Hi, Sorry for poor English While doing a System Backup, I am getting a lot of errors in Event Viewer. The Backup itself is saying it finished Sucessfully. Because the messages are Scaring and I already lost 1TB of Data on other External Drive also while doing System...
  10. Many Different BSOD Errors At Random Intervals

    in Windows 10 BSOD Crashes and Debugging
    Many Different BSOD Errors At Random Intervals: Hi, I've been having seemingly random BSOD's over the past couple of months. I recently reset my BIOS and this went away for a week, however, earlier today I received another. Oddly enough, the first time I ran the DM log collector utility this also Bluescreened the...