[Rhaom]

Ok, so...

I not so long ago built a brand new computer for a family member and everything worked fine for about 2 months, then I started getting bluescreens all the time specifically.

MEMORY_MANAGEMENT (0x000001A) & (0x0000024)

I ran memtest and tested the memory and it didnt come up with any issues, I have run hardware tests and found no issues with any of the other hardware.

I have changed the motherboard, new powersupply, I have tried both ram sticks seperatly and 2 completely different ram sticks, different graphics card and no matter what I do when I try each component on its own I cannot reproduce the error but as soon as I put it all together again, it starts to boot then just cycles through the same 2 bluescreens MEMORY_MANAGEMENT (0x000001A) & (0x0000024) over and over again.

I have tried booting with Linux to test if its a driver or a hardware issue and linux has no issues but then all the drivers are also up to date, I read on a different forum that sometimes USB keyboards and such can cause issues so I changed to PS/2 and still the same 2 bluescreens cycle.

I am at a total loss as to what to try next... the only thing left i can think of is to reformat and change back to 32-bit. I would love to hear if anybody has any other suggestions before I go ahead and do this.

I can post dxdiags and any other tests if need be (the computer is on windows 7 Home Premium 64-bit)

Edited by Rhaom, 23 December 2010 - 12:40 PM.

[Advertisements]

Download BlueScreenView
No installation required.
Double click on BlueScreenView.exe file to run the program.
When scanning is done, go Edit>Select All.
Go File>Save Selected Items, and save the report as BSOD.txt.
Open BSOD.txt in Notepad, copy all content, and paste it into your next reply.

Thanks to Broni for the instructions and program

[rshaffer61]

Download BlueScreenView
No installation required.
Double click on BlueScreenView.exe file to run the program.
When scanning is done, go Edit>Select All.
Go File>Save Selected Items, and save the report as BSOD.txt.
Open BSOD.txt in Notepad, copy all content, and paste it into your next reply.

Thanks to Broni for the instructions and program

[Rhaom]

It seems there is actually 3 or 4 different bluescreens in the cycle I just keep seeing the same ones..,

Here you go


==================================================
Dump File : 122410-23930-01.dmp
Crash Time : 24/12/2010 02:45:26
Bug Check String : NTFS_FILE_SYSTEM
Bug Check Code : 0x00000024
Parameter 1 : 00000000`001904fb
Parameter 2 : fffff880`06ae9c28
Parameter 3 : fffff880`06ae9490
Parameter 4 : fffff800`02e57ccd
Caused By Driver : Ntfs.sys
Caused By Address : Ntfs.sys+213d8
File Description :
Product Name :
Company :
File Version :
Processor : x64
Computer Name :
Full Path : C:\Windows\Minidump\122410-23930-01.dmp
Processors Count : 3
Major Version : 15
Minor Version : 7600
Dump File Size : 284,648
==================================================

==================================================
Dump File : 122410-29764-01.dmp
Crash Time : 24/12/2010 02:24:21
Bug Check String : BAD_POOL_HEADER
Bug Check Code : 0x00000019
Parameter 1 : 00000000`00000003
Parameter 2 : fffffa80`0395a680
Parameter 3 : fffffa80`0395a682
Parameter 4 : fffffa80`0395a680
Caused By Driver : Ntfs.sys
Caused By Address : Ntfs.sys+ebae
File Description :
Product Name :
Company :
File Version :
Processor : x64
Computer Name :
Full Path : C:\Windows\Minidump\122410-29764-01.dmp
Processors Count : 3
Major Version : 15
Minor Version : 7600
Dump File Size : 284,400
==================================================

==================================================
Dump File : 122410-21777-01.dmp
Crash Time : 24/12/2010 02:17:07
Bug Check String : MEMORY_MANAGEMENT
Bug Check Code : 0x0000001a
Parameter 1 : 00000000`00041790
Parameter 2 : fffffa80`0166ab80
Parameter 3 : 00000000`0000ffff
Parameter 4 : 00000000`00000000
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+70740
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7600.16617 (win7_gdr.100618-1621)
Processor : x64
Computer Name :
Full Path : C:\Windows\Minidump\122410-21777-01.dmp
Processors Count : 3
Major Version : 15
Minor Version : 7600
Dump File Size : 285,192
==================================================

