|
Computer Crashing - Need help
|
|
Senior Member
5 product reviews
|
23. May 2006 @ 12:49 |
Link to this message
|
|
I wouldnt try it. Seriously better safe than sorry.
|
|
Advertisement
|
|
|
|
|
dolphin2
Suspended due to non-functional email address
|
23. May 2006 @ 13:24 |
Link to this message
|
|
Do NOT do that! Your CPU will overheat and might "blow" out.
|
|
TheFear
Junior Member
|
23. May 2006 @ 15:28 |
Link to this message
|
|
Is thermal paste something that doesn't disappear over time? I originally thought that thermal paste eventually disappears over time under the heatsink, which is why it needs a new application of it. I guess I was wrong. It's good to apply new thermal paste to the CPU once in a while right? How often should the time span be? Should I apply the new layer of silver compound to the other computers in the house?
|
|
fuggedup
Junior Member
|
23. May 2006 @ 15:54 |
Link to this message
|
|
the rule is
when you get a heatsink to remove the crappy gray dry past they have on it totaly.
then take silver compound and put that on because it will transfer heat faster making your cpu last longer and also make it run faster buy cooling it better
past is good for life.. my silver compound has been on this computer and is still the same as when i first put it on 2 or 3 years ago
I live my life one warez download at a time.
|
|
dolphin2
Suspended due to non-functional email address
|
23. May 2006 @ 18:44 |
Link to this message
|
|
What the thermal paste does is seal in the little imperfections (pock marks) on the top of the CPU and the heat sink. Thus making a perfectly flat surface for the two devices by removing the air that would otherwise be trapped between them. This allows for better heat transfer.
|
|
TheFear
Junior Member
|
4. June 2006 @ 15:35 |
Link to this message
|
Hello everybody. I know this is an old thread, but I finally got around to getting some of that new hardware that might help. Sorry if you need to read all the above posts to remind yourselves of my problem.
I went to surf the net for a new power supply (previously suggested), and I found one with a good price and excellent user reviews & ratings. I now have 450 Watts of power.
I also got the CPU Silver Compound (previously suggested). Applied it, and seems to be working smoothly and effectively.
I have also uninstalled Ram Idle LE (as previously suggested).
Now, all that's left is to test it, so I opened up DVD Shrink again, and started encoding DVD files. I kept my task manager open to see the available RAM and CPU usage. My DVD Shrink went to about 60% complete, with a high CPU-usage percentage (almost always 100%)the whole time, and then crashed again! This is exactly what happened before, so the PSU and the Silver Compound didn't change much. I will still keep the PSU since it is nevertheless an improvement.
Also, when we got this computer, we got two of them, both exactly the same specs. The other one was for my cousin, and he moved out, and was able to upgrade it a lot. He had the same restarting/crashing problem as I do, and what he did was he randomly replaced hardware until it got fixed. He replaced the Motherboard, Video Card, Hard Drive, RAM (added more), and Case. After replacing all that stuff, he says the problem is fixed. He insists that the problem got fixed after the replacement of the old hard drive, and says that it was the hard drive's problem causing the crashing (he didn't specify how or why). Do you think this sort of miracle is also possible for me? (as in do you think I should get a new hard drive?)
Thanks in advance for and help
|
|
dolphin2
Suspended due to non-functional email address
|
4. June 2006 @ 15:56 |
Link to this message
|
|
|
TheFear
Junior Member
|
4. June 2006 @ 16:40 |
Link to this message
|
|
Do I just open the debugwiz like you said, and just leave the Microsoft Debugging tools?
|
|
dolphin2
Suspended due to non-functional email address
|
4. June 2006 @ 16:55 |
Link to this message
|
|
Yes
|
|
TheFear
Junior Member
|
4. June 2006 @ 17:28 |
Link to this message
|
Ok, I did that debugwiz, and here's the resulting text file:
It's very lengthy...
--------------------
Opened log file 'c:\debuglog.txt'
Microsoft (R) Windows Debugger Version 6.6.0003.5
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\WINDOWS\Minidump\Mini060406-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_gdr.050301-1519
Kernel base = 0x804d7000 PsLoadedModuleList = 0x805624a0
Debug session time: Sun Jun 4 17:11:42.312 2006 (GMT-4)
System Uptime: 0 days 7:49:07.013
Loading Kernel Symbols
.....................................................................................................................................
Loading User Symbols
Loading unloaded module list
...................
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1000008E, {c0000005, 804ecba4, ee8bcbbc, 0}
Probably caused by : ntkrnlmp.exe ( nt!IopSynchronousServiceTail+96 )
Followup: MachineOwner
---------
0: 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: 804ecba4, The address that the exception occurred at
Arg3: ee8bcbbc, Trap Frame
Arg4: 00000000
Debugging Details:
------------------
OVERLAPPED_MODULE: Address regions for 'Udfs' and 'kmixer.sys' overlap
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at "0x%08lx" referenced memory at "0x%08lx". The memory could not be "%s".
FAULTING_IP:
nt!IopCompleteRequest+5c
804ecba4 8b4308 mov eax,[ebx+0x8]
TRAP_FRAME: ee8bcbbc -- (.trap ffffffffee8bcbbc)
.trap ffffffffee8bcbbc
ErrCode = 00000000
eax=00000000 ebx=00f8c9d8 ecx=00f8ca18 edx=00000001 esi=806ff410 edi=8210bda8
eip=804ecba4 esp=ee8bcc30 ebp=ee8bcc78 iopl=0 nv up ei pl zr na po nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010246
nt!IopCompleteRequest+0x5c:
804ecba4 8b4308 mov eax,[ebx+0x8] ds:0023:00f8c9e0=????????
.trap
Resetting default scope
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: DRIVER_FAULT
BUGCHECK_STR: 0x8E
LAST_CONTROL_TRANSFER: from 8056f541 to 804ecba4
IRP_ADDRESS: 00f8c9d8
DEVICE_OBJECT: ff954a58
STACK_TEXT:
ee8bcc78 8056f541 00f8ca18 ee8bccb4 ee8bccc0 nt!IopCompleteRequest+0x5c
ee8bcca0 8057f13f ff954a58 00000000 8210bda8 nt!IopSynchronousServiceTail+0x96
ee8bcd38 804dd99f 000004b0 00000000 00000000 nt!NtReadFile+0x55d
ee8bcd38 7c90eb94 000004b0 00000000 00000000 nt!KiFastCallEntry+0xfc
WARNING: Frame IP not in any known module. Following frames may be wrong.
0e2cfe24 00000000 00000000 00000000 00000000 0x7c90eb94
STACK_COMMAND: kb
FOLLOWUP_IP:
nt!IopSynchronousServiceTail+96
8056f541 8a4d17 mov cl,[ebp+0x17]
SYMBOL_STACK_INDEX: 1
FOLLOWUP_NAME: MachineOwner
SYMBOL_NAME: nt!IopSynchronousServiceTail+96
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 42250f77
FAILURE_BUCKET_ID: 0x8E_nt!IopSynchronousServiceTail+96
BUCKET_ID: 0x8E_nt!IopSynchronousServiceTail+96
Followup: MachineOwner
---------
eax=00000000 ebx=00f8c9d8 ecx=00f8ca18 edx=00000001 esi=806ff410 edi=8210bda8
eip=804ecba4 esp=ee8bcc30 ebp=ee8bcc78 iopl=0 nv up ei pl zr na po nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010246
nt!IopCompleteRequest+0x5c:
804ecba4 8b4308 mov eax,[ebx+0x8] ds:0023:00f8c9e0=????????
ChildEBP RetAddr Args to Child
ee8bcc78 8056f541 00f8ca18 ee8bccb4 ee8bccc0 nt!IopCompleteRequest+0x5c (FPO: [Non-Fpo])
ee8bcca0 8057f13f ff954a58 00000000 8210bda8 nt!IopSynchronousServiceTail+0x96 (FPO: [Non-Fpo])
ee8bcd38 804dd99f 000004b0 00000000 00000000 nt!NtReadFile+0x55d (FPO: [Non-Fpo])
ee8bcd38 7c90eb94 000004b0 00000000 00000000 nt!KiFastCallEntry+0xfc (FPO: [0,0] TrapFrame @ ee8bcd64)
WARNING: Frame IP not in any known module. Following frames may be wrong.
0e2cfe24 00000000 00000000 00000000 00000000 0x7c90eb94
start end module name
804d7000 806fd000 nt ntkrnlmp.exe Tue Mar 01 19:57:27 2005 (42250F77)
806fd000 8071dd00 hal halmacpi.dll Wed Aug 04 01:59:09 2004 (41107B2D)
bafc5000 bafeef00 kmixer kmixer.sys Wed Aug 04 02:07:46 2004 (41107D32)
bafef000 bafff280 Udfs Udfs.SYS Wed Aug 04 02:00:27 2004 (41107B7B)
bf800000 bf9c1180 win32k win32k.sys Wed Oct 05 20:05:44 2005 (43446A58)
bf9c2000 bf9d3580 dxg dxg.sys Wed Aug 04 02:00:51 2004 (41107B93)
bf9d4000 bfa0f000 ati2dvag ati2dvag.dll Tue Feb 22 21:36:23 2005 (421BEC27)
bfa0f000 bfa3f000 ati2cqag ati2cqag.dll Tue Feb 22 21:20:49 2005 (421BE881)
bfa3f000 bfa70000 atikvmag atikvmag.dll Tue Feb 22 21:23:15 2005 (421BE913)
bfa70000 bfc907a0 ati3duag ati3duag.dll Tue Feb 22 21:32:33 2005 (421BEB41)
bfc91000 bfcfcc40 ativvaxx ativvaxx.dll Tue Feb 22 21:27:01 2005 (421BE9F5)
edfc5000 edfd6980 NAVENG NAVENG.Sys Thu Feb 23 18:37:13 2006 (43FE4729)
edfd7000 ee098b40 NavEx15 NavEx15.Sys Thu Feb 23 18:57:28 2006 (43FE4BE8)
ee099000 ee0f1000 SAVRT SAVRT.SYS Mon Mar 07 17:49:41 2005 (422CDA85)
ee2d1000 ee311100 HTTP HTTP.sys Fri Oct 08 19:48:20 2004 (41672744)
ee6aa000 ee6fb300 srv srv.sys Mon May 09 20:17:49 2005 (427FFDAD)
ee724000 ee750400 mrxdav mrxdav.sys Wed Aug 04 02:00:49 2004 (41107B91)
ee931000 ee940900 Cdfs Cdfs.SYS Wed Aug 04 02:14:09 2004 (41107EB1)
ef288000 ef29c400 wdmaud wdmaud.sys Wed Aug 04 02:15:03 2004 (41107EE7)
ef475000 ef483d80 sysaudio sysaudio.sys Wed Aug 04 02:15:54 2004 (41107F1A)
ef5bd000 ef5ec700 symidsco symidsco.sys Tue Jan 10 21:55:48 2006 (43C473B4)
ef5ed000 ef615dc0 SYMFW SYMFW.SYS Tue Apr 05 14:11:07 2005 (4252D4BB)
ef76e000 ef778180 SYMNDIS SYMNDIS.SYS Tue Apr 05 14:11:01 2005 (4252D4B5)
ef816000 ef818f60 SYMREDRV SYMREDRV.SYS Tue Apr 05 14:11:10 2005 (4252D4BE)
ef85e000 ef861280 ndisuio ndisuio.sys Wed Aug 04 02:03:10 2004 (41107C1E)
ef9ae000 ef9c5480 dump_atapi dump_atapi.sys Wed Aug 04 01:59:41 2004 (41107B4D)
ef9c6000 ef9e9000 Fastfat Fastfat.SYS Wed Aug 04 02:14:15 2004 (41107EB7)
efa89000 efaf7400 mrxsmb mrxsmb.sys Tue Jan 18 23:26:50 2005 (41EDE18A)
efaf8000 efb22a00 rdbss rdbss.sys Wed Oct 27 21:13:57 2004 (418047D5)
efb23000 efb36000 SAVRTPEL SAVRTPEL.SYS Mon Mar 07 17:49:43 2005 (422CDA87)
efb36000 efb88000 SPBBCDrv SPBBCDrv.sys Wed Jul 21 19:08:26 2004 (40FEF76A)
efb88000 efba9d00 afd afd.sys Wed Aug 04 02:14:13 2004 (41107EB5)
efbaa000 efbd1c00 netbt netbt.sys Wed Aug 04 02:14:36 2004 (41107ECC)
efbd2000 efbeeac0 SYMEVENT SYMEVENT.SYS Mon Jan 16 14:39:30 2006 (43CBF672)
efbef000 efc0ff00 ipnat ipnat.sys Wed Sep 29 18:28:36 2004 (415B3714)
efc38000 efc77ce0 SYMTDI SYMTDI.SYS Tue Apr 05 14:10:52 2005 (4252D4AC)
efc78000 efccfd80 tcpip tcpip.sys Thu Jan 12 21:28:12 2006 (43C7103C)
efcd0000 efce2400 ipsec ipsec.sys Wed Aug 04 02:14:27 2004 (41107EC3)
f7e27000 f7e29900 Dxapi Dxapi.sys Fri Aug 17 16:53:19 2001 (3B7D843F)
f7edb000 f7f0e200 update update.sys Wed Aug 04 01:58:32 2004 (41107B08)
f7f35000 f7f65100 rdpdr rdpdr.sys Wed Aug 04 02:01:10 2004 (41107BA6)
f7f66000 f7f76e00 psched psched.sys Wed Aug 04 02:04:16 2004 (41107C60)
f7f9f000 f7fb5680 ndiswan ndiswan.sys Wed Aug 04 02:14:30 2004 (41107EC6)
f7fb6000 f80ba4e0 AGRSM AGRSM.sys Fri Mar 04 12:02:18 2005 (4228949A)
f80bb000 f80f9580 airplus airplus.sys Mon Sep 08 04:06:35 2003 (3F5C388B)
f80fa000 f811ce80 USBPORT USBPORT.SYS Wed Aug 04 02:08:34 2004 (41107D62)
f811d000 f8140980 portcls portcls.sys Wed Aug 04 02:15:47 2004 (41107F13)
f8141000 f81ce300 smwdm smwdm.sys Tue May 27 17:05:41 2003 (3ED3D325)
f81cf000 f81f1680 ks ks.sys Wed Aug 04 02:15:20 2004 (41107EF8)
f81f2000 f8205900 parport parport.sys Wed Aug 04 01:59:04 2004 (41107B28)
f8206000 f8219780 VIDEOPRT VIDEOPRT.SYS Wed Aug 04 02:07:04 2004 (41107D08)
f821a000 f8313000 ati2mtag ati2mtag.sys Tue Feb 22 21:36:03 2005 (421BEC13)
f8317000 f831ac80 mssmbios mssmbios.sys Wed Aug 04 02:07:47 2004 (41107D33)
f835b000 f8375580 Mup Mup.sys Wed Aug 04 02:15:20 2004 (41107EF8)
f8376000 f83a2a80 NDIS NDIS.sys Wed Aug 04 02:14:27 2004 (41107EC3)
f83a3000 f842f480 Ntfs Ntfs.sys Wed Aug 04 02:15:06 2004 (41107EEA)
f8430000 f8446780 KSecDD KSecDD.sys Wed Aug 04 01:59:45 2004 (41107B51)
f8447000 f8458f00 sr sr.sys Wed Aug 04 02:06:22 2004 (41107CDE)
f8459000 f845a000 fltmgr fltmgr.sys unavailable (00000000)
f8478000 f848f480 atapi atapi.sys Wed Aug 04 01:59:41 2004 (41107B4D)
f8490000 f84b5700 dmio dmio.sys Wed Aug 04 02:07:13 2004 (41107D11)
f84b6000 f84d4880 ftdisk ftdisk.sys Fri Aug 17 16:52:41 2001 (3B7D8419)
f84d5000 f84e5a80 pci pci.sys Wed Aug 04 02:07:45 2004 (41107D31)
f84e6000 f8513d80 ACPI ACPI.sys Wed Aug 04 02:07:35 2004 (41107D27)
f8535000 f853dc00 isapnp isapnp.sys Fri Aug 17 16:58:01 2001 (3B7D8559)
f8545000 f854f500 MountMgr MountMgr.sys Wed Aug 04 01:58:29 2004 (41107B05)
f8555000 f8561c80 VolSnap VolSnap.sys Wed Aug 04 02:00:14 2004 (41107B6E)
f8565000 f856de00 disk disk.sys Wed Aug 04 01:59:53 2004 (41107B59)
f8575000 f8581200 CLASSPNP CLASSPNP.SYS Wed Aug 04 02:14:26 2004 (41107EC2)
f8585000 f858fe80 uagp35 uagp35.sys Wed Aug 04 02:07:43 2004 (41107D2F)
f85b5000 f85c3080 redbook redbook.sys Wed Aug 04 01:59:34 2004 (41107B46)
f85c5000 f85d3b80 drmk drmk.sys Wed Aug 04 02:07:54 2004 (41107D3A)
f85d5000 f85e1880 rasl2tp rasl2tp.sys Wed Aug 04 02:14:21 2004 (41107EBD)
f85e5000 f85ef200 raspppoe raspppoe.sys Wed Aug 04 02:05:06 2004 (41107C92)
f85f5000 f8600d00 raspptp raspptp.sys Wed Aug 04 02:14:26 2004 (41107EC2)
f8605000 f860d900 msgpc msgpc.sys Wed Aug 04 02:04:11 2004 (41107C5B)
f8625000 f862ef00 termdd termdd.sys Wed Aug 04 01:58:52 2004 (41107B1C)
f8645000 f864e480 NDProxy NDProxy.SYS Fri Aug 17 16:55:30 2001 (3B7D84C2)
f8685000 f8693100 usbhub usbhub.sys Wed Aug 04 02:08:40 2004 (41107D68)
f8695000 f869d700 wanarp wanarp.sys Wed Aug 04 02:04:57 2004 (41107C89)
f86a5000 f86ad700 netbios netbios.sys Wed Aug 04 02:03:19 2004 (41107C27)
f86c5000 f86cd880 Fips Fips.SYS Fri Aug 17 21:31:49 2001 (3B7DC585)
f86d5000 f86ddd80 HIDCLASS HIDCLASS.SYS Wed Aug 04 02:08:18 2004 (41107D52)
f8765000 f876dd00 intelppm intelppm.sys Wed Aug 04 01:59:19 2004 (41107B37)
f8775000 f8784d80 serial serial.sys Wed Aug 04 02:15:51 2004 (41107F17)
f8785000 f8791e00 i8042prt i8042prt.sys Wed Aug 04 02:14:36 2004 (41107ECC)
f8795000 f879f380 imapi imapi.sys Wed Aug 04 02:00:12 2004 (41107B6C)
f87a5000 f87b1180 cdrom cdrom.sys Wed Aug 04 01:59:52 2004 (41107B58)
f87b5000 f87bb200 PCIIDEX PCIIDEX.SYS Wed Aug 04 01:59:40 2004 (41107B4C)
f87bd000 f87c1900 PartMgr PartMgr.sys Fri Aug 17 21:32:23 2001 (3B7DC5A7)
f87c5000 f87c9e20 PxHelp20 PxHelp20.sys Tue Feb 01 18:23:42 2005 (42000F7E)
f87d5000 f87db000 symlcbrd symlcbrd.sys Thu Sep 02 21:56:06 2004 (4137CF36)
f8855000 f885c9a0 SYMIDS SYMIDS.SYS Tue Apr 05 14:11:16 2005 (4252D4C4)
f885d000 f885e000 fdc fdc.sys unavailable (00000000)
f8865000 f886b000 kbdclass kbdclass.sys Wed Aug 04 01:58:32 2004 (41107B08)
f886d000 f8871280 usbohci usbohci.sys Wed Aug 04 02:08:34 2004 (41107D62)
f8875000 f887b800 usbehci usbehci.sys Wed Aug 04 02:08:34 2004 (41107D62)
f887d000 f8885000 sisnic sisnic.sys Wed Oct 29 02:55:09 2003 (3F9F725D)
f8885000 f888c580 Modem Modem.SYS Wed Aug 04 02:08:04 2004 (41107D44)
f888d000 f8891880 TDI TDI.SYS Wed Aug 04 02:07:47 2004 (41107D33)
f8895000 f8899580 ptilink ptilink.sys Fri Aug 17 16:49:53 2001 (3B7D8371)
f889d000 f88a1080 raspti raspti.sys Fri Aug 17 16:55:32 2001 (3B7D84C4)
f88a5000 f88aaa00 mouclass mouclass.sys Wed Aug 04 01:58:32 2004 (41107B08)
f88ad000 f88b2000 flpydisk flpydisk.sys Wed Aug 04 01:59:24 2004 (41107B3C)
f88c5000 f88ca200 vga vga.sys Wed Aug 04 02:07:06 2004 (41107D0A)
f88cd000 f88ce000 Msfs Msfs.SYS unavailable (00000000)
f88d5000 f88dc880 Npfs Npfs.SYS Wed Aug 04 02:00:38 2004 (41107B86)
f88e5000 f88eb180 HIDPARSE HIDPARSE.SYS Wed Aug 04 02:08:15 2004 (41107D4F)
f88ed000 f88f3500 usbprint usbprint.sys Wed Aug 04 02:01:23 2004 (41107BB3)
f8925000 f8929500 watchdog watchdog.sys Wed Aug 04 02:07:32 2004 (41107D24)
f8945000 f8948000 BOOTVID BOOTVID.dll Fri Aug 17 16:49:09 2001 (3B7D8345)
f89e5000 f89e7280 rasacd rasacd.sys Fri Aug 17 16:55:39 2001 (3B7D84CB)
f8a01000 f8a03580 hidusb hidusb.sys Fri Aug 17 17:02:16 2001 (3B7D8658)
f8a05000 f8a07f80 mouhid mouhid.sys Fri Aug 17 16:47:57 2001 (3B7D82FD)
f8a11000 f8a14c80 serenum serenum.sys Wed Aug 04 01:59:06 2004 (41107B2A)
f8a15000 f8a17980 gameenum gameenum.sys Wed Aug 04 02:08:20 2004 (41107D54)
f8a29000 f8a2b580 ndistapi ndistapi.sys Fri Aug 17 16:55:29 2001 (3B7D84C1)
f8a35000 f8a36b80 kdcom kdcom.dll Fri Aug 17 16:49:10 2001 (3B7D8346)
f8a37000 f8a38100 WMILIB WMILIB.SYS Fri Aug 17 17:07:23 2001 (3B7D878B)
f8a39000 f8a3a000 dmload dmload.sys unavailable (00000000)
f8a53000 f8a54620 SYMDNS SYMDNS.SYS Tue Apr 05 14:10:54 2005 (4252D4AE)
f8a57000 f8a58120 aeaudio aeaudio.sys Mon Apr 01 09:39:14 2002 (3CA87112)
f8a5d000 f8a5e100 swenum swenum.sys Wed Aug 04 01:58:41 2004 (41107B11)
f8a5f000 f8a60280 USBD USBD.SYS Fri Aug 17 17:02:58 2001 (3B7D8682)
f8a61000 f8a62f00 Fs_Rec Fs_Rec.SYS Fri Aug 17 16:49:37 2001 (3B7D8361)
f8a63000 f8a64080 Beep Beep.SYS Fri Aug 17 16:47:33 2001 (3B7D82E5)
f8a65000 f8a66080 mnmdd mnmdd.SYS Fri Aug 17 16:57:28 2001 (3B7D8538)
f8a67000 f8a68080 RDPCDD RDPCDD.sys Fri Aug 17 16:46:56 2001 (3B7D82C0)
f8a77000 f8a78100 dump_WMILIB dump_WMILIB.SYS Fri Aug 17 17:07:23 2001 (3B7D878B)
f8ae7000 f8ae8000 ParVdm ParVdm.SYS unavailable (00000000)
f8afd000 f8afdd00 pciide pciide.sys Fri Aug 17 16:51:49 2001 (3B7D83E5)
f8b1a000 f8b1ac00 audstub audstub.sys Fri Aug 17 16:59:40 2001 (3B7D85BC)
f8be1000 f8be2000 Null Null.SYS unavailable (00000000)
f8c00000 f8c00d00 dxgthk dxgthk.sys Fri Aug 17 16:53:12 2001 (3B7D8438)
Unloaded modules:
bafd6000 bb000000 kmixer.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
bafd6000 bb000000 kmixer.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
bafd6000 bb000000 kmixer.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
bafd6000 bb000000 kmixer.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
f87ed000 f87f4000 USBSTOR.SYS
Timestamp: unavailable (00000000)
Checksum: 00000000
f8815000 f881c000 USBSTOR.SYS
Timestamp: unavailable (00000000)
Checksum: 00000000
bafd6000 bb000000 kmixer.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
edb89000 edbb3000 kmixer.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
edb89000 edbb3000 kmixer.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
edcf3000 edd1d000 kmixer.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
ef23b000 ef265000 kmixer.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
f8bb5000 f8bb6000 drmkaud.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
ef41d000 ef42a000 DMusic.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
ef265000 ef288000 aec.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
ef455000 ef463000 swmidi.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
f8a7b000 f8a7d000 splitter.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
f86b5000 f86be000 processr.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
f88bd000 f88c2000 Cdaudio.SYS
Timestamp: unavailable (00000000)
Checksum: 00000000
f89e1000 f89e4000 Sfloppy.SYS
Timestamp: unavailable (00000000)
Checksum: 00000000
Closing open log file c:\debuglog.txt
-----------------
|
|
fuggedup
Junior Member
|
4. June 2006 @ 18:41 |
Link to this message
|
|
if he is saying it was replacing the hard drive then the problem is that something in your windows is messed up
only issue you will ever have with a hard drive (the drive its self) is if it stops working
this would mean.. the drive does not spin any more.. or if the plates (theey are metal) get damaged.
so when he got the new hard drive he had to put windows back on it.. (fresh install)
thats also why it was advised above for you to use the debug tool
here is what i advise.
back up your word documents, mp3s, ect..
write down the software you use so you remember what to install
then format then reinstall windows.
i always reinstall every 6months to 1year.. most hard core pc guys and girls do
I live my life one warez download at a time.
|
|
dolphin2
Suspended due to non-functional email address
|
4. June 2006 @ 18:49 |
Link to this message
|
|
Your log isn't as large as some others I've seen. Give me a bit to read thru it all.
|
|
TheFear
Junior Member
|
4. June 2006 @ 19:14 |
Link to this message
|
|
If something in my Windows is messed up, is it okay to re-install Windows with the same Windows CD that I used to install my current messed up one?
Also, when I re-install windows, or format the Hard Drive, I just save all of my important files onto one of my other two partitions of the hard drive, and I just format the C Drive, the place with all the Windows files, program files, etc. Is that okay? Or should I completely format the whole thing, all three pieces of my hard drive?
|
|
TheFear
Junior Member
|
5. June 2006 @ 11:23 |
Link to this message
|
|
And how's the debug log analysis going? I'm eagar to hear what I need to do.
|
|
dolphin2
Suspended due to non-functional email address
|
6. June 2006 @ 10:10 |
Link to this message
|
|
I'm still learning to read the DeBug logs. I'm not an expert by any means. However, from what I've seen and understand about your log, it seems there is a memory address problem. There are several addresses in the log that show as unknown or unavailable. This can be caused by it not being emptied or refreshed quickly enough or it's faulty. Bottom line: the cause of this is most likely your RAM.
|
|
janrocks
Suspended permanently
|
6. June 2006 @ 12:50 |
Link to this message
|
|
I noticed this is still going...I had a strange example of this problem earlier in the week...a machine that would just shut down and reboot without any error.. I couldn't trace the problem apart from it seemed worse when trying to send or recieve large amounts of data across the network... re-installing the FTP app didn't help, also using another.. In the end totally wiping the partition and reinstalling xp clean seems to have done the trick.. Looks like some hidden DoS attack trojan had welded itself into windows somewhere..be careful what you back up..only essential stuff that you can't replace. This thing if it is a trojan/virus is probably something that either you have installed or an active script attack from some dodgy website... You don't have limewire installed do you?
We seem to have cured the problem but it's still a bit fingers crossed.. I also found these kind of ram errors but they have gone now...maybe where the trojan is living, loading itself from the much maligned win.ini file every reboot???
This message has been edited since posting. Last time this message was edited on 6. June 2006 @ 12:53
|
|
dolphin2
Suspended due to non-functional email address
|
6. June 2006 @ 17:15 |
Link to this message
|
|
@janrocks Was the system you were working on getting the Blue Screen with Stop Errors?
My understanding of win.ini is that it's only called upon for 16bit apps.
I'm not questioning your knowledge, please don't get me wrong. Like everyone else, I'm only trying to learn.
The log he posted was from a memory.dmp file. Do you encounter many of them? I'm just learning the ins and outs of them. From what I've read, if it was a virus/trojan there would (most likely) be a looping of addresses or a "filling" of many. I didn't notice that within the log.
I welcome your opinions.
|
|
TheFear
Junior Member
|
7. June 2006 @ 08:36 |
Link to this message
|
|
If it is a problem with my memory, should I be replacing RAM or adding RAM? Is my current RAM faulty, and in need of replacement? Or do I just need more of it?
|
|
ddp
Moderator
|
7. June 2006 @ 08:40 |
Link to this message
|
|
use a pencil eraser on the gold contacts of the memory stick to remove oxidation than reseat the stick to see if still a problem or not. do you have a spare hd to load windows on to see if it is a software corruption or not?
|
|
dolphin2
Suspended due to non-functional email address
|
7. June 2006 @ 10:53 |
Link to this message
|
|
Do as ddp has suggested twice now. Clean the RAM contacts. If that shows no improvement, replace the RAM.
|
|
TheFear
Junior Member
|
7. June 2006 @ 12:13 |
Link to this message
|
Unfortunately, I do not have an extra hard drive to load windows.
I used an eraser on the gold contacts of the RAM and reseated it. Was that supposed to have solved the problem? Should I go test if it worked by opening DVD Shrink again?
|
|
dolphin2
Suspended due to non-functional email address
|
7. June 2006 @ 12:44 |
Link to this message
|
|
Yes. Test it and post the results.
|
|
TheFear
Junior Member
|
7. June 2006 @ 14:45 |
Link to this message
|
|
Well it happened again, the computer crashed midway when encoding, same as before.
I did the Windows Memory Diagnostic again and it says the RAM is all good.
|
|
janrocks
Suspended permanently
|
7. June 2006 @ 16:45 |
Link to this message
|
|
Info for dolphin2.. The machine just powered off...no errors, nothing. Just a hard reboot and then back on as if nothing had happened. No dump files kept and when I ran a remote debug on a linked machine nothing strange logged.. It just shutdown like the plug had been pulled, then back on again.. weird.. Reinstalled xp after totally blanking the partition (twice) with some drive erasing app..sorry can't remember which.. and it's been fine ever since (believe!!..it's been tested to the limit since on 20% overclock) It's really weird how it didn't flag any errors whatsoever..and the hijack this scans didn't show anything out of the ordinary..It was like an internal denial of service attack with respect to the ethernet connection only..the cable modem on this machine for some reason is on usb?? or that would have been the thing affected.. i.e..no internet..
The only thing I came up with was that the owner had installed some warez app without disconnecting his cable modem, something happened during the install and apparently it didn't ask for a code or key when it should have...
The only ideas i can come up with maybe it's a dodgy registry key from some warez....is this a legit copy of windows, and everything else legally installed too because theres a lot of things going on with respect to unregistered software at the moment..
As to the other questions..I don't believe this is a hardware error as such, unless it's something to do with the ide controller chip which is very unlikely. I have seen a pc lose drives one after another over a period of a few weeks...but it didn't do the reboot to error, just lost the drives on reboot. That was the ide controller chip...
The reference to win.ini was just because I have found the odd little thing that edits the file, and then at a random point after startup makes a 16 bit system call which runs the file and executes a hard reboot...the thing to look for on the end of it is [code] <space> /w [/code] The old dos batch file reboot command..also check win.nt for it maybe?? but that should stop the machine booting in the first palce.
Memory dumps...it only takes a few bytes of code to make a system call
and it's not obvious what is going on..especially with windows virtual paging.
The only advice I have is to completely clean the drive...including the partitions and then I would put a different os on it just to wipe the MBR..then partition again..format and re-install windows.Then add any apps one at a time and test until the problem comes back..to be honest I would dump any downloaded apps and get them again, if they have been paid for then the key provided will still work...This maybe a lot of work, but better to be safe, or we're all just going to be going round and round in circles forever... It does seem like something has found it's way into the extra free space left with xp partitioning or the MBR..most likely the free space.
I see a lot of weird messups, I work weekends for a local pc repair business, and while this seems a bit unique, I do see a lot of this sort of thing.. hope that helps some if any :-)
This message has been edited since posting. Last time this message was edited on 7. June 2006 @ 17:08
|
|
Advertisement
|
|
|
|
TheFear
Junior Member
|
7. June 2006 @ 17:04 |
Link to this message
|
|
My Windows is not a legit copy. :(
There are no programs illegally installed, it's either freeware or trials.
I do have limewire though, I use it to download music and movies.
Is this a RAM problem, or a virus problem?
|
