[Kritikal]

Over the past week or so, My computer has been crashing several times a day. It's almost always the same bugcheck code, which makes me believe it's something specific, not a RAM issue or HD problem. I've included the contents of debugging the memory dump if anyone has an idea what the problem is.

Microsoft (R) Windows Debugger Version 6.9.0003.113 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [D:\WINDOWS\MEMORY.DMP]
Kernel Summary Dump File: Only kernel address space is available

Symbol search path is: SRV*d:\symbols*http://msdl.microsoft.com/download/symbols

Executable search path is: 
Windows XP Kernel Version 2600 (Service Pack 2) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 2600.xpsp_sp2_qfe.070719-1309
Kernel base = 0x804d7000 PsLoadedModuleList = 0x805634c0
Debug session time: Sat May  3 08:51:24.187 2008 (GMT-4)
System Uptime: 1 days 12:26:25.913
Loading Kernel Symbols
......................................................................................................................................
Loading User Symbols

Loading unloaded module list
................................
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck C2, {7, cd4, 3e, ffb2c008}

*** ERROR: Module load completed but symbols could not be loaded for aswRdr.SYS
*** ERROR: Module load completed but symbols could not be loaded for aswMon2.SYS
*** ERROR: Module load completed but symbols could not be loaded for dump_IdeChnDr.sys
*** ERROR: Module load completed but symbols could not be loaded for VX6000Xp.sys
*** ERROR: Module load completed but symbols could not be loaded for aswSP.SYS
*** ERROR: Module load completed but symbols could not be loaded for xusb21.sys
*** ERROR: Symbol file could not be found.  Defaulted to export symbols for VX6KCamd.sys - 
*** ERROR: Symbol file could not be found.  Defaulted to export symbols for Aavmker4.SYS - 
*** WARNING: Unable to verify timestamp for Null.SYS
*** ERROR: Module load completed but symbols could not be loaded for Null.SYS
*** ERROR: Module load completed but symbols could not be loaded for atitray.sys
*** ERROR: Module load completed but symbols could not be loaded for aswTdi.SYS
*** ERROR: Module load completed but symbols could not be loaded for ntiowp.SYS
*** WARNING: Unable to verify timestamp for ati2dvag.dll
*** ERROR: Module load completed but symbols could not be loaded for ati2dvag.dll
*** WARNING: Unable to verify timestamp for ati2cqag.dll
*** ERROR: Module load completed but symbols could not be loaded for ati2cqag.dll
*** WARNING: Unable to verify timestamp for atikvmag.dll
*** ERROR: Module load completed but symbols could not be loaded for atikvmag.dll
*** WARNING: Unable to verify timestamp for atiok3x2.dll
*** ERROR: Module load completed but symbols could not be loaded for atiok3x2.dll
*** WARNING: Unable to verify timestamp for ati3duag.dll
*** ERROR: Module load completed but symbols could not be loaded for ati3duag.dll
*** WARNING: Unable to verify timestamp for ativvaxx.dll
*** ERROR: Module load completed but symbols could not be loaded for ativvaxx.dll
*** ERROR: Module load completed but symbols could not be loaded for aj1zit2s.SYS
*** ERROR: Module load completed but symbols could not be loaded for ati2mtag.sys
*** ERROR: Module load completed but symbols could not be loaded for IdeChnDr.sys
*** ERROR: Module load completed but symbols could not be loaded for sptd.sys
*** ERROR: Module load completed but symbols could not be loaded for PxHelp20.sys
*** ERROR: Symbol file could not be found.  Defaulted to export symbols for drmk.sys - 
*** ERROR: Module load completed but symbols could not be loaded for secdrv.sys
*** ERROR: Module load completed but symbols could not be loaded for aswFsBlk.sys
*** ERROR: Module load completed but symbols could not be loaded for IdeBusDr.sys
*** WARNING: Unable to verify timestamp for dmload.sys
*** ERROR: Module load completed but symbols could not be loaded for dmload.sys
*** WARNING: Unable to verify timestamp for Fs_Rec.SYS
*** ERROR: Module load completed but symbols could not be loaded for Fs_Rec.SYS
*** ERROR: Module load completed but symbols could not be loaded for mc298.tmp
Probably caused by : ntkrnlmp.exe ( nt!ExFreePoolWithTag+2c1 )

Followup: MachineOwner
---------

0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

BAD_POOL_CALLER (c2)
The current thread is making a bad pool request.  Typically this is at a bad IRQL level or double freeing the same allocation, etc.
Arguments:
Arg1: 00000007, Attempt to free pool which was already freed
Arg2: 00000cd4, (reserved)
Arg3: 0000003e, Memory contents of the pool block
Arg4: ffb2c008, Address of the block of pool being deallocated

Debugging Details:
------------------


POOL_ADDRESS:  ffb2c008 Nonpaged pool expansion

BUGCHECK_STR:  0xc2_7

DEFAULT_BUCKET_ID:  INTEL_CPU_MICROCODE_ZERO

PROCESS_NAME:  System

LAST_CONTROL_TRANSFER:  from 80551fc5 to 805375a2

