Event 1001 BugCheck Event 41 Kernel-Power Event 4 k57nd60a

Memory exception but we need to examine the DMP files to find out why.



We do need the DMP file as it contains the only record of the sequence of events leading up to the crash, what drivers were loaded, and what was responsible.

If you are overclocking STOP


We could also use some system information, which you can get easily by running msinfo32.
To do that go to start>run>type msinfo32>enter

When it is finished running go to file>save>name it and upload to us here.


You may be able to get the DMP files without crashing by booting into safe mode (F8) with networking.

To enable us to assist you with your computer's BSOD symptoms, upload the contents of your "\Windows\Minidump" folder.

The procedure:

* Copy the contents of \Windows\Minidump to another (temporary) location somewhere on your machine.
* Zip up the copy.
* Attach the ZIP archive to your post using the "paperclip" (file attachments) button.
*If the files are too large please upload them to a file sharing service like "Rapidshare" and put a link to them in your reply.

To ensure minidumps are enabled:

* Go to Start, in the Search Box type: sysdm.cpl, press Enter.
* Under the Advanced tab, click on the Startup and Recovery Settings... button.
* Ensure that Automatically restart is unchecked.
* Under the Write Debugging Information header select Small memory dump (256 kB) in the dropdown box (the 256kb varies).
* Ensure that the Small Dump Directory is listed as %systemroot%\Minidump.
* OK your way out.
* Reboot if changes have been made.

Ah, it seems this particular dump file disappeared when I rolled the system back. I'd tried to update the VGA driver with the generic CCC and it messed some stuff up so I'll have to come back when it happens again. Didn't think it would do that, dang.

BUT, if it helps any I notice some weird figures in Task Manager with the Physical Memory... system claims there's only 22MB free at this moment out of 4090, cached 2434, Available 2412? System's only been on for 6 hours and 20 minutes to run (only) MBAM to rule out adware. Is that perhaps an indication of a bad RAM module or something else?

I have never noticed this before, but when checking Task Manager other times, I've never seen it so low. There's no explanation for it, only MBAM running the system shouldn't be caching so much memory...

More on the above, I now keep hitting 0 free Physical Memory (bounces around from 20 to 0). I'd appreciate some information on what that means or indicates. I am simply browsing with FF and watching a AVI file. What do I do from here? I feel this may be in relation to the BSOD problems.

MagusMagnus said:

More on the above, I now keep hitting 0 free Physical Memory (bounces around from 20 to 0). I'd appreciate some information on what that means or indicates. I am simply browsing with FF and watching a AVI file. What do I do from here? I feel this may be in relation to the BSOD problems.

Ok event id 43 is simply a dirty shutdown (unexpected) for anything further we need the DMP files to find why the memory exception is happening.

Is the error the issue, or the memory?

Alright, I found the previous .DMP before this most recent one. Just different address to and from strings, everything else is the same. I'll post any more that occur. Didn't know rolling the system back a little bit would take any .DMP made after the restore point with it. Now I know, will back them up elsewhere in future.

I'd thought that 0 free Physical Memory might be related so posted it here. I ran Windows' utility to check it and there weren't any errors so I will assume the RAM is fine until or unless anything else crops up in relation to it. But if that is an issue, I'd like to know. Don't think it's worth a new thread over, so far anyway.

MagusMagnus said:

Alright, I found the previous .DMP before this most recent one. Just different address to and from strings, everything else is the same. I'll post any more that occur. Didn't know rolling the system back a little bit would take any .DMP made after the restore point with it. Now I know, will back them up elsewhere in future.

I'd thought that 0 free Physical Memory might be related so posted it here. I ran Windows' utility to check it and there weren't any errors so I will assume the RAM is fine until or unless anything else crops up in relation to it. But if that is an issue, I'd like to know. Don't think it's worth a new thread over, so far anyway.

These crashes were caused by memory corruption/exception (Cx05) probably a driver.
Please run these two tests to verify your memory and find which driver is causing the problem.

* If you are overclocking anything reset to default before running these tests.
In other words STOP!!!

* If you have raid update its Driver.



Memtest.

*Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder or another ISO burning program. Memtest86+ - Advanced Memory Diagnostic Tool

*Boot from the CD, and leave it running for at least 5-7 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.

Any errors are indicative of a memory problem.

If a known good stick fails in a motherboard slot it is probably the slot.

RAM - Test with Memtest86+



