DUMP DATA - random restarts and BSOD's

Thanks
I noticed that I have 3 slots for ram sticks inside my computer and next to these slots I have words printed DDR1, DDR2 and SDR1. I have removed both sticks of DDR RAM and replaced them with one stick of my old Ram from another old computer which was not DDR, think it says on it SDR RAM and is 128mb. I have put this RAM in the SDR slot.

Now I might be tempting fate here seeing as I have only been on the internet for 5-10 minutes but I have not had a restart yet and that seems like a record as I couldn't get here to reply until now. There is a definite improvement.

Hopefully I have found the cause of my problem. Two questions though:

1. Assuming this is the problem - Will this 128mb SDR RAM be OK for the time being until I am able to get new ram in a week or two? It won't put any stress on the system i.e. is it powerful enough?

2. Out of curiosity, is it possible to have a fault with a computer that in turn makes the RAM turn bad? For example, could I have a problem with some hardware in this computer that might turn the new RAM or any RAM I plug in bad? Or is this not possible?
Also is it possible (as I have 2 sticks of DDR memory that are seemingly bad) that the slots in which the DDR ram fit are bad but the RAM itself is OK?

I am praying that this is the end of the problem - Thanks very much Joe I'll let you know

 

assuming that RAM is compatible with your motherboard, it being 'undersized' will not cause undo stress to your machine. You can expect it to act a little slower than normal.

Ram goes bad. its very sensitive to all sorts of things, and will just go bad for no reason. Its very common for it to be the first hardware component to fail on a machine.

I hope this is it, as well, because its an easy fix, and relitivly inexpensive.

 

I found this forum while looking for a solution to a bad pool error and thought I would join up to let you know what I discovered.

2 days ago I was at a client who's PC had gone very slow, crashes, lockups etc. I said that because it was a P4 1.6 it was simply showing its age and we agreed on a price to upgrade the system.

While I was messing around on site I was fiddling inside the machine swapping ram etc then I started getting blue screens and bad pool errors. At that point I took the machine back to base to start the upgrade.

A new gigabyte mobo, 3.2Ghz P4 and 256 DDR later I started to reinstall XP on the existing partition when.....guess what.....same error.

After a dose of KILLDISK to wipe the partition the installation has gone through without an error.

My conclusion is that its harddrive related and nothing to do with the RAM. I suspect a normal format or reinstall would not remove the error but only by wiping the disk will you clear the problem.

 

My conclusion is that its harddrive related and nothing to do with the RAM. I suspect a normal format or reinstall would not remove the error but only by wiping the disk will you clear the problem.

I'm glad that worked out for you with success, but i would not advocate this as a solution in general.

 

well bad news,
About 10 minutes after I posted my last post I had the usual restart with the undersized Ram and haven't been able to use the internet till now because the restarts would happen almost as soon as I connected.

I went to a different computer shop to the one I took it to before to explain the problem and he started saying about re installing windows I told him this has already been tried and didn't work and he said well we can try it again. So I didn't bother taking the computer in.

