Xp is crashing! BSOD

Yes, and since you have stated that you are using cable, then disable the dialup modem via device manager, or even better yet, as mattman suggested, physically remove it.

 

I just scanned this thread after not paying a lot of attention to it but looking in once or twice during the last few days. Since your motherboard no longer recognizes your CPU, its probably a safe bet that you borked things up along the way. And, since mailman is usually pretty darn thorough and he feels you may have flashed the wrong BIOS files, lets get back to some basics.

Do not try any of those automatic BIOS update tools available through Windows or a windows based utility.

You are going to need three things and they should all be put on the same floppy. First is DrDOS, second is AWDFLASH and the third is your extracted BIOS files. You can do your own legwork to find and install these to a floppy. When that has been completed, let us know and I'll walk you through flashing your BIOS.

Until you get this right, you are just spinning your wheels so I will make no other comments for the time being.

 

Hi, Rockster. Thanks for your compliments and for jumping into the water with us.

AWDFLASH is for flashing Award BIOS. Tcm9669's BIOS appears to be AMI. (Tcm9669, I suggest confirming this by looking on the BIOS chip's sticker on your motherboard.)

It seems the AMI BIOS flash utility TCM9669 needs is included in the .ZIP file (if the .ZIP file I directly linked to is the correct BIOS) as ADSFI713.exe and the BIOS v1.9 file name is A7043VMS.190

Tcm9669, for your convenience, here's a link to the DrDos ($35.00 USD) product page (if that is indeed the utility Rockster suggested). I don't know for sure if a bootdisk.com utility (which I expect is free) will suffice.

 

Thanks for your explanation, Matt. I don't trust Everest's accuracy regarding temps/voltages and now I don't fully trust its accuracy regarding mobo model/chipset ID either.

From now on, I will probably suggest confirming Everest's mobo model/revision number by opening the case and reading it on the mobo and/or reading the BIOS info on the black boot screen. Regarding laptops, I guess we should double-check Everests reports at the laptop manufacturers' websites as well as the black boot screen.

I'll get to work on canned instructions.

 

OK, thats two of the three required then - forgive me on AWDFLASH. The other one needed is drdflash which is a freebie. Google drdflash to find a safe download location.

Once downloaded, put a floppy in your drive bay and run drdflash - it will make the necessary files for you. Then extract that ZIP referenced by mailman to the same floppy disc - now you have a boot floppy that will permit flashing the proper BIOS properly.



edit: checking mailman's link to bootdisk.com, the second diamond labeled driver free boot disks (for flashing) is in fact a link (1,2 or 3) to drdflash.

 

Well I read either on the website or on the zip file it self not to install the BIOS from the floppy, ir not making the files on the floppy it's self and installing from there.. I'm uncertain what to do...

All I need is a Windows 98 Start up disk! But I can't find one from that website :S

 

I downloaded the drdflash.exe file via the first mirror link (polarhome.com/service/bootdisk/DOS/Dr-DOS/drdflash.exe) at bootdisk.com. Then I double-clicked the downloaded file to start the boot floppy creation process.

The created floppy boot disk has four hidden? files consuming a total of 119 KB.

Code:

A:\AUTOEXEC.BAT	14	3/26/2000 18:42
A:\COMMAND.COM	66,785	1/7/1999 07:03
A:\IBMBIO.COM	24,810	1/7/1999 07:03
A:\IBMDOS.COM	30,880	1/7/1999 07:03

