BSOD help please

[markshim]

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.

 

[zigzag3143]

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.

 

[markshim]

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.

View attachment 208221

View attachment 208224

hope this helps

 

[markshim]

any help with this please?

 

[zigzag3143]

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

 

[markshim]

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

 

[markshim]

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

 

[markshim]

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

 

[zigzag3143]

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

 

[markshim]

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

[FONT=Segoe UI, Arial][FONT=Segoe UI, Arial]Crash dumps are enabled on your computer.
[/FONT][/FONT]

[FONT=Segoe UI, Arial]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: [FONT=Segoe UI, Arial]ntoskrnl.exe[/FONT] (nt+0x7CC80)
Bugcheck code: 0xDE (0x2, 0xFFFFF8A011995370, 0xFFFFF8A011995361, 0x2285558C0)
Error: [FONT=Segoe UI, Arial]POOL_CORRUPTION_IN_FILE_AREA[/FONT]
file path: C:\Windows\system32\ntoskrnl.exe
product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
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.
[/FONT]

[FONT=Segoe UI, Arial]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: [FONT=Segoe UI, Arial]ntfs.sys[/FONT] (Ntfs+0x7C9EF)
Bugcheck code: 0xDE (0x2, 0xFFFFF8A011995370, 0xFFFFF8A011995361, 0x2285558C0)
Error: [FONT=Segoe UI, Arial]POOL_CORRUPTION_IN_FILE_AREA[/FONT]
file path: C:\Windows\system32\drivers\ntfs.sys
product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
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.
[/FONT]

[FONT=Segoe UI, Arial]
Conclusion
</B>[/FONT]
[FONT=Segoe UI, Arial]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.

View attachment 210158[/FONT]

 

[James7679]

Have you tried this?

 

[markshim]

my ram has already been tested and has no errors

 

[markshim]

hi there,

can i have some help with this please?

 

[writhziden]

As mentioned, it could still be memory even if it passed through Memtest86+. Memtest86+ does not stress the memory in the same way Windows does, so it only catches certain ranges of errors. Sometimes, a better check is to run Windows normally with one module in one slot at a time and test each module and each slot.

Before proceeding with the above more time intensive task, we should check software/driver issues.

• An underlying driver may be incompatible\conflicting with your system. Run Driver Verifier to find any issues. To run Driver Verifier, do the following:
  
  a. Backup your system and user files
  b. Create a system restore point
  c. If you do not have a Windows 7 DVD, Create a system repair disc
  d. In Windows 7:

  • Click the Start Menu
  • Type verifier in Search programs and files (do not hit enter)
  • Right click verifier and click Run as administrator
  • Put a tick in Create custom settings (for code developers) and click next
  • Put a tick in Select individual settings from a full list and click next
  • Set up the individual settings as in the image and click next
    View attachment 210234
  • Put a tick in Select driver names from a list
  • Put a tick next to all non-Microsoft drivers.
  • Click Finish.
  • Restart your computer.

  
  If Windows cannot start in normal mode with driver verifier running, start in safe mode. If it cannot start in safe mode or normal mode, restore the system restore point using http://www.sevenforums.com/tutorials/700-system-restore.html OPTION TWO.
  
  Thanks to zigzag3143 for contributing to the Verifier steps.
  If you are unable to start Windows with all drivers being verified or if the blue screen crashes fail to create .dmp files, run them in groups of 5 or 10 until you find a group that causes blue screen crashes and stores the blue screen .dmp files.​
  The idea with Verifier is to cause the system to crash, so do the things you normally do that cause crashes. After you have a few crashes, upload the crash reports for us to take a look and try to find patterns.
  
  When you are ready to disable Verifier: Start Menu -> All Programs -> Accessories -> Right click Command Prompt -> Run as administrator -> Type the following command and then Enter:
  verifier /reset​
  -> Restart your computer.

 

[markshim]

hi there,

i will do another memtest and leave it running while i am out at the gym. the only thing with the driver verifier is that the BSOD happens at random times and doens`t happen day in day out can take awhile to get one.

 

[markshim]

hi there,

i have just ran memtest again and it got to about 15mins in and it came up with 2 errors so i stopped the test.
what does this mean? do i need to try and RMA it to corsair? and how do i do it if i do ?

 

[markshim]

hello,

just letting you know that i have just tested one stick of ram at a time to see if i could find out which one is faulty, i tested for the same time as i got the last errors which was 20mins in.

both sticks did not have any errors come up. i think the ram i have isn`t compatible with my motherboard set on auto and defult settings. because i am not good at changing bios settings i have put my ols sticks of ram back in for now, untill i get my new asus sabertooth 990fx board when the piledriver comes out.

if i still get the BSOD with my old sticks of ram back in then at least i will know that its either drivers or my motherboard.

 

[James7679]

Suggestion, do them one at a time until you find the offender. Then put the "good" one in it's place and retest. If it comes back clean, then that should rule out the MoBo. And yes RMA them.

 

[markshim]

hi,

well i have tested them in both of the motherboard slots that i was using at the time i got the BSOD and there is no errors. i think it is just that my ram is not compatible with my motherboard, i should of looked before buying them really but i didn`t think because i have never bought ram before. i think there are ways around it by changing settings in the bios but i would rather use my old sticks for now untill i get a new motherboard in the summer. if i get anymore BSOD with my old sticks in then i know it must be drivers.

 

[writhziden]

Memory is rather finicky, so errors do not always show up in the same patterns. That is why we recommend running Memtest86+ for at least seven passes. I have seen cases where it took up to 21 passes to get one error and determine RAM was bad. I would recommend testing the RAM modules you have individually for more passes, or test one at a time in one slot at a time by doing your normal routine in Windows. If you do not crash in twice the amount of time it typically takes (on average) for you to get a crash, then the module and slot is probably good.

If you crash, try the module in another slot. If you crash with all slots, the module is likely bad. If you find a good module and slot, test all slots with the good module to make sure you do not have a bad slot. Then test the other modules in the good slot to find any bad modules.


The above is just a suggestion and is completely optional, and you can just run with the old RAM if you like until you get a new board.