Memory error message while shutting down Windows

Forums › Microsoft Windows › Memory error message while shutting down Windows

jolsba

1 post

Wannabe Geek

#11091 1-Jan-2007 14:22

Please help! I just bought a Compaq Presario V3018CL notebook computer. I am wondering why 8 out of 10 times while shutting dowm Windows, I always get the error message that says "the instruction at ox5ad71531 referenced at 0x00000014. The memory could not be "read". Click on ok to terminate the program. Click cancel to debug the program. Aclick on either has not helped. Neither has numerous calls to HP Tech guys been helpful either. Anybody with solution(s) to this nagging error mesage?

[Moderator edit (MF): moved to Windows forum]

freitasm

BDFL - Memuneh
79263 posts

Uber Geek

Administrator

ID Verified

Trusted

Geekzone

Lifetime subscriber

#56695 1-Jan-2007 14:27

Welcome to Geekzone... This could be either a bad program or a faulty memory. I recommend you try the Microsoft Windows Memory Diagnostic tool. It will help you create a bootable CD that will run memory tests. If it identify errors then you can call the technician and ask for repair.

If everything else is ok, then start looking at which programs you have installed, and make sure to run and antivirus and an antispyware. I recommend Avast and Microsoft Windows Defender, they are both free. Make sure you only have one of each type (one antivirus and one antispyware) on your system otherwise it can cause conflicts.

Also firewall programs can cause these problems.

weblordpepe

460 posts

Ultimate Geek
Inactive user

#57115 6-Jan-2007 18:03

Yeah I would lean towards either:

Faulty hardware (memory or hard drive) - suggest as freitasm suggested

Faulty drivers. Drivers working at the kernel layer and stuff can touch the OS in all sorts of interesting & dirty ways, and if they're crooked then you can get errors which appear to be hardware errors. - Check any non-OEM drivers that were installed since the problems started.

Windows XP basically never blue screens these days unless its a drivers issue or a hardware issue. Or a wacky kernel configuration issue (thanks PAE and Embedded VC++).