==================================================
Dump File : 122410-28579-01.dmp
Crash Time : 24/12/2010 02:15:25
Bug Check String : NTFS_FILE_SYSTEM
Bug Check Code : 0x00000024
Parameter 1 : 00000000`001904fb
Parameter 2 : fffff880`08562238
Parameter 3 : fffff880`08561aa0
Parameter 4 : fffff880`012bb91b
Caused By Driver : Ntfs.sys
Caused By Address : Ntfs.sys+aa91b
File Description :
Product Name :
Company :
File Version :
Processor : x64
Computer Name :
Full Path : C:\Windows\Minidump\122410-28579-01.dmp
Processors Count : 3
Major Version : 15
Minor Version : 7600
Dump File Size : 284,704
==================================================

==================================================
Dump File : 122410-22230-01.dmp
Crash Time : 24/12/2010 02:08:11
Bug Check String : SYSTEM_SERVICE_EXCEPTION
Bug Check Code : 0x0000003b
Parameter 1 : 00000000`c0000005
Parameter 2 : fffff880`0183f087
Parameter 3 : fffff880`06b03cc0
Parameter 4 : 00000000`00000000
Caused By Driver : MpFilter.sys
Caused By Address : MpFilter.sys+15087
File Description :
Product Name :
Company :
File Version :
Processor : x64
Computer Name :
Full Path : C:\Windows\Minidump\122410-22230-01.dmp
Processors Count : 3
Major Version : 15
Minor Version : 7600
Dump File Size : 284,704
==================================================

==================================================
Dump File : 122410-22432-01.dmp
Crash Time : 24/12/2010 02:06:14
Bug Check String : BAD_POOL_HEADER
Bug Check Code : 0x00000019
Parameter 1 : 00000000`00000003
Parameter 2 : fffffa80`0395a310
Parameter 3 : fffffa80`0395a312
Parameter 4 : fffffa80`0395a310
Caused By Driver : MpFilter.sys
Caused By Address : MpFilter.sys+107f0
File Description :
Product Name :
Company :
File Version :
Processor : x64
Computer Name :
Full Path : C:\Windows\Minidump\122410-22432-01.dmp
Processors Count : 3
Major Version : 15
Minor Version : 7600
Dump File Size : 284,704
==================================================

==================================================
Dump File : 122410-21231-01.dmp
Crash Time : 24/12/2010 02:04:00
Bug Check String : MEMORY_MANAGEMENT
Bug Check Code : 0x0000001a
Parameter 1 : 00000000`00041790
Parameter 2 : fffffa80`01589f70
Parameter 3 : 00000000`0000ffff
Parameter 4 : 00000000`00000000
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+70740
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7600.16617 (win7_gdr.100618-1621)
Processor : x64
Computer Name :
Full Path : C:\Windows\Minidump\122410-21231-01.dmp
Processors Count : 3
Major Version : 15
Minor Version : 7600
Dump File Size : 284,400
==================================================

==================================================
Dump File : 122410-22713-01.dmp
Crash Time : 24/12/2010 02:01:52
Bug Check String : CRITICAL_OBJECT_TERMINATION
Bug Check Code : 0x000000f4
Parameter 1 : 00000000`00000003
Parameter 2 : fffffa80`05e8cb30
Parameter 3 : fffffa80`05e8ce10
Parameter 4 : fffff800`031dd5d0
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+70740
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7600.16617 (win7_gdr.100618-1621)
Processor : x64
Computer Name :
Full Path : C:\Windows\Minidump\122410-22713-01.dmp
Processors Count : 3
Major Version : 15
Minor Version : 7600
Dump File Size : 284,784
==================================================

==================================================
Dump File : 122410-28158-01.dmp
Crash Time : 24/12/2010 01:59:13
Bug Check String : MEMORY_MANAGEMENT
Bug Check Code : 0x0000001a
Parameter 1 : 00000000`00005003
Parameter 2 : fffff700`01080000
Parameter 3 : 00000000`000006e6
Parameter 4 : 0000063f`00000dce
Caused By Driver : Ntfs.sys
Caused By Address : Ntfs.sys+9f421
File Description :
Product Name :
Company :
File Version :
Processor : x64
Computer Name :
Full Path : C:\Windows\Minidump\122410-28158-01.dmp
Processors Count : 3
Major Version : 15
Minor Version : 7600
Dump File Size : 289,664
==================================================

