Stop 0x0000001a MEMORY_MANAGEMENT BSOD

[Guest]

I'm getting a seemingly random BSOD with the stop error of 0x0000001a and a
description of MEMORY_MANAGEMENT.

I'm running Vista Ultimate 32-bit with 4gb of ram (although only 2.75gb
shows available). I'm running an nVidia 680i motherboard with 4gb of
Kingston ram and an Intel quad-core 2.66ghz CPU.

Has anyone else run into this? Is 4gb simply too much for 32-bit Vista?

Thanks

 

[Tim B.]

Sounds like a bad memory module to me.

I'd grab an ISO of memtest86 and run it on your system for a while

 

[Guest]

Actually, I'm having the same problem, only 2GB of RAM. My Windows XP was
running rock stable for over a year with the exact same RAM, but I get random
"Memory Management" errors in Vista. I ran Memtest86 for 12 hours with no
errors. Any other suggestions?

 

[Guest]

Me too. 2Gb RAM same errors, memtest86 ran overnight fine. For me it is
definitely associated with running either Adobe Photoshop Elements 5 or
Google Picassa while importing large numbers of photos....

 

[Chad Harris]

Hi Baxtor--

Not knowing where your other posts are--you sure didn't provide much info.

Can you boot to Vista? ***What in the world have you tried to do to fix
this so far? Did I mention you haven't given any info about whether you get
the BSOD and can still run Vista or you get the BSOD and you're having
problems or can't boot to Vista.

BSODs are often associated with not being able to boot the OS but that sure
isn't aren't always the case.

Have you checked for hardware causes? Have you added any new HDW or
driver(s) for hdw lately?

MSFT has a couple or more MSKBs addressing this issue, but I don't find (as
is sometimes the case) them that helpful. Many apply to Vista but MSFT
hasn't gotten around to labelling many that do for Vista yet and may never.

http://support.microsoft.com/kb/282504

http://support.microsoft.com/kb/885272

http://msdn2.microsoft.com/en-us/library/ms818864.aspx

You asked for a cure, and in several places from what I saw on the web. I'd
try these (again I'd have to be clairvoyant to know if you can boot to
Windows Vista--but I'm signed up for a course in that this semester):

I'd either use System File Checker (and if that does not helpyou), Startup
Repair (if you own a Vista DVD), which does not require a no boot situation
to help you fix many Vista components, or try Sytem Restorefrom either the
Vista DVD's Recovery link or from the F8 menu. Links that show you how to
do this are below.

***SFC as a Remedy***:

SFC or System File Checker is a bit like the spare tire in your car or a
backup battery I suppose. In Vista of course, they have changed it somewhat
and come up with a new name--Redmond stands for name it something different
twice a year and now it's part of WRP or Windows Resource Protection. It
scans protected resources including thousands of files, libraries, critical
folders, and essential registry keys, and it replaces those that are
corrupted with intact ones. It fixes a lot of problems in Windows XP, OE,
Windows Vista, Win Mail, IE6, and on Vista or if it is installed on XP, IE7.
It protects these things from changes by any source including
administrators, by keeping a spare of most of them.


How to Run SFC:

Type "cmd" into the Search box above the Start Button>and when cmd comes up
at the top of the Start menu>right click cmd and click "run as Admin" and
when the cmd prompt comes up at the cmd prompt type "sfc /scannow" no quotes
and let it run. This may fix things quite a bit. It replaces corrupt files
with intact ones, if you're not familiar with it.

If no help from SFC, you can try a restore point to before this happened or
you try the steps below if you have a Vista DVD:

***Startup Repair from the Vista DVD***

How to Use The Vista DVD to Repair Vista (Startup Repair is misnamed by the
Win RE team and it can be used to fix many Vista components even when you
can boot to Vista):

http://www.windowsvista.windowsreinstall.com/vistaultimate/repairstartup/index.htm

If you elect to run Startup repair from the Vista DVD (it can fix major
components in Vista--I've verified this many many times; it's good for more
than startup problems, and the Win RE team simply screwed up when they named
it not understanding its full functionality):

Startup Repair will look like this when you put in the Vista DVD:

http://www.vistaclues.com/wp-content/uploads/2006/12/click-repair-your-computer.png

You run the startup repair tool this way (and system restore from here is
also sometimes effective):

http://support.microsoft.com/kb/925810/en-us

How To Run Startup Repair In Vista Ultimate (Multiple Screenshots)
http://www.windowsvista.windowsreinstall.com/vistaultimate/repairstartup/index.htm

It will automatically take you to this on your screen:

http://www.vistaclues.com/wp-content/uploads/2006/12/click-repair-your-computer.png

That will allow you to go to the Vista setup that has a Repair link on
thelower left corner>click it and then you'll see a gray backgrounded list
and I want you to click Startup Repair from it and follow the directions.

The gray screen after you click the first link in the above pic will look
like this:

http://www.windowsreinstall.com/winvista/images/repair/staruprepair/Image17.gif

Click Startup Repair, the link at the top and after it scans>click OK and
let it try to repair Vista. It will tell you if it does, and if it
doesn't, try System Restore from the Recovery Link on the DVD. If these
don't work booting into Safe Mode by tapping the F8 key and using System
Restore from one of the safe modes besides VGA may work. That means you
have the option to try 4 different safe modes to get to system restore, (one
from the Recovery link on the DVD) and sometimes one will work when the
others won't.

You could also try a Repair Install with Vista which is done exactly the
same way as in XP:

***Repair Install Steps*** (can be used for Vista) MVP Doug Knox
http://www.microsoft.com/windowsxp/using/helpandsupport/learnmore/tips/doug92.mspx


***Using the F8 Environment***

***Taking Full Advantage of the F8 Options (Windows Advanced Options Menu)
by starting the PC and tapping F8 once per second when the firmware screen
with the pc manufacturer's name shows a few seconds after restarting***:

The F8 options in Vista are the same as XP, and the link for Safe Mode Boot
options is labled XP by MSFT but they are the same for Vista (they haven't
updated to add Vista to the title as they have with several MSKBs that apply
to both).

Again, pressing F8 repeatedly when you seem the firmware screen may be is a
generic way to launch Windows RE on some OEM Vista computers.

You could also:

Think: I have 4 different ways to get back my XP at F8 and try 'em in order.
1) Safe Mode 2) Safe Mode with Cmd to Sys Restore which is simply a cmd
prompt in safe mode 3) Safe Mode with Neworking 4) LKG or Last Known Good
Configuration