STACK_TEXT:  
f8bf5c5c 80551fc5 000000c2 00000007 00000cd4 nt!KeBugCheckEx+0x1b
f8bf5cac 805513e3 ffb2c008 00000000 f8bf5cc8 nt!ExFreePoolWithTag+0x2c1
f8bf5cbc f850b7af ffb2c008 f8bf5ce4 f8509481 nt!ExFreePool+0xf
f8bf5cc8 f8509481 f8529020 ffb2c008 00000000 Ntfs!ExFreeToNPagedLookasideList+0x1e
f8bf5ce4 f8509666 ffb2c008 00000001 00000000 Ntfs!NtfsCleanupIrpContext+0x10d
f8bf5cfc f8533614 ffb2c008 00000000 00000000 Ntfs!NtfsCompleteRequest+0x35
f8bf5d7c 804e23b5 00000000 00000000 833c75b8 Ntfs!NtfsFspClose+0x1a5
f8bf5dac 80575138 00000000 00000000 00000000 nt!ExpWorkerThread+0xef
f8bf5ddc 804ec6c9 804e22f1 00000000 00000000 nt!PspSystemThreadStartup+0x34
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!ExFreePoolWithTag+2c1
80551fc5 83f801          cmp     eax,1

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt!ExFreePoolWithTag+2c1

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  469f6017

FAILURE_BUCKET_ID:  0xc2_7_nt!ExFreePoolWithTag+2c1

BUCKET_ID:  0xc2_7_nt!ExFreePoolWithTag+2c1

Followup: MachineOwner
---------

0: kd> lmv
start    end        module name
804d7000 806fe000   nt         (pdb symbols)          d:\symbols\ntkrnlmp.pdb\849B1B926BE54679AA53D90008EAEB7C2\ntkrnlmp.pdb
    Loaded symbol image file: ntkrnlmp.exe
    Image path: ntkrnlmp.exe
    Image name: ntkrnlmp.exe
    Timestamp:        Thu Jul 19 08:59:03 2007 (469F6017)
    CheckSum:         00211D64
    ImageSize:        00227000
    File version:     5.1.2600.3181
    Product version:  5.1.2600.3181
    File flags:       0 (Mask 3F)
    File OS:          40004 NT Win32
    File type:        1.0 App
    File date:        00000000.00000000
    Translations:     0409.04b0
    CompanyName:      Microsoft Corporation
    ProductName:      Microsoft® Windows® Operating System
    InternalName:     ntkrnlmp.exe
    OriginalFilename: ntkrnlmp.exe
    ProductVersion:   5.1.2600.3181
    FileVersion:      5.1.2600.3181 (xpsp_sp2_qfe.070719-1309)
    FileDescription:  NT Kernel & System
    LegalCopyright:   © Microsoft Corporation. All rights reserved.

[Saxon]

Hi,

First of all run memtest for a few hours just to rule out any ram issue. Also download the hirens boot disk an run PC Check that is on there the tests you should run are under hard drive diagnostics an they are called "Non Destructive writetest" and a "Read verify test" set the tests to run for 4 Hours a time.

But thank you for providing a crash dump, Googleing the first error INTEL_CPU_MICROCODE_ZERO most of the results are about your IEEE 1394 controller try updating the driver software.

IEEE 1394 General Troubleshooting MS trouble shooting guide.
IEEE 1394 interface - Wikipedia, the free encyclopedia IEEE 1394 (Also known as firewire)

[networkgeek]

Originally Posted by Chris Chadwick

Hi,

First of all run memtest for a few hours just to rule out any ram issue. Also download the hirens boot disk an run PC Check that is on there the tests you should run are under hard drive diagnostics an they are called "Non Destructive writetest" and a "Read verify test" set the tests to run for 4 Hours a time.

But thank you for providing a crash dump, Googleing the first error INTEL_CPU_MICROCODE_ZERO most of the results are about your IEEE 1394 controller try updating the driver software.

IEEE 1394 General Troubleshooting MS trouble shooting guide.
IEEE 1394 interface - Wikipedia, the free encyclopedia IEEE 1394 (Also known as firewire)

If the memory checks out and updating all the motherboard drivers dont work , then your next move is to backup data and try a repair install of windows.

before you do the install though, have you thought about running some virus and spyware scans? Sometimes infections can damage system files

Also you can attempt to system restore back to before the problems happened too.

[Kritikal]

I've run memtest86 for 3 full passes, done the HD diagnostics, and have done a low-level format and reinstallation of Windows prior to posting this thread.

I'll check the IEEE 1394 idea before I post again. Thanks for your help thus far.

[Ste]

A reformat and re installation may be your next step, if after that, the problem persists, you are looking at a bad power supply or bad motherboard...

[Mak213]

Originally Posted by Kritikal

I've run memtest86 for 3 full passes, done the HD diagnostics, and have done a low-level format and reinstallation of Windows prior to posting this thread.

I'll check the IEEE 1394 idea before I post again. Thanks for your help thus far.

3 Full passes is not the same as 4 full hours.