==================================================
Dump File : 122410-21450-01.dmp
Crash Time : 24/12/2010 01:34:12
Bug Check String : MEMORY_MANAGEMENT
Bug Check Code : 0x0000001a
Parameter 1 : 00000000`00041790
Parameter 2 : fffffa80`017084d0
Parameter 3 : 00000000`0000ffff
Parameter 4 : 00000000`00000000
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+70740
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7600.16617 (win7_gdr.100618-1621)
Processor : x64
Computer Name :
Full Path : C:\Windows\Minidump\122410-21450-01.dmp
Processors Count : 3
Major Version : 15
Minor Version : 7600
Dump File Size : 285,936
==================================================

==================================================
Dump File : 122410-25287-01.dmp
Crash Time : 24/12/2010 01:22:47
Bug Check String : MEMORY_MANAGEMENT
Bug Check Code : 0x0000001a
Parameter 1 : 00000000`00041790
Parameter 2 : fffffa80`017025f0
Parameter 3 : 00000000`0000ffff
Parameter 4 : 00000000`00000000
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+70740
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7600.16617 (win7_gdr.100618-1621)
Processor : x64
Computer Name :
Full Path : C:\Windows\Minidump\122410-25287-01.dmp
Processors Count : 3
Major Version : 15
Minor Version : 7600
Dump File Size : 285,472
==================================================

==================================================
Dump File : 122410-24414-01.dmp
Crash Time : 24/12/2010 01:20:21
Bug Check String : SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
Bug Check Code : 0x1000007e
Parameter 1 : ffffffff`c0000005
Parameter 2 : fffff800`02e9fd8b
Parameter 3 : fffff880`03162978
Parameter 4 : fffff880`031621e0
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+45d8b
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7600.16617 (win7_gdr.100618-1621)
Processor : x64
Computer Name :
Full Path : C:\Windows\Minidump\122410-24414-01.dmp
Processors Count : 3
Major Version : 15
Minor Version : 7600
Dump File Size : 285,008
==================================================

[rshaffer61]

I am at a total loss as to what to try next... the only thing left i can think of is to reformat and change back to 32-bit. I would love to hear if anybody has any other suggestions before I go ahead and do this.

I can post dxdiags and any other tests if need be (the computer is on windows 7 Home Premium 64-bit)

So the system originally had Win7 32 bit OS and then you installed the 64 bit version?
Is the new version a store bought retail, oem or burned version?
If the latter then where did it come from?
Try this and let me know the results.
Run hard drive diagnostics: http://www.tacktech....ay.cfm?ttid=287
Make sure, you select tool, which is appropriate for the brand of your hard drive.
Depending on the program, it'll create bootable floppy, or bootable CD.
If downloaded file is of .iso type, use ImgBurn: http://www.imgburn.com/ to burn .iso file to a CD (select "Write image file to disc" option), and make the CD bootable.

NOTE. If your hard drive is made by Toshiba, unfortunately, you're out of luck, because Toshiba doesn't provide any diagnostic tool.

Thanks to Broni for the instructions


You may need to do a Startup Repair to correct this.

[Rhaom]

It was on 32bit then i did a complete format, fresh install of 64bit and in answer to the question it is store bought retail version.

Both drives are WD5000AAKS and they both come back clean

[rshaffer61]

OK then do the HD diagnostics and let me know what the results are.

OOps just reread your post and you did the diagnostics on both drive correct?

The memory management error shows as follows:

0x0000001A: MEMORY_MANAGEMENT
(Click to consult the online MSDN article.)
This memory management error is usually hardware related. See the General Troubleshooting of STOP Messages checklist above. If this occurs while installing Windows, also check the Windows system requirements including the amount of RAM and disk space required to load the operating system. If none of the above resolves the problem, see the MSDN article linked above for further steps.

Please do the following.


Download and install Free Everest Home Edition
Open it.
1: In left pane expand Computer folder.
2: Click once on Summary
3: In upper menu, go Report
4: And then to Quick Report-Summary
5: Save it in text file, and paste it in your next post.
Click the + by computer, click on Sensor. Get a screenshot and post it so I can check your temps and voltages...


DO NOT INCLUDE ANYTHING UNDER THE LINE THAT SAYS "DEBUG- PCI"

[Rhaom]

Yes i did indeed say both drives came up error free and here is the info you asked for

