BSOD help please

hi guys,

my pc has been running fine untill about 10 mins ago when i left my room and came back windows had restarted and BSOD ?

i wasn`t even doing anything on my pc ?

here is the whocrashed results, can anyone help please . . .

Crash Dump Analysis

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.


On Sat 21/04/2012 13:56:17 GMT your computer crashed
crash dump file: C:\Windows\Minidump\042112-21013-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC80)
Bugcheck code: 0x1A (0x8884, 0xFFFFFA8006790200, 0xFFFFFA8006790440, 0x300)
Error: MEMORY_MANAGEMENT
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a severe memory management error occurred.
This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


On Sat 21/04/2012 13:56:17 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x1A (0x8884, 0xFFFFFA8006790200, 0xFFFFFA8006790440, 0x300)
Error: MEMORY_MANAGEMENT
Bug check description: This indicates that a severe memory management error occurred.
This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.

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.

hi there,

here is my msinfo32 and my minidump, also i have ran a memtest and did 1 pass with no errors. my memory was tested over night about 2 months ago as well and it passed.

Attachment 208221

Attachment 208224

hope this helps

any help with this please?

markshim said:

any help with this please?

Memory management probably caused by your 2005 asacpi.sys



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).

i don`t have that motherboard tho, i have a Asus M4A79T deluxe

i have found the same thing on my motherboard page tho, should i download and install it? do i need to uninstall anything first ?

ok i have downloaded and installed that driver and it now says 2009, i will keep you posted. thank you for the help

markshim said:

ok i have downloaded and installed that driver and it now says 2009, i will keep you posted. thank you for the help

Good Job and good luck

hi there,

i thought i should post here about the BSOD i have just had, i think it is different from the last one i had but i don`t know anything about BSODs. here is my who crashed repost and my minidump. can anyone help me please ?

Crash Dump Analysis
</B>
Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.


On Fri 04/05/2012 15:28:04 GMT your computer crashed
crash dump file: C:\Windows\Minidump\050412-17955-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC80)
Bugcheck code: 0xDE (0x2, 0xFFFFF8A011995370, 0xFFFFF8A011995361, 0x2285558C0)
Error: POOL_CORRUPTION_IN_FILE_AREA
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a driver has corrupted pool memory that is used for holding pages destined for disk.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


On Fri 04/05/2012 15:28:04 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ntfs.sys (Ntfs+0x7C9EF)
Bugcheck code: 0xDE (0x2, 0xFFFFF8A011995370, 0xFFFFF8A011995361, 0x2285558C0)
Error: POOL_CORRUPTION_IN_FILE_AREA
file path: C:\Windows\system32\drivers\ntfs.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT File System Driver
Bug check description: This indicates that a driver has corrupted pool memory that is used for holding pages destined for disk.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system which cannot be identified at this time.



Conclusion
</B>
2 crash dumps have been found and analyzed.
Read the topic general suggestions for troubleshooting system crashes for more information.

Note that it's not always possible to state with certainty whether a reported driver is actually responsible for crashing your system or that the root cause is in another module. Nonetheless it's suggested you look for updates for the products that these drivers belong to and regularly visit Windows update or enable automatic updates for Windows. In case a piece of malfunctioning hardware is causing trouble, a search with Google on the bug check errors together with the model name and brand of your computer may help you investigate this further.

Attachment 210158