BleepingComputer.com: Vista X64 Won't Load Into Normal Mode

Jump to content


Register a free account to unlock additional features at BleepingComputer.com
Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.

Click here to Register a free account now! or read our Welcome Guide to learn how to use this site.

Page 1 of 1
  • You cannot start a new topic
  • You cannot reply to this topic

Vista X64 Won't Load Into Normal Mode 0x000000E4 error

#1 User is offline   sld72382 

  • New Member
  • Pip
  • Find Topics
  • Group: Members
  • Posts: 5
  • Joined: 30-May 06

Posted 10 August 2008 - 09:10 AM

Hopefully this won't come down to a format. :huh:

My Vista x64 box won't load into normal mode, when I try to, I get the blue screen with the error 0x000000E4 (very next set of numbers are all 0's). I tried 2 last known good configurations and 1 system restore, that used to work but it doesn't anymore.

I tried updating the drivers for my video card and it didn't work.

Any help would be appreciated!

If I do need to format, thank goodness I have an eSATA drive that works in safe mode.

Oops forgot the specs:

Vista Ultimate x64
E6600
8800GTS
2 250GB hard drives in raid 0
Asus P5N-E mobo
Corsair power supply

This post has been edited by sld72382: 10 August 2008 - 11:06 AM

#2 User is offline   usasma 

  • Still visually handicapped, new avatar (a camel) :0)
  • PipPipPipPipPipPip
  • Find Topics
  • Group: Members
  • Posts: 16,689
  • Joined: 02-October 05
  • Gender:Male
  • Location:Southeastern CT, USA

Posted 10 August 2008 - 07:29 PM

STOP 0xe4 is usually caused by a driver freeing memory that it's not supposed to touch (namely, a worker thread from the executive).
The most likely culprit would be your video drivers - but an examination of the memory dump from it may tell us what it is.

Here's a link to how to examine memory dumps: http://forums.majorgeeks.com/showthread.php?t=35246
Copy and paste the analysis here for us to have a look at and we'll see what we can find.
- John
**If you need a more detailed explanation, please ask for it. I have the Knack. **

Share this topic:


Page 1 of 1
  • You cannot start a new topic
  • You cannot reply to this topic

1 User(s) are reading this topic
0 members, 1 guests, 0 anonymous users