BSOD restoring from Hibernation in XP Pro SP2

[Guest]

I have a new Desktop, sp2 w/ 512 mb Ram.

Two problems, really:
I can hibernate fine, but if I try to bring it back up, the computer hangs
on trying to load the OS off a disc - which I made sure in BIOS it shouldn't
do.
I have to turn it off, then it tries to load and presents me with a BSOD.
Restarts, and unless I select, delete restoration data, we go through it all
again.

Now, normal restarts are almost as hard. It turns off, then I see three
screens: One is a memory test, The next gives me the option to enter config
for RAID, the third is a list of IDE, where it will generally hang.
I turn it off again, and then it works fine.

What the Helzinky is going on?!

And PUHLEEZE don't tell me to mess with its innards or drivers- I just got
those all working!

Lara

 

[Guest]

The BSOD is
kernel stack inpage error

This only happens when I try to restore from hibernation.
Turning of system caching does nothing.

This is an entirely new computer, and has never been on the internet, so it
should not have a virus.
I have run chckdisk and it came up clean.

I will be running a memory test in a few moments.
A few other things on this pc have been screwed up by the builder- it was
custom built for me.
Is this something massively wrong? Or do I just need a screwdriver and a few
hours to fix it?
I'd really rather have the computer than have to return it. But I don't
relish the idea of tinkering in it.

 

[Ron Martell]

The BSOD is
kernel stack inpage error

This only happens when I try to restore from hibernation.
Turning of system caching does nothing.

This is an entirely new computer, and has never been on the internet, so it
should not have a virus.
I have run chckdisk and it came up clean.

I will be running a memory test in a few moments.
A few other things on this pc have been screwed up by the builder- it was
custom built for me.
Is this something massively wrong? Or do I just need a screwdriver and a few
hours to fix it?
I'd really rather have the computer than have to return it. But I don't
relish the idea of tinkering in it.

From http://www.aumha.org/win5/kbestop.htm
"0x00000077: KERNEL_STACK_INPAGE_ERROR
A page of kernel data requested from the pagefile could not be found
or read into memory. This message also can indicate disk hardware
failure, disk data corruption, or possible virus infection."

There should be 4 parameter codes included in the error message, which
are important for diagnosing the probable cause of the error.
From http://msdn2.microsoft.com/en-us/library/ms794027.aspx
"If the first parameter is 0 or 1, the stack signature in the kernel
stack was not found. This error is probably caused by defective
hardware, such as a RAM error.

If the first parameter is 2, the driver stack returned an inconsistent
status for the read of the page. For example, the driver stack
returned a success status even though it did not read the whole page.

If the first parameter is any value other than 0, 1, or 2, then the
value is an NTSTATUS error code that is returned by the driver stack
after attempting to retrieve the page. The precise cause of this error
can be determined from the I/O status code (the second parameter). "

Hope this is of some assistance.

Good luck


Ron Martell Duncan B.C. Canada
--
Microsoft MVP (1997 - 2006)
On-Line Help Computer Service
http://onlinehelp.bc.ca
Syberfix Remote Computer Repair

"Anyone who thinks that they are too small to make a difference
has never been in bed with a mosquito."

 

[Guest]

Using Event Viewer, here are the parameters I found:
1 c000000e
2 c000000e
3 00000000
4 01b13000

If my RAM'S the trouble, what can I do?

 

[Ron Martell]

Using Event Viewer, here are the parameters I found:
1 c000000e
2 c000000e
3 00000000
4 01b13000

If my RAM'S the trouble, what can I do?

From those error parameters I suspect that the primary suspect should
be the hard drive.

Go to the hard drive manufacturer's web site and download their free
diagnostic test utility. Run that to check out the drive for hardware
problems.

Good luck

Ron Martell Duncan B.C. Canada
--
Microsoft MVP (1997 - 2006)
On-Line Help Computer Service
http://onlinehelp.bc.ca
Syberfix Remote Computer Repair

"Anyone who thinks that they are too small to make a difference
has never been in bed with a mosquito."

 

[Guest]

Alright, I have a Maxtor 200 gig hard drive, which, from research, seems to
be susceptible to one particular problem: boot sector corruption after
unexpected power loss. It has been accidentally switched off since I got it.

Its format is NTFS, not FAT. All the boot sector recovery software I can
find seems to want a FAT format.

Can you recommend any software that would find and fix this problem- if I
have it- without killing my data or, at least, my OS?

Please? Thank you so much for your help!

 

[Ron Martell]

Alright, I have a Maxtor 200 gig hard drive, which, from research, seems to
be susceptible to one particular problem: boot sector corruption after
unexpected power loss. It has been accidentally switched off since I got it.

Its format is NTFS, not FAT. All the boot sector recovery software I can
find seems to want a FAT format.

Can you recommend any software that would find and fix this problem- if I
have it- without killing my data or, at least, my OS?

Please? Thank you so much for your help!

Start with the Maxtor factory diagnostic test. Download the utility
from
http://www.seagate.com/ww/v/index.j...toid=a37d8b9c4a8ff010VgnVCM100000dd04090aRCRD

Boot sector corruption would normall manifest itself in a very obvious
way - the drive won't boot at all. I suspect that your problem is
something different.

If your computer does not have a 3.5 inch diskette drive to create the
Maxtor diagnostic disk the post a response back here and I will try to
help you work around this issue.

Good luck
Ron Martell Duncan B.C. Canada
--
Microsoft MVP (1997 - 2006)
On-Line Help Computer Service
http://onlinehelp.bc.ca
Syberfix Remote Computer Repair

"Anyone who thinks that they are too small to make a difference
has never been in bed with a mosquito."

 

[Guest]

Hi LaraPhoenix, is your Desktop based on an Asus Motherboard with the Nforce4
Chipset?
If that's the situation don't worry about your hard drive or your memory
modules, simply disable ACPI function in BIOS and disable all energy savings
in your Operating System.
If this works, then the only way is to wait the manufacturer and/or MS
develop Bios version or new ACPI Driver the OS can manage better.