Looks like the boot disk will have room for you to place all additional necessary files on the same disk (so you don't have to swap disks).

Code:

A7043VMS.190	524,288	1/18/2005 10:54
ADSFI713.exe	30,934	3/11/2004 17:14
Backup of your original BIOS

Total space consumed on the floppy (without the backup of the original BIOS): 661 KB


Information from the "About" link in the "Driver Free Disk For BIOS Flashing 1 | 2 | 3 | About" line at bootdisk.com:

Once you boot with the Dr-DOS bootable floppy disk you just created and copied the necessary files to,

At the A:\ prompt, type in the following command
[FONT= "Courier New"][SIZE= "3"]ADSFI713.exe A7043VMS.190[/SIZE][/FONT]
and then press the Enter key.

Follow the on-screen prompts to update the BIOS.

CAUTION: DO NOT TURN OFF THE POWER or RESET/REBOOT the SYSTEM before the BIOS update is completed, stopping the BIOS UPATE before it is completed will cause the system to become non-functional.

Reboot the system once the BIOS update has been completed.

After the BIOS update flash is complete, remove the floppy disk from the floppy drive and you can shut down your computer by pressing the power button for several seconds. Then press the power button as normal to boot your computer.

 

[SIZE= "2"][/SIZE]Here are the official instructions fom your motherboard site, starting with the pertinent stuff.

[SIZE= "1"]5. Boot the system with a bootable floppy disk
a. A Windows 98/ME startup disk can be used
b. Or you can create an MS-DOS startup disk under Windows XP, to create an MS-DOS startup disk under Windows XP, right click on the 3 ½ floppy drive icon under my computer and select format. On the format dialog box, check the box next to “Create MS-DOS startup disk” and then click the start button to make a MS-DOS startup disk.
6 Once you boot off of the bootable floppy disk, replace the bootable floppy disk with the floppy disk containing the bios files.
7. At the A:\ prompt, you will type in the following command
a. A:\FLASHUTILITY BIOSFILE.VER
b. The flash utility will be the .EXE file included in the BIOS you downloaded. For example: ADSFI712.EXE = BIOS FLASH UTILITY
c. The BIOS file will end with the version number you downloaded. For example:
A6728ims.210 = BIOS file version 2.10
8. To update the BIOS using the example above you would type the following command.
a. A:\ADSFI712 A6728ims.210, then push the enter key.
b. Follow the onscreen prompts to update the BIOS.
9. DO NOT TURN OFF THE POWER or RESET/REBOOT the SYSTEM before the BIOS update is completed, stopping the BIOS UPATE before it is completed will cause the system to become non-functional.
10. Reboot the system once the bios update has been completed. [/SIZE]

I put everything on one disk and the first thing I do after booting from the disk is type dir and hit enter so I can review all the files and write down the exact name of the BIOS bin file. Then I will run the flash utility executable and plug in the BIOS name when prompted. You will also be given an opportunity to save your old BIOS. For safety sake, follow the mfg's instructions above. Then you can holler at them if you go bust. If you do encounter problems, we can send you to a site that will gladly sell you a pre-programmed chip.

 

Well YES! The BIOS is installed, thanks!! Now what is next?

 

I have to confess, I still haven't read through your thread but after reading a couple of the recent suggestions from a few people whom I highly respect, I'd say you should go into your Control Panel > System > Hardware > Device Manager and remove the modem. Then shut down, open up your case and physically yank the modem - it will make an attractive conversation piece once its out of your machine. Then reboot and if there is any modem software that can be removed using add/remove programs - remove it.

Now try running for a while and let us know whats going on. In the meantime, I'll try to read your thread but you have several of the best working with you right now and I'm sure they will be following this too.

 

Tcm9669,

Glad your BIOS flash seems to have gone well. I'd like to see a new Everest report too.

 

Here you go.
http://www.finditglobally.com/Report3.txt

Should I uninstall the modem or just disable it?

 

Thanks!

Your most recent Everest report states,

so it looks like you still have the 04/11/2005 BIOS installed (which may or may not be appropriate for your motherboard).

Before flashing your BIOS with boot floppy disk, did you check your BIOS for BIOS FLASH PROTECTION and make sure it's DISABLED?

First verify your modem is a card plugged into the motherboard (and, therefore, removable).

Alternatively, Rockster's suggestion may be carried out as follows.

1. Hold down your Windows key and press the Pause/Break key on your keyboard.
   (This will open the "System Properties" window.)
2. Then click on the Hardware tab.
3. Then click on the Device Manager button.
4. Then expand "Modems ".
5. Right-click the SoftV92 Data Fax Modem and and click "Uninstall ".
6. Apply/OK your way out and shut down your computer.
7. Then physically remove the modem from its motherboard slot (while the computer is OFF).
8. Then start your computer.

 

NOTE: I have edited my post above with pertinent details since my original post.


If the modem is not removable from the motherboard, then I suggest you disable the SoftV92 Data Fax Modem (as noahdfear suggested in Post #45) instead of uninstalling it. Othwerwise, I expect Windows will try to reinstall drivers for the modem during the next boot.

 

Good point.

Mailman, I would not entrust any reading of the BIOS information to an OS based "reader" (Everest or any other system reader). Motherboard manufacturers stipulate opening the case and reading the model number and revision number from the motherboard itself. I have not seen that this has been done (maybe I am wrong).

Matt

 

Well I think that there is a problem with Everest then. Because the BIOS was installed successfully. Btw so far no BSODs. Thanks, but I think there will be more.

 

Well it crashed again, dump is here, Thanks.:
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\Mini081107-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: Sat Aug 11 09:44:35.296 2007 (GMT+2)
System Uptime: 0 days 0:12:54.968
Loading Kernel Symbols
.........................................................................................................................................
Loading User Symbols
Loading unloaded module list
.........
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000008E, {c0000005, 80594047, ad60bbdc, 0}

Probably caused by : ntkrnlmp.exe ( nt!CmpDereferenceNameControlBlockWithLock+40 )

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

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

KERNEL_MODE_EXCEPTION_NOT_HANDLED_M (1000008e)
This is a very common bugcheck. Usually the exception address pinpoints
the driver/function that caused the problem. Always note this address
as well as the link date of the driver/image that contains this address.
Some common problems are exception code 0x80000003. This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG. This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG. This will let us see why this breakpoint is
happening.
Arguments:
Arg1: c0000005, The exception code that was not handled
Arg2: 80594047, The address that the exception occurred at
Arg3: ad60bbdc, Trap Frame
Arg4: 00000000

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


EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at "0x%08lx" referenced memory at "0x%08lx ". The memory could not be "%s ".

FAULTING_IP:
nt!CmpDereferenceNameControlBlockWithLock+40
80594047 8b08 mov ecx,dword ptr [eax]

TRAP_FRAME: ad60bbdc -- (.trap 0xffffffffad60bbdc)
.trap 0xffffffffad60bbdc
ErrCode = 00000000
eax=1edaba30 ebx=00000000 ecx=1edaba2c edx=00000385 esi=e125ba2c edi=e125ba28
eip=80594047 esp=ad60bc50 ebp=ad60bc58 iopl=0 nv up ei pl nz na pe cy
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010207
nt!CmpDereferenceNameControlBlockWithLock+0x40:
80594047 8b08 mov ecx,dword ptr [eax] ds:0023:1edaba30=????????
.trap
Resetting default scope

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: DRIVER_FAULT

BUGCHECK_STR: 0x8E

PROCESS_NAME: explorer.exe

LAST_CONTROL_TRANSFER: from 80594096 to 80594047

STACK_TEXT:
ad60bc58 80594096 e125ba28 e281a3f8 e102b50c nt!CmpDereferenceNameControlBlockWithLock+0x40
ad60bc6c 8059413b e11ddb00 e1bb3960 8057419e nt!CmpCleanUpKcbCacheWithLock+0x22
ad60bc78 8057419e ad60bc8c 8057417f e281a3f8 nt!CmpGetDelayedCloseIndex+0x16
ad60bc80 8057417f e281a3f8 ad60bc98 805740ab nt!CmpAddToDelayedClose+0xa
ad60bc8c 805740ab e281a3f8 ad60bcb0 805747c2 nt!CmpDereferenceKeyControlBlockWithLock+0x38
ad60bc98 805747c2 e281a3f8 00000000 e12cbd68 nt!CmpDereferenceKeyControlBlock+0x12
ad60bcb0 8056e78f e12cbd80 00000000 e12cbd68 nt!CmpDeleteKeyObject+0x92
ad60bccc 804e1f77 e12cbd80 00000000 0000088e nt!ObpRemoveObjectRoutine+0xdf
ad60bce4 80570dde 861b97e8 e44fa510 8584fbe8 nt!ObfDereferenceObject+0x4c
ad60bcfc 80570cfc e44fa510 e12cbd80 0000088e nt!ObpCloseHandleTableEntry+0x155
ad60bd44 80570d46 0000088e 00000001 00000000 nt!ObpCloseHandle+0x87
ad60bd58 804ddf0f 0000088e 034ff610 7c90eb94 nt!NtClose+0x1d
ad60bd58 7c90eb94 0000088e 034ff610 7c90eb94 nt!KiFastCallEntry+0xfc
WARNING: Frame IP not in any known module. Following frames may be wrong.
034ff610 00000000 00000000 00000000 00000000 0x7c90eb94


STACK_COMMAND: kb

FOLLOWUP_IP:
nt!CmpDereferenceNameControlBlockWithLock+40
80594047 8b08 mov ecx,dword ptr [eax]

SYMBOL_STACK_INDEX: 0

SYMBOL_NAME: nt!CmpDereferenceNameControlBlockWithLock+40

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 41107faa

FAILURE_BUCKET_ID: 0x8E_nt!CmpDereferenceNameControlBlockWithLock+40

BUCKET_ID: 0x8E_nt!CmpDereferenceNameControlBlockWithLock+40

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

eax=1edaba30 ebx=00000000 ecx=1edaba2c edx=00000385 esi=e125ba2c edi=e125ba28
eip=80594047 esp=ad60bc50 ebp=ad60bc58 iopl=0 nv up ei pl nz na pe cy
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010207
nt!CmpDereferenceNameControlBlockWithLock+0x40:
80594047 8b08 mov ecx,dword ptr [eax] ds:0023:1edaba30=????????
ChildEBP RetAddr Args to Child
ad60bc58 80594096 e125ba28 e281a3f8 e102b50c nt!CmpDereferenceNameControlBlockWithLock+0x40 (FPO: [Non-Fpo])
ad60bc6c 8059413b e11ddb00 e1bb3960 8057419e nt!CmpCleanUpKcbCacheWithLock+0x22 (FPO: [Non-Fpo])
ad60bc78 8057419e ad60bc8c 8057417f e281a3f8 nt!CmpGetDelayedCloseIndex+0x16 (FPO: [0,0,0])
ad60bc80 8057417f e281a3f8 ad60bc98 805740ab nt!CmpAddToDelayedClose+0xa (FPO: [Non-Fpo])
ad60bc8c 805740ab e281a3f8 ad60bcb0 805747c2 nt!CmpDereferenceKeyControlBlockWithLock+0x38 (FPO: [Non-Fpo])
ad60bc98 805747c2 e281a3f8 00000000 e12cbd68 nt!CmpDereferenceKeyControlBlock+0x12 (FPO: [Non-Fpo])
ad60bcb0 8056e78f e12cbd80 00000000 e12cbd68 nt!CmpDeleteKeyObject+0x92 (FPO: [Non-Fpo])
ad60bccc 804e1f77 e12cbd80 00000000 0000088e nt!ObpRemoveObjectRoutine+0xdf (FPO: [Non-Fpo])
ad60bce4 80570dde 861b97e8 e44fa510 8584fbe8 nt!ObfDereferenceObject+0x4c (FPO: [0,0,0])
ad60bcfc 80570cfc e44fa510 e12cbd80 0000088e nt!ObpCloseHandleTableEntry+0x155 (FPO: [Non-Fpo])
ad60bd44 80570d46 0000088e 00000001 00000000 nt!ObpCloseHandle+0x87 (FPO: [Non-Fpo])
ad60bd58 804ddf0f 0000088e 034ff610 7c90eb94 nt!NtClose+0x1d (FPO: [Non-Fpo])
ad60bd58 7c90eb94 0000088e 034ff610 7c90eb94 nt!KiFastCallEntry+0xfc (FPO: [0,0] TrapFrame @ ad60bd64)
WARNING: Frame IP not in any known module. Following frames may be wrong.
034ff610 00000000 00000000 00000000 00000000 0x7c90eb94
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)
ad71a000 ad743f00 kmixer kmixer.sys Wed Aug 04 08:07:46 2004 (41107D32)
ad9ec000 ada2c380 HTTP HTTP.sys Wed Aug 04 08:00:09 2004 (41107B69)
add33000 addaa3a0 HSF_V124 HSF_V124.sys Tue May 29 18:05:40 2001 (3B13C8D4)
addab000 adddbc00 HSF_FAXX HSF_FAXX.sys Tue May 29 18:09:54 2001 (3B13C9D2)
ade2c000 ade7e180 srv srv.sys Wed Aug 04 08:14:44 2004 (41107ED4)
adea7000 adf06800 HSF_K56K HSF_K56K.sys Tue May 29 18:11:09 2001 (3B13CA1D)
adf07000 adf23440 HSF_FSKS HSF_FSKS.sys Tue May 29 18:10:42 2001 (3B13CA02)
adf24000 adf6ac40 HSF_FALL HSF_FALL.sys Tue May 29 18:08:30 2001 (3B13C97E)
ae05b000 ae087400 mrxdav mrxdav.sys Wed Aug 04 08:00:49 2004 (41107B91)
ae0a0000 ae0a2e40 mdmxsdk mdmxsdk.sys Wed Mar 17 20:04:10 2004 (4058A12A)
ae34d000 ae361400 wdmaud wdmaud.sys Wed Aug 04 08:15:03 2004 (41107EE7)
b07e2000 b07ee620 HSF_TONE HSF_TONE.sys Tue May 29 18:08:53 2001 (3B13C995)
b1763000 b1786000 Fastfat Fastfat.SYS Wed Aug 04 08:14:15 2004 (41107EB7)
b3b73000 b3b99bc0 omcamvid omcamvid.sys Fri Sep 07 23:28:12 2001 (3B993BEC)
b3b9a000 b3c626c0 avg7core avg7core.sys Fri Jun 15 11:13:22 2007 (46725832)
b3de1000 b3de2080 avg7rsw avg7rsw.sys Tue Jul 26 14:10:51 2005 (42E6284B)
b3ded000 b3dee360 avgtdi avgtdi.sys Thu Aug 25 11:59:58 2005 (430D969E)
b4c57000 b4c5b500 watchdog watchdog.sys Wed Aug 04 08:07:32 2004 (41107D24)
b4c7f000 b4c84820 OVTCAMD OVTCAMD.SYS Fri Aug 31 19:56:07 2001 (3B8FCFB7)
b519e000 b51a9e00 STREAM STREAM.SYS Wed Aug 04 08:07:58 2004 (41107D3E)
b5cc1000 b5cc4780 dump_scsiport dump_scsiport.sys Wed Aug 04 07:59:51 2004 (41107B57)
b7f75000 b7fe3380 mrxsmb mrxsmb.sys Wed Aug 04 08:15:14 2004 (41107EF2)
b7fe4000 b800f180 rdbss rdbss.sys Wed Aug 04 08:20:05 2004 (41108015)
b8038000 b8059d00 afd afd.sys Wed Aug 04 08:14:13 2004 (41107EB5)
b805a000 b807af00 ipnat ipnat.sys Wed Aug 04 08:04:48 2004 (41107C80)
b807b000 b80a2c00 netbt netbt.sys Wed Aug 04 08:14:36 2004 (41107ECC)
b80a3000 b80faa80 tcpip tcpip.sys Wed Aug 04 08:14:39 2004 (41107ECF)
b80fb000 b810d400 ipsec ipsec.sys Wed Aug 04 08:14:27 2004 (41107EC3)
b814e000 b8156080 ipfltdrv ipfltdrv.sys Fri Aug 17 22:55:07 2001 (3B7D84AB)
ba5b3000 ba5b5280 rasacd rasacd.sys Fri Aug 17 22:55:39 2001 (3B7D84CB)
baef4000 baf03900 Cdfs Cdfs.SYS Wed Aug 04 08:14:09 2004 (41107EB1)
baf04000 baf12d80 sysaudio sysaudio.sys Wed Aug 04 08:15:54 2004 (41107F1A)
baf14000 baf1c700 netbios netbios.sys Wed Aug 04 08:03:19 2004 (41107C27)
baf34000 baf3c700 wanarp wanarp.sys Wed Aug 04 08:04:57 2004 (41107C89)
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)
f6dc8000 f6dcb280 ndisuio ndisuio.sys Wed Aug 04 08:03:10 2004 (41107C1E)
f6dee000 f6df6880 Fips Fips.SYS Sat Aug 18 03:31:49 2001 (3B7DC585)
f702e000 f7061200 update update.sys Wed Aug 04 07:58:32 2004 (41107B08)
f7062000 f7092100 rdpdr rdpdr.sys Wed Aug 04 08:01:10 2004 (41107BA6)
f70bb000 f70cbe00 psched psched.sys Wed Aug 04 08:04:16 2004 (41107C60)
f70cc000 f70e2680 ndiswan ndiswan.sys Wed Aug 04 08:14:30 2004 (41107EC6)
f70e3000 f7106980 portcls portcls.sys Wed Aug 04 08:15:47 2004 (41107F13)
f7107000 f7129980 viaudios viaudios.sys Mon May 24 08:11:06 2004 (40B191FA)
f712a000 f713d900 parport parport.sys Wed Aug 04 07:59:04 2004 (41107B28)
f713e000 f7160e80 USBPORT USBPORT.SYS Wed Aug 04 08:08:34 2004 (41107D62)
f7161000 f7183680 ks ks.sys Wed Aug 04 08:15:20 2004 (41107EF8)
f7184000 f7197780 VIDEOPRT VIDEOPRT.SYS Wed Aug 04 08:07:04 2004 (41107D08)
f7198000 f731f000 ati2mtag ati2mtag.sys Wed May 03 18:50:42 2006 (4458DF62)
f731f000 f732dd00 dump_viamraid dump_viamraid.sys Mon Jul 05 03:52:59 2004 (40E8B47B)
f732f000 f7338480 NDProxy NDProxy.SYS Fri Aug 17 22:55:30 2001 (3B7D84C2)
f738f000 f7398f00 termdd termdd.sys Wed Aug 04 07:58:52 2004 (41107B1C)
f739f000 f73a7900 msgpc msgpc.sys Wed Aug 04 08:04:11 2004 (41107C5B)
f73af000 f73bad00 raspptp raspptp.sys Wed Aug 04 08:14:26 2004 (41107EC2)
f75f4000 f75f6900 Dxapi Dxapi.sys Fri Aug 17 22:53:19 2001 (3B7D843F)
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 f78da180 cdrom cdrom.sys Wed Aug 04 07:59:52 2004 (41107B58)
f78de000 f78ec080 redbook redbook.sys Wed Aug 04 07:59:34 2004 (41107B46)
f78ee000 f78fae00 i8042prt i8042prt.sys Wed Aug 04 08:14:36 2004 (41107ECC)
f78fe000 f790dd80 serial serial.sys Wed Aug 04 08:15:51 2004 (41107F17)
f791e000 f792cb80 drmk drmk.sys Wed Aug 04 08:07:54 2004 (41107D3A)
f792e000 f7938600 fetnd5bv fetnd5bv.sys Tue Apr 17 05:59:43 2007 (4624462F)
f793e000 f7947200 VcommMgr VcommMgr.sys Mon Mar 05 13:17:39 2007 (45EC0A63)
f794e000 f795a880 rasl2tp rasl2tp.sys Wed Aug 04 08:14:21 2004 (41107EBD)
f795e000 f7968200 raspppoe raspppoe.sys Wed Aug 04 08:05:06 2004 (41107C92)
f7a2e000 f7a3c100 usbhub usbhub.sys Wed Aug 04 08:08:40 2004 (41107D68)
f7a8e000 f7a96d00 intelppm intelppm.sys Wed Aug 04 07:59:19 2004 (41107B37)
f7a9e000 f7aa8380 imapi imapi.sys Wed Aug 04 08:00:12 2004 (41107B6C)
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)
f7b16000 f7b1aa80 Msfs Msfs.SYS Wed Aug 04 08:00:37 2004 (41107B85)
f7b46000 f7b4b000 usbuhci usbuhci.sys Wed Aug 04 08:08:34 2004 (41107D62)
f7b4e000 f7b54800 usbehci usbehci.sys Wed Aug 04 08:08:34 2004 (41107D62)
f7b56000 f7b5ba00 mouclass mouclass.sys Wed Aug 04 07:58:32 2004 (41107B08)
f7b5e000 f7b64000 kbdclass kbdclass.sys Wed Aug 04 07:58:32 2004 (41107B08)
f7b66000 f7b67000 fdc fdc.sys unavailable (00000000)
f7b6e000 f7b74c00 blueletaudio blueletaudio.sys Mon Mar 05 13:16:00 2007 (45EC0A00)
f7b76000 f7b7b180 BlueletSCOAudio BlueletSCOAudio.sys Mon Mar 05 13:16:16 2007 (45EC0A10)
f7b7e000 f7b85580 Modem Modem.SYS Wed Aug 04 08:08:04 2004 (41107D44)
f7b86000 f7b8a880 TDI TDI.SYS Wed Aug 04 08:07:47 2004 (41107D33)
f7b8e000 f7b92580 ptilink ptilink.sys Fri Aug 17 22:49:53 2001 (3B7D8371)
f7b96000 f7b9a080 raspti raspti.sys Fri Aug 17 22:55:32 2001 (3B7D84C4)
f7b9e000 f7ba4b80 VComm VComm.sys Mon Mar 05 13:17:23 2007 (45EC0A53)
f7ba6000 f7bacc80 avg7rsxp avg7rsxp.sys Tue Jan 30 16:08:42 2007 (45BF5F7A)
f7bf6000 f7bfd880 Npfs Npfs.SYS Wed Aug 04 08:00:38 2004 (41107B86)
f7bfe000 f7c03000 flpydisk flpydisk.sys Wed Aug 04 07:59:24 2004 (41107B3C)
f7c1e000 f7c23200 vga vga.sys Wed Aug 04 08:07:06 2004 (41107D0A)
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)
f7d02000 f7d05c80 serenum serenum.sys Wed Aug 04 07:59:06 2004 (41107B2A)
f7d06000 f7d08580 ndistapi ndistapi.sys Fri Aug 17 22:55:29 2001 (3B7D84C1)
f7d12000 f7d14c80 btnetdrv btnetdrv.sys Mon Mar 05 13:18:00 2007 (45EC0A78)
f7d26000 f7d29c80 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)
f7d56000 f7d57700 RootMdm RootMdm.sys Fri Aug 17 22:57:36 2001 (3B7D8540)
f7d58000 f7d59100 swenum swenum.sys Wed Aug 04 07:58:41 2004 (41107B11)
f7d6a000 f7d6b280 USBD USBD.SYS Fri Aug 17 23:02:58 2001 (3B7D8682)
f7d72000 f7d73a80 ParVdm ParVdm.SYS Fri Aug 17 22:49:49 2001 (3B7D836D)
f7dc6000 f7dc7f00 Fs_Rec Fs_Rec.SYS Fri Aug 17 22:49:37 2001 (3B7D8361)
f7dc8000 f7dc9080 Beep Beep.SYS Fri Aug 17 22:47:33 2001 (3B7D82E5)
f7dcc000 f7dcd080 mnmdd mnmdd.SYS Fri Aug 17 22:57:28 2001 (3B7D8538)
f7dce000 f7dcf080 RDPCDD RDPCDD.sys Fri Aug 17 22:46:56 2001 (3B7D82C0)
f7dfa000 f7dfab80 Null Null.SYS Fri Aug 17 22:47:39 2001 (3B7D82EB)
f7dfb000 f7dfbf80 avgclean avgclean.sys Tue Aug 22 00:55:15 2006 (44EA39D3)
f7eee000 f7eeec00 audstub audstub.sys Fri Aug 17 22:59:40 2001 (3B7D85BC)
f7f2b000 f7f2bd00 dxgthk dxgthk.sys Fri Aug 17 22:53:12 2001 (3B7D8438)

