Blue Screen Dump Files

I've been trying to reinstall vista for a couple of days now and always get a blue screen at some point when using the newly installed OS. It usually happens immediately after logging in. I've ran CHKDSK several times and it never finds any errors. I've attached several of the dump files and hope that someone could give me an idea of what's causing the problem.

Regards

Hello jlsparks,
As you can see, three dump files and three different causes.

STOP 0x000000D1: DRIVER_IRQL_NOT_LESS_OR_EQUAL
Usual causes: Device driver
Probably caused by ecache.sys


STOP 0x0000008E: KERNEL_MODE_EXCEPTION_NOT_HANDLED
Usual causes: Insufficient disk space, Device driver, Video card, BIOS, Breakpoint in startup without having a debugger attached, Hardware incompatibility, Faulty system service, 3rd party remote control, Memory
Probably caused by Memory corruption


STOP 0x0000000A: IRQL_NOT_LESS_OR_EQUAL
Usual causes: Kernel mode driver, System Service, BIOS, Windows, Virus scanner, Backup tool, compatibility
Probably caused by ntkrpamp.exe

First open a command prompt as administrator and type sfc/scannow press enter and let it scan, if errors are found you may need to do this more than once, until system is clean.

If it completes the scan with no BSOD, remove all your memory and try one stick at a time. this will eliminate the memory.

If anything is overclocked, set it back to default.

Remove any USB devices, printers, BT, external HDD's.

Check that the system is getting enough cooling, check vents and fans are running.

Just for now, remove your AV. (don't forget to reinstall)

Have you added any new hardware/software ?.


As this is a fresh install, do you have all the drivers installed, sound, video, chipset, and any others you need ?.

Some malware can affect the system files, so just to be sure, scan with this free app.

Malwarebytes


What prompted you to re-install the OS ?.

Give this a try, if you need any more help just ask, good luck and post your results.

Thanks for the quick response!

I had to re-install Vista again since my last post because I would get the BSOD before I could run anything. After the re-install I got the BSOD during the first complete startup, but I've not had any more up to this post. The minidump is attached. After running sfc/scannow I get "Windows Resource Protection found corrupt files but was unable to fix some of them. Details are included in the CBS.log" I've included that here as well. I also ran Malwarebytes (finished clean) and attached the log.

My system in not overclocked, I checked all my fans (cleaned them and made sure they were all running at an appropriate speed), disconnected all non-essential hardware, and I'm currently testing each stick of memory one at a time.

I have not installed any nonessential drivers yet just to be sure they won't cause any additional problems, and at the time of posting there is no additional software installed, save Malwarebytes.

I decided to go back to Vista a few days ago after getting a BSOD. It was the excuse I needed to finally go back after struggling for months with NIC problems with Windows 7. I believe the blue screen I recieved then was caused by a virus corrupting registry files, and thought reinstalling the OS would solve that. So far, I've done clean installs each time and always get the BSOD at some point or another. This leads me to believe it may be a memory issue entirely, given recent success with just one stick.

Thanks for your comments and any additional input is much appreciated!!

Hello,

All I have just done is parse your CBS log file for easy reading, and I will leave the BSoD part for Stoneys-Nutz, as he is doing that. Also, I have to urgently go offline now, so sorry that I have not explained how to fix the errors. For your interest, here is how to parse the CBS.log for next time (top yellow box) Believe me when I say that you are in the best hands for BSoDs with Stoneys-Nutz. http://www.vistax64.com/tutorials/66978-system-files-sfc-command.html

Richard

Thanks!

Using this site How to use the System File Checker tool to troubleshoot missing or corrupted system files on Windows Vista or on Windows 7 I've been able to replace the corrupted .dll files sfc couldn't fix. I scanned again with sfc and it found no errors this time. I guess for now I'll continue testing ram sticks to see if one is the culprit. So far so good on the first one.

Well done on replacing that file. Sorry I was not of more help and good luck testing that memory.

Richard