Xp is crashing! BSOD

So.. any help please?

 

You mention another AVG file in the first post. If you would like to test without it you can just uninstall it. Reinstall again after testing. I don't use the e-mail checker or Resident Shield (I control manually). You could try installing without them and testing.

Try testing the HDD with the manufacturer's testing utilities.

Try disabling some of the major onboard hardware in the BIOS settings at startup, like the audio and LAN and test without them. If there proves to be a resource problem, you can replace them with add-in cards.

Matt

 

I already tested the system without AVG, when I had a fresh install of windows XP, but it still crashed.

Well on the Cd's provided there are no such utilities, can you point me some so I can download from the Internet?

I will try this and let you know... I find out how.

 

If you go to Device Manager and open Disk Drives you will see the model of your HDD. You can put that model number into a websearch and you could find the name of the manufacturer. Adding the word utility might get you straight to the download page. Everest in my signature should give you plenty of information if it compatible with your computer.

Unless it is a SATA drive, you should only need the floppy disk based testing utilities. Some utilities are being changed to .iso CD burning files for SATA.

Matt

 

Yess it is a SATA and I do have a floppy with a utility so I can format my PC and install it onto the SATA drive.. but thats all.

And I searched the model number but a bunch of Russian and non-related sites came up.

 

You can try Everest, under the heading Storage -> ATA.

If you can see the label on the drive itself, you just need the manufacturer's name. Some examples, the tools/utilities for Seagate are Diskwizard and Seatools, Maxtor: Maxblast and Powermax, Western Digital: Lifeguard, Hitachi: Drive Fitness Test.

If you would like to post the model number, we may be able to trace it.

Matt

 

I downloaded SeaTools, because I have a Seagate HD, and DiscWizard is 102mb.. and it doesn't seem to help me.. if I read correctly it will help me if im going to format/ or something my HD.. so I dont need it.right?

 

Well seatools seems to have an error, when I press to make a test the application is displaying an error and crashes (the app not the pc)

 

At least I am most familiar with Seatools

Seatools does have the testing utilities, although I have only used the floppy disk version up until now. Are you sure it is not a boot CD, where you need to boot to the CD you have made instead of the HDD at startup?

If you are sure you are running the tests correctly and they won't work, then I might be more certain that the HDD is having problems. To save me checking back, I'm sure I suggested pulling out and reseating the connectors to the drives, were you able to do so? You will definitely need to do that. (I was asked to look at a computer where I work, it would not boot into Windows. After trying a few things, I decided to try a reinstall of Windows. That would not work either. I reseated the connectors, reinstalled Windows and it is going like nothing ever happened...drat! they were going to give it to me if I could not fix it .)

It seems like we need to rule out a problem with the HDD first.

