Xp is crashing! BSOD

I would listen to this man!! cpc2004 post #78

He knows from which he speaks as do I and I see the same!

Check RAM, power supply, video card.

And outlet power from wall for possible spikes and brownout conditions!!!!!!!!!!!!!!!!!!

Jakex

 

I've been thinking about that statement, and I feel it sounds like the parent that tells their child 'because I said so'. While I may sometimes be that type of parent, I'm not your's and I don't mean to come off that way. I also know that were it me sitting in your seat, I would be left wanting to know why the modem is being called upon, and it would eat at me (cuz I'm a need-to-know-why type of guy). So, I thought I would try to shed some light on the 'why', as best I can. Bear in mind, that the forthcoming explanation consists of 1 part knowledge, 1 part logic, and zero parts expertise (I don't have any expertise), and may not be entirely correct. Heck, it might be totally wrong, but it sounds sensible.

When you start your computer for the first time after an installation of the operating system or the addition of a new piece of hardware, Windows' Hardware Detection wizard recognizes that there is new hardware and proceeds to install drivers for it, thereby making it a useable resource. Anytime you restart the computer after that, Windows knows where the drivers are for the hardware it detects and loads them, so that the resource is available without the need to re-install the drivers again. So, knowing that the modem drivers are automatically loaded when you start the system, we also know it's seen as an available resource. The Windows operating system is it's own resource manager, and it's doles out it's available resources to various processes in such a way as to attempt keeping an even kilter; not taking away too much from any 1 process, while allotting the one's in need of more as much as it can. Windows also determines what type of resource it has available for each process and will make it available when needed.

Among other things, a dump log shows us what you were doing at the time of a crash. Ok, that's only a partially correct statement. More precisely, it shows us how your computer responded to what you were doing at the time of the crash by telling us what drivers it called upon. That translates to the resource being called upon.

I can't tell you exactly what caused Windows to call upon the resource made available by the modem, but that's what is happening in every log you've posted. I do know that it called upon it only because it's available, and Windows needed to provide more of the type of resource that the modem provides to a process. My guess is bandwidth, which is also made available by the ethernet connection. In trying to keep the load on the available resources well balanced, Windows is trying to throw some of the need onto the modem.

In my opinion, it's important to uninstall a device via the device manager before physically removing it. This tells Windows that the device is no longer an available resource, and removes the device's drivers from it's list of known drivers to load.

I don't KNOW that the modem is the cause of the crashes, but I do know that removing it is a good place to start.

 

I am disappointed (and frustrated) with the information Everest is now reporting (for the reasons mattman stated). "The "unknown" status bugs me.

Out of curiousity, when you boot, what BIOS information is displayed on one of the initial black screens?

If you press the Pause/Break key immediately when the BIOS info appears, that should stop the boot process and allow you time to write down the information. Once you have written the BIOS information, you can press the Enter key to continue with the boot.


Per noahdfear's strong recommendation to leave the BIOS alone for now, I will not continue with further suggestions regarding flashing the BIOS for your situation and will leave those suggestions up to others.

I profusely apologize for suggesting such a potentially dangerous action.


cpc2004 is considered around here to be an expert regarding analyzing dump logs. I would certainly fully investigate possible issues cpc2004 has presented (as Jakex also apparently thinks you should do).

Even though noahdfear stated,

I disagree. I have read many messages he has posted that indicate the opposite. He might not be an expert at analyzing dump logs but he certainly is an expert in many other respects.

If you want to read other messages noahdfear has posted to help determine whether he is worthy of listening to, please click here and read the associated threads.

 

Well thanks for all these replies, I will uninstall and remove the modem tomorrow as now it's late. I will let you know how it goes.

 

Tcm9669: We'll all be looking forward to see what happens. It can be confusing when advice is coming from many different quarters but you are fortunate in that several of the best this board has to offer are following your thread.

Mailman: Don't let Dave's comments turn you into a Conscienctious Objector re: the BIOS. In general, I am both in agreement and disagreement with Dave's comments. Flashing a BIOS is no "willy-nilly, lets try it just in case it might work" solution. Done incorrectly, it will render a machine unbootable. If there is no specific reason for flashing a BIOS except to get the latest revision, I would agree with Dave. However, motherboard manufacturers update BIOS files to resolve very specific issues and if a problem resolution is referenced in a BIOS revision, by all means - its time to flash. I'd also like to draw your attention to a little device called the BIOS Savior - you can find this at ESKIT Data's web site in Sweden and it permits mounting a second BIOS chip piggybacked with a toggle switch. One can test or use different revisions and even use this for fixing bad flashes without an EEPROM programmer.

 

