Diskeeper FUBARed my page file?

[Abunai]

I just had a BSOD and I think Diskeeper freaked out because of it. My page file used to be on the first row and now its all the way on the bottom. I didnt set a boot-time defrag or anything. Ive never had a bad experience with Diskeeper, but Ive never seen it move the page file on its own volition like this. Here's a cap of what my drive looks like now...

http://img103.echo.cx/img103/1378/diskeepercap8yf.jpg

Ive since defragged because it was pretty badly fragmented but there was a big empty space on the top left corner where the page file used to be. Anything to worry about? I remember reading somewhere that a computer can get pretty sluggish depending on the placement of the page file on the drive.

 

[Nothinman]

Placement of the pagefile will not cause a BSOD unless there's bad sectors on that portion of the disk.

 

[Abunai]

No I didnt mean to infer the placement of the pagefile caused the BSOD. Im not sure what caused that yet. Im saying I think the BSOD may have resulted in my page file being moved for some reason. First it was on the top bar (front of disk?) and post-BSoD its now on the bottom bar (end of the disk?). Im trying to figure out why that happend and if its anything to be concerned about.

 

[2cpuminimum]

Maybe your pagefile was deleted and then recreated by windows. Or got tired of the inner sectors of the HD and decided to move. run chkdsk and if it doesn't find any reason to be concerned, there probably isn't one. Except for the BSOD, how did you get a BSOD? hardware failure or software? The bsod is cause for concern, the pagefile moving is not. If you really want it to sit still, put it on its own partition and set min=max=1024MB.

 

[Nothinman]

IIRC as of XP the built-in defrag routines allow movement of the pagefile, so that shouldn't cause any problems either. Perhaps if you would post what STOP code the BSOD was,then we can all stop guessing.

 

[Phoenix86]

Originally posted by: Nothinman
IIRC as of XP the built-in defrag routines allow movement of the pagefile, so that shouldn't cause any problems either. Perhaps if you would post what STOP code the BSOD was,then we can all stop guessing.

I didn't think the built in defragger could touch the PF at all... If it is related to the movement of the PF then it's likely bad sectors on the HDD like you said. That would generate page_fault_in_nonpaged_area, but yeah he could just post the actual error. Then we can all put our crystal ball away.

 

[Bozo]

During the BSOD, XP did a memory dump to the page file area. If the page file was too small, it got moved.
Check the event viewer to find the problem.

Bozo

 

[Nothinman]

I didn't think the built in defragger could touch the PF at all...

I don't think it does, but he said he's using DiskKeeper and the screenshot he posted is of the full version. But that doesn't mean XP doesn't provide an API to do that.

 

[corkyg]

Why not just delete the page file, reboot, and Windows will build a new one.

 

[Phoenix86]

Originally posted by: corkyg
Why not just delete the page file, reboot, and Windows will build a new one.

Because if the cause is bad sectors, he's going to want to know that sooner rather than later...

 

[Abunai]

perhaps it wasn't a BSoD, those are supposed to stay on right? (Ive honestly never encountered one before) It was blue with serveral lines of yellow text but it flashed by incredibly quickly and rebooted on its own before I could make it out. All I could read was something about a driver error.

I might know what caused it now, I was overclocking the CPU the night before, Prime stable for 12 hours. Humidity went way up though and I didnt like the temps (52c 100% load) so I reverted to default clocks in the BIOS, or so I thought. Somehow I didnt save changes to CMOS and have been running the same clock since. I had Firefox and Prime running (large FFT) while downloading a big avi file when it happened, perhaps the temps got too high and caused some type of error? How that relates to the Page File moving on its own Im not sure.

I ran CHKDISK and it didnt come up with anything. Couldn't find anything relevant in the Event Viewer either.

 

[Nothinman]

perhaps it wasn't a BSoD, those are supposed to stay on right?

There's a setting to automatically reboot after a STOP error, sadly it's turned on by default.

 

[Bozo]

To turn off auto reboot, go to Control Panel>System. Open the Advanced tab. In the Startup an Recovery window, click on Settings. There you can uncheck the box to automatically restart. You can also see the drop down list as to what gets dumped to the hard drive.
Like I said before, If there was more files in memory than the page file could handle, then the page file got move and made larger.

Bozo