Don't overlook that it may be a problem with the IDE Controller. If the IDE Controller is getting confused, it may have an influence on the SATA Controller.
Have you installed any extra optical drives on the IDE/PATA Controller? If so, are the jumper settings correct? (One other point, personally, I don't like setting an optical drive as master on the primary IDE, that is usually where the BIOS is looking for the boot information.)

Matt

 

Sorry for not replying but my computer was at the technician for repairing because I could not install XP because of the RAM, although I ran all tests on the RAM it was corrupted, not I have just one module, 1Gb. But my PC is still crashing! They tried another HD etc etc.. but the Problem of the BSOD still persisted.. I don't think there is much to do.

 

It may be that the motherboard is defective...although, I have concentrated on the drive.
It may be that the drive controller is defective (that is part of the motherboard chipset).

I can't see that you have posted your system specifications (quick check).

You may just need a replacement for the drive controller. A PCI IDE or SATA drive controller card is not very expensive.
You may need a replacement of the motherboard. Reasonably good motherboards are not expensive. Changing the motherboard is the part that requires research.

Matt
Edit: Check for drivers recommended by the (motherboard) manufacturer.
Do a BIOS upgrade before changing the motherboard.

 

BTW, Everest (linked in mattman's signature) is handy for determining your hardware specifications such as motherboard manufaturer/model number, currently installed BIOS revision number, and many other hardware details.

 

Please post another 1 or 2 recent dumps.

 

I have to pay for the BIOS upgrade.. I think. And besides this I never done a BIOS upgrade.. I don't want to end up with my PC freaked. And besides that before it worked perfectly.. why not now?

I would exclude (IMO) anything related to the HD, because they (the technicians) ran a lot of testing on it.

"PCI IDE or SATA drive controller card" What is that?

Changing the motherboard? Wow, that is a little expensive.. in my country everything is.

Ow and just to let you know.. I tried some other OS like Ubuntu, Kubuntu, Xubuntu, Freespire, OpenSuse and I think some more.. I never had these problems... no crashing at all... but my father is obsessed with XP. I was of the idea to downgrade to 2000 or something like that.


@mailman:

Yes I tried that.

@noahdfear:
I have just one at the moment.
Here you guys go (This is a fresh install of XP, with some Vista Mods if this helps.):



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\Mini080507-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: Sun Aug 5 19:28:42.765 2007 (GMT+2)
System Uptime: 0 days 1:24:03.445
Loading Kernel Symbols
..................................................................................................................................
Loading User Symbols
Loading unloaded module list
................
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1A, {3451, c03b99ec, 86422be8, 0}

Probably caused by : memory_corruption ( nt!MmInPageKernelStack+11c )

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

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

MEMORY_MANAGEMENT (1a)
# Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 00003451, The PTEs of an outswapped kernel thread stack are corrupt.
Arg2: c03b99ec
Arg3: 86422be8
Arg4: 00000000

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


BUGCHECK_STR: 0x1a_3451

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: DRIVER_FAULT

PROCESS_NAME: System

LAST_CONTROL_TRANSFER: from 805261ac to 80537832

STACK_TEXT:
f7ca5d5c 805261ac 0000001a 00003451 c03b99ec nt!KeBugCheckEx+0x1b
f7ca5d8c 804eba67 00422be8 00000000 867bab30 nt!MmInPageKernelStack+0x11c
f7ca5da4 804e8a4b 86422c48 80576b24 00000000 nt!KiInSwapKernelStacks+0x16
f7ca5dac 80576b24 00000000 00000000 00000000 nt!KeSwapProcessOrStack+0x7c
f7ca5ddc 804eed86 804e89d4 00000000 00000000 nt!PspSystemThreadStartup+0x34
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16


STACK_COMMAND: kb

FOLLOWUP_IP:
nt!MmInPageKernelStack+11c
805261ac 6a00 push 0

SYMBOL_STACK_INDEX: 1

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP: 41107faa

SYMBOL_NAME: nt!MmInPageKernelStack+11c

IMAGE_NAME: memory_corruption

FAILURE_BUCKET_ID: 0x1a_3451_nt!MmInPageKernelStack+11c

BUCKET_ID: 0x1a_3451_nt!MmInPageKernelStack+11c

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

eax=f7abe13c ebx=c03b99ec ecx=00000000 edx=000003c0 esi=c03b99ec edi=003ffffc
eip=80537832 esp=f7ca5d44 ebp=f7ca5d5c 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!KeBugCheckEx+0x1b:
80537832 5d pop ebp
ChildEBP RetAddr Args to Child
f7ca5d5c 805261ac 0000001a 00003451 c03b99ec nt!KeBugCheckEx+0x1b (FPO: [Non-Fpo])
f7ca5d8c 804eba67 00422be8 00000000 867bab30 nt!MmInPageKernelStack+0x11c (FPO: [Non-Fpo])
f7ca5da4 804e8a4b 86422c48 80576b24 00000000 nt!KiInSwapKernelStacks+0x16 (FPO: [Non-Fpo])
f7ca5dac 80576b24 00000000 00000000 00000000 nt!KeSwapProcessOrStack+0x7c (FPO: [1,0,0])
f7ca5ddc 804eed86 804e89d4 00000000 00000000 nt!PspSystemThreadStartup+0x34 (FPO: [Non-Fpo])
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16
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)
af4dd000 af4ef180 dump_viamraid dump_viamraid.sys Tue May 18 10:07:20 2004 (40A9C438)
af590000 af5b9f00 kmixer kmixer.sys Wed Aug 04 08:07:46 2004 (41107D32)
af79a000 af7da380 HTTP HTTP.sys Wed Aug 04 08:00:09 2004 (41107B69)
af87f000 af882780 dump_scsiport dump_scsiport.sys Wed Aug 04 07:59:51 2004 (41107B57)
afbd1000 afc483a0 HSF_V124 HSF_V124.sys Tue May 29 18:05:40 2001 (3B13C8D4)
afc71000 afcc3180 srv srv.sys Wed Aug 04 08:14:44 2004 (41107ED4)
afcc4000 afcf4c00 HSF_FAXX HSF_FAXX.sys Tue May 29 18:09:54 2001 (3B13C9D2)
afcf5000 afd54800 HSF_K56K HSF_K56K.sys Tue May 29 18:11:09 2001 (3B13CA1D)
afd7d000 afd99440 HSF_FSKS HSF_FSKS.sys Tue May 29 18:10:42 2001 (3B13CA02)
afd9a000 afde0c40 HSF_FALL HSF_FALL.sys Tue May 29 18:08:30 2001 (3B13C97E)
afec1000 afec3e40 mdmxsdk mdmxsdk.sys Wed Mar 17 20:04:10 2004 (4058A12A)
afed1000 afefd400 mrxdav mrxdav.sys Wed Aug 04 08:00:49 2004 (41107B91)
b014b000 b015f400 wdmaud wdmaud.sys Wed Aug 04 08:15:03 2004 (41107EE7)
b2d5c000 b2d7f000 Fastfat Fastfat.SYS Wed Aug 04 08:14:15 2004 (41107EB7)
b2d7f000 b2da5bc0 omcamvid omcamvid.sys Fri Sep 07 23:28:12 2001 (3B993BEC)
b2da6000 b2e6e6c0 avg7core avg7core.sys Fri Jun 15 11:13:22 2007 (46725832)
b2e6f000 b2edd380 mrxsmb mrxsmb.sys Wed Aug 04 08:15:14 2004 (41107EF2)
b2ede000 b2f09180 rdbss rdbss.sys Wed Aug 04 08:20:05 2004 (41108015)
b2f0a000 b2f2bd00 afd afd.sys Wed Aug 04 08:14:13 2004 (41107EB5)
b2f2c000 b2f4cf00 ipnat ipnat.sys Wed Aug 04 08:04:48 2004 (41107C80)
b2f4d000 b2f74c00 netbt netbt.sys Wed Aug 04 08:14:36 2004 (41107ECC)
b2f75000 b2fcca80 tcpip tcpip.sys Wed Aug 04 08:14:39 2004 (41107ECF)
b2fcd000 b2fdf400 ipsec ipsec.sys Wed Aug 04 08:14:27 2004 (41107EC3)
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)
ee175000 ee17d080 ipfltdrv ipfltdrv.sys Fri Aug 17 22:55:07 2001 (3B7D84AB)
f04aa000 f04ac900 Dxapi Dxapi.sys Fri Aug 17 22:53:19 2001 (3B7D843F)
f11e3000 f11e4360 avgtdi avgtdi.sys Thu Aug 25 11:59:58 2005 (430D969E)
f11e9000 f11eaa80 ParVdm ParVdm.SYS Fri Aug 17 22:49:49 2001 (3B7D836D)
f236c000 f237b900 Cdfs Cdfs.SYS Wed Aug 04 08:14:09 2004 (41107EB1)
f237c000 f2387e00 STREAM STREAM.SYS Wed Aug 04 08:07:58 2004 (41107D3E)
f238c000 f2394700 netbios netbios.sys Wed Aug 04 08:03:19 2004 (41107C27)
f23ac000 f23b4700 wanarp wanarp.sys Wed Aug 04 08:04:57 2004 (41107C89)
f3768000 f3776100 usbhub usbhub.sys Wed Aug 04 08:08:40 2004 (41107D68)
f3788000 f3791480 NDProxy NDProxy.SYS Fri Aug 17 22:55:30 2001 (3B7D84C2)
f3879000 f387d500 watchdog watchdog.sys Wed Aug 04 08:07:32 2004 (41107D24)
f3fcf000 f3fd6880 Npfs Npfs.SYS Wed Aug 04 08:00:38 2004 (41107B86)
f3fd7000 f3fdc200 vga vga.sys Wed Aug 04 08:07:06 2004 (41107D0A)
f41a2000 f41ae620 HSF_TONE HSF_TONE.sys Tue May 29 18:08:53 2001 (3B13C995)
f4d46000 f4d4cc80 avg7rsxp avg7rsxp.sys Tue Jan 30 16:08:42 2007 (45BF5F7A)
f4d4e000 f4d53820 OVTCAMD OVTCAMD.SYS Fri Aug 31 19:56:07 2001 (3B8FCFB7)
f4d56000 f4d5aa80 Msfs Msfs.SYS Wed Aug 04 08:00:37 2004 (41107B85)
f4d5e000 f4d63000 flpydisk flpydisk.sys Wed Aug 04 07:59:24 2004 (41107B3C)
f556d000 f557bd80 sysaudio sysaudio.sys Wed Aug 04 08:15:54 2004 (41107F1A)
f6b28000 f6b30880 Fips Fips.SYS Sat Aug 18 03:31:49 2001 (3B7DC585)
f7073000 f70a6200 update update.sys Wed Aug 04 07:58:32 2004 (41107B08)
f716b000 f716d280 rasacd rasacd.sys Fri Aug 17 22:55:39 2001 (3B7D84CB)
f716f000 f719f100 rdpdr rdpdr.sys Wed Aug 04 08:01:10 2004 (41107BA6)
f71a0000 f71b0e00 psched psched.sys Wed Aug 04 08:04:16 2004 (41107C60)
f71b1000 f71c7680 ndiswan ndiswan.sys Wed Aug 04 08:14:30 2004 (41107EC6)
f71c8000 f71eb980 portcls portcls.sys Wed Aug 04 08:15:47 2004 (41107F13)
f71ec000 f720e980 viaudios viaudios.sys Mon May 24 08:11:06 2004 (40B191FA)
f720f000 f7222900 parport parport.sys Wed Aug 04 07:59:04 2004 (41107B28)
f7223000 f7245e80 USBPORT USBPORT.SYS Wed Aug 04 08:08:34 2004 (41107D62)
f7246000 f72ed400 HSFCXTS2 HSFCXTS2.sys Fri Jun 18 00:55:36 2004 (40D22168)
f72ee000 f73ec480 HSFDPSP2 HSFDPSP2.sys Fri Jun 18 00:55:00 2004 (40D22144)
f73ed000 f740f680 ks ks.sys Wed Aug 04 08:15:20 2004 (41107EF8)
f7410000 f7445b80 HSFBS2S2 HSFBS2S2.sys Fri Jun 18 00:56:20 2004 (40D22194)
f7446000 f7459780 VIDEOPRT VIDEOPRT.SYS Wed Aug 04 08:07:04 2004 (41107D08)
f745a000 f75e1000 ati2mtag ati2mtag.sys Wed May 03 18:50:42 2006 (4458DF62)
f75fd000 f7600280 ndisuio ndisuio.sys Wed Aug 04 08:03:10 2004 (41107C1E)
f7629000 f7643580 Mup Mup.sys Wed Aug 04 08:15:20 2004 (41107EF8)
f7644000 f7670a80 NDIS NDIS.sys Wed Aug 04 08:14:27 2004 (41107EC3)
f7671000 f76fd480 Ntfs Ntfs.sys Wed Aug 04 08:15:06 2004 (41107EEA)
f76fe000 f7714780 KSecDD KSecDD.sys Wed Aug 04 07:59:45 2004 (41107B51)
f7715000 f7726f00 sr sr.sys Wed Aug 04 08:06:22 2004 (41107CDE)
f7727000 f7745780 fltmgr fltmgr.sys Wed Aug 04 08:01:17 2004 (41107BAD)
f7746000 f775d800 SCSIPORT SCSIPORT.SYS Wed Aug 04 07:59:39 2004 (41107B4B)
f775e000 f7770180 viamraid viamraid.sys Tue May 18 10:07:20 2004 (40A9C438)
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 f7866e00 disk disk.sys Wed Aug 04 07:59:53 2004 (41107B59)
f786e000 f787a200 CLASSPNP CLASSPNP.SYS Wed Aug 04 08:14:26 2004 (41107EC2)
f787e000 f7886b80 PxHelp20 PxHelp20.sys Wed Oct 18 19:33:53 2006 (45366581)
f788e000 f7898e80 uagp35 uagp35.sys Wed Aug 04 08:07:43 2004 (41107D2F)
f78be000 f78ccb80 drmk drmk.sys Wed Aug 04 08:07:54 2004 (41107D3A)
f78ce000 f78da880 rasl2tp rasl2tp.sys Wed Aug 04 08:14:21 2004 (41107EBD)
f78de000 f78e8200 raspppoe raspppoe.sys Wed Aug 04 08:05:06 2004 (41107C92)
f78ee000 f78f9d00 raspptp raspptp.sys Wed Aug 04 08:14:26 2004 (41107EC2)
f78fe000 f7906900 msgpc msgpc.sys Wed Aug 04 08:04:11 2004 (41107C5B)
f791e000 f7927f00 termdd termdd.sys Wed Aug 04 07:58:52 2004 (41107B1C)
f7a4e000 f7a56d00 intelppm intelppm.sys Wed Aug 04 07:59:19 2004 (41107B37)
f7a5e000 f7a68380 imapi imapi.sys Wed Aug 04 08:00:12 2004 (41107B6C)
f7a6e000 f7a7a180 cdrom cdrom.sys Wed Aug 04 07:59:52 2004 (41107B58)
f7a7e000 f7a8c080 redbook redbook.sys Wed Aug 04 07:59:34 2004 (41107B46)
f7a8e000 f7a9ae00 i8042prt i8042prt.sys Wed Aug 04 08:14:36 2004 (41107ECC)
f7a9e000 f7aadd80 serial serial.sys Wed Aug 04 08:15:51 2004 (41107F17)
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)
f7af6000 f7afd580 Modem Modem.SYS Wed Aug 04 08:08:04 2004 (41107D44)
f7afe000 f7b03000 usbuhci usbuhci.sys Wed Aug 04 08:08:34 2004 (41107D62)
f7b06000 f7b0c800 usbehci usbehci.sys Wed Aug 04 08:08:34 2004 (41107D62)
f7b0e000 f7b13a00 mouclass mouclass.sys Wed Aug 04 07:58:32 2004 (41107B08)
f7b16000 f7b1c000 kbdclass kbdclass.sys Wed Aug 04 07:58:32 2004 (41107B08)
f7b1e000 f7b1f000 fdc fdc.sys unavailable (00000000)
f7b26000 f7b2ca00 fetnd5 fetnd5.sys Fri Jul 20 13:40:24 2001 (3B5818A8)
f7b2e000 f7b32880 TDI TDI.SYS Wed Aug 04 08:07:47 2004 (41107D33)
f7b36000 f7b3a580 ptilink ptilink.sys Fri Aug 17 22:49:53 2001 (3B7D8371)
f7b3e000 f7b42080 raspti raspti.sys Fri Aug 17 22:55:32 2001 (3B7D84C4)
f7c3e000 f7c41000 BOOTVID BOOTVID.dll Fri Aug 17 22:49:09 2001 (3B7D8345)
f7cf2000 f7cf5c80 serenum serenum.sys Wed Aug 04 07:59:06 2004 (41107B2A)
f7cf6000 f7cf8580 ndistapi ndistapi.sys Fri Aug 17 22:55:29 2001 (3B7D84C1)
f7d1e000 f7d21c80 mssmbios mssmbios.sys Wed Aug 04 08:07:47 2004 (41107D33)
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)
f7d4e000 f7d4f100 swenum swenum.sys Wed Aug 04 07:58:41 2004 (41107B11)
f7d94000 f7d95280 USBD USBD.SYS Fri Aug 17 23:02:58 2001 (3B7D8682)
f7d9c000 f7d9df00 Fs_Rec Fs_Rec.SYS Fri Aug 17 22:49:37 2001 (3B7D8361)
f7d9e000 f7d9f080 Beep Beep.SYS Fri Aug 17 22:47:33 2001 (3B7D82E5)
f7da0000 f7da1080 mnmdd mnmdd.SYS Fri Aug 17 22:57:28 2001 (3B7D8538)
f7da2000 f7da3080 RDPCDD RDPCDD.sys Fri Aug 17 22:46:56 2001 (3B7D82C0)
f7da6000 f7da7080 avg7rsw avg7rsw.sys Tue Jul 26 14:10:51 2005 (42E6284B)
f7e65000 f7e65d00 dxgthk dxgthk.sys Fri Aug 17 22:53:12 2001 (3B7D8438)
f7ed1000 f7ed1c00 audstub audstub.sys Fri Aug 17 22:59:40 2001 (3B7D85BC)
f7eff000 f7effb80 Null Null.SYS Fri Aug 17 22:47:39 2001 (3B7D82EB)
f7f00000 f7f00f80 avgclean avgclean.sys Tue Aug 22 00:55:15 2006 (44EA39D3)