Couldn't have said it better myself.

 

Well let's just leave this BIOS thing, the now I upgraded it and everything went fine! No problems so let's just leave it... now I just uninstalled and physically removed the modem! Now cross your fingers and hope that I never see a BSOD again! Thanks.

 

Thanks again, guys! Rest assured, I'll stick around and help when I can.

Tcm9669, you got it. I won't say that "dirty acronym" again in this thread for awhile unless someone else mentions it again or unless I discover something I'm fairly certain applies to your issue.

Rockster, thanks for your tip about the toggle (described here? - no mention of "ESKIT" or Sweden) Given I like to tinker, looks like something I want to get for my own machine.

 

Approximately one hour later -> System is running fine!

 

An hour is a good start. Keep us posted in the days to come please.

 

Yes, you can bet on that! If this will resolve my issue I will try to be active on this forum. And perhaps help others with minor issues, more software related. Keep your fingers crossed until now no crashes (so as not to mention that acronym lol)

EDIT: Another hour, still ok. I'm going to leave it overnight, I will let you know if it crashes during the night.

Thanks.

 

I left my PC overnight, It didn't crash!! Yes, but that doesn't mean it's fixed, because sometimes my PC takes 3 or four days before it crashes again.. It is absolutely random, it can crash like 10 times in a few hours, or it can crash just one time in 4 days! So let's see, I will keep you updated.

Thanks.

 

Well it crashed again, I will post the dump file when I get back from work.

 

Well this one was cause by 'CLASSPNP.SYS', this is the first time that a crash was caused by that file. Here is the dump file:


Opened log file 'c:\debuglog.txt'

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


