System Loses Power Randomly

There's even less in that one. Did you give it time for all the steps to run?

carwiz said:

There's even less in that one. Did you give it time for all the steps to run?

Yes, it said it completed successfully!

Are there any other tools I could try? What are you looking for in particular?

Thanks for your help!

I was wanting to look at the System Events Log. The MSinfo file helps too as it gives a detailed look at the system hardware, programs and services running. There's other lists included but most are duplications of MSinfo in text form. The Application Events Log is useful at times also.

Did you run the DM Collector as administrator? If not, try that. I noticed it doesn't say that in the instructions but the other "Grab All" collector does or it won't pull all the info.

carwiz said:

I was wanting to look at the System Events Log. The MSinfo file helps too as it gives a detailed look at the system hardware, programs and services running. There's other lists included but most are duplications of MSinfo in text form. The Application Events Log is useful at times also.

Did you run the DM Collector as administrator? If not, try that. I noticed it doesn't say that in the instructions but the other "Grab All" collector does or it won't pull all the info.

I ran it as an administrator, not too sure why it didn't work!

Update: I've run it again and i've attached the file, no errors while it was collecting!

That's better. It looks like it's all there now. I'll have a detailed look at it during lunch as I gotta run for now. Unless someone else steps in to take a peek in the mean time. I know, it's hard being on the other side of the globe.

I'll post a quick help request and see if someone is available now.

carwiz said:

That's better. It looks like it's all there now. I'll have a detailed look at it during lunch as I gotta run for now. Unless someone else steps in to take a peek in the mean time. I know, it's hard being on the other side of the globe.

I'll post a quick help request and see if someone is available now.

Thanks! I'm in no rush, I've had this problem for 4 years; I managed to suppress it so it only happens every 7-8 months so I can wait a few hours!

Thanks again for your help up to this point.

A few things to do: The disk controller driver and BIOS could very well be the cause of Power Fault errors.