--------[ EVEREST Home Edition © 2003-2005 Lavalys, Inc. ]------------------------------------------------------------

Version EVEREST v2.20.405
Homepage http://www.lavalys.com/
Report Type Quick Report
Computer OWNER-PC
Generator Owner
Operating System Windows 7 Home Premium Home Edition 6.1.7600
Date 2010-12-24
Time 06:38


--------[ Summary ]-----------------------------------------------------------------------------------------------------

Computer:
Operating System Windows 7 Home Premium Home Edition
OS Service Pack -
DirectX 4.09.00.0904 (DirectX 9.0c)
Computer Name OWNER-PC
User Name Owner

Motherboard:
CPU Type 2x , 3000 MHz
Motherboard Name Unknown
Motherboard Chipset Unknown
System Memory 4096 MB
BIOS Type Unknown
Communication Port Communications Port (COM1)
Communication Port Printer Port (LPT1)

Display:
Video Adapter GeForce GTS 250
Video Adapter GeForce GTS 250
Monitor Generic PnP Monitor [NoDB] (LHG080034231)
Monitor Generic PnP Monitor [NoDB] (153293587)

Multimedia:
Audio Adapter High Definition Audio Controller [NoDB]

Storage:
IDE Controller Standard Dual Channel PCI IDE Controller
IDE Controller Standard Dual Channel PCI IDE Controller
Floppy Drive Floppy disk drive
Disk Drive WDC WD5000AAKS-00UU3A0 ATA Device (465 GB, IDE)
Disk Drive WDC WD5000AAKS-00YGA0 ATA Device (465 GB, IDE)
Optical Drive HL-DT-ST DVD-RAM GH22LS30 ATA Device
SMART Hard Disks Status OK

Partitions:
C: (NTFS) 476835 MB (328044 MB free)
E: (NTFS) 99 MB (70 MB free)
G: (NTFS) 476834 MB (453775 MB free)
Total Size 931.4 GB (763.6 GB free)

Input:
Keyboard Microsoft Digital Media Keyboard 3000 (IntelliType Pro)
Mouse Logitech HID-compliant G3/MX518 Optical Mouse

Network:
Network Adapter Realtek PCIe GBE Family Controller (192.168.0.4)

Peripherals:
Printer EPSON1400DE (Epson Stylus SX420W)
Printer Fax
Printer Microsoft XPS Document Writer
USB1 Controller Standard OpenHCD USB Host Controller [NoDB]
USB1 Controller Standard OpenHCD USB Host Controller [NoDB]
USB1 Controller Standard OpenHCD USB Host Controller [NoDB]
USB1 Controller Standard OpenHCD USB Host Controller [NoDB]
USB1 Controller Standard OpenHCD USB Host Controller [NoDB]
USB2 Controller Standard Enhanced PCI to USB Host Controller [NoDB]
USB2 Controller Standard Enhanced PCI to USB Host Controller [NoDB]
USB Device Logitech USB G3 (MX518) Optical Mouse
USB Device Microsoft Hardware USB Keyboard
USB Device USB Composite Device
USB Device USB Input Device

Attached Thumbnails

• 

[rshaffer61]

0x0000007E: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
(Click to consult the online MSDN article.)
A system thread generated an exception which the error handler did not catch. There are numerous individual causes for this problem, including hardware incompatibility, a faulty device driver or system service, or some software issues. Check Event Viewer (EventVwr.msc) for additional information.

Again it is showing numerous reasons for the error.

Download WhoCrashed from the link in my signature below
This program checks for any drivers which may have been causing your computer to crash....

Click on the file you just downloaded and run it.

Put a tick in Accept then click on Next
Put a tick in the Don't create a start menu folder then click Next
Put a tick in Create a Desktop Icon then click on Install and make sure there is a tick in Launch Whocrashed before clicking Finish
Click Analyze
It will want to download the Debugger and install it Say Yes
WhoCrashed will create report but you have to scroll down to see it
Copy and paste it into your next reply







http://www.resplendence.com/downloads

[Rhaom]

Ok, I downloaded and Analyzed with WhoCrashed but it didnt ask me to download a debugger

I have some experience in technical repairs field but not as much as the tech help I can get from this site but from what I am reading its telling me that the errors are with 3 different files.

ntoskrnl.exe
ntfs.sys
mpfilter.sys

Below is the WhoCrashed information:

System Information (local)
--------------------------------------------------------------------------------