Driver verifier

Using Driver Verifier is an iffy proposition. Most times it'll crash and it'll tell you what the driver is. But sometimes it'll crash and won't tell you the driver. Other times it'll crash before you can log in to Windows. If you can't get to Safe Mode, then you'll have to resort to offline editing of the registry to disable Driver Verifier.

So, 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/Win7 Startup Repair feature).

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 "Special Pool", "Force Pending I/O Requests" and "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.

If you are using win 8 add these

- Concurrency Stress Test
- DDI compliance checking

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.

Reboot into Windows (after the crash) and turn off Driver Verifier by going back in and selecting "Delete existing settings" on the first page, then locate and zip up the memory dump file and upload it with your next post.

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. You did create a restore point didnt you?

Driver Verifier

Using Driver Verifier (Windows Drivers)

Before I risk it with driver verifier, do you believe if I simply clean installed the OS and reloaded all of the originally supplied drivers that this issue will or could possibly resolve itself? I was planning on doing it soon anyway. Please let me know and thank you very much for your assistance.

Also, the manufacturer of my system hasn't released new drivers for it since before I bought it. I'd attempted to install the latest generic ATI CCC/driver but it resulted in changing my graphics card series number. I'm wondering if that matters. AMD's site states that they recommend we use the ones supplied by our system maker too, so not sure what to do concerning that. This and the other drivers are mostly from 2009... Acer has very poor support. My notebook series is lumped in with all the other sub-series of it so its very difficult to even pull up the original drivers off of their downloads site. Really annoying.


Haven't had another BSOD yet but the Physical Memory still keeps bottoming out on me. I'll run Memtest86 in a while.

MagusMagnus said:

Before I risk it with driver verifier, do you believe if I simply clean installed the OS and reloaded all of the originally supplied drivers that this issue will or could possibly resolve itself? I was planning on doing it soon anyway. Please let me know and thank you very much for your assistance.

Also, the manufacturer of my system hasn't released new drivers for it since before I bought it. I'd attempted to install the latest generic ATI CCC/driver but it resulted in changing my graphics card series number. I'm wondering if that matters. AMD's site states that they recommend we use the ones supplied by our system maker too, so not sure what to do concerning that. This and the other drivers are mostly from 2009... Acer has very poor support. My notebook series is lumped in with all the other sub-series of it so its very difficult to even pull up the original drivers off of their downloads site. Really annoying.


Haven't had another BSOD yet but the Physical Memory still keeps bottoming out on me. I'll run Memtest86 in a while.

If it is software and you dont re-install the same software you have now a clean install will probably work.

If it is hardware, or the same software it will not

The correct drivers is very important. If there are no new drivers, you may be able to help by re-installing older drivers in compatibility mode.

Is the system win 7 compliant?

Yes, the system originally came with Windows 7 preloaded onto it. Had to load the retail version due to the system refusing to take the OEM copy back onto a new hard drive. Long story short, the OEM kept stating it couldn't install on the system again because of hardware. Three self-made sets, as well as two from Acer failed citing the same crap. So it's been on a retail 7 install since late 2011.

About the software, I saw Firefox was stated to be involved with the latest crash cited in either bluescreenview or else with the windows debugging tool. Makes me suspicious because it will continually climb in private working set memory until it exceeds 1,000,000K and crashes out. But then it doesn't really make sense to me because why would I be the only one on these forced updates they're doing, to be getting this particular BSOD all of a sudden? But it DID say FireFox was involved...


Anyway, I ran an extended test (x2 pass) with Window's memory tool and it still claims the RAM is fine. I didn't do Memtest86, takes way too long and I'd think Windows' tool would have pulled something up if there were anything wrong, so don't think a longer test is needed.

I also took the liberty of running a full scan of MBAM, system is clean.

So I guess I will begin making my preparations for the new clean install. It is going to take me a few days. Lots of files to move, then lists of programs to take down etc. so I will report back in here to tell you how it goes when I'm done.

Oh, and as for the drivers... IS there some magical utility that can tell me which ones have new ones available and where to get the legitimate ones, not some stupid malware phishing scheme as most seem to be? Acer will be absolutely no assistance on this but seems most of the hardware manufacturers aren't going to be either, least of all ATI (you would think they at least would keep all drivers instead of just the generic CCC, but they don't). I am just concerned with using the generic CCC because it changes my graphics card series number and that just doesn't seem right to me.