Win7 64bit reboots.

You may be facing either temp or hardware problem even a weak battery on the board itself. The last RC installation here put on back in May was just removed a week ago when a new drive replaced another seeing the 32bit 7 replace the 64bit RC.

I've been looking over the "Debugging Tools for Windows - Native x64" with the latest being the March 27th release available at Install Debugging Tools for Windows 64-bit Version#

The information with that shows: "Probably caused by ntoskrnl.exe ( nt+71f00 )" without quotations. The question now is how frequent are the restarts? every 2hrs.?

Not much useful information in the dump files. The most significant (IMO) is the presence of Ppm in the stack text. This is the Executive accessing the PnP Manager. Please disconnect all USB devices while we're testing this problem.

And then, please try running Driver Verifier (without the USB devices). If you don't get a BSOD within 36 hours, then try it with the USB devices plugged in. Please follow these instructions:

Using Driver Verifier is an iffy proposition. Most times it'll crash and it'll tell you what the driver is. But sometimes it'll crash and won't tell you the driver. Other times it'll crash before you can log in to Windows. If you can't get to Safe Mode, then you'll have to resort to offline editing of the registry to disable Driver Verifier.

So, I'd suggest that you first backup your stuff and then make sure you've got access to another computer so you can contact us if problems arise. Then make a System Restore point (so you can restore the system using the Vista/Win7 Startup Repair feature).

Then, here's the procedure:
- 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.

Reboot into Windows (after the crash) and turn off Driver Verifier by going back in and selecting "Delete existing settings" on the first page, then locate and zip up the memory dump file and upload it with your next post.

If you can't get into Windows because it crashes too soon, try it in Safe Mode.
If you can't get into Safe Mode, try using System Restore from your installation DVD to set the system back to the previous restore point that you created.
If that doesn't work, post back and we'll have to see about fixing the registry entry off-line.

More info on this at this link: Using Driver Verifier to identify issues with Windows drivers for advanced users

I came up dry with the dump files there as well. Without any indication of a temp or hardware problem the next step would be looking at a driver or set hanging on you or one of the startup items triggering a restart for an unfinished update that never completed the installation.

Hopefully the driver verifier tool there will help narrow it down.

While you are safe mode go into the msconfig utility and disable all startup items in the startup tab there. Type "msconfig" at the Run command line to open that up.

Have you installed anything new right before seeing the series of restarts? Take a look at the last thing that went on as one likely cause.

Please check the C:\Windows\Minidump folder for additional dump files (that's what Driver Verifier is supposed to do).

If you find them, please zip them up and upload them so we can have a look at them.