Correction: I listed this first because I found the errors first but do this LAST. The driver updates ( #2) need priority before rebuilding the index.
1. The log is filled with Search indexing errors.
Control Panel > Indexing > Advanced > Rebuild Index.

2. Check to see if there's any motherboard driver updates. Your Marvel Disk controller driver is tanking. Also check to see if there's a BIOS update.

Code:

 
Event[51310]:
  Log Name: System
  Source: mvs91xx
 
Date: 2015-06-05T22:42:09.324
  Event ID: 36
  Task: 
N/A
  Level: Information
  Opcode: N/A
  Keyword: 
Classic
  User: N/A
  User Name: N/A
  Computer: 
Dholi
  Description: 
Command [0x28] on physical disk 1 failed. Sense 
key=0x3, ASC=0x11, ASCQ=0x0.
 
 
Event[51311]:
  Log Name: System
  Source: Disk
 
Date: 2015-06-05T22:42:09.324
  Event ID: 11
  Task: 
N/A
  Level: Error
  Opcode: N/A
  Keyword: 
Classic
  User: N/A
  User Name: N/A
  Computer: 
Dholi
  Description: 
The driver detected a controller error on 
\Device\Harddisk0\DR0.

3. See if there's an update for Avast. (AvastVBox) If you don't run VBOX all the time, disable the virtual network adaptor or remove/disable the AvastVBox NG component.
Control panel > software > avast > change > remove the NG component

Code:

 
Event[51247]:
  Log Name: System
  Source: Service Control 
Manager
  Date: 2015-06-05T12:39:15.830
  Event ID: 
7000
  Task: N/A
  Level: Error
  Opcode: N/A
 
Keyword: Classic
  User: N/A
  User Name: N/A
 
Computer: Dholi
  Description: 
The AvastVBox COM Service service 
failed to start due to the following error: 
The service did not respond to 
the start or control request in a timely fashion.

4. Item #2 should take care of this too. Windows tried to create a dump file the disk wasn't there.

Code:

 
Event[50862]:
  Log Name: System
  Source: volmgr
 
Date: 2015-06-04T22:04:08.033
  Event ID: 46
  Task: 
N/A
  Level: Error
  Opcode: N/A
  Keyword: 
Classic
  User: N/A
  User Name: N/A
  Computer: 
Dholi
  Description: 
Crash dump initialization failed!

In case if relevant: The volmgr event can happen if you have pagefile on some other drive/partition and/or no pagefile on C or too small for at least a kernel dump (600MB should suffice).

carwiz said:

A few things to do: The disk controller driver and BIOS could very well be the cause of Power Fault errors.

Correction: I listed this first because I found the errors first but do this LAST. The driver updates ( #2) need priority before rebuilding the index.
1. The log is filled with Search indexing errors.
Control Panel > Indexing > Advanced > Rebuild Index.

2. Check to see if there's any motherboard driver updates. Your Marvel Disk controller driver is tanking. Also check to see if there's a BIOS update.

Code:

 
Event[51310]:
  Log Name: System
  Source: mvs91xx
 
Date: 2015-06-05T22:42:09.324
  Event ID: 36
  Task: 
N/A
  Level: Information
  Opcode: N/A
  Keyword: 
Classic
  User: N/A
  User Name: N/A
  Computer: 
Dholi
  Description: 
Command [0x28] on physical disk 1 failed. Sense 
key=0x3, ASC=0x11, ASCQ=0x0.
 
 
Event[51311]:
  Log Name: System
  Source: Disk
 
Date: 2015-06-05T22:42:09.324
  Event ID: 11
  Task: 
N/A
  Level: Error
  Opcode: N/A
  Keyword: 
Classic
  User: N/A
  User Name: N/A
  Computer: 
Dholi
  Description: 
The driver detected a controller error on 
\Device\Harddisk0\DR0.

3. See if there's an update for Avast. (AvastVBox) If you don't run VBOX all the time, disable the virtual network adaptor or remove/disable the AvastVBox NG component.
Control panel > software > avast > change > remove the NG component

Code:

 
Event[51247]:
  Log Name: System
  Source: Service Control 
Manager
  Date: 2015-06-05T12:39:15.830
  Event ID: 
7000
  Task: N/A
  Level: Error
  Opcode: N/A
 
Keyword: Classic
  User: N/A
  User Name: N/A
 
Computer: Dholi
  Description: 
The AvastVBox COM Service service 
failed to start due to the following error: 
The service did not respond to 
the start or control request in a timely fashion.

4. Item #2 should take care of this too. Windows tried to create a dump file the disk wasn't there.

Code:

 
Event[50862]:
  Log Name: System
  Source: volmgr
 
Date: 2015-06-04T22:04:08.033
  Event ID: 46
  Task: 
N/A
  Level: Error
  Opcode: N/A
  Keyword: 
Classic
  User: N/A
  User Name: N/A
  Computer: 
Dholi
  Description: 
Crash dump initialization failed!

Hi Carwiz,

Thanks for taking your time to take a look at this. I have read what you have suggested and so far I have:

1. Updated Marvell Driver from the Asus Website, it installed this thing called a 'Magni Driver'
2. I repair-installed Avast, the avast forum suggested that the VBox application had been corrupted, I'm no longer getting errors from this.
3. I've rebuilt the search index as suggested

There have been 10 BIOS updates since I bought the Motherboard, shall I update to the latest version?


Thanks


MistUnleashed

EDIT: I just updated the BIOS to the latest version and it seems to have added these Kernel-Processor-Power events to my system Event Log in the Event Viewer... is this normal?

Also in options in my BIOS my HDD is set to IDE < I have a choice out of: RAID, AHCI and IDE - Do I leave it as IDE?

Finally, what do I set 'Hard-Disk Write Protect' to? Do I leave it as it is?

See Screenshot Below.