Unloaded modules:
f04be000 f04c2000 dump_scsipor
Timestamp: unavailable (00000000)
Checksum: 00000000
b2d49000 b2d5c000 dump_viamrai
Timestamp: unavailable (00000000)
Checksum: 00000000
f4d7e000 f4d85000 USBSTOR.SYS
Timestamp: unavailable (00000000)
Checksum: 00000000
af590000 af5ba000 kmixer.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
af590000 af5ba000 kmixer.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
af590000 af5ba000 kmixer.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
af590000 af5ba000 kmixer.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
b00fe000 b0128000 kmixer.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
f7e75000 f7e76000 drmkaud.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
f790e000 f791b000 DMusic.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
b0128000 b014b000 aec.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
f79ce000 f79dc000 swmidi.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
f7d38000 f7d3a000 splitter.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
f239c000 f23a5000 processr.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
f3fdf000 f3fe4000 Cdaudio.SYS
Timestamp: unavailable (00000000)
Checksum: 00000000
f7147000 f714a000 Sfloppy.SYS
Timestamp: unavailable (00000000)
Checksum: 00000000
Closing open log file c:\debuglog.txt

 

Update your modem drivers and reboot. Let us know if that helps.

 

Tcm9669, if Dave's suggestion about your modem drivers doesn't resolve your issue, then please tell us your motherboard manufacturer and model number.

 