Unloaded modules:
ae300000 ae32a000 kmixer.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
f7ed8000 f7ed9000 drmkaud.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
b9b0d000 b9b1a000 DMusic.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
ae32a000 ae34d000 aec.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
b6fea000 b6ff8000 swmidi.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
b49d6000 b49d8000 splitter.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
f6e0e000 f6e17000 processr.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
f7c16000 f7c1b000 Cdaudio.SYS
Timestamp: unavailable (00000000)
Checksum: 00000000
ba5b7000 ba5ba000 Sfloppy.SYS
Timestamp: unavailable (00000000)
Checksum: 00000000
Closing open log file c:\debuglog.txt

 

You re-installed windows and your windows still crashes with random pattern. They are symptom of hardware error as hardware occurs randomly. One minidump was crashed with bugcheck code 1A and BC 1A is always related to ram problem.

 

What is the status with the modem? Did you uninstall and remove it? Disable it? So that you might understand why I suggested it in the first place, below is an excerpt from your last dump.


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)
ad71a000 ad743f00 kmixer kmixer.sys Wed Aug 04 08:07:46 2004 (41107D32)
ad9ec000 ada2c380 HTTP HTTP.sys Wed Aug 04 08:00:09 2004 (41107B69)
add33000 addaa3a0 HSF_V124 HSF_V124.sys Tue May 29 18:05:40 2001 (3B13C8D4)
addab000 adddbc00 HSF_FAXX HSF_FAXX.sys Tue May 29 18:09:54 2001 (3B13C9D2)
ade2c000 ade7e180 srv srv.sys Wed Aug 04 08:14:44 2004 (41107ED4)
adea7000 adf06800 HSF_K56K HSF_K56K.sys Tue May 29 18:11:09 2001 (3B13CA1D)
adf07000 adf23440 HSF_FSKS HSF_FSKS.sys Tue May 29 18:10:42 2001 (3B13CA02)
adf24000 adf6ac40 HSF_FALL HSF_FALL.sys Tue May 29 18:08:30 2001 (3B13C97E)