Try to F8 to the Windows Adv Options Menu>try 3 safe modes there (I don't
use WGA) and Last Known Good>then I go to Win RE in Vista. That gives you a
choice of Safe Mode, Safe Mode with Networking,and Safe Mode with Command
Prompt.

These methods are outlined in

A description of the Safe Mode Boot options in Windows XP/and Vista
http://support.microsoft.com/kb/315222/

Frequently Asked Questions Regarding System Restore from MSFT:

http://www.microsoft.com/technet/prodtechnol/winxppro/plan/faqsrwxp.mspx


System Restore can be run from the Win RE recovery environment from the same
link as Startup Repair, and sometimes it will work from one F8 safe mode
location or from the Win Recovery Environment when it won't work from other
locations.


How to start the System Restore tool at a command prompt in Windows XP

http://support.microsoft.com/default.aspx?scid=kb;en-us;304449

Good luck,

CH

 

[Guest]

Try mscofig boot advanced box limit ram to 1536mb, and run if it works go
back and make it permanent.

 

[DorothyJ]

Hi,

There is a way to stop the PC from rebooting after the BSOD, so you can see
the error messages. I have started taking photos with my digital camera. See
http://www.howtogeek.com/howto/wind...reen-of-death-by-preventing-automatic-reboot/

 

[Mark H]

Have you tried running the verifier.exe command from an elevated prompt?
http://msdn.microsoft.com/en-us/library/ms792861.aspx

This program will slow check each driver as it is used for additional
details and hopefully provide you a better error code to work with as Stop
0x01 is rather generic. Addtionally, the BSOD usually supplies a file name
where the error occurs (e.g. Win32k.sys) and four parameters which could be
helpful in this case.

Lastly, this article may help:
http://support.microsoft.com/kb/935936 (Look near the top for the Hotfix
link.)

 

[Mark H]

Oops... now that I've posted, I realized the error code was 0x1a, not 0x01

 

[Mark H]

Let's try again...
Are you using QuickTime 7?
http://support.microsoft.com/kb/932094
(You can use the hotfix link at the top of the page.)
(Note: This is part of SP1)

 

[snowbound]

I just started having this happen to me. XP sp2, Dell (that was my first
mistake...). I am keeping a log. The BSOD stays until I manually reboot, so
I have no problem writing essential info down. Mine is dumping so often it
is pointless to try to take pic with digital camera: I'm not sure I'd be able
to upload and print. I doubt it is slow RAM. Otherwise it would just be
sluggish, not dump. I am surprised that Microsoft hasn't put out a white
paper on this. Feeling it is going to cost me money to fix.

If anybody actually knows what is going on here, it could save me some time
& $.

 

[Carey Frisch [MVP]]

Somehow you landed in the "Windows Vista" newsgroup.
The "Windows XP" newsgroup is right over here:
http://www.microsoft.com/windowsxp/...g=microsoft.public.windowsxp.help_and_support

--
Carey Frisch
Microsoft MVP
Windows Desktop Experience -
Windows Vista Enthusiast

---------------------------------------------------------------

I just started having this happen to me. XP sp2, Dell (that was my first
mistake...). I am keeping a log. The BSOD stays until I manually reboot, so
I have no problem writing essential info down. Mine is dumping so often it
is pointless to try to take pic with digital camera: I'm not sure I'd be able
to upload and print. I doubt it is slow RAM. Otherwise it would just be
sluggish, not dump. I am surprised that Microsoft hasn't put out a white
paper on this. Feeling it is going to cost me money to fix.

If anybody actually knows what is going on here, it could save me some time
& $.

 

[snowbound]

I landed here because this is apparently the only thread one MS forums that
even mentions this problem, so I added mine. I also posted a new thread in
the windowsxp group. From a general online search, it appears that this is a
common problem that has not been answered satisfactorily, either in Vista and
XP. Amazing to me, though, how many people want to revert to XP from Vista.
Me, next computer I am going to seriously consider something else entirely.

 

[Glen Roberts]

1. Using google I found at least 10 pages of people reporting this
particular error

2. Please perform basic PC testing first before complaining about something

3. If possible, try running in safe mode for awhile and see if the BSOD
still occurs

4. The actual error could quite likely be failed or bad physical RAM
4a - If possible, remove each RAM "board" (one at a time) in your PC and
see if you can work out which one has failed (or is corrupting your memory)
4b - If possible, replace each RAM "board" (one at a time) in your PC
and see if you can work out which one had failed (or is corrupting your
memory)

5. If you have bad or failing RAM, it won't matter what OS you are
running... they will all crash or fail if you have bad RAM in your PC!