BSOD x2 - Memory Dump and FLTMNGR.SYS

[AlwaysBroken]

Recently my windows installation became corrupted to the point where I gave up and wiped my hard drive and re-installed Windows I reinstalled and reloaded what I could but now I have gotten back to back BSOD. The first said something about Memory Dump and the second said fltmngr.sys. Both times the screen turned off before I could read much more.

I run Windows 7 Ultimate (64bit), it was OEM but I had to reinstall myself as I can't take it back to the store where I bought it (S Korea). The computer is about two years old (in July).

Any assistance in helping me fix my computer would be appreciated. I don't know much about fixing my computer beyond what I've already tried.

 

[zigzag3143]

You uploaded the application instead of the data. Please try this method.

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.

 

[AlwaysBroken]

Apologies, the only file that I saw in my Documents folder was that app and I assumed it was saved as a file opened in the same program I ran to check everything. The requested info should be attached now.

Also I have never overclocked anything, I don't trust myself to do it right

 

[zigzag3143]

Apologies, the only file that I saw in my Documents folder was that app and I assumed it was saved as a file opened in the same program I ran to check everything. The requested info should be attached now.

Also I have never overclocked anything, I don't trust myself to do it right

No worries. You would be surprised at how often that happens.

Before we can even investigate the underlying problem asacpi.sys has to be updated. Yours is from 2005.

Asacpi.sys

The pre 2009 version of this driver is a known BSOD cause.

Please visit this link: Asus tek computer inc. -support- drivers and download p7p55d le

ASUSTeK Computer Inc. -Support- Drivers and Download P7P55D LE
ASUSTeK Computer Inc. - Motherboards- ASUS P5K-VM

Scroll down to the utilities category, then scroll down to the "atk0110 driver for windowsxp/vista/windows 7 32&64-bit" (it's about the 12th item down).

Download and install it.

Go to c:\windows\system32\drivers to check and make sure that the asacpi.sys file is date stamped from 2009 or 2010 (not before).

 

[AlwaysBroken]

I've installed the driver and it now has a date of 2010. Windows also updated and said i need to install my power management driver, it sent me to a site and i downloaded what it said to (Cool and Quiet 2.18.01) but when I ran it, it said it was not supported