New
#11
1. Okay I do have Service Pack 1 so I changed that in my System Specs (I could swear it said that before in more detail).
2. The reason I mentioned Windows6.1-KB2670838-x64.msu was to see if I had the latest Direct X - which I do.
3. I opened DxDiag and it came up with a message talking about Direct3D... So I clicked no and it did whatever it was supposed to do without crashing... Here are the two logs: 32 BIT LOG ; 64 BIT LOG
4. I managed to get LOGON.SCR to work! Just not any other screensavers (Ribbons.scr) or I get the Direct 3D error... Still progress!!! I didn't use two backslashes, I set the screensaversecure value to 1 (Note the R at the end of screensaveR), I also kept LOGON.SCR in system32 not SysWow64.
5. I scan my pc and have it on automated disk defrags, scans, cleanups etc... So no worries in that department.
Anyways thank you for the response! I am glad we made some progress (I am just not sure what made LOGON.SCR work exactly)... So all that is left is the Direct 3D error so I can use a custom screensaver... If there is no way possible I am happy with LOGON.SCR.
Regards, Radical924