See the files I have bolded above? Those are modem drivers, and they are being called into use just before the crash occurs. Knowing that you are using broadband, I have to ask, why is the modem being called? And the answer is ............ (drumroll) ................ it doesn't matter why. You don't use it, so take it out of the machine and it's out of the picture as suspect. The modem is a PCI card modem, not integrated. How do I know that? Follow the MSI link I posted back on post #45 and you'll get a description of the motherboard ..... no integrated modem listed. No integrated video either. Now we look at your everest report, and we see the video is a Palit Radeon 9250 AGP. We also see that PCI Slot 4 is in use. Bingo! PCI modem.

Open the device manager and right click>Uninstall the SoftV92 Data Fax Modem then shut down the computer and physically remove the modem. If it blue screens again after removing the modem, post the new dump.

 

Maybe I shouldn't, but I decided to add some comments. mailman has done a great deal of work toward flashing your BIOS, and is to be commended for that. However, my own opinion is that flashing the BIOS is risky business, and can easily leave your computer unbootable. Only if there was specific evidence of need for flashing the BIOS, or only after all other avenues have been exhausted, would I ever recommend flashing the BIOS. I would try every driver available for every device attached and even try replacements for said devices before I would flash the BIOS. It's a bit late now to exhaust all other avenues first, but I recommend at this point to leave the BIOS alone, until we have eliminated all other possibilities.