they way you worded it there it sounds like you may have the M2-ATX set to "standard atx function" or may not have the ignition wire (the white wire) properly wired. This could cause the system to power down improperly and in turn give you the windows errors you're seeing.
also check your device manager to see if there is any device with "?" or not installed drivers.
I had this issue with my bluesoleil driver that cause my computer to restart with the "windows has recovered from an error" at startup.
I also have occasional bsod that appears to be xport's issue which curiosity is currently working on.
I'm hoping some of you guys much smarter than me can shed some light on. I have been looking for issues items that could be the cause of all these problems. In device manager, nothing showed a problem; however, I noticed under "view" in device manager, there is an option to show all hidden items as well. I did this, and a system file was "stopped" and it said the device could not be started properly. It was "null.sys" in the windows 32 folder. I couldn't "manually" start this, so I clicked "uninstall". Now, it shows no error, but what is null.sys? I did a search and many say it is a cause for BSOD and crashing (which I was experiencing)...but was mine corrupt and I need it? Haven't had a startup issue since I removed it; however, boot times and resume is really slow (like 2 minutes or more).....suggestions?
Could you replace that file then? Certainly seems there is something with timing on shutdown that is causing problems with W7......
I have a M2- ATX which I could try on one of my Zotac boards, and see if I have the same concern - with the Carnetix and PicoPSU combo, no problem though.....
Weird!! Ok, I completely formatted my computer. On fresh start, Null shows fine in device manager. Windows prompts me for a mandatory update, and immediately after restart, the exclamation point shows up over the "null" in device manager. What the heck? Any suggestions?
maybe you could try rolling back your computer to right after the fresh install, and determining what the update was?
if you do determine that it is the update causing the issue, don't use that update..
My OLD 2001 Mitsubishi Eclipse GT:
"The Project That Never Ended, until it did"
next project? subaru brz
most likely you have a device that is missing driver for windows 7, you'll have to identify which one it is and locate the driver for it. Or when you figured it out and have no driver, you can always disabled it in bios or remove it from hardware if it is removable