Blue Screens and Random Reboots

one stop code is 101, which we have discussed before.

Code:

BugCheck 101, {31, 0, fffff88002f63180, 2}

Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )

Followup: MachineOwner
---------
PROCESS_NAME:  svchost.exe
BugCheck A, {fffff88003a64d80, 2, 0, fffff80002a8f5db}

Probably caused by : ntkrnlmp.exe ( nt!KiSearchForNewThread+26b )

Followup: MachineOwner
---------
PROCESS_NAME:  javaw.exe

Not sure what to suggest you more, Have you checked this article before?
STOP 0x101: CLOCK_WATCHDOG_TIMEOUT troubleshtg

If you had the same problems with Vista, then I am 99.99% sure that somewhere you have a hardware problem/conflict .. were you using the same computer then that you are now??

Tews said:

If you had the same problems with Vista, then I am 99.99% sure that somewhere you have a hardware problem/conflict .. were you using the same computer then that you are now??

+1 I concur.

Lets enable driver verifier and see if we can get some more conclusive .dmp files...follow these instructions...

- Go to Start and type in "verifier" (without the quotes) and press Enter
- Select "Create custom settings (for code developers)" and click "Next"
- Select "Select individual settings from a full list" and click "Next"
- Select everything EXCEPT FOR "Low Resource Simulation" and click "Next"
- Select "Select driver names from a list" and click "Next"
Then select all drivers NOT provided by Microsoft and click "Next"
- Select "Finish" on the next page.

Reboot the system and wait for it to crash to the Blue Screen. Continue to use your system normally, and if you know what causes the crash, do that repeatedly. The objective here is to get the system to crash because Driver Verifier is stressing the drivers out. If it doesn't crash for you, then let it run for at least 36 hours of continuous operation (an estimate on my part).

Have you checked the minidump folder for any new .dmp files??