3 week old computer many BSOD

I recently bought this compaq presario, and I have had nothing but issues with it..It is set to go back to the company next week, but thought to try a few more things.

I will get random crashes could go 2 days and nothing wrong, or could have 3 crashes in 4 hours..No program seems to cause it, just happensm I have done the destructive recovery option from compaq, 2 times and still nothing..No other hard ware has been put on..Just the stuff from compaq..

Here is my log and I THANK YOU IN ADVANCE...






Opened log file 'c:\debuglog.txt'

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


Loading Dump File [C:\WINDOWS\Minidump\Mini022507-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols; SRV*e:\localsymbols*http://msdl.microsoft.com/download/symbols
Executable search path is: C:\WINDOWS;C:\WINDOWS\system32;C:\WINDOWS\system32\drivers
Windows XP Kernel Version 2600 (Service Pack 2) UP Free x86 compatible
Product: WinNt
Built by: 2600.xpsp_sp2_gdr.050301-1519
Kernel base = 0x804d7000 PsLoadedModuleList = 0x805531a0
Debug session time: Sun Feb 25 01:10:22.656 2007 (GMT-6)
System Uptime: 0 days 1:25:41.225
Loading Kernel Symbols
......................................................................................................................................
Loading User Symbols
Loading unloaded module list
................
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck A, {4, 2, 1, 804ff322}

Probably caused by : ntkrnlpa.exe ( nt!KiTimerExpiration+86 )

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

kd> !analyze -v;r;kv;lmtn;.logclose;q
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

IRQL_NOT_LESS_OR_EQUAL (a)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high. This is usually
caused by drivers using improper addresses.
If a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: 00000004, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000001, value 0 = read operation, 1 = write operation
Arg4: 804ff322, address which referenced memory

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


WRITE_ADDRESS: 00000004

CURRENT_IRQL: 2

FAULTING_IP:
nt!KiTimerExpiration+86
804ff322 895f04 mov dword ptr [edi+4],ebx

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: DRIVER_FAULT

BUGCHECK_STR: 0xA

TRAP_FRAME: f7a3bf38 -- (.trap fffffffff7a3bf38)
.trap fffffffff7a3bf38
ErrCode = 00000002
eax=80552470 ebx=80552470 ecx=84563800 edx=000000ff esi=0000004e edi=00000000
eip=804ff322 esp=f7a3bfac ebp=f7a3bfd0 iopl=0 nv up ei ng nz ac pe cy
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010297
nt!KiTimerExpiration+0x86:
804ff322 895f04 mov dword ptr [edi+4],ebx ds:0023:00000004=????????
.trap
Resetting default scope

LAST_CONTROL_TRANSFER: from 804ff322 to 8053f853

STACK_TEXT:
f7a3bf38 804ff322 badb0d00 000000ff f79850cd nt!KiTrap0E+0x233
f7a3bfd0 80540d5d 80551f80 00000000 0005054e nt!KiTimerExpiration+0x86
f7a3bff4 80540a2a f6ac6814 00000000 00000000 nt!KiRetireDpcList+0x46
f7a3bff8 f6ac6814 00000000 00000000 00000000 nt!KiDispatchInterrupt+0x2a
WARNING: Frame IP not in any known module. Following frames may be wrong.
f7a3bffc 00000000 00000000 00000000 00000000 0xf6ac6814


STACK_COMMAND: kb

FOLLOWUP_IP:
nt!KiTimerExpiration+86
804ff322 895f04 mov dword ptr [edi+4],ebx

SYMBOL_STACK_INDEX: 1

SYMBOL_NAME: nt!KiTimerExpiration+86

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

IMAGE_NAME: ntkrnlpa.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 42250a1d

FAILURE_BUCKET_ID: 0xA_W_nt!KiTimerExpiration+86

BUCKET_ID: 0xA_W_nt!KiTimerExpiration+86

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

eax=ffdff13c ebx=00000002 ecx=00000000 edx=00000000 esi=804ff322 edi=00000004
eip=8053f853 esp=f7a3bf20 ebp=f7a3bf38 iopl=0 nv up ei ng nz na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00000286
nt!KiTrap0E+0x233:
8053f853 f7457000000200 test dword ptr [ebp+70h],20000h ss:0010:f7a3bfa8=00010297
ChildEBP RetAddr Args to Child
f7a3bf38 804ff322 badb0d00 000000ff f79850cd nt!KiTrap0E+0x233 (FPO: [0,0] TrapFrame @ f7a3bf38)
f7a3bfd0 80540d5d 80551f80 00000000 0005054e nt!KiTimerExpiration+0x86 (FPO: [Non-Fpo])
f7a3bff4 80540a2a f6ac6814 00000000 00000000 nt!KiRetireDpcList+0x46 (FPO: [0,0,0])
f7a3bff8 f6ac6814 00000000 00000000 00000000 nt!KiDispatchInterrupt+0x2a (FPO: [Uses EBP] [0,0,1])
WARNING: Frame IP not in any known module. Following frames may be wrong.
f7a3bffc 00000000 00000000 00000000 00000000 0xf6ac6814
start end module name
804d7000 806cd280 nt ntkrnlpa.exe Tue Mar 01 18:34:37 2005 (42250A1D)
806ce000 806ee380 hal halaacpi.dll Wed Aug 04 00:59:05 2004 (41107B29)
b8468000 b847f480 dump_atapi dump_atapi.sys Wed Aug 04 00:59:41 2004 (41107B4D)
b985e000 b9880080 RDPWD RDPWD.SYS Thu Jun 09 18:52:39 2005 (42A8D647)
b9c3e000 b9c42000 mdmxsdk mdmxsdk.sys unavailable (00000000)
b9d32000 b9d83480 srv srv.sys Mon Aug 14 05:34:39 2006 (44E051BF)
b9dac000 b9dec280 HTTP HTTP.sys Thu Mar 16 19:33:09 2006 (441A03C5)
ba638000 ba664400 mrxdav mrxdav.sys Wed Aug 04 01:00:49 2004 (41107B91)
ba753000 ba767400 wdmaud wdmaud.sys Wed Jun 14 04:00:44 2006 (448FD03C)
badf8000 badfb900 ndisuio ndisuio.sys Mon Jun 20 20:52:55 2005 (42B772F7)
bf800000 bf9c1180 win32k win32k.sys Wed Oct 05 19:05:44 2005 (43446A58)
bf9c2000 bf9d3580 dxg dxg.sys Wed Aug 04 01:00:51 2004 (41107B93)
bf9d4000 bfd99a00 nv4_disp nv4_disp.dll Tue May 09 18:33:45 2006 (446126D9)
f36c7000 f36ea000 Fastfat Fastfat.SYS Wed Aug 04 01:14:15 2004 (41107EB7)
f36ea000 f37b14a0 avg7core avg7core.sys Wed Sep 27 08:27:37 2006 (451A7C49)
f37b2000 f37dea00 wg111v2 wg111v2.sys Mon Nov 20 01:48:47 2006 (45615DDF)
f384f000 f385dd80 sysaudio sysaudio.sys Wed Aug 04 01:15:54 2004 (41107F1A)
f38a7000 f3915a00 mrxsmb mrxsmb.sys Fri May 05 04:41:42 2006 (445B1DD6)
f3916000 f3940a00 rdbss rdbss.sys Fri May 05 04:47:55 2006 (445B1F4B)
f3941000 f3962d00 afd afd.sys Wed Aug 04 01:14:13 2004 (41107EB5)
f3963000 f3983f00 ipnat ipnat.sys Wed Sep 29 17:28:36 2004 (415B3714)
f3984000 f39abc00 netbt netbt.sys Wed Aug 04 01:14:36 2004 (41107ECC)
f39ac000 f39bf000 cmdmon cmdmon.sys unavailable (00000000)
f39bf000 f3a16d80 tcpip tcpip.sys Thu Apr 20 06:51:47 2006 (444775D3)
f3a17000 f3a29400 ipsec ipsec.sys Wed Aug 04 01:14:27 2004 (41107EC3)
f3a9a000 f3abb700 portcls portcls.sys Tue Mar 16 13:58:17 2004 (40574E49)
f3abc000 f3eef000 RtkHDAud RtkHDAud.sys Tue Mar 07 23:26:58 2006 (440E6B22)
f68c1000 f68f4200 update update.sys Wed Aug 04 00:58:32 2004 (41107B08)
f68f5000 f6925100 rdpdr rdpdr.sys Wed Aug 04 01:01:10 2004 (41107BA6)
f6926000 f6936e00 psched psched.sys Wed Aug 04 01:04:16 2004 (41107C60)
f6b57000 f6b6d680 ndiswan ndiswan.sys Wed Aug 04 01:14:30 2004 (41107EC6)
f6b8a000 f6b8c280 rasacd rasacd.sys Fri Aug 17 15:55:39 2001 (3B7D84CB)
f6b8e000 f6b90900 Dxapi Dxapi.sys Fri Aug 17 15:53:19 2001 (3B7D843F)
f6b96000 f6bcc580 NVSNPU NVSNPU.SYS Fri Mar 03 16:30:30 2006 (4408C386)
f6bcd000 f6c17780 NVNRM NVNRM.SYS Fri Mar 03 16:30:44 2006 (4408C394)
f6c18000 f6c3d000 HDAudBus HDAudBus.sys Fri Jan 07 19:07:15 2005 (41DF3243)
f6c3d000 f6cf3000 HSX_CNXT HSX_CNXT.sys Tue Dec 06 13:20:41 2005 (4395E489)
f6cf3000 f6dea000 HSX_DP HSX_DP.sys Tue Dec 06 13:20:36 2005 (4395E484)
f6dea000 f6e2f000 HSXHWBS2 HSXHWBS2.sys Tue Dec 06 13:20:48 2005 (4395E490)
f6e2f000 f6e51680 ks ks.sys Wed Aug 04 01:15:20 2004 (41107EF8)
f6e52000 f6e74e80 USBPORT USBPORT.SYS Wed Aug 04 01:08:34 2004 (41107D62)
f6e75000 f6e88780 VIDEOPRT VIDEOPRT.SYS Wed Aug 04 01:07:04 2004 (41107D08)
f6e89000 f71e8340 nv4_mini nv4_mini.sys Tue May 09 18:45:53 2006 (446129B1)
f7231000 f724b580 Mup Mup.sys Wed Aug 04 01:15:20 2004 (41107EF8)
f724c000 f7278a80 NDIS NDIS.SYS Wed Aug 04 01:14:27 2004 (41107EC3)
f7279000 f7305480 Ntfs Ntfs.sys Wed Aug 04 01:15:06 2004 (41107EEA)
f7306000 f731c780 KSecDD KSecDD.sys Wed Aug 04 00:59:45 2004 (41107B51)
f731d000 f732ef00 sr sr.sys Wed Aug 04 01:06:22 2004 (41107CDE)
f732f000 f734e780 fltMgr fltMgr.sys Mon Aug 21 04:14:57 2006 (44E97991)
f734f000 f7366800 SCSIPORT SCSIPORT.SYS Wed Aug 04 00:59:39 2004 (41107B4B)
f7367000 f73aa000 ftsata2 ftsata2.sys Wed Jun 29 05:03:15 2005 (42C271E3)
f73aa000 f73c1480 atapi atapi.sys Wed Aug 04 00:59:41 2004 (41107B4D)
f73c2000 f7496e80 iaStor iaStor.sys Fri Jun 17 09:33:38 2005 (42B2DF42)
f7497000 f74bc700 dmio dmio.sys Wed Aug 04 01:07:13 2004 (41107D11)
f74bd000 f74db880 ftdisk ftdisk.sys Fri Aug 17 15:52:41 2001 (3B7D8419)
f74dc000 f74eca80 pci pci.sys Wed Aug 04 01:07:45 2004 (41107D31)
f74ed000 f751ad80 ACPI ACPI.sys Wed Aug 04 01:07:35 2004 (41107D27)
f761c000 f7624c00 isapnp isapnp.sys Fri Aug 17 15:58:01 2001 (3B7D8559)
f762c000 f763ae80 ohci1394 ohci1394.sys Wed Aug 04 01:10:05 2004 (41107DBD)
f763c000 f7649000 1394BUS 1394BUS.SYS Wed Aug 04 01:10:03 2004 (41107DBB)
f764c000 f7656500 MountMgr MountMgr.sys Wed Aug 04 00:58:29 2004 (41107B05)
f765c000 f7668c80 VolSnap VolSnap.sys Wed Aug 04 01:00:14 2004 (41107B6E)
f766c000 f7674e00 disk disk.sys Wed Aug 04 00:59:53 2004 (41107B59)
f767c000 f7688200 CLASSPNP CLASSPNP.SYS Wed Aug 04 01:14:26 2004 (41107EC2)
f768c000 f7695000 bb_run bb-run.sys Tue Nov 04 18:45:11 2003 (3FA84817)
f769c000 f76a7080 PxHelp20 PxHelp20.sys Fri Aug 19 13:05:00 2005 (43061F4C)
f76ac000 f76b9000 inspect inspect.sys unavailable (00000000)
f76dc000 f76e4900 msgpc msgpc.sys Wed Aug 04 01:04:11 2004 (41107C5B)
f76ec000 f76f5f00 termdd termdd.sys Wed Aug 04 00:58:52 2004 (41107B1C)
f76fc000 f7705480 NDProxy NDProxy.SYS Fri Aug 17 15:55:30 2001 (3B7D84C2)
f770c000 f771a100 usbhub usbhub.sys Wed Aug 04 01:08:40 2004 (41107D68)
f772c000 f773ab80 drmk drmk.sys Wed Aug 04 01:07:54 2004 (41107D3A)
f773c000 f7744700 netbios netbios.sys Wed Aug 04 01:03:19 2004 (41107C27)
f775c000 f7764880 Fips Fips.SYS Fri Aug 17 20:31:49 2001 (3B7DC585)
f776c000 f7774700 wanarp wanarp.sys Wed Aug 04 01:04:57 2004 (41107C89)
f777c000 f778ad80 arp1394 arp1394.sys Wed Aug 04 00:58:28 2004 (41107B04)
f779c000 f77ab900 Cdfs Cdfs.SYS Wed Aug 04 01:14:09 2004 (41107EB1)
f780c000 f781a000 AmdK8 AmdK8.sys Mon Mar 07 15:58:10 2005 (422CCE72)
f781c000 f7826380 imapi imapi.sys Wed Aug 04 01:00:12 2004 (41107B6C)
f782c000 f7838180 cdrom cdrom.sys Wed Aug 04 00:59:52 2004 (41107B58)
f783c000 f784a080 redbook redbook.sys Wed Aug 04 00:59:34 2004 (41107B46)
f784c000 f785b180 nic1394 nic1394.sys Wed Aug 04 00:58:28 2004 (41107B04)
f785c000 f7868e00 i8042prt i8042prt.sys Wed Aug 04 01:14:36 2004 (41107ECC)
f786c000 f7878880 rasl2tp rasl2tp.sys Wed Aug 04 01:14:21 2004 (41107EBD)
f787c000 f7886200 raspppoe raspppoe.sys Wed Aug 04 01:05:06 2004 (41107C92)
f788c000 f7897d00 raspptp raspptp.sys Wed Aug 04 01:14:26 2004 (41107EC2)
f789c000 f78a2200 PCIIDEX PCIIDEX.SYS Wed Aug 04 00:59:40 2004 (41107B4C)
f78a4000 f78a8900 PartMgr PartMgr.sys Fri Aug 17 20:32:23 2001 (3B7DC5A7)
f78ec000 f78f0500 watchdog watchdog.sys Wed Aug 04 01:07:32 2004 (41107D24)
f78f4000 f78fa000 symlcbrd symlcbrd.sys Tue Feb 01 00:13:32 2005 (41FF1E0C)
f7904000 f7908a40 AegisP AegisP.sys Fri Jun 10 09:29:52 2005 (42A9A3E0)
f795c000 f7961500 TDTCP TDTCP.SYS Wed Aug 04 00:58:52 2004 (41107B1C)
f7964000 f7969900 aracpi aracpi.sys Tue Aug 02 18:19:13 2005 (42EFFF71)
f796c000 f7970280 usbohci usbohci.sys Wed Aug 04 01:08:34 2004 (41107D62)
f7974000 f797a980 usbehci usbehci.sys Wed Mar 30 20:13:52 2005 (424B4ED0)
f797c000 f7983580 Modem Modem.SYS Wed Aug 04 01:08:04 2004 (41107D44)
f7984000 f7989a00 mouclass mouclass.sys Wed Aug 04 00:58:32 2004 (41107B08)
f798c000 f7992000 kbdclass kbdclass.sys Wed Aug 04 00:58:32 2004 (41107B08)
f7994000 f7998880 TDI TDI.SYS Wed Aug 04 01:07:47 2004 (41107D33)
f79a4000 f79a8580 ptilink ptilink.sys Fri Aug 17 15:49:53 2001 (3B7D8371)
f79ac000 f79b0080 raspti raspti.sys Fri Aug 17 15:55:32 2001 (3B7D84C4)
f79d4000 f79d9200 vga vga.sys Wed Aug 04 01:07:06 2004 (41107D0A)
f79dc000 f79e0a80 Msfs Msfs.SYS Wed Aug 04 01:00:37 2004 (41107B85)
f79e4000 f79eb880 Npfs Npfs.SYS Wed Aug 04 01:00:38 2004 (41107B86)
f79ec000 f79f2780 USBSTOR USBSTOR.SYS Wed Aug 04 01:08:44 2004 (41107D6C)
f7a1c000 f7a23000 avg7rsxp avg7rsxp.sys unavailable (00000000)
f7a2c000 f7a2f000 BOOTVID BOOTVID.dll Fri Aug 17 15:49:09 2001 (3B7D8345)
f7ae4000 f7ae7300 nvnetbus nvnetbus.sys Fri Mar 03 16:31:02 2006 (4408C3A6)
f7ae8000 f7aea780 arpolicy arpolicy.sys Tue Aug 02 18:19:13 2005 (42EFFF71)
f7aec000 f7aee580 ndistapi ndistapi.sys Fri Aug 17 15:55:29 2001 (3B7D84C1)
f7b0c000 f7b0fc80 mssmbios mssmbios.sys Wed Aug 04 01:07:47 2004 (41107D33)
f7b1c000 f7b1db80 kdcom kdcom.dll Fri Aug 17 15:49:10 2001 (3B7D8346)
f7b1e000 f7b1f100 WMILIB WMILIB.SYS Fri Aug 17 16:07:23 2001 (3B7D878B)
f7b20000 f7b21500 viaide viaide.sys Wed Aug 04 00:59:42 2004 (41107B4E)
f7b22000 f7b23580 intelide intelide.sys Wed Aug 04 00:59:40 2004 (41107B4C)
f7b24000 f7b25700 dmload dmload.sys Fri Aug 17 15:58:15 2001 (3B7D8567)
f7b38000 f7b39380 armoucfltr armoucfltr.sys Tue Aug 02 18:19:15 2005 (42EFFF73)
f7b3a000 f7b3b500 arkbcfltr arkbcfltr.sys Tue Aug 02 18:19:14 2005 (42EFFF72)
f7b3c000 f7b3d100 swenum swenum.sys Wed Aug 04 00:58:41 2004 (41107B11)
f7b3e000 f7b3f280 USBD USBD.SYS Fri Aug 17 16:02:58 2001 (3B7D8682)
f7b46000 f7b47f00 Fs_Rec Fs_Rec.SYS Fri Aug 17 15:49:37 2001 (3B7D8361)
f7b48000 f7b49080 Beep Beep.SYS Fri Aug 17 15:47:33 2001 (3B7D82E5)
f7b4a000 f7b4b080 mnmdd mnmdd.SYS Fri Aug 17 15:57:28 2001 (3B7D8538)
f7b4c000 f7b4d080 RDPCDD RDPCDD.sys Fri Aug 17 15:46:56 2001 (3B7D82C0)
f7b50000 f7b51080 avg7rsw avg7rsw.sys Tue Jul 26 07:10:51 2005 (42E6284B)
f7b74000 f7b75100 dump_WMILIB dump_WMILIB.SYS Fri Aug 17 16:07:23 2001 (3B7D878B)
f7bb2000 f7bb3360 avgtdi avgtdi.sys Thu Aug 25 04:59:58 2005 (430D969E)
f7be4000 f7be4d00 pciide pciide.sys Fri Aug 17 15:51:49 2001 (3B7D83E5)
f7be5000 f7be5680 giveio giveio.sys Wed Apr 03 21:33:25 1996 (316334F5)
f7bf5000 f7bf6000 guard guard.sys unavailable (00000000)
f7cae000 f7caeb80 Null Null.SYS Fri Aug 17 15:47:39 2001 (3B7D82EB)
f7caf000 f7cb0000 AvgAsCln AvgAsCln.sys unavailable (00000000)
f7cb0000 f7cb1000 avgclean avgclean.sys unavailable (00000000)
f7d3c000 f7d3cc00 audstub audstub.sys Fri Aug 17 15:59:40 2001 (3B7D85BC)
f7d58000 f7d58d00 dxgthk dxgthk.sys Fri Aug 17 15:53:12 2001 (3B7D8438)

Unloaded modules:
b9098000 b90c3000 kmixer.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
f36af000 f36c7000 dump_atapi.s
Timestamp: unavailable (00000000)
Checksum: 00000000
b9113000 b913e000 kmixer.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
b9a39000 b9a64000 kmixer.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
ba665000 ba690000 kmixer.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
f7c50000 f7c51000 drmkaud.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
ba730000 ba753000 aec.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
bae38000 bae45000 DMusic.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
bae58000 bae66000 swmidi.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
f7b98000 f7b9a000 splitter.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
ba6d0000 ba6e0000 Serial.SYS
Timestamp: unavailable (00000000)
Checksum: 00000000
f774c000 f7755000 processr.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
f79cc000 f79d1000 Cdaudio.SYS
Timestamp: unavailable (00000000)
Checksum: 00000000
f6b8e000 f6b91000 Sfloppy.SYS
Timestamp: unavailable (00000000)
Checksum: 00000000
f79c4000 f79c9000 Flpydisk.SYS
Timestamp: unavailable (00000000)
Checksum: 00000000
f79bc000 f79c3000 Fdc.SYS
Timestamp: unavailable (00000000)
Checksum: 00000000
Closing open log file c:\debuglog.txt

 

Hi, longtimefan. Welcome to Windows BBS!

Thanks for posting your DebugWiz-generated dump info.

If you post a couple more DebugWiz-generated reports for other recent BSOD dumps, those might help BSOD experts nail down the culprit more easily. BSOD experts seem to routinely ask for 2 or 3 dump analysis reports to help them determine whether the issue appears hardware-related or not (especially when the dump log points to a Windows protected system file, as in your case).

I think you do not need to include the module list portions (from "start end module name" to the end of the debuglog.txt report) of your other dumps though since I think they're going to be the same as your already-posted report. (BSOD experts, please correct me if I am wrong.)

BSOD experts seem to often suggest stress-testing RAM when troubleshooting BSODs.

In case you decide to test your RAM for errors, all of the following RAM testers have been recommended in this forum. However, there are differing opinions on which RAM tester is "best ".

• Microsoft's Windows Memory Diagnostic
• Memtest86
• 
  [*]DocMem

 

Thnaks for your reply..And you are correct about same errors..Before I did the recovery option the dumps did have that same file listed.. Searching about it didnt provided to much info for me..But did find this..

http://www.auditmysoftware.com/process/ntkrnlpa

rocess: Ntkrnlpa.exe

Program: Operating System Kernel

Publisher: Microsoft Corporation

Purpose: Main OS file

Propriety: Potentially Undesirable

Perception: System

Postscript: Operating System Kernel could be legitimate Windows OS process. Operating System Kernel is the Operating System (OS) kernel for computers with memory of 4GB or more. CAUTION: Various trojan/worm/spyware overwrite or create a file by this name.

I have avg anti spyware along with spybot..All have had updates and scanned systems with nothing found..did a hijack log and again tomcoyotes fourm found nothign wrong with my log..I also have comodo firewall installed.

I have done the updates for my video drivers, but no need for bios updates as the available one is same version as I have.


Here is a dump w/o the parts you said not to include, that I have from the 1st day after I did the recovery..

I am doing the memory test from Microsoft now and see what that turns up..

Thanks again !!



Opened log file 'c:\debuglog.txt'

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


Loading Dump File [C:\WINDOWS\Minidump\Mini022207-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols; SRV*e:\localsymbols*http://msdl.microsoft.com/download/symbols
Executable search path is: C:\WINDOWS;C:\WINDOWS\system32;C:\WINDOWS\system32\drivers
Windows XP Kernel Version 2600 (Service Pack 2) UP Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 2600.xpsp_sp2_gdr.050301-1519
Kernel base = 0x804d7000 PsLoadedModuleList = 0x805531a0
Debug session time: Thu Feb 22 19:06:36.656 2007 (GMT-6)
System Uptime: 0 days 3:04:53.231
Loading Kernel Symbols
.....................................................................................................................................
Loading User Symbols
Loading unloaded module list
...............
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000000A, {0, 2, 1, 804ff320}

Probably caused by : ntkrnlpa.exe ( nt!KiTimerExpiration+84 )

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

kd> !analyze -v;r;kv;lmtn;.logclose;q
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

IRQL_NOT_LESS_OR_EQUAL (a)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high. This is usually
caused by drivers using improper addresses.
If a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: 00000000, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000001, value 0 = read operation, 1 = write operation
Arg4: 804ff320, address which referenced memory

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


WRITE_ADDRESS: 00000000

CURRENT_IRQL: 2

FAULTING_IP:
nt!KiTimerExpiration+84
804ff320 893b mov dword ptr [ebx],edi

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: DRIVER_FAULT

BUGCHECK_STR: 0xA

PROCESS_NAME: firefox.exe

LAST_CONTROL_TRANSFER: from 80540d5d to 804ff320

STACK_TEXT:
f7a3bfd0 80540d5d 80551f80 00000000 000ad54e nt!KiTimerExpiration+0x84
f7a3bff4 80540a2a f3cf2d44 00000000 00000000 nt!KiRetireDpcList+0x46
f7a3bff8 f3cf2d44 00000000 00000000 00000000 nt!KiDispatchInterrupt+0x2a
WARNING: Frame IP not in any known module. Following frames may be wrong.
80540a2a 00000000 00000009 bb835675 00000128 0xf3cf2d44


STACK_COMMAND: kb

FOLLOWUP_IP:
nt!KiTimerExpiration+84
804ff320 893b mov dword ptr [ebx],edi

SYMBOL_STACK_INDEX: 0

SYMBOL_NAME: nt!KiTimerExpiration+84

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

IMAGE_NAME: ntkrnlpa.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 42250a1d

FAILURE_BUCKET_ID: 0xA_W_nt!KiTimerExpiration+84

BUCKET_ID: 0xA_W_nt!KiTimerExpiration+84

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

eax=80552470 ebx=00000000 ecx=835f3888 edx=000000ff esi=0000004e edi=00000000
eip=804ff320 esp=f7a3bfac ebp=f7a3bfd0 iopl=0 nv up ei ng nz ac pe cy
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010297
nt!KiTimerExpiration+0x84:
804ff320 893b mov dword ptr [ebx],edi ds:0023:00000000=????????
ChildEBP RetAddr Args to Child
f7a3bfd0 80540d5d 80551f80 00000000 000ad54e nt!KiTimerExpiration+0x84 (FPO: [Non-Fpo])
f7a3bff4 80540a2a f3cf2d44 00000000 00000000 nt!KiRetireDpcList+0x46 (FPO: [0,0,0])
f7a3bff8 f3cf2d44 00000000 00000000 00000000 nt!KiDispatchInterrupt+0x2a (FPO: [Uses EBP] [0,0,1])
WARNING: Frame IP not in any known module. Following frames may be wrong.
80540a2a 00000000 00000009 bb835675 00000128 0xf3cf2d44

Unloaded modules:
b873d000 b8768000 kmixer.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
b8b3f000 b8b6a000 kmixer.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
b8c0a000 b8c35000 kmixer.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
ba67c000 ba6a7000 kmixer.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
f7cd6000 f7cd7000 drmkaud.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
ba7f7000 ba804000 DMusic.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
ba6a7000 ba6ca000 aec.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
ba827000 ba835000 swmidi.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
f7b78000 f7b7a000 splitter.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
ba6ea000 ba6fa000 Serial.SYS
Timestamp: unavailable (00000000)
Checksum: 00000000
f771c000 f7725000 processr.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
f799c000 f79a1000 Cdaudio.SYS
Timestamp: unavailable (00000000)
Checksum: 00000000
f6ab2000 f6ab5000 Sfloppy.SYS
Timestamp: unavailable (00000000)
Checksum: 00000000
f7994000 f7999000 Flpydisk.SYS
Timestamp: unavailable (00000000)
Checksum: 00000000
f798c000 f7993000 Fdc.SYS
Timestamp: unavailable (00000000)
Checksum: 00000000
Closing open log file c:\debuglog.txt

 

Okay I ran both Microsoft's Windows Memory Diagnostic and Memtest86..

Windows ran for about 45 mins and no errors found..Mem test for about 6 hours using the standard test and no errors found..

Not sure if I posted this..

but I have windows media edition, and I just foubnd out my Netgear usb wireless adapter to connect to my router..and netgear DOES NOT support media edition..

so that is probably my issue?

 

From the stack trace, it is memory problem. Some faulty ram can pass memtest. Make sure that the ram is compatible to the motherboard.

For example : If the ram and the motherboard has dual mode compatibility problem, you must stop using dual mode and switch to single channel mode

 

Thanks for the reply..But this is all pre built from compaq, wouldnt they make sure it was all compatible?

And how would I go about verify if they are compatible..I am not really sure how to check that..

Thanks again!!

 

This is not compatibility issue between the ram and m/b. If you have spare ram from another PC, swap the ram.

 

Okay I will give that a shot, thanks for all your help

 

I back Christer 100%.

PS
A bit of experience speaking.

Not with a PC but other things.

BillyBob

 

Ditto on the above. If you aren't careful you will wind up with a machine and the manufacturers terms of what they will and will not fix. I'd return it to the place of purchase and absolutely insist on a replacement or a refund, not just a fix. If it was a builder, then I'd go with a fix but a major mfg isn't equipped to fix it locally and that means third party involvement and that in turn means you get to be the gopher and the guinnea pig.

 

I fully understand that..but opening the case happened the 1st time I called tech sip[port..They told me to do it LOL

and if my wirelss netgear issue doesnt solve this problem, I am sending it back...Wont mess with switching ram around..

 

I also support Christer's recommendation. I've been in your situation when tech support (my local builder) instructed me to "open the box ". I then requested he send me a email giving me permission to open the box. I never had to refer back to the email, but it is always nice to have warranty issues in writing.

 

Just an update, I shipped it out last week Sunday and it is on its way back as of today..

customer service couldn't answer my questions on what was wrong with it..But I should have it back by Tuesday

But someone from Net Gear did offer this advice on the irq BSOD ( I was talking with them cuz of numerous dropped connections on my wireless usb adapter)



This can occur when you have many ports, for instance camera readers, that each require a bit of IRQ, or interrupt request, to operate. The interrupt request is the map that your computer has to everything connected to it. Too many ports, even if they're not in use, eat up your available IRQ, and can cause this crash when Windows tries accessing something and is out of IRQ to hand out.

To fix this, simply disable in BIOS ports that are not used: if you do not have a traditional parallel port, try disabling that. You'll need to consult your manufacturer for how to do this for your specific motherboard and system.



Wanted to thank everyone for the help and when the puter comes back there is suppose to be a repair sheet with it and what they did..I'll post that

 

just a fast update...that computer was still giving the same errors even after being repaired by them..

So in order to help me out, they sent me a brand new one..Not same model, a totaly different one with major upgrades from what I had paid for..

1 gb of ram, with 4 more slots to add more ram...... only had 512 b4...

H/d about 1/3 bigger..

Chip set and processor is even a step or 2 above on what I had prior, along with windows Vista..

So in a sense I got a $800 machine for 480$

Thanks for everyones input and help!!