New PC build - need help debugging event errors

[fullofclovers]

Hi, I recently built my new workstation about 2 weeks ago and have discovered a bunch of critical and other error reports within Windows 8 Event Viewer. I haven't had any BSODs or system freezing fortunately but do find it odd to have these errors without any visible symptoms that I have noticed.

In particular I'm getting Critical Event ID 41 randomly. I've noticed Error Event ID 29 and Error Event ID 6008 occur at the same time of the Critical Event error.

I have over 150 random Error Events and 729 Warnings over the past 7 days.

I've ran memtest over night with no errors and all my temps are normal. Using Samsung's Magician software I checked my SSD and I don't see any errors. I have my mobo's latest BIOS and the only change I had to make was changing my memory's profile to it's recommended clock speed/voltage.

My system appears stable, but am nervous of any possible underlining issue(s) that may come up.

Also, I noticed today my power settings changed by themselves to "Balanced" mode from what I set to "High Performance". Not sure if it's worth noting, just found it odd.

Attached are my system logs/specs. Any idea on what all these errors are reporting on would be greatly appreciated.

My PC:
Windows 8 64bit
Intel Core i7-4770K 3.5GHz
Asus Z87 - Pro mobo
Corsair Vengeance - 32GB @ 1600
Samsung 840 Pro 256 SSD
Corsair HX850 - 850W PSU
EVGA SuperClocked GeForce GTX 770 2GB

 

[usasma]

Can't see much here. I did see an error with the fast startup, so I'd suggest disabling that for now (it's in the bottom of the Power Options screen when you click on the "Choose what the power button does" sidebar link).

Lot's of DCOM errors, but nothing certain to link them to. Please do this (it's useful for spotting patterns):
Please do the following:
- open Event Viewer (eventvwr.msc)
- expand the Custom Views category (left click on the > next to the words "Custom Views")
- right click on Administrative Events
- select "Save all Events in Custom View as..."
- save the file as Admin.evtx
- zip up the file (right click on it, select "Send to", select "Compressed (zipped) folder")
- upload it with your next post (if it's too big, then upload it to a free file-hosting service and post a link here).

 

[usasma]

Whoops! Misread your post and skipped the Event ID 41 errors (they're "Critical" not "Error" when scanning the logs - another benefit of using the Admin events log).

Event ID 41 is simply Windows telling us that it doesn't know why it shut down. In most cases this is a hardware problem, frequently due to overheating. As this is a new build, are you certain that you put thermal conductive material between the CPU and the cooler? Beyond that, try this free utility to monitor your temps (I don't know what you used to monitor your temps - but this may be a bit more thorough): HWMonitor CPUID - System & hardware benchmark, monitoring, reporting

Open up the case and point a house fan into it on HIGH. See if that decreases the frequency of the BSOD's.

When the system has just shut down, try this (BE VERY, VERY CAREFUL!!!)
- unplug the system from the wall
- grab hold of the metal of the case with one hand
- with the other hand, feel around inside the case (BUT DO NOT TOUCH ANYTHING).
If anything is too hot, you'll be able to feel it before actually touching it.
FYI - I've received 2nd degree burns when doing this - BE CAREFUL!!!


Another common problem that I've faced is bad connections. For years I had to reseat everything once I finished a build because there'd inevitably be at least one connection that I didn't fully seat. Test each and every connection on the new system, then do it again just to be sure.

Good luck!

 

[fullofclovers]

Here is that log file you requested. Also, I'm not having BSODs. Only the kernal event errors.

Temps are good throughout my system as well.

 

[usasma]

Interestingly, 2ms after the Fast Startup failed, the system threw a Event ID 41 error (on both 12 & 15 July).
Fast Startup failed with this error:

// MessageId: STATUS_NOT_SAME_DEVICE
//
// MessageText:
//
// {Incorrect Volume}
// The target file of a rename request is located on a different device than the source of the rename request.
//
#define STATUS_NOT_SAME_DEVICE ((NTSTATUS)0xC00000D4L)​

Have you disabled Fast Startup as I asked in Post #2:

.... I did see an error with the fast startup, so I'd suggest disabling that for now (it's in the bottom of the Power Options screen when you click on the "Choose what the power button does" sidebar link).

Has that helped?

More info on Fast Startup: Delivering fast boot times in Windows 8 - Building Windows 8 - Site Home - MSDN Blogs

 

[fullofclovers]

I did disable Fast Startup and haven't been getting those errors. Hopefully that's the last of them! Thanks for the help!

Any idea of the network issues I'm receiving?

 

[usasma]

No specific ideas about the networking problems. Could you describe them in more detail please?

Try:
1) Updating the network drivers on your computer (both wired and wireless if so equipped). If you have the latest drivers, then uninstall them and install a freshly downloaded copy of the latest drivers.
2) If using a wired connection, try another cable and make sure it's firmly plugged into the computer and to the router/modem. Hold them in with constant pressure (we have this problem at work because the cables are used a lot).
3) Try another computer on the same cable as this computer and see if it has connection issues
4) Try this computer on another router/modem and see if it has issues also.
5) Disable other "internet aware" programs to see if they're causing problems.
6) Post over in the Networking and Sharing forum for some more expert help with networking issues: Network & Sharing - Windows 8 Forums