• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1945
  • Last Modified:

Vista BSOD 0x000000BE "An Attempt Was Made to Write to read Only Memory"

Relatively new Vista Home installation on Dell Inspiron 531.  Was running fine, then suddenly it BSOD's on boot with Stop 0x000000BE "An Attempt Was Made to Write to read Only Memory".  Vista repar does not fix it.  cannot boot into safe mode.  I cannot boot to the safe mode or safe mode with command prompt.  

Screen shot attached.  Would appreciate assistance resolving this.  
IMG00048-20100903-1118.jpg
0
doughonea
Asked:
doughonea
1 Solution
 
NuttycomputerCommented:
This is usually caused by a faulty driver or device. Start removing peripheral devices one at a time until your to bare components. Mouse Keyboard Monitor.

If you get that far and still have the error appearing you need to start opening it up and remove any components that are un-needed for minimal boot. This would be any 3rd party cards or extra video cards etc.

Hopefully by systematically removing each of these you'll discover where the problem lies.

0
 
doughoneaAuthor Commented:
If it helps, I was able to recover the memory dump.  It is attached.

Also, when I run startup repair, it BSOD's with the same error.  I have disabled everything in board except the hard drive and USB (since I need that for the keyboard).  I tried unplugging both keyboard and mouse and still errors.
MEMORY.zip
0
 
NuttycomputerCommented:
Looking at the memory dump from the following in it "IMAGE_NAME:  ntkrpamp.exe" this lists the probable cause of the BSOD which is the NT Kernal System.

Based upon this information it looks like it may be faulty memory. Remove all your memory sticks except one or two (depending on size and quantity) Try to boot with that alone. If no go swap the slot your final memory stick is in. If no go swap that stick out with one of the other ones you pulled out.
FOLLOWUP_IP: 
nt!KiTrap0E+dc
81e55dd4 85c0            test    eax,eax

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt!KiTrap0E+dc

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrpamp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4b7d1e08

FAILURE_BUCKET_ID:  0xBE_nt!KiTrap0E+dc

BUCKET_ID:  0xBE_nt!KiTrap0E+dc

Followup: MachineOwner

Open in new window

0
New feature and membership benefit!

New feature! Upgrade and increase expert visibility of your issues with Priority Questions.

 
che6auscCommented:
A 3rd party driver has passed bad data to the kernel(nt).  Update all your major drivers from the manufacturer of the hardware(i.e. network, graphics, chipset,etc).    Also look for a bios update for your motherboard.  Run memtest86  for at least 3 passes to rule out memory as a cause.
http://www.memtest.org/

Post system specs if you cannot find drivers.
0
 
doughoneaAuthor Commented:
How can I update the drivers if it won't boot?
0
 
doughoneaAuthor Commented:
Also, I tried swapping all the RAM chips, etc.
0
 
NuttycomputerCommented:
doughonea,

If the memory swap failed then unfortunately it looks like it may be the OS or a faulty driver as che6ausc stated. Unfortunately because you can't get into Safe Mode it complicates things.

What I suggest doing now is getting your Windows Vista disk and loading into the Repair/recovery console from the disk. If it asks if you want to run Startup Repair or Automatically repair select no. Instead we are going to want to run a System Restore to an earlier date to clear out any drivers or updates that may have caused this.

For a graphical tutorials see this link: http://www.bleepingcomputer.com/tutorials/tutorial142.html
0
 
NuttycomputerCommented:
Additionally if System Restore fails to resolve the issue then you have to decide if it's worth it to try to recover or not. If you have the availability to just backup files and reinstall a fresh copy of windows that might be easier than the next suggestion found at this KB Article http://support.microsoft.com/kb/927525 which involves finding the last driver installed and disabling it if it isn't required to start computer.
0
 
doughoneaAuthor Commented:
When I choose the repair option, it starts searching for the Windows installation and then BSOD's.  Sigh....

Guess I am going to have to reformat.
0
 
doughoneaAuthor Commented:
Is there any way to determine which driver is causing the problem, so I might be able to rename that file and get the system to boot?  If I can boot it I can repair Vista with the DVD.
0
 
NuttycomputerCommented:
Unfortunately the memory dump isn't indicating a specific driver. If you know what drivers may have been installed right before this happened then you can try those but based on the fact that the memory dump provides an indescript message and that you can't even launch repair from the CD it looks like the OS itself is dead. :(
0
 
doughoneaAuthor Commented:
It's not my computer and the user isn't very reliable for telling me what she did.  :-(

0
 
doughoneaAuthor Commented:
I will hold this open for a day and see of anybody else has anything to offer.  
0
 
NuttycomputerCommented:
If it's any consolation you can make the restore of files process less painful. I would recommend doing a backup anyway but when you reinstall windows don't do a format just let it install over the current windows installation.

If it detects it like it should it will move all those files into a folder called Windows.old greatly increasing recovery time. If not then you still have your offsite backup and nothing is lost.
0
 
doughoneaAuthor Commented:
I have a Ghost image of the machine, but you're right, this is easier.  Not sure why they did away with the repair install that they had in XP.  
0
 
NuttycomputerCommented:
"Not sure why they did away with the repair install that they had in XP."

The old repair install caused a lot of problems and people thought it was something it wasn't. It was designed to get the computer to a working state so that backups of files could be made before a complete format and reinstall. Unfortunately a lot of people just assumed that it "fixed" everything but instead further down the line one would see a lot of Registry issues start to crop up as well as file association errors.

In other words the repair install was a holy mess and I'm glad they got rid of it :)
0
 
doughoneaAuthor Commented:
The expert was very responsive.  I didn't get the answer i was hoping for, but I did learn that I had reached the point that I needed to just move on.
0
 
cheekymediaCommented:
Thanks to this thread, I resolved my continuous windows server 2008 boot loop by removing all 4 1GB memory and adding back one by one.  One of them was the guilty party, as with 3GB installed and one on my desk, the server boots perfectly.  Thanks.
0

Featured Post

How to Use the Help Bell

Need to boost the visibility of your question for solutions? Use the Experts Exchange Help Bell to confirm priority levels and contact subject-matter experts for question attention.  Check out this how-to article for more information.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now