computer name: OWNER-PC
windows version: Windows 7 , 6.1, build: 7600
windows dir: C:\Windows
CPU: AuthenticAMD AMD Athlon™ II X3 440 Processor AMD586, level: 16
3 logical processors, active mask: 7
RAM: 4292403200 total
VM: 2147352576, free: 1966432256



--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.


On Fri 24/12/2010 15:30:37 GMT your computer crashed
crash dump file: C:\Windows\Minidump\122410-20248-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70740)
Bugcheck code: 0x7A (0x1, 0xFFFFFFFFC0000005, 0xFFFFFA80061B2060, 0xFFFFF68000007000)
Error: KERNEL_DATA_INPAGE_ERROR
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that the requested page of kernel data from the paging file could not be read into memory.
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 24/12/2010 15:30:37 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: 0x7A (0x1, 0xFFFFFFFFC0000005, 0xFFFFFA80061B2060, 0xFFFFF68000007000)
Error: KERNEL_DATA_INPAGE_ERROR
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that the requested page of kernel data from the paging file could not be read into memory.
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 24/12/2010 03:05:41 GMT your computer crashed
crash dump file: C:\Windows\Minidump\122410-21356-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x765DA)
Bugcheck code: 0x1000009F (0x4, 0x258, 0xFFFFFA80039DE680, 0xFFFFF80000B9C510)
Error: CUSTOM_ERROR
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
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 24/12/2010 02:25:03 GMT your computer crashed
crash dump file: C:\Windows\Minidump\122410-23930-01.dmp
This was probably caused by the following module: ntfs.sys (Ntfs+0x213D8)
Bugcheck code: 0x24 (0x1904FB, 0xFFFFF88006AE9C28, 0xFFFFF88006AE9490, 0xFFFFF80002E57CCD)
Error: NTFS_FILE_SYSTEM
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 a problem occurred in the NTFS file system.
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.


On Fri 24/12/2010 02:17:53 GMT your computer crashed
crash dump file: C:\Windows\Minidump\122410-29764-01.dmp
This was probably caused by the following module: ntfs.sys (Ntfs+0xEBAE)
Bugcheck code: 0x19 (0x3, 0xFFFFFA800395A680, 0xFFFFFA800395A682, 0xFFFFFA800395A680)
Error: BAD_POOL_HEADER
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 pool header is corrupt.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. 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 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.


On Fri 24/12/2010 02:15:45 GMT your computer crashed
crash dump file: C:\Windows\Minidump\122410-21777-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70740)
Bugcheck code: 0x1A (0x41790, 0xFFFFFA800166AB80, 0xFFFF, 0x0)
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 Fri 24/12/2010 02:09:12 GMT your computer crashed
crash dump file: C:\Windows\Minidump\122410-28579-01.dmp
This was probably caused by the following module: ntfs.sys (Ntfs+0x213D8)
Bugcheck code: 0x24 (0x1904FB, 0xFFFFF88008562238, 0xFFFFF88008561AA0, 0xFFFFF880012BB91B)
Error: NTFS_FILE_SYSTEM
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 a problem occurred in the NTFS file system.
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.


On Fri 24/12/2010 02:06:57 GMT your computer crashed
crash dump file: C:\Windows\Minidump\122410-22230-01.dmp
This was probably caused by the following module: mpfilter.sys (MpFilter+0x15087)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF8800183F087, 0xFFFFF88006B03CC0, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\drivers\mpfilter.sys
product: Microsoft Malware Protection
company: Microsoft Corporation
description: Microsoft antimalware file system filter driver
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
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.


On Fri 24/12/2010 02:04:49 GMT your computer crashed
crash dump file: C:\Windows\Minidump\122410-22432-01.dmp
This was probably caused by the following module: mpfilter.sys (MpFilter+0x107F0)
Bugcheck code: 0x19 (0x3, 0xFFFFFA800395A310, 0xFFFFFA800395A312, 0xFFFFFA800395A310)
Error: BAD_POOL_HEADER
file path: C:\Windows\system32\drivers\mpfilter.sys
product: Microsoft Malware Protection
company: Microsoft Corporation
description: Microsoft antimalware file system filter driver
Bug check description: This indicates that a pool header is corrupt.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. 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 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.


