Windows 10: Windows 10 fails

Hi guys,
After 5 days of tooting my horn about how flawlessly Windows 10 was, and how beautiful the game playing experience was, I had my 1st issue. My audio started crackling, and then failed all together. I uninstalled and reinstalled my Creative drivers, my control panel for my X-fi wasn't recognized, and, although my headphones worked, my speakers didn't.
I shut it down, turned off the PS, and let it sit over night. I went and swore and swore, and swore some more at my wife.
I was going to come and revert back to Windows 7, but when I turned on my PC, I had audio. I gamed, and it works. So, If you have issues with your PC, turn it off, and let it set, call my wife and swear it her, I swear it works....... hahaha, no, but, seriously, try turning it off, if it only goes to standby, unplug it, and let it set for a few minutes, and see if that helps. It worked for me. Driver updates will come...... for most. Until then, there maybe a lot of cold re-boots instore for us.

:)

 

Windows 10 Unexpected shutdown on start up

OK, so i figured it out myself

Found the logfile in "C:\Windows\Minidump".

You need the Windows Development Kit to open it and a bit of googling to understand it.

Found out that a Daemon driver caused an error. Removed Daemon but this didn't solve it. (ps: Daemon itself worked normally).

I let hibernate my computer again and found another error with sptd2.sys: SCSI Pass Through Direct layer

More google and ended up on the duplexsecure site. Downloaded the W10 version and voila: problem fixed.

For the Windows support team: It would be really helpfull if you could pass problems to a more skilled helpdesk who can do more than proposing the standard solutions in case those won't work.

Cheers

 

Windows 10 Unexpected shutdown on start up

OK, so I also found out that this occurs when sleepmode (for me after 3 hours) changes into hibernate mode.

Seems like the going into hibernate and/or starting up from HIbernate results in a shutdown. In safeboot it works perfectly.

Anyone any idea how I can figure out where it goes wrong. Is there a way to log this (I couldn't find it in bootlog)