Jump to content

Welcome to Geeks to Go - Register now for FREE

Geeks To Go is a helpful hub, where thousands of volunteer geeks quickly serve friendly answers and support. Check out the forums and get free advice from the experts. Register now to gain access to all of our features, it's FREE and only takes one minute. Once registered and logged in, you will be able to create topics, post replies to existing threads, give reputation to your fellow members, get your own private messenger, post status updates, manage your profile and so much more.

Create Account How it Works

Stop 0X000000F4; computer reboots constantly

  • Please log in to reply



    New Member

  • Member
  • Pip
  • 1 posts

My computer has been rebooting constantly for the past 2 weeks, more so in the last couple of days. At first my puter was going to a blue screen which gave me the error message: kernel_stack_inpage_error. I researched this and was told to do a virus check, which I ran about 6 times. No virus'.

Then it started giving me the same blue screen but with a different message on top with the number sequences: 0X000000F4 (0X00000003, 0X86CB16A0, 0X86CB1814 and then I didn't catch the last sequence). I also researched this (0X000000F4) and came upon a thread on this website.

I conducted a memory test on memtest.org. Ran 3 passes all good. Now I am about to run a HW diagnostic test as soon as I find a flippin floppy disk in the attic. I'm pretty good at researching what the problem is with my computer and fixing it (per the instructions I find) but I've never come across this before. Can someone tell me what I need to do next or what the problem might be. I'll report back after I've done the HW test.

I have XP SP2.

  • 0




    Trusted Tech

  • Banned
  • PipPipPipPipPip
  • 2,663 posts
The STOP error codes are crucial in pinpointing the cause of the problem, that is if you can find a good and easy to understand reference resource! I can tell you, however, that in my case the cause of the 'kernel_stack_inpage_error' message was tracked down to a failing hard disk which was less than two years old.
  • 0

Similar Topics

0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users

As Featured On:

Microsoft Yahoo BBC MSN PC Magazine Washington Post HP