Win7 64bit reboots.

[hinerakatauri1979]

I have a problem where windows just restarts, even if I am not doing anything. I have tried keeping drivers default and updating them to last version.

I have also done a memory test and it did not detect any problems.

Could someone please look at my dump and advice.

 

[hinerakatauri1979]

I added another dump file.

 

[Night Hawk]

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.?

 

[hinerakatauri1979]

Hi restarts are random, sometimes 5 times a day the 1 week ok. I have tested it for temp problems and my cpu and gpu temps stay well within the normal range. I also have updated the bios to the last version.

Strange thing is that my vista installation (which i replaced with windows 7) never had this problem.
All my drivers are for windows 7. I also have tested my memory many times and even a 12 hour marathon. it didn't show any problems. When playing games it almost never reboots. reboots are mostly when it is idle.

 

[usasma]

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

 

[Night Hawk]

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.

 

[hinerakatauri1979]

I tried the verifier, but when enabled it keeps rebooting. I can see my login screen and then it reboots.
I've let it do that for 5 time, then disabled the verifier in Safe mode.

 

[Night Hawk]

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.

 

[usasma]

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.

 

[evilgod905]

laptop or computer?

if your using a computer did u mix up 2 type of different rams?, i had the same problem my windows kept restarting.

 

[Night Hawk]

That will cause immediate problems if this is being seen on a brand new build or you added additional memory in lately. You didn't fill out your system specs or provide that information that might be a help here in solving the problem.

Note that problems with power supplies while most of the draw is seen during the post tests can also play a role. If the board is a year old+ you may have to replace the battery on it as another possible cause. Once a battery becomes weak you will tend to see sudden restarts out of the clear blue! Eventually you will press the power button one day and then see nothing! when a battery goes completely.

These are some other things to consider before assuming any hardware fault being realized.

 

[hinerakatauri1979]

I think I've solved the problem. not sure why vista didn't have a problem.
I tried different memory settings, did not help, tried increasing memory voltage did not help. What did help was lowering the FSB frequency from 333 to 332. with 333 memory was slightly overclocked by default. with 332 it is 1 Mhz lower.

 

[Night Hawk]

That would suggest it was still memory related but not for the same reason as finding a bad dimm or mismatch. By lowering the memory clock a bit it appears all the memory installed is now keeping pace as it should with matched timings.

The 332 x 2 = 664mhz still applies. But at least you made some headway there.

 

[hinerakatauri1979]

Actually this is my specs now:
Specification Intel(R) Core(TM)2 Quad CPU Q8200 @ 2.33GHz ( running at 2326Mhz)

CM2X2048-8500C5 2x (running at
Memory Frequency 534.6 MHz (5:8)
CAS# latency (CL) 5.0
RAS# to CAS# delay (tRCD) 7
RAS# Precharge (tRP) 7
Cycle Time (tRAS) 24
Row Refresh Cycle Time (tRFC) 68
Command Rate (CR) 2T
MCHBAR I/O Base address 0x0FED14000
MCHBAR I/O Size 4096

 

[Night Hawk]

That seems to be working out for you there. Since you found things more stable with the slower timings that suggests the board is a little particular about what memory goes on.

I noticed the memory was at 2.1v in the text file you added. Have you tried changing that at all like dropping it to 1.9-1.95v? Memory will tend to run cooler with the lower voltage setting.

 

[hinerakatauri1979]

I want to test my system for a few days before trying something.

 

[Night Hawk]

I can readily agree with that. Presently the 4gb of PC2-6400 memory used here stays at 1.8v 4-4-4-12 2T and has been doing well since Dec. 2008. CPU-Z shows the 1.8v there. That's DDR2 800 however that will run that low.

Otherwise at least according to someone at the Corsair forum and as long as your cpu supports the speed you simply load the optimal defaults in the bios with the 2.1v for that memory to see 5-5-5-15 2T

Mostly this was a problem seen with the 64bit Vista seeing reboots due to an incompatibility with hardwares. But you also saw problems simply getting the older 64bit Windows on with more then 2gb installed as well. The only other to look at would be the HPET setting there to see if that is enabled. Otherwise see how it goes for now.