After many frustrating days I decided to do a system restore (I didn't really want to do this because last time I did this, before I had windows reinstalled, a lot of windows icons became unclickable).

I did the system restore to before I installed service pack 2 as it was when I installed sp2 that the problem became much worse and I am back on the internet again. I am still getting random restarts but at least they only happen intermittently so I can get on the internet for sometimes 2-3 hours before a restart happens.

After I installed windows sp2 and after a crash, very infrequently when trying to get on the internet I would be able to send an error report to Microsoft and it would usually say something about bad memory. But now, after the system restore it is back to blaming a device driver or sometimes graphics device driver.

A weird thing used to happen when SP2 was installed and when I was always having restarts when the internet connected: If I minimized the page so it was on the taskbar I wouldn't get a crash, but as soon as I restored the page and I could see an internet page then I would get a crash. I minimized the my home page on the internet as soon as it appeared and could get to google most of the time as long as I didn't have the page in view while it loaded and as long as I kept it minimized until it had finished loading it would not crash I could have the internet on for hours with the page on the taskbar (useless I know!) as soon as I restored the screen and started scrolling I would get a restart(I wouldn't need to scroll if the page was in the process of loading - I would get a restart almost straight away) I couldn't get to reply on here because I couldn't click on my topic and then minimize the screen quick enough.
I tested this over and over and it was definetely happening;

page on taskbar out of sight - no restart,

page loading in view or scrolling on an already loaded page in view - restart

Not sure what to do now - the computer shops don't seem to know what is happening even when they have the computer in their hands.

Just in case it helps here is my latest debug log:

Opened log file 'c:\debuglog.txt'
Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols

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


Loading Dump File [C:\WINDOWS\Minidump\Mini102704-16.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
*** ERROR: Symbol file could not be found. Defaulted to export symbols for ntoskrnl.exe -
Windows XP Kernel Version 2600 UP Free x86 compatible
Product: WinNt
Built by: 2600.xpclnt_qfe.010827-1803
Kernel base = 0x804d7000 PsLoadedModuleList = 0x80545028
Debug session time: Wed Oct 27 23:40:09 2004
System Uptime: 0 days 5:30:24.790
*** ERROR: Symbol file could not be found. Defaulted to export symbols for ntoskrnl.exe -
Loading Kernel Symbols
...............................................................................................................
Loading unloaded module list
................
Loading User Symbols
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 50, {bcba4218, 0, bf81f2eb, 0}

***** Kernel symbols are WRONG. Please fix symbols to do analysis.

*** ERROR: Symbol file could not be found. Defaulted to export symbols for win32k.sys -
Probably caused by : memory_corruption

Followup: memory_corruption
---------

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

PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced. This cannot be protected by try-except,
it must be protected by a Probe. Typically the address is just plain bad or it
is pointing at freed memory.
Arguments:
Arg1: bcba4218, memory referenced.
Arg2: 00000000, value 0 = read operation, 1 = write operation.
Arg3: bf81f2eb, If non-zero, the instruction address which referenced the bad memory
address.
Arg4: 00000000, (reserved)

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

***** Kernel symbols are WRONG. Please fix symbols to do analysis.


READ_ADDRESS: unable to get nt!MmPoolCodeEnd
unable to get nt!MmSpecialPoolEnd
unable to get nt!MmPagedPoolEnd
unable to get nt!MmNonPagedPoolEnd
unable to get nt!MmNonPagedPoolStart
unable to get nt!MmSpecialPoolStart
unable to get nt!MmPagedPoolStart
unable to get nt!MiSessionPoolStart
unable to get nt!MiSessionPoolEnd
unable to get nt!MmNonPagedPoolExpansionStart
unable to get nt!MmPoolCodeStart
bcba4218

FAULTING_IP:
win32k!EngQueryPerformanceFrequency+bbf
bf81f2eb 8b1b mov ebx,[ebx]

MM_INTERNAL_CODE: 0

CUSTOMER_CRASH_COUNT: 16

DEFAULT_BUCKET_ID: COMMON_SYSTEM_FAULT

BUGCHECK_STR: 0x50

LAST_CONTROL_TRANSFER: from 80513d79 to 804f64ff

STACK_TEXT:
WARNING: Stack unwind information not available. Following frames may be wrong.
ea987b78 80513d79 00000050 bcba4218 00000000 nt!KeBugCheckEx+0x19
ea987bc4 80531f70 00000000 bcba4218 00000000 nt!MmTrimAllSystemPagableMemory+0x4f1f
ea987bdc ea9884c8 00000010 00000000 58000000 nt!Kei386EoiHelper+0x2388
00000000 00000000 00000000 00000000 00000000 0xea9884c8


STACK_COMMAND: .bugcheck ; kb

CHKIMG_EXTENSION: !chkimg -lo 50 -d !nt
!chkimg -lo 50 -d !nt
80533362-80533373 18 bytes - nt!KiDispatchInterrupt+222

[ d8 0f 22 d8 c3 0f 20 e0:e0 25 7f ff ff ff 0f 22 ]
8053337a - nt!KiDispatchInterrupt+23a (+0x18)

[ c3:00 ]
19 errors : !nt (80533362-8053337a)

MODULE_NAME: memory_corruption

IMAGE_NAME: memory_corruption

FOLLOWUP_NAME: memory_corruption

DEBUG_FLR_IMAGE_TIMESTAMP: 0

MEMORY_CORRUPTOR: LARGE

BUCKET_ID: MEMORY_CORRUPTION_LARGE

Followup: memory_corruption
---------

eax=ffdff13c ebx=00000050 ecx=ea987bdc edx=80533689 esi=c02f2e90 edi=806a22bc
eip=804f64ff esp=ea987b60 ebp=ea987b78 iopl=0 nv up ei ng nz na po nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00000286
nt!KeBugCheckEx+0x19:
804f64ff 5d pop ebp
ChildEBP RetAddr Args to Child
WARNING: Stack unwind information not available. Following frames may be wrong.
ea987b78 80513d79 00000050 bcba4218 00000000 nt!KeBugCheckEx+0x19
ea987bc4 80531f70 00000000 bcba4218 00000000 nt!MmTrimAllSystemPagableMemory+0x4f1f
ea987bdc ea9884c8 00000010 00000000 58000000 nt!Kei386EoiHelper+0x2388
00000000 00000000 00000000 00000000 00000000 0xea9884c8
start end module name
804d7000 806a0e80 nt ntoskrnl.exe Mon Feb 25 23:32:36 2002 (3C7AC994)
806a1000 806b4280 hal halacpi.dll Fri Aug 17 21:48:11 2001 (3B7D830B)
bf800000 bf9b7580 win32k win32k.sys Sat Aug 18 04:52:56 2001 (3B7DE698)
bf9b8000 bfac9200 SiSGRV SiSGRV.dll Tue Dec 30 11:06:10 2003 (3FF15C22)
bff80000 bff90a80 dxg dxg.sys Fri Aug 17 22:55:56 2001 (3B7D92EC)
ea56f000 ea595e00 kmixer kmixer.sys Fri Aug 17 22:00:45 2001 (3B7D85FD)
ea8de000 ea8f0a00 ipnat ipnat.sys Fri Aug 17 21:55:11 2001 (3B7D84AF)
ea9e1000 ea9ed960 ntgrip ntgrip.sys Wed Mar 28 23:36:56 2001 (3AC26788)
eaa81000 eaad1a80 srv srv.sys Sat Aug 18 02:32:06 2001 (3B7DC596)
eac9a000 eac9d500 asyncmac asyncmac.sys Fri Aug 17 21:55:29 2001 (3B7D84C1)
ead31000 ead44700 wdmaud wdmaud.sys Sat Aug 18 04:42:48 2001 (3B7DE438)
eae19000 eae21180 HIDCLASS HIDCLASS.SYS Fri Aug 17 22:02:18 2001 (3B7D865A)
eae2d000 eae2fe80 secdrv secdrv.sys Fri Jan 16 13:16:04 2004 (4007E414)
eae51000 eae7b280 mrxdav mrxdav.sys Fri Aug 17 21:50:20 2001 (3B7D838C)
eb034000 eb053e80 afd afd.sys Sat Aug 18 02:30:36 2001 (3B7DC53C)
eb0b8000 eb0baf80 ndisuio ndisuio.sys Fri Aug 17 21:53:53 2001 (3B7D8461)
eb1d4000 eb1e9280 dump_atapi dump_atapi.sys Fri Aug 17 21:51:49 2001 (3B7D83E5)
eb212000 eb275880 mrxsmb mrxsmb.sys Sat Aug 18 04:31:45 2001 (3B7DE1A1)
eb276000 eb29e000 rdbss rdbss.sys Sat Aug 18 04:44:30 2001 (3B7DE49E)
eb29e000 eb2c2b00 netbt netbt.sys Sat Aug 18 02:32:18 2001 (3B7DC5A2)
eb2eb000 eb33ae00 tcpip tcpip.sys Sat Aug 18 02:31:44 2001 (3B7DC580)
eb36b000 eb36e900 watchdog watchdog.sys Fri Aug 17 21:59:35 2001 (3B7D85B7)
ebf83000 ebf91080 sysaudio sysaudio.sys Sat Aug 18 04:47:26 2001 (3B7DE54E)
ec003000 ec010400 swmidi swmidi.sys Fri Aug 17 22:00:42 2001 (3B7D85FA)
fc023000 fc044780 update update.sys Sat Aug 18 04:53:56 2001 (3B7DE6D4)
fc069000 fc06bb00 srvkp srvkp.sys Thu Jul 03 10:12:53 2003 (3F03F395)
fc06d000 fc099580 rdpdr rdpdr.sys Fri Aug 17 21:50:45 2001 (3B7D83A5)
fc09a000 fc0aa180 psched psched.sys Fri Aug 17 21:54:25 2001 (3B7D8481)
fc0ab000 fc0c0900 ndiswan ndiswan.sys Sat Aug 18 02:30:58 2001 (3B7DC552)
fc0c1000 fc0d3980 parport parport.sys Fri Aug 17 21:50:05 2001 (3B7D837D)
fc0d4000 fc133900 ALCXSENS ALCXSENS.SYS Thu Dec 11 11:38:41 2003 (3FD85741)
fc134000 fc154f80 portcls portcls.sys Sat Aug 18 04:31:59 2001 (3B7DE1AF)
fc155000 fc1e7c00 ALCXWDM ALCXWDM.SYS Wed Feb 18 15:51:07 2004 (403389EB)
fc1e8000 fc206180 USBPORT USBPORT.SYS Fri Aug 17 22:03:07 2001 (3B7D868B)
fc207000 fc226d00 ks ks.sys Wed Dec 04 17:09:38 2002 (3DEE36D2)
fc227000 fc279c00 ham50 ham50.sys Thu Apr 19 20:52:03 2001 (3ADF41E3)
fc27a000 fc2e2700 sisgrp sisgrp.sys Tue Dec 30 11:06:38 2003 (3FF15C3E)
fc32b000 fc344600 Mup Mup.sys Sat Aug 18 04:21:29 2001 (3B7DDF39)
fc345000 fc36c700 NDIS NDIS.sys Sat Aug 18 02:31:13 2001 (3B7DC561)
fc36d000 fc3ef400 Ntfs Ntfs.sys Sat Aug 18 02:33:04 2001 (3B7DC5D0)
fc3f0000 fc403780 KSecDD KSecDD.sys Fri Aug 17 21:50:01 2001 (3B7D8379)
fc404000 fc415300 sr sr.sys Fri Aug 17 22:00:38 2001 (3B7D85F6)
fc416000 fc42b280 atapi atapi.sys Fri Aug 17 21:51:49 2001 (3B7D83E5)
fc42c000 fc44fb80 dmio dmio.sys Fri Aug 17 21:58:27 2001 (3B7D8573)
fc450000 fc46e880 ftdisk ftdisk.sys Fri Aug 17 21:52:41 2001 (3B7D8419)
fc46f000 fc49ac00 ACPI ACPI.sys Fri Aug 17 21:57:52 2001 (3B7D8550)
fc4bc000 fc4cb400 pci pci.sys Fri Aug 17 21:58:04 2001 (3B7D855C)
fc4cc000 fc4d4c00 isapnp isapnp.sys Fri Aug 17 21:58:01 2001 (3B7D8559)
fc4dc000 fc4e5280 MountMgr MountMgr.sys Fri Aug 17 21:47:36 2001 (3B7D82E8)
fc4ec000 fc4f8000 VolSnap VolSnap.sys Fri Aug 17 21:53:19 2001 (3B7D843F)
fc4fc000 fc504380 disk disk.sys Fri Aug 17 21:52:31 2001 (3B7D840F)
fc50c000 fc516f80 CLASSPNP CLASSPNP.SYS Sat Aug 18 02:32:31 2001 (3B7DC5AF)
fc54c000 fc558600 usbhub usbhub.sys Fri Aug 17 22:03:11 2001 (3B7D868F)
fc56c000 fc579b00 ipsec ipsec.sys Sat Aug 18 02:30:42 2001 (3B7DC542)
fc57c000 fc584200 wanarp wanarp.sys Fri Aug 17 21:55:23 2001 (3B7D84BB)
fc58c000 fc594180 netbios netbios.sys Fri Aug 17 21:54:00 2001 (3B7D8468)
fc59c000 fc5a4880 Fips Fips.SYS Sat Aug 18 02:31:49 2001 (3B7DC585)
fc5bc000 fc5cb300 Cdfs Cdfs.SYS Sat Aug 18 04:33:34 2001 (3B7DE20E)
fc62c000 fc63be00 VIDEOPRT VIDEOPRT.SYS Fri Aug 17 21:57:42 2001 (3B7D8546)
fc63c000 fc645980 Imapi Imapi.SYS Fri Aug 17 21:53:17 2001 (3B7D843D)
fc64c000 fc657980 cdrom cdrom.sys Fri Aug 17 21:52:25 2001 (3B7D8409)
fc65c000 fc669a00 redbook redbook.sys Fri Aug 17 21:51:37 2001 (3B7D83D9)
fc66c000 fc67a000 drmk drmk.sys Fri Aug 17 22:01:08 2001 (3B7D8614)
fc67c000 fc68b400 serial serial.sys Sat Aug 18 04:27:19 2001 (3B7DE097)
fc68c000 fc698700 i8042prt i8042prt.sys Sat Aug 18 04:44:51 2001 (3B7DE4B3)
fc69c000 fc6a7e00 rasl2tp rasl2tp.sys Sat Aug 18 02:30:47 2001 (3B7DC547)
fc6ac000 fc6b5800 raspppoe raspppoe.sys Fri Aug 17 21:55:33 2001 (3B7D84C5)
fc6bc000 fc6c7580 raspptp raspptp.sys Sat Aug 18 02:30:51 2001 (3B7DC54B)
fc6cc000 fc6d4400 msgpc msgpc.sys Fri Aug 17 21:54:19 2001 (3B7D847B)
fc6dc000 fc6e5380 termdd termdd.sys Fri Aug 17 21:46:42 2001 (3B7D82B2)
fc71c000 fc725480 NDProxy NDProxy.SYS Fri Aug 17 21:55:30 2001 (3B7D84C2)
fc73c000 fc741c80 PCIIDEX PCIIDEX.SYS Fri Aug 17 21:51:46 2001 (3B7D83E2)
fc744000 fc748900 PartMgr PartMgr.sys Sat Aug 18 02:32:23 2001 (3B7DC5A7)
fc74c000 fc752b00 viaagp viaagp.sys Fri Aug 17 21:58:00 2001 (3B7D8558)
fc754000 fc75ad00 viaagp1 viaagp1.sys Wed Jul 02 11:08:01 2003 (3F02AF01)
fc76c000 fc771c80 HIDPARSE HIDPARSE.SYS Fri Aug 17 22:02:04 2001 (3B7D864C)
fc7bc000 fc7c3780 processr processr.sys Fri Aug 17 21:48:32 2001 (3B7D8320)
fc7c4000 fc7cb080 Modem Modem.SYS Fri Aug 17 21:57:35 2001 (3B7D853F)
fc7d4000 fc7d8a00 usbuhci usbuhci.sys Fri Aug 17 22:03:04 2001 (3B7D8688)
fc7e4000 fc7e5000 fdc fdc.sys unavailable (00000000)
fc7ec000 fc7f1600 mouclass mouclass.sys Fri Aug 17 21:47:50 2001 (3B7D82F6)
fc7f4000 fc7f9b80 kbdclass kbdclass.sys Fri Aug 17 21:47:47 2001 (3B7D82F3)
fc804000 fc808580 ptilink ptilink.sys Fri Aug 17 21:49:53 2001 (3B7D8371)
fc80c000 fc810080 raspti raspti.sys Fri Aug 17 21:55:32 2001 (3B7D84C4)
fc82c000 fc82d000 flpydisk flpydisk.sys unavailable (00000000)
fc844000 fc848c80 vga vga.sys Fri Aug 17 21:57:51 2001 (3B7D854F)
fc84c000 fc850680 Msfs Msfs.SYS Fri Aug 17 21:50:02 2001 (3B7D837A)
fc854000 fc85b380 Npfs Npfs.SYS Fri Aug 17 21:50:03 2001 (3B7D837B)
fc8cc000 fc8cf000 BOOTVID BOOTVID.dll Fri Aug 17 21:49:09 2001 (3B7D8345)
fc958000 fc95bf00 MODEMCSA MODEMCSA.sys Fri Aug 17 21:57:37 2001 (3B7D8541)
fc988000 fc98ba80 serenum serenum.sys Fri Aug 17 21:50:13 2001 (3B7D8385)
fc98c000 fc98e280 rasacd rasacd.sys Fri Aug 17 21:55:39 2001 (3B7D84CB)
fc990000 fc992c00 kbfilter kbfilter.SYS Tue Nov 27 07:07:19 2001 (3C033BA7)
fc994000 fc996600 gameenum gameenum.sys Fri Aug 17 22:02:29 2001 (3B7D8665)
fc998000 fc99a580 ndistapi ndistapi.sys Fri Aug 17 21:55:29 2001 (3B7D84C1)
fc9a8000 fc9abf80 TDI TDI.SYS Fri Aug 17 21:57:25 2001 (3B7D8535)
fc9bc000 fc9bdb80 kdcom kdcom.dll Fri Aug 17 21:49:10 2001 (3B7D8346)
fc9be000 fc9bf100 WMILIB WMILIB.SYS Fri Aug 17 22:07:23 2001 (3B7D878B)
fc9c0000 fc9c1800 viaidexp viaidexp.sys Thu Oct 18 07:12:14 2001 (3BCE72BE)
fc9c2000 fc9c3000 dmload dmload.sys unavailable (00000000)
fc9ee000 fc9ef280 USBD USBD.SYS Fri Aug 17 22:02:58 2001 (3B7D8682)
fc9f6000 fc9f7000 Fs_Rec Fs_Rec.SYS unavailable (00000000)
fc9f8000 fc9f9080 Beep Beep.SYS Fri Aug 17 21:47:33 2001 (3B7D82E5)
fc9fa000 fc9fb080 mnmdd mnmdd.SYS Fri Aug 17 21:57:28 2001 (3B7D8538)
fc9fc000 fc9fd080 RDPCDD RDPCDD.sys Fri Aug 17 21:46:56 2001 (3B7D82C0)
fca0e000 fca0f100 dump_WMILIB dump_WMILIB.SYS Fri Aug 17 22:07:23 2001 (3B7D878B)
fca46000 fca47000 ParVdm ParVdm.SYS unavailable (00000000)
fca4e000 fca4f2a0 WBHWDOCT WBHWDOCT.SYS Thu Dec 27 02:17:40 2001 (3C2A84C4)
fcb1a000 fcb1ac00 audstub audstub.sys Fri Aug 17 21:59:40 2001 (3B7D85BC)
fcb25000 fcb26000 swenum swenum.sys Wed Dec 04 17:10:07 2002 (3DEE36EF)
fcb4e000 fcb4f000 Null Null.SYS unavailable (00000000)
fcb9d000 fcb9dd00 dxgthk dxgthk.sys Fri Aug 17 21:53:12 2001 (3B7D8438)

Unloaded modules:
ea56f000 ea596000 kmixer.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
ea56f000 ea596000 kmixer.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
eabf2000 eac00000 swmidi.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
ea56f000 ea596000 kmixer.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
ea56f000 ea596000 kmixer.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
ea56f000 ea596000 kmixer.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
ea56f000 ea596000 kmixer.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
ea56f000 ea596000 kmixer.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
ead0a000 ead31000 kmixer.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
fcb75000 fcb76000 drmkaud.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
ead45000 ead61000 aec.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
eaf34000 eaf41000 DMusic.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
fc5ac000 fc5ba000 swmidi.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
fca42000 fca44000 splitter.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
fc834000 fc839000 Cdaudio.SYS
Timestamp: unavailable (00000000)
Checksum: 00000000
fc97c000 fc97f000 Sfloppy.SYS
Timestamp: unavailable (00000000)
Checksum: 00000000
Closing open log file c:\debuglog.txt

 

Just to point out that you might have a variant of "blaster ". However, you will still need to determine precisely which virus/worm you have, if any. And if it is one of the DCOM worms, you will need to download the appropriate program to remove it. Or just install them both, they won't hurt..This might help in the random restarts, if it is infact a worm.

For MSBlast:
http://www.symantec.com/avcenter/FixBlast.exe

For Welchia/Nachi:
http://www.symantec.com/avcenter/FixWelch.exe

I would go back - 98 if I was you, or, buy new RAM or PC even, then install XP on that...XP is "fussy logic" .

For future installs, I suggest you download the "blaster" patch to a blank floppy or cd. When you have installed XP fresh, run the patch straight away, load essential drivers, mobo drivers etc, no programs or software that you don't need yet. Connect to the internet, browse some sites (note, DON "T VISIT MSN.COM), before you hit the internet, change your home page to www.google.com. To make sure everything is fine with "NDIS.sys ", visit this site www.unrealtournament.com, if all is well, and no BSoD has occured, then go to start<programs<accessories<system tools<system restore. Create a restore point called "perfect ". Then, go to update by clicking the "Windows update" tab in the start menu, update all critical patches. Create restore point and call it perfect_2. (remember, DON "T go to msn.com), the home page that is set on a clean install loads spyware called "avenue ", if you have spybot load its S&D Resident to block any bad stuff from any sites you visit. Go back to MS (windows update), download or if you have it already, SP1, install it, then create restore point called "perfect_3 ". Go back to MS, and download SP2, install, restart, then create restore point "perfect_4 ". Then go back to MS, download all the updated drivers it discovered for your hardware, install them, create restore point "perfect_5 ". If you don't get any errors up to this point, then go ahead and install all your software, games ect...then create restore point called "AMAZING_Uncertain ".

Now, if at any point in time you get any errors, write down the information on paper when you hit the (blue screen of death) or the problem that happens by descirption, and post the stuff in that board or here and wait for a solution, then rollback or restore you previous setting that worked, which would be perfect_5 and so on depending on when you had an eror. If you can't get to a forum board to get help, simply restore to perfect_5 or whatever restore point works, then post it.

But if you don't get any errors after a week or so after the created point called "AMAZING_Uncertain ", then make one last restore point called "AMAZING_Certain ". That will be your best bet and most recent restore point if anything after this point goes bad.

Makes things a lot easier to troublshoot yourself. This way, you can at least have some idea at what point and in what driver or program started it, if it was infact a drivers fault, a update or a service packs fault, which would lead you to stay at a perfect point to be able to contact any manufacturer or forum board tech that will have a fix, updated driver, solution for the program driver or error that occured. Bottom line, you won't have any problems trying to get help.

After all that, if you have the money, invest in an identical HDD, ghost that perfect drive - the new one, and store it away in a far away place or a vault. If at anytime then after you get any problems with that HDD, and you want to format that drive, simply format that drive, grab the ghosted HDD in the vault, make that drive master, and the formatted drive slave, and ghost it again, then store that one away, and do this for ever..Saves time, loading headaches, and above all, you know it workz ..

On another note, about XP SP2. Some machines and hardware don't like this pack, and makes things worse in some cases. Best thing to do, is note down what is conflicting, then remove the pack. Because updating to newest drivers in some cases doesn't work. In my experience with this pack on over 15,000+ machines, brand new and older, it happens on most with new configurations, and some with mixed components. Most times, MS will tell you that it's a certain device driver that caused the problem, and to either, remove the driver or the hardware that they say caused it. This is out right stupid, trying to tell you that your hardware is at fault, when infact, it's the pack that changed things or something that changed on the system that hasen't allowed your hardware or software to work with it, and needs to be setup in a certain way for it to work with your stuff. MS is getting lazy. ..Even a message I got on a pc I was doing was "buy a new GC" - lmfao.
Well guess what? it was a new fx550 which was digitally signed, every component in this new machine was well, NEW It was not the drivers fault, but the packs. I sent the dump to MS, and they confirmed and gave a hotfix. If it was the drivers fault, why were they able to fix it without me changing anyhting other than applying the patch . This just goes to show that the more they try to make their stuff ups in the beginning better, they just create more problems and blame your hardware or drivers, they should test more before signing anything.

IMHO, Windows is the biggest beta test in history!!!..

I must admit though, Channy is trying his hardest to fix things. But MS shouldn't have rushed it to market with all the holes in the start. To them, profit comes before stability and security.

Just my two cents worth.

 

What evidence are you basing the recommendation on besides 'its rebooting unexpectedly'?

I agree. At this point we have tried quite a bit of post mortem analysis without any fruit. Since we have pretty high certainty this is not a memory problem, based on your testing, its worthwhile to take this painful step to isolate the phenomenon.

Unrelated to this thread, but SP2 enforces quite a bit of 'good programming' that in times past was permitted to be a bit sloppy. This exposed tons of bugs in drivers, not all the vendors have caught up yet, even after a year, and many folks are not keeping thier software up to date, running old drivers on a new platform. I'm glad you had a good experience with finding a problem that could be corrected with an update to the OS.

Monk- im sorry to recommend rebuilding in pieces, but without expending a lot of both of our time, i think its going to be the fastest way to get you stable again, or at least get the tshooting down to a reasonable set of factors to isolate.

 

"But MS shouldn't have rushed it to market with all the holes in the start. To them, profit comes before stability and security. "

Errr iq454 - if we are still talking about SP2, I don't think M$ made much profit from that. And while I've dealt with a few machines that choked on SP2, overall I have been pretty happy with the speed, stability, and additional security it offers.

I am impressed with 15k machines ( "In my experience with this pack on over 15,000+ machines, brand new and older ") either updated to SP2 or fresh-installed with slipstreamed SP2. Considering the RTM date for the SP was less than 100 days ago, that's serious numbers even with good push servers since I have to assume that many systems aren't in a single building so you probably aren't pushing over a hardwired LAN. Our central IT folks recently brought our WAN to it's knees for a while just pushing out a MS Office SP and that was no where near the size of XP SP2 and only to 3-4K PCs.

 

I've been through this problem after upgrading a customers computer with new motherboard, cpu and graphics card. They had a GB of DDR memory that we kept. I checked this site to see if there were any solutions and saw this thread but no answer as to what could be causing the problem.

The problem turned out to be very simple. The powersupply was not quite up to driving the new hardware. Its seems that as the voltage dropped away the computer would have memory or graphics crashes (mostly bad pool caller bluescreen)

Put in a Antec 400w power supply and all the random restarts and bluescreens stopped. The computer worked completely normal after changing the power supply.

Not saying this is the solution for u but its something simple u may have overlooked.

 

The Cleaner - welcome to the forum.

It is a simple item but you are correct that it's easy to overlook and could well cause the problem. Thanks.

 

WOW ! ive been searching the net for a thread like this...

I HAVE THE SAME **** PROBLEM!!! i have an msi 865pe neo2 platinum with a 3ghz CPU and i did a format yesterday... while installing msn messenger i got a win32k.sys crash...

could this be a worm?

 

well my computer finally stopped working about a month ago (haven't had access to computer till now). When I turn my computer on now I get a BSOD with a message saying 'unmountable boot volume'. I can't get to the desktop.

I am thinking of changing the hard drive does this sound right?

Thanks