|29 Jul 2011||#2|
| || |
Memory management probably caused by a driver.
You have drivers from as far back as 2006.
mdmxsdk.sys 6/19/2006 5:26:59 PM 0x8c1fa000 0x8c1fd180 0x00003180 0x449716a3 AtiPcie.sys 10/30/2006 2:23:10 PM 0x8aff4000 0x8affc000 0x00008000 0x4546430e UBHelper.sys 1/30/2008 9:30:26 PM 0x8aae0000 0x8aae8000 0x00008000 0x47a124b2 usbfilter.sys 5/28/2008 6:54:13 PM 0x8f7a1000 0x8f7aa000 0x00009000 0x483de295 mwlPSDVDisk.sys 9/22/2008 11:52:50 PM 0x905aa000 0x905bc000 0x00012000 0x48d86812 mwlPSDNServ.sys 9/22/2008 11:53:01 PM 0x905bc000 0x905c5000 0x00009000 0x48d8681d mwlPSDFilter.sys 9/22/2008 11:53:08 PM 0x8abcf000 0x8abd8000 0x00009000 0x48d86824 HSX_CNXT.sys 10/15/2008 8:29:13 PM 0x91d20000 0x91dd5000 0x000b5000 0x48f68ad9 HSXHWAZL.sys 10/15/2008 8:30:03 PM 0x96cbc000 0x96cf9000 0x0003d000 0x48f68b0b HSX_DPV.sys 10/15/2008 8:32:04 PM 0x96cf9000 0x96dfb000 0x00102000 0x48f68b84 XAudio32.sys 11/4/2008 3:32:19 PM 0x9e4ec000 0x9e4f4000 0x00008000 0x4910a343 SynTP.sys 12/5/2008 2:14:54 AM 0x90b2c000 0x90b5c680 0x00030680 0x4938c6de NTIDrvr.sys 3/24/2009 11:09:51 PM 0x8f744000 0x8f74c000 0x00008000 0x49c9a07f DKbFltr.sys 3/25/2009 11:10:12 PM 0x8f7d7000 0x8f7e1000 0x0000a000 0x49caf214 k57nd60x.sys 4/26/2009 7:23:19 AM 0x90af0000 0x90b2c000 0x0003c000 0x49f44427 athr.sys 6/9/2009 2:04:52 PM 0x8f600000 0x8f710000 0x00110000 0x4a2ea444 RtHDMIV.sys 6/24/2009 6:23:10 AM 0x91cb2000 0x91cd7600 0x00025600 0x4a41fe8e RTKVHDA.sys 7/6/2009 5:12:43 AM 0x96a34000 0x96cbb140 0x00287140 0x4a51c00b
- search Google for the name of the driver
- compare the Google results with what's installed on your system to figure out which device/program it belongs to
- visit the web site of the manufacturer of the hardware/program to get the latest drivers (DON'T use Windows Update or the Update driver function of Device Manager).
- if there are difficulties in locating them, post back with questions and someone will try and help you locate the appropriate program.
- - Driver manufacturer links are on this page: Drivers and Downloads
Please run these two tests after updating the drivers
Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder or another ISO burning program.
Boot from the CD, and leave it running for at least 5 or 6 passes.
Just remember, any time Memtest reports errors, it can be either bad RAM or a bad motherboard slot.
Test the sticks individually, and if you find a good one, test it in all slots.
I'd suggest that you first backup your stuff and then make sure you've got access to another computer so you can contact us if problems arise. Then make a System Restore point (so you can restore the system using the Vista/Windows 7 Startup Repair feature).
In Windows 7 you can make a Startup Repair disk by going to Start....All Programs...Maintenance...Create a System Repair Disc - with Windows Vista you'll have to use your installation disk or the "Repair your computer" option at the top of the Safe Mode menu .
Then, here's the procedure:
- Go to Start and type in "verifier" (without the quotes) and press Enter
- Select "Create custom settings (for code developers)" and click "Next"
- Select "Select individual settings from a full list" and click "Next"
- Select everything EXCEPT FOR "Low Resource Simulation" and click "Next"
- Select "Select driver names from a list" and click "Next"
Then select all drivers NOT provided by Microsoft and click "Next"
- Select "Finish" on the next page.
Reboot the system and wait for it to crash to the Blue Screen. Continue to use your system normally, and if you know what causes the crash, do that repeatedly. The objective here is to get the system to crash because Driver Verifier is stressing the drivers out. If it doesn't crash for you, then let it run for at least 36 hours of continuous operation (an estimate on my part).
If you can't get into Windows because it crashes too soon, try it in Safe Mode.
If you can't get into Safe Mode, try using System Restore from your installation DVD to set the system back to the previous restore point that you created.
|My System Specs|
|06 Aug 2011||#3|
| || |
Well I've been trying to replace all the drivers, got through many of them. Before I could finish the problem got worse (more frequent). Now I can't boot at all - tried everything I could find on the web (safe mode, alt-F10, boot from Windows installation disk, recovery disk, etc.).
With the recovery, boot, installation disks it either says "bootmgr is missing" or I get a Windows Boot Manager window that says Windows failed to start, repair it with the installation disk and says:
Info: Windows failed to load because the system registry file is missing or corrupt
|My System Specs|
|09 Aug 2011||#5|
| || |
Thanks for the reply.
I booted with "ultimate boot cd" and ran some tests - one of the memory dimms gave a LOT of errors, when I replaced it I could boot with the Windows CD.
Everything was gone from my hard drive (I tried some system restore that was for the Vista system that came with the laptop) I think that may have wiped it. I figured I'd have to reinstall anyway.
Reinstalled Windows 7 and everything is working fine (I will make sure to update drivers).
|My System Specs|
|Similar help and support threads for2: Acer 5536 laptop BSOD|
|Acer Aspire 5536 Bios Won't Boot||Hardware & Devices|
|Acer Laptop BSOD's / IRQL_NOT_LESS_OR_EQUAL||BSOD Help and Support|
|BSOD at random times, laptop acer aspire||BSOD Help and Support|
|BSOD Tribes Ascend, BF3, Random BSOD BUGCODE_USB_DRIVER Acer Laptop||BSOD Help and Support|
|Acer Aspire 5536 built-in mic not working||Drivers|
|BSoD with new Acer Laptop||BSOD Help and Support|
|Random BSOD New acer laptop||BSOD Help and Support|