Loading Dump File [C:\WINDOWS\Minidump\Mini081407-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
Executable search path is: C:\WINDOWS;C:\WINDOWS\system32;C:\WINDOWS\system32\drivers
Windows XP Kernel Version 2600 (Service Pack 2) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 2600.xpsp_sp2_rtm.040803-2158
Kernel base = 0x804d7000 PsLoadedModuleList = 0x805644a0
Debug session time: Mon Aug 13 23:06:32.296 2007 (GMT+2)
System Uptime: 0 days 5:53:16.969
Loading Kernel Symbols
.........................................................................................................................................
Loading User Symbols
Loading unloaded module list
...........
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 100000D1, {7a67ed50, 2, 1, f787fa41}

*** ERROR: Symbol file could not be found. Defaulted to export symbols for avg7rsw.sys -
Probably caused by : CLASSPNP.SYS ( CLASSPNP!NewTransferPacket+6a )

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

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

DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
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 kernel debugger is available get stack backtrace.
Arguments:
Arg1: 7a67ed50, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000001, value 0 = read operation, 1 = write operation
Arg4: f787fa41, address which referenced memory

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


WRITE_ADDRESS: 7a67ed50

CURRENT_IRQL: 2

FAULTING_IP:
CLASSPNP!NewTransferPacket+6a
f787fa41 8937 mov dword ptr [edi],esi

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: DRIVER_FAULT

BUGCHECK_STR: 0xD1

PROCESS_NAME: firefox.exe

LAST_CONTROL_TRANSFER: from f787fa66 to f787fa41

STACK_TEXT:
b0be569c f787fa66 867c80f8 00000000 85a0b4e0 CLASSPNP!NewTransferPacket+0x6a
b0be56b0 f787ece1 867e09a0 00000001 867e0a58 CLASSPNP!DequeueFreeTransferPacket+0x44
b0be56e4 f787ee49 867e09a0 000a1000 85a0b4e0 CLASSPNP!ServiceTransferRequest+0x68
b0be5708 804e19ee 867e09a0 00000000 8677ecb0 CLASSPNP!ClassReadWrite+0xff
b0be5718 f7ab636c 867cbee8 85a0b628 b0be5754 nt!IopfCallDriver+0x31
b0be5728 804e19ee 86746198 85a0b4e0 85a0b64c PartMgr!PmReadWrite+0x93
b0be5738 f77b01c6 86768100 867463c0 85a0b400 nt!IopfCallDriver+0x31
b0be5754 804e19ee 867cbe30 85a0b4e0 867456e0 ftdisk!FtDiskReadWrite+0x194
b0be5764 f784e51a 867cb5d8 867cb5d8 b0be5794 nt!IopfCallDriver+0x31
b0be5774 804e19ee 867cb5d8 85a0b4e0 85a0b4e0 VolSnap!VolSnapRead+0x26
b0be5784 f7685243 864fa7b8 85a0b4e0 b0be5974 nt!IopfCallDriver+0x31
b0be5794 f7684da6 864fa7b8 867cb5d8 fdb04000 Ntfs!NtfsSingleAsync+0x6d
b0be5974 f76876fe 864fa7b8 85a0b4e0 e47157b0 Ntfs!NtfsNonCachedIo+0x2f8
b0be5a54 f7686fbf 864fa7b8 85a0b4e0 00000001 Ntfs!NtfsCommonRead+0xbdd
b0be5af4 804e19ee 86768020 85a0b4e0 867c5820 Ntfs!NtfsFsdRead+0x22d
b0be5b04 f7728459 b0be5b50 804e19ee 86769dd0 nt!IopfCallDriver+0x31
b0be5b0c 804e19ee 86769dd0 85a0b4e0 85a0b4e0 sr!SrPassThrough+0x31
b0be5b1c f7d9245c 86138ec0 86296f38 8662ad00 nt!IopfCallDriver+0x31
WARNING: Stack unwind information not available. Following frames may be wrong.
b0be5b50 8051c19d 86465808 85a22c09 8662ad08 avg7rsw!AvgWrapAllocatePoolWithTag+0x6e
b0be5b70 805e58b8 86138ec0 85a22c70 8662ad08 nt!IoAsynchronousPageRead+0x1b
b0be5b98 805e571e 85fc6008 00000000 00000012 nt!MiPfExecuteReadList+0x4b
b0be5bc4 805e3c4e 00000086 00000061 00000000 nt!MmPrefetchPages+0xf9
b0be5c4c 805e3b6a b0be5c74 01000000 00000000 nt!CcPfPrefetchSections+0x3b0
b0be5c8c 805e3d1d e5430000 00080000 85a12020 nt!CcPfPrefetchScenario+0x7b
b0be5d08 8058ad59 85a12020 e11ca4f0 00000000 nt!CcPfBeginAppLaunch+0x158
b0be5d50 804eed86 00000000 7c810867 00000001 nt!PspUserThreadStartup+0xeb
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16


STACK_COMMAND: kb

FOLLOWUP_IP:
CLASSPNP!NewTransferPacket+6a
f787fa41 8937 mov dword ptr [edi],esi

SYMBOL_STACK_INDEX: 0

SYMBOL_NAME: CLASSPNP!NewTransferPacket+6a

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: CLASSPNP

IMAGE_NAME: CLASSPNP.SYS

DEBUG_FLR_IMAGE_TIMESTAMP: 41107ec2

FAILURE_BUCKET_ID: 0xD1_W_CLASSPNP!NewTransferPacket+6a

BUCKET_ID: 0xD1_W_CLASSPNP!NewTransferPacket+6a

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

eax=00000000 ebx=867c8008 ecx=867c8090 edx=00000000 esi=86097828 edi=7a67ed50
eip=f787fa41 esp=b0be5690 ebp=b0be569c iopl=0 nv up ei pl zr na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010246
CLASSPNP!NewTransferPacket+0x6a:
f787fa41 8937 mov dword ptr [edi],esi ds:0023:7a67ed50=????????
ChildEBP RetAddr Args to Child
b0be569c f787fa66 867c80f8 00000000 85a0b4e0 CLASSPNP!NewTransferPacket+0x6a (FPO: [Non-Fpo])
b0be56b0 f787ece1 867e09a0 00000001 867e0a58 CLASSPNP!DequeueFreeTransferPacket+0x44 (FPO: [Non-Fpo])
b0be56e4 f787ee49 867e09a0 000a1000 85a0b4e0 CLASSPNP!ServiceTransferRequest+0x68 (FPO: [Non-Fpo])
b0be5708 804e19ee 867e09a0 00000000 8677ecb0 CLASSPNP!ClassReadWrite+0xff (FPO: [Non-Fpo])
b0be5718 f7ab636c 867cbee8 85a0b628 b0be5754 nt!IopfCallDriver+0x31 (FPO: [0,0,0])
b0be5728 804e19ee 86746198 85a0b4e0 85a0b64c PartMgr!PmReadWrite+0x93 (FPO: [Non-Fpo])
b0be5738 f77b01c6 86768100 867463c0 85a0b400 nt!IopfCallDriver+0x31 (FPO: [0,0,0])
b0be5754 804e19ee 867cbe30 85a0b4e0 867456e0 ftdisk!FtDiskReadWrite+0x194 (FPO: [Non-Fpo])
b0be5764 f784e51a 867cb5d8 867cb5d8 b0be5794 nt!IopfCallDriver+0x31 (FPO: [0,0,0])
b0be5774 804e19ee 867cb5d8 85a0b4e0 85a0b4e0 VolSnap!VolSnapRead+0x26 (FPO: [Non-Fpo])
b0be5784 f7685243 864fa7b8 85a0b4e0 b0be5974 nt!IopfCallDriver+0x31 (FPO: [0,0,0])
b0be5794 f7684da6 864fa7b8 867cb5d8 fdb04000 Ntfs!NtfsSingleAsync+0x6d (FPO: [Non-Fpo])
b0be5974 f76876fe 864fa7b8 85a0b4e0 e47157b0 Ntfs!NtfsNonCachedIo+0x2f8 (FPO: [Non-Fpo])
b0be5a54 f7686fbf 864fa7b8 85a0b4e0 00000001 Ntfs!NtfsCommonRead+0xbdd (FPO: [Non-Fpo])
b0be5af4 804e19ee 86768020 85a0b4e0 867c5820 Ntfs!NtfsFsdRead+0x22d (FPO: [Non-Fpo])
b0be5b04 f7728459 b0be5b50 804e19ee 86769dd0 nt!IopfCallDriver+0x31 (FPO: [0,0,0])
b0be5b0c 804e19ee 86769dd0 85a0b4e0 85a0b4e0 sr!SrPassThrough+0x31 (FPO: [Non-Fpo])
b0be5b1c f7d9245c 86138ec0 86296f38 8662ad00 nt!IopfCallDriver+0x31 (FPO: [0,0,0])
WARNING: Stack unwind information not available. Following frames may be wrong.
b0be5b50 8051c19d 86465808 85a22c09 8662ad08 avg7rsw!AvgWrapAllocatePoolWithTag+0x6e
b0be5b70 805e58b8 86138ec0 85a22c70 8662ad08 nt!IoAsynchronousPageRead+0x1b (FPO: [Non-Fpo])
start end module name
804d7000 80704000 nt ntkrnlmp.exe Wed Aug 04 08:18:18 2004 (41107FAA)
80704000 80724d00 hal halmacpi.dll Wed Aug 04 07:59:09 2004 (41107B2D)
b00cc000 b00f5f00 kmixer kmixer.sys Wed Aug 04 08:07:46 2004 (41107D32)
b0468000 b04a8380 HTTP HTTP.sys Wed Aug 04 08:00:09 2004 (41107B69)
b06b1000 b07283a0 HSF_V124 HSF_V124.sys Tue May 29 18:05:40 2001 (3B13C8D4)
b07b9000 b07c5620 HSF_TONE HSF_TONE.sys Tue May 29 18:08:53 2001 (3B13C995)
b0841000 b0893180 srv srv.sys Wed Aug 04 08:14:44 2004 (41107ED4)
b0894000 b08c4c00 HSF_FAXX HSF_FAXX.sys Tue May 29 18:09:54 2001 (3B13C9D2)
b08c5000 b0924800 HSF_K56K HSF_K56K.sys Tue May 29 18:11:09 2001 (3B13CA1D)
b0925000 b0941440 HSF_FSKS HSF_FSKS.sys Tue May 29 18:10:42 2001 (3B13CA02)
b0942000 b0988c40 HSF_FALL HSF_FALL.sys Tue May 29 18:08:30 2001 (3B13C97E)
b0a79000 b0aa5400 mrxdav mrxdav.sys Wed Aug 04 08:00:49 2004 (41107B91)
b0ada000 b0adce40 mdmxsdk mdmxsdk.sys Wed Mar 17 20:04:10 2004 (4058A12A)
b0b86000 b0b8e080 ipfltdrv ipfltdrv.sys Fri Aug 17 22:55:07 2001 (3B7D84AB)
b0e33000 b0e47400 wdmaud wdmaud.sys Wed Aug 04 08:15:03 2004 (41107EE7)
b30ea000 b30f9900 Cdfs Cdfs.SYS Wed Aug 04 08:14:09 2004 (41107EB1)
b33aa000 b33ac900 Dxapi Dxapi.sys Fri Aug 17 22:53:19 2001 (3B7D843F)
b362f000 b3630360 avgtdi avgtdi.sys Thu Aug 25 11:59:58 2005 (430D969E)
b373b000 b373e280 ndisuio ndisuio.sys Wed Aug 04 08:03:10 2004 (41107C1E)
b3743000 b3746780 dump_scsiport dump_scsiport.sys Wed Aug 04 07:59:51 2004 (41107B57)
b38e6000 b3909000 Fastfat Fastfat.SYS Wed Aug 04 08:14:15 2004 (41107EB7)
b6783000 b67a9bc0 omcamvid omcamvid.sys Fri Sep 07 23:28:12 2001 (3B993BEC)
b68d1000 b69996c0 avg7core avg7core.sys Fri Jun 15 11:13:22 2007 (46725832)
b699a000 b6a08380 mrxsmb mrxsmb.sys Wed Aug 04 08:15:14 2004 (41107EF2)
b6a09000 b6a34180 rdbss rdbss.sys Wed Aug 04 08:20:05 2004 (41108015)
b7057000 b7078d00 afd afd.sys Wed Aug 04 08:14:13 2004 (41107EB5)
b7079000 b70a0c00 netbt netbt.sys Wed Aug 04 08:14:36 2004 (41107ECC)
b70a1000 b70c1f00 ipnat ipnat.sys Wed Aug 04 08:04:48 2004 (41107C80)
b719a000 b71f1a80 tcpip tcpip.sys Wed Aug 04 08:14:39 2004 (41107ECF)
b71f2000 b7204400 ipsec ipsec.sys Wed Aug 04 08:14:27 2004 (41107EC3)
b7b91000 b7b99880 Fips Fips.SYS Sat Aug 18 03:31:49 2001 (3B7DC585)
b7f73000 b7f7b700 netbios netbios.sys Wed Aug 04 08:03:19 2004 (41107C27)
b7f83000 b7f8b700 wanarp wanarp.sys Wed Aug 04 08:04:57 2004 (41107C89)
b7fd3000 b7fe1d00 dump_viamraid dump_viamraid.sys Mon Jul 05 03:52:59 2004 (40E8B47B)
b8340000 b8347880 Npfs Npfs.SYS Wed Aug 04 08:00:38 2004 (41107B86)
b8348000 b834ca80 Msfs Msfs.SYS Wed Aug 04 08:00:37 2004 (41107B85)
b8350000 b8355200 vga vga.sys Wed Aug 04 08:07:06 2004 (41107D0A)
b9211000 b9215500 watchdog watchdog.sys Wed Aug 04 08:07:32 2004 (41107D24)
b9219000 b921e000 flpydisk flpydisk.sys Wed Aug 04 07:59:24 2004 (41107B3C)
b9239000 b923e820 OVTCAMD OVTCAMD.SYS Fri Aug 31 19:56:07 2001 (3B8FCFB7)
b935f000 b9361280 rasacd rasacd.sys Fri Aug 17 22:55:39 2001 (3B7D84CB)
b9429000 b9434e00 STREAM STREAM.SYS Wed Aug 04 08:07:58 2004 (41107D3E)
bf800000 bf9c0380 win32k win32k.sys Wed Aug 04 08:17:30 2004 (41107F7A)
bf9c1000 bf9d2580 dxg dxg.sys Wed Aug 04 08:00:51 2004 (41107B93)
bf9d3000 bfa16000 ati2dvag ati2dvag.dll Wed May 03 18:51:00 2006 (4458DF74)
bfa16000 bfa5b000 ati2cqag ati2cqag.dll Wed May 03 18:09:20 2006 (4458D5B0)
bfa5b000 bfa91000 atikvmag atikvmag.dll Wed May 03 18:15:58 2006 (4458D73E)
bfa91000 bfd228a0 ati3duag ati3duag.dll Wed May 03 18:35:24 2006 (4458DBCC)
bfd23000 bfe7ac00 ativvaxx ativvaxx.dll Wed May 03 18:29:13 2006 (4458DA59)
bffa0000 bffe5c00 ATMFD ATMFD.DLL Wed Aug 04 09:56:56 2004 (411096C8)
eebbf000 eebcdd80 sysaudio sysaudio.sys Wed Aug 04 08:15:54 2004 (41107F1A)
f71ef000 f7222200 update update.sys Wed Aug 04 07:58:32 2004 (41107B08)
f725c000 f728c100 rdpdr rdpdr.sys Wed Aug 04 08:01:10 2004 (41107BA6)
f72f0000 f7300e00 psched psched.sys Wed Aug 04 08:04:16 2004 (41107C60)
f7301000 f730f100 usbhub usbhub.sys Wed Aug 04 08:08:40 2004 (41107D68)
f73a1000 f73b7680 ndiswan ndiswan.sys Wed Aug 04 08:14:30 2004 (41107EC6)
f73b8000 f73db980 portcls portcls.sys Wed Aug 04 08:15:47 2004 (41107F13)
f73dc000 f73fe980 viaudios viaudios.sys Mon May 24 08:11:06 2004 (40B191FA)
f73ff000 f7412900 parport parport.sys Wed Aug 04 07:59:04 2004 (41107B28)
f7413000 f7435e80 USBPORT USBPORT.SYS Wed Aug 04 08:08:34 2004 (41107D62)
f7436000 f7458680 ks ks.sys Wed Aug 04 08:15:20 2004 (41107EF8)
f7459000 f746c780 VIDEOPRT VIDEOPRT.SYS Wed Aug 04 08:07:04 2004 (41107D08)
f746d000 f75f4000 ati2mtag ati2mtag.sys Wed May 03 18:50:42 2006 (4458DF62)
f7618000 f761bc80 mssmbios mssmbios.sys Wed Aug 04 08:07:47 2004 (41107D33)
f763c000 f7656580 Mup Mup.sys Wed Aug 04 08:15:20 2004 (41107EF8)
f7657000 f7683a80 NDIS NDIS.sys Wed Aug 04 08:14:27 2004 (41107EC3)
f7684000 f7710480 Ntfs Ntfs.sys Wed Aug 04 08:15:06 2004 (41107EEA)
f7711000 f7727780 KSecDD KSecDD.sys Wed Aug 04 07:59:45 2004 (41107B51)
f7728000 f7739f00 sr sr.sys Wed Aug 04 08:06:22 2004 (41107CDE)
f773a000 f7758780 fltmgr fltmgr.sys Wed Aug 04 08:01:17 2004 (41107BAD)
f7759000 f7770800 SCSIPORT SCSIPORT.SYS Wed Aug 04 07:59:39 2004 (41107B4B)
f7771000 f7788480 atapi atapi.sys Wed Aug 04 07:59:41 2004 (41107B4D)
f7789000 f77ae700 dmio dmio.sys Wed Aug 04 08:07:13 2004 (41107D11)
f77af000 f77cd880 ftdisk ftdisk.sys Fri Aug 17 22:52:41 2001 (3B7D8419)
f77ce000 f77dea80 pci pci.sys Wed Aug 04 08:07:45 2004 (41107D31)
f77df000 f780cd80 ACPI ACPI.sys Wed Aug 04 08:07:35 2004 (41107D27)
f782e000 f7836c00 isapnp isapnp.sys Fri Aug 17 22:58:01 2001 (3B7D8559)
f783e000 f7848500 MountMgr MountMgr.sys Wed Aug 04 07:58:29 2004 (41107B05)
f784e000 f785ac80 VolSnap VolSnap.sys Wed Aug 04 08:00:14 2004 (41107B6E)
f785e000 f786cd00 viamraid viamraid.sys Mon Jul 05 03:52:59 2004 (40E8B47B)
f786e000 f7876e00 disk disk.sys Wed Aug 04 07:59:53 2004 (41107B59)
f787e000 f788a200 CLASSPNP CLASSPNP.SYS Wed Aug 04 08:14:26 2004 (41107EC2)
f788e000 f7896b80 PxHelp20 PxHelp20.sys Fri Feb 02 22:23:57 2007 (45C3ABED)
f789e000 f78a8e80 uagp35 uagp35.sys Wed Aug 04 08:07:43 2004 (41107D2F)
f78ce000 f78d8380 imapi imapi.sys Wed Aug 04 08:00:12 2004 (41107B6C)
f78de000 f78ea180 cdrom cdrom.sys Wed Aug 04 07:59:52 2004 (41107B58)
f78ee000 f78fc080 redbook redbook.sys Wed Aug 04 07:59:34 2004 (41107B46)
f78fe000 f790ae00 i8042prt i8042prt.sys Wed Aug 04 08:14:36 2004 (41107ECC)
f790e000 f791dd80 serial serial.sys Wed Aug 04 08:15:51 2004 (41107F17)
f792e000 f793cb80 drmk drmk.sys Wed Aug 04 08:07:54 2004 (41107D3A)
f793e000 f7948600 fetnd5bv fetnd5bv.sys Tue Apr 17 05:59:43 2007 (4624462F)
f794e000 f7957200 VcommMgr VcommMgr.sys Mon Mar 05 13:17:39 2007 (45EC0A63)
f795e000 f796a880 rasl2tp rasl2tp.sys Wed Aug 04 08:14:21 2004 (41107EBD)
f796e000 f7978200 raspppoe raspppoe.sys Wed Aug 04 08:05:06 2004 (41107C92)
f797e000 f7989d00 raspptp raspptp.sys Wed Aug 04 08:14:26 2004 (41107EC2)
f798e000 f7996900 msgpc msgpc.sys Wed Aug 04 08:04:11 2004 (41107C5B)
f79be000 f79c7f00 termdd termdd.sys Wed Aug 04 07:58:52 2004 (41107B1C)
f7a0e000 f7a17480 NDProxy NDProxy.SYS Fri Aug 17 22:55:30 2001 (3B7D84C2)
f7a9e000 f7aa6d00 intelppm intelppm.sys Wed Aug 04 07:59:19 2004 (41107B37)
f7aae000 f7ab4200 PCIIDEX PCIIDEX.SYS Wed Aug 04 07:59:40 2004 (41107B4C)
f7ab6000 f7aba900 PartMgr PartMgr.sys Sat Aug 18 03:32:23 2001 (3B7DC5A7)
f7abe000 f7ac6000 videX32 videX32.sys Tue Oct 17 14:22:24 2006 (4534CB00)
f7ac6000 f7acd000 BTHidMgr BTHidMgr.sys Mon Mar 05 13:17:09 2007 (45EC0A45)
f7b0e000 f7b14c80 avg7rsxp avg7rsxp.sys Tue Jan 30 16:08:42 2007 (45BF5F7A)
f7b56000 f7b5b000 usbuhci usbuhci.sys Wed Aug 04 08:08:34 2004 (41107D62)
f7b5e000 f7b64800 usbehci usbehci.sys Wed Aug 04 08:08:34 2004 (41107D62)
f7b66000 f7b6ba00 mouclass mouclass.sys Wed Aug 04 07:58:32 2004 (41107B08)
f7b6e000 f7b74000 kbdclass kbdclass.sys Wed Aug 04 07:58:32 2004 (41107B08)
f7b76000 f7b77000 fdc fdc.sys unavailable (00000000)
f7b7e000 f7b84c00 blueletaudio blueletaudio.sys Mon Mar 05 13:16:00 2007 (45EC0A00)
f7b86000 f7b8b180 BlueletSCOAudio BlueletSCOAudio.sys Mon Mar 05 13:16:16 2007 (45EC0A10)
f7b8e000 f7b95580 Modem Modem.SYS Wed Aug 04 08:08:04 2004 (41107D44)
f7b96000 f7b9a880 TDI TDI.SYS Wed Aug 04 08:07:47 2004 (41107D33)
f7b9e000 f7ba2580 ptilink ptilink.sys Fri Aug 17 22:49:53 2001 (3B7D8371)
f7ba6000 f7baa080 raspti raspti.sys Fri Aug 17 22:55:32 2001 (3B7D84C4)
f7bae000 f7bb4b80 VComm VComm.sys Mon Mar 05 13:17:23 2007 (45EC0A53)
f7c3e000 f7c41000 BOOTVID BOOTVID.dll Fri Aug 17 22:49:09 2001 (3B7D8345)
f7c42000 f7c45680 vbtenum vbtenum.sys Mon Mar 05 13:16:57 2007 (45EC0A39)
f7d06000 f7d09c80 serenum serenum.sys Wed Aug 04 07:59:06 2004 (41107B2A)
f7d0a000 f7d0c580 ndistapi ndistapi.sys Fri Aug 17 22:55:29 2001 (3B7D84C1)
f7d1a000 f7d1cc80 btnetdrv btnetdrv.sys Mon Mar 05 13:18:00 2007 (45EC0A78)
f7d2e000 f7d2fb80 kdcom kdcom.dll Fri Aug 17 22:49:10 2001 (3B7D8346)
f7d30000 f7d31100 WMILIB WMILIB.SYS Fri Aug 17 23:07:23 2001 (3B7D878B)
f7d32000 f7d33500 viaide viaide.sys Wed Aug 04 07:59:42 2004 (41107B4E)
f7d34000 f7d35700 dmload dmload.sys Fri Aug 17 22:58:15 2001 (3B7D8567)
f7d56000 f7d57700 RootMdm RootMdm.sys Fri Aug 17 22:57:36 2001 (3B7D8540)
f7d5a000 f7d5b100 swenum swenum.sys Wed Aug 04 07:58:41 2004 (41107B11)
f7d72000 f7d73280 USBD USBD.SYS Fri Aug 17 23:02:58 2001 (3B7D8682)
f7d92000 f7d93080 avg7rsw avg7rsw.sys Tue Jul 26 14:10:51 2005 (42E6284B)
f7daa000 f7daba80 ParVdm ParVdm.SYS Fri Aug 17 22:49:49 2001 (3B7D836D)
f7dbc000 f7dbdf00 Fs_Rec Fs_Rec.SYS Fri Aug 17 22:49:37 2001 (3B7D8361)
f7dbe000 f7dbf080 Beep Beep.SYS Fri Aug 17 22:47:33 2001 (3B7D82E5)
f7dc0000 f7dc1080 mnmdd mnmdd.SYS Fri Aug 17 22:57:28 2001 (3B7D8538)
f7dc2000 f7dc3080 RDPCDD RDPCDD.sys Fri Aug 17 22:46:56 2001 (3B7D82C0)
f7e6d000 f7e6dc00 audstub audstub.sys Fri Aug 17 22:59:40 2001 (3B7D85BC)
f7ecd000 f7ecdd00 dxgthk dxgthk.sys Fri Aug 17 22:53:12 2001 (3B7D8438)
f7f15000 f7f15b80 Null Null.SYS Fri Aug 17 22:47:39 2001 (3B7D82EB)
f7f16000 f7f16f80 avgclean avgclean.sys Tue Aug 22 00:55:15 2006 (44EA39D3)

Unloaded modules:
b0196000 b01c0000 kmixer.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
b0196000 b01c0000 kmixer.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
b0de6000 b0e10000 kmixer.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
b329b000 b329c000 drmkaud.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
f6fff000 f700c000 DMusic.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
f791e000 f792c000 swmidi.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
b0e10000 b0e33000 aec.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
f7dc4000 f7dc6000 splitter.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
b7ba1000 b7baa000 processr.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
b8360000 b8365000 Cdaudio.SYS
Timestamp: unavailable (00000000)
Checksum: 00000000
b936b000 b936e000 Sfloppy.SYS
Timestamp: unavailable (00000000)
Checksum: 00000000
Closing open log file c:\debuglog.txt



Thanks.

 

I remind you I am not an expert regarding dump logs.

It appears to me you are still loading dial-up modem drivers.

 

I'd like to wait until Dave gets back to look at this but all of these are again related to the conexent modem drivers. Question is, what is calling for the modem if the connection is broadband? I just did a quick search and found this.

Now, theres a little more where I pulled this information from. I believe, as the article indicates, that this is a hidden system file but because of the possiblilty of malware and the fact that Dave is so good at this and the current error he pegged a couple of days ago, it would be smart to do nothing until he reviews this dump file.



edit: Please note, I am not endorsing the running of the program referenced at the bottom of the linked page either - wait for Dave.

 

Well I disabled, uninstalled and unplugged the modem.. and I'm on cable not broadband, it's completely different. Btw it can't be of malaware because even during setup it crashed. I don't think that during setup there should be any maleware, and the XP CD is original so it can't be infected.

 

Cable is broadband.

Open System Information; Start>All Programs>Accessories>System Tools>System Information
Expand Hardware Resources and click the IRQs entry. Wait for it to poulate and see if the modem is listed.
Now expand Components and click the Modem entry and wait for it to populate. Is it listed?

If the modem is present in either place, while the entry is selected, click File>Export. Give it a name and save it to the desktop. Post the contents of those txt files please.

I also recommend you get your hands on a good utility to test the harddrive. I'm quite sure Rockster can provide some recommendations for that.

 

Lol, in my country they are totally different, the modems, stability and speed. But leave that!

The Harddrive is fine, As I told you I took my PC to a technician and they tested the Harddrive too. It's fine.

And there are no dialup modems listed in those 2 sections.

 

What I see when reading back through is that you took the pc to a technician and they tried a different hard drive. Not the same thing as testing yours. Your last crash is indicative of a possible problem with the hard drive, which is why I suggested testing it. If you would rather tell me what's not wrong instead of running a test as suggested, then I must assume that you're capable of fixing this yourself. Since you're here though, asking for assistance, we know you are not, nor is your technician apparently. It would make things much easier, and you have a better chance of continued assistance, if you would just run some simple tests as requested.

Meanwhile, you still have conexant modem drivers loading, or at least trying to. Put the modem back in and boot up. It should automatically be recognized and find the drivers. Open the Control Panel>Phone and Modem Options>Modems tab and remove the modem. Now check the device manager, and if present, right click>Uninstall the modem. Shut down and physically remove the modem.

If you get another blue screen after that, and those same drivers are listed in the dump, do a search of the registry for the following items using RegSeeker.

HSF_V124.sys
HSF_TONE.sys
HSF_FAXX.sys
HSF_K56K.sys
HSF_FSKS.sys
HSF_FALL.sys

Select the results and click Action>Export and name it the same as the term searched for. The exports will be found in the RegSeeker\backups folder as registry files. You can open them in notepad with a right click>Edit. Post the results please.