In the loaded modules section I see Viamraid.sys is being loaded. At the top of the start-end module name section it has dump_viamraid.sys.

There is only one harddrive, correct? There should not be any RAID systems running?

That would ring alarm bells for me.

Check the information about the computer (for example, some OEM computer manufacturers are releasing models with RAID 0 drives and unsuspecting customers will not realise that this can be hazardous if the RAID array is broken). The system has a RAID controller, drivers are loading then being "dumped ", by my reading.

If there should not be a RAID array set up, I would go to Device Manager and disable the RAID controller. In fact, I don't bother installing RAID controller drivers if I am not planning to use it. If someone has tried setting up a RAID array when there is only one HDD, that is probably the cause of the problems. I have only studied RAID, I have not done any troubleshooting on it. The people here might give you further advice on how to stop the RAID drivers from loading:
http://www.motherboards.org/forums/viewforum.php?f=3
...IF they are not supposed to be getting loaded.
Another place may be the forums at VIA:
www.viaarena.com

RAID is a pretty involved subject, so unfortunately, I maybe not able to give you much further advice.

Matt

 

In any event, the more details you can provide about your computer, the better.

In Everest, if you right-click on the appropriate display window, select "Copy All" and then paste the info into a forum message, that will eliminate several assumptions one may make in troubleshooting your issue (such as Dave's guess about your hard drive configuration). The information that would probably answer Dave's most recent question/assumption would possibly be answered by pasting the "Summary" info from Everest.

Hardware configuration details, such as Everest's "Motherboard" and "BIOS" info may be helpful in determining the cause of your issue.

I suspect you will not have to pay for a BIOS update if we can determine the make/model # of your motherboard. Motherboard manufacturers often offer BIOS update free of charge. I suspect your conclusion about having to pay for a BIOS update resulted from clicking on the incorrect link in Everest.

For example, my Everest info links to "esupport.com" for a possible "pay" BIOS update in Everest's BIOS window. However, if I go to the ASUS website (My motherboard is an ASUS brand.) linked in the "Motherboard" display in Everest, I can search, download, and install a BIOS update free of charge.

 

Well I dont have any drivers as it is auto detected by Windows. As soon as I install Windows it is detected. And It CAN'T be from the modem drivers because previously I had 2 other types of internet(meaning 2 different modems) and at that time meaning that it is not the issue.

 

Yes there is one harddrive ( partitioned into 2 )and as far as I know it is a SATA RAID.. what is the problem with that?