Solved

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

Posted on 2010-09-03
18
1,827 Views
Last Modified: 2012-05-10
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
Comment
Question by:doughonea
18 Comments
 
LVL 6

Expert Comment

by:Nuttycomputer
ID: 33597717
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
 

Author Comment

by:doughonea
ID: 33597870
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
 
LVL 6

Expert Comment

by:Nuttycomputer
ID: 33598083
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
 
LVL 6

Expert Comment

by:che6ausc
ID: 33598118
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
 

Author Comment

by:doughonea
ID: 33598162
How can I update the drivers if it won't boot?
0
 

Author Comment

by:doughonea
ID: 33598169
Also, I tried swapping all the RAM chips, etc.
0
 
LVL 6

Expert Comment

by:Nuttycomputer
ID: 33598202
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
 
LVL 6

Expert Comment

by:Nuttycomputer
ID: 33598225
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
 

Author Comment

by:doughonea
ID: 33598347
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
Maximize Your Threat Intelligence Reporting

Reporting is one of the most important and least talked about aspects of a world-class threat intelligence program. Here’s how to do it right.

 

Author Comment

by:doughonea
ID: 33598360
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
 
LVL 6

Expert Comment

by:Nuttycomputer
ID: 33598381
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
 

Author Comment

by:doughonea
ID: 33598394
It's not my computer and the user isn't very reliable for telling me what she did.  :-(

0
 

Author Comment

by:doughonea
ID: 33598402
I will hold this open for a day and see of anybody else has anything to offer.  
0
 
LVL 6

Accepted Solution

by:
Nuttycomputer earned 500 total points
ID: 33598421
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
 

Author Comment

by:doughonea
ID: 33598437
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
 
LVL 6

Expert Comment

by:Nuttycomputer
ID: 33598468
"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
 

Author Closing Comment

by:doughonea
ID: 33599532
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
 

Expert Comment

by:cheekymedia
ID: 35229179
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

What Security Threats Are You Missing?

Enhance your security with threat intelligence from the web. Get trending threat insights on hackers, exploits, and suspicious IP addresses delivered to your inbox with our free Cyber Daily.

Join & Write a Comment

The main issue when installing Vista and XP in dual boot is when you have to reinstall any of the two when something fails, let's say a hard disk failure, a lost partition, virus, etc. What commonly happens is that you lose all your hard work config…
The Service applet starts in Extended Mode by Default, with a taskpad on the left of the services pane. This view mode was introduced in XP. As I find it not very usefull, I like to use the Standard view as default, and without the Console tree. …
The Task Scheduler is a powerful tool that is built into Windows. It allows you to schedule tasks (actions) on a recurring basis, such as hourly, daily, weekly, monthly, at log on, at startup, on idle, etc. This video Micro Tutorial is a brief intro…
Get a first impression of how PRTG looks and learn how it works.   This video is a short introduction to PRTG, as an initial overview or as a quick start for new PRTG users.

705 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

17 Experts available now in Live!

Get 1:1 Help Now