First time I left the computer alone for about an hour, then moved the mouse, the same thing happened again. Checked for virus etc., all clean this time.

From the time when I first got the computer I switched off all energy saving options I could.
I can only assume that there is one item (possibly part of the motherboard?) that goes into sleep mode after a considerable time (does not happen after 5 minutes), which I cannot prevent from happening, and this interferes with v8 somehow.

Guess I'll do AstroPulse until v9 comes along.
Thanks all for trying

So if you don't hear from me during the next month then all went well.

Or one of the viruses won a round. Hope you keep on top of them.

---

Several spyware but also one virus (apparently without payload) found.

Malwarebytes reports Superantispyware itself as spyware, though that might be a false positive.

I've re-allowed v8 units, so if you don't hear from me during the next month then all went well.

Thanks a lot for all the help, all you guys (especially Ageless).

CRITICAL_OBJECT_TERMINATION indicates that a critical component of windows was modified in memory and windows detected the change and shutdown the system.

I would run a full diagnostic on the system, starting with an anti-virus scan, an anti-malware scan (with Malwarebytes Anti-Malware and Superantispyware), a root-kit scan, and a system file checker (sfc /scannow as administrator).

AV scan: check with Trend Micro online scan, Bitdefender online scan (may need Internet Explorer), or Kaspersky's free scanner.

Malwarebytes Anti Malware free (don't forget to update after install).
Superantispyware (don't forget to update after install).
Malwarebytes anti root-kit scanner
Sophos anti root-kit scanner

Use the first answer to see how to run the system file checker as administrator.

Some say to check the hard drive(s) with a hard drive diagnostic tool, as it may be an I/O error between the HDD and the keyboard. Similarly, it's then wise to update the motherboard chipset drivers. you can check for the chipset with CPU-Z.

---

Awesome, never knew things like this software exist. Now, does this mean anything to any of you?

031016-26535-01.dmp 2016/03/10 21:59:27 CRITICAL_OBJECT_TERMINATION 0x000000f4 00000000`00000003 fffffa80`0bfe1b10 fffffa80`0bfe1df0 fffff800`03186780 ntoskrnl.exe ntoskrnl.exe+74080 NT Kernel & System Microsoft® Windows® Operating System Microsoft Corporation 6.1.7601.19160 (win7sp1_gdr.160211-0600) x64 ntoskrnl.exe+74080 C:\Windows\Minidump\031016-26535-01.dmp 8 15 7601 417 885 2016/03/10 22:01:46

030516-22105-01.dmp 2016/03/05 16:16:45 CRITICAL_OBJECT_TERMINATION 0x000000f4 00000000`00000003 fffffa80`0c56e060 fffffa80`0c56e340 fffff800`03182e80 rdpbus.sys rdpbus.sys+4f2c060 Microsoft RDP Bus Device driver Microsoft® Windows® Operating System Microsoft Corporation 6.1.7600.16385 (win7_rtm.090713-1255) x64 ntoskrnl.exe+743c0 C:\Windows\Minidump\030516-22105-01.dmp 8 15 7601 417 693 2016/03/05 16:19:27

I forgot about NirSoft. They have some really helpful software. I'm surprised that SysInternals doesn't have something like that.

Yes.

But he can better use Nirsoft BlueScreenView to easily find that information.

---

Right click on my computer, then click on properties. Then Advanced/Startup & Recover/settings. In System Failure, uncheck automatically restart. System then won't restart on BSOD.

If "Write an event to the system log" is already checked, wouldn't there already be information saved from both BSoDs for Mog to view or copy/paste here?

Right click on my computer, then click on properties. Then Advanced/Startup & Recover/settings. In System Failure, uncheck automatically restart. System then won't restart on BSOD.

No worries.

---

Grant
Darwin NT

No problem, Grant. I'll just switch to another project and leave Seti on Astropulse only.
Thank you for taking the time and try to help.

It went by so fast I couldn't read what it says, and I'm not about to try and recreate the problem.

Which will make it next to impossible for people to help you with the fault that you- and it would appear from the lack of similar issues over the last few months it's only you- are experiencing. Add to that your computers are hidden so people can't check your system details or any of the results you have returned to see if there's anything of use there either.

---

Grant
Darwin NT

Apparently I was updated to v8 automatically. Got two BSoD since. Seti only comes on after inactivity, and the BSoD happened when I moved the mouse and the WU got suspended again. It went by so fast I couldn't read what it says, and I'm not about to try and recreate the problem. Two days of lost work is quite enough. That's what beta testing is for.

Seti runs on a Gigabyte GTX 750Ti (GV-N75TOC-2GI) on Windows 7 64-bit.