On Fri 24/12/2010 02:02:38 GMT your computer crashed
crash dump file: C:\Windows\Minidump\122410-21231-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70740)
Bugcheck code: 0x1A (0x41790, 0xFFFFFA8001589F70, 0xFFFF, 0x0)
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 Fri 24/12/2010 02:00:28 GMT your computer crashed
crash dump file: C:\Windows\Minidump\122410-22713-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70740)
Bugcheck code: 0xF4 (0x3, 0xFFFFFA8005E8CB30, 0xFFFFFA8005E8CE10, 0xFFFFF800031DD5D0)
Error: CRITICAL_OBJECT_TERMINATION
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 process or thread crucial to system operation has unexpectedly exited or been terminated.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
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 24/12/2010 01:52:46 GMT your computer crashed
crash dump file: C:\Windows\Minidump\122410-28158-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70740)
Bugcheck code: 0x1A (0x5003, 0xFFFFF70001080000, 0x6E6, 0x63F00000DCE)
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 Fri 24/12/2010 01:33:16 GMT your computer crashed
crash dump file: C:\Windows\Minidump\122410-21450-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70740)
Bugcheck code: 0x1A (0x41790, 0xFFFFFA80017084D0, 0xFFFF, 0x0)
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 Fri 24/12/2010 01:21:17 GMT your computer crashed
crash dump file: C:\Windows\Minidump\122410-25287-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70740)
Bugcheck code: 0x1A (0x41790, 0xFFFFFA80017025F0, 0xFFFF, 0x0)
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 Fri 24/12/2010 01:18:53 GMT your computer crashed
crash dump file: C:\Windows\Minidump\122410-24414-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x45D8B)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF80002E9FD8B, 0xFFFFF88003162978, 0xFFFFF880031621E0)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
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 system thread generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.



--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------

15 crash dumps have been found and analyzed.
Read the topic general suggestions for troubleshooting system crashes for more information.

Edited by Rhaom, 24 December 2010 - 05:34 AM.

[rshaffer61]

Tutorial for running chkdsk in Win 7 located HERE.

[Rhaom]

ok, I have run multiple CHKDSKs before and not come across anything and i am fairly sure it came across nothing this time also, it tells me the volumes are clean

[rshaffer61]

OK then on to the next step.
Go HERE and read the tutorial that shows how to do SFC or System File Checker and running in a Elevated Command Prompt in Vista and Win7.

[Rhaom]

ok, Slight break there

Hope you have had a good few days over christmas

As far as the stage we are at goes, I ran an SFC Scan and it also came back clean, the screenshot is attacthed below

Attached Thumbnails

• 

[rshaffer61]

If you have more than one RAM module installed, try starting computer with one RAM stick at a time.

NOTE Keep in mind, the manual check listed above is always superior to the software check, listed below. DO NOT proceed with memtest, if you can go with option A

B. If you have only one RAM stick installed...
...run memtest...

1. Download - Pre-Compiled Bootable ISO (.zip)
2. Unzip downloaded memtest86+-2.11.iso.zip file.
3. Inside, you'll find memtest86+-2.11.iso file.
4. Download, and install ImgBurn: http://www.imgburn.com/
5. Insert blank CD into your CD drive.
6. Open ImgBurn, and click on Write image file to disc
7. Click on Browse for a file... icon:



8. Locate memtest86+-2.11.iso file, and click Open button.
9. Click on ImgBurn green arrow to start burning bootable memtest86 CD:



10. Once the CD is created, boot from it, and memtest will automatically start to run. You may have to change the boot sequence in your BIOS to make it work right.

To change Boot Sequence in your BIOS

Reboot the system and at the first post screen (where it is counting up memory) start tapping the DEL button
This will enter you into the Bios\Cmos area.
Find the Advanced area and click Enter
Look for Boot Sequence or Boot Options and highlight that click Enter
Now highlight the first drive and follow the directions on the bottom of the screen on how to modify it and change it to CDrom.
Change the second drive to the C or Main Drive
Once that is done then click F10 to Save and Exit
You will prompted to enter Y to verify Save and Exit. Click Y and the system will now reboot with the new settings.


The running program will look something like this depending on the size and number of ram modules installed:




It's recommended to run 5-6 passes. Each pass contains very same 8 tests.

This will show the progress of the test. It can take a while. Be patient, or leave it running overnight.



The following image is the test results area:



The most important item here is the “errors” line. If you see ANY errors, even one, most likely, you have bad RAM.