okej, ska testa det! finns det nåt alternativ till daemon tools då?
o vad är alcohol 120%?
datorn startar om sig! hjälper en formatering?
56 svar · 1 464 visningar · startad av Klauz · sida 2 av 3
Trådstarten, av Klauz
Har haft min laptop (3,06Ghz, 512ram, radeon 9000) i snart ett år och den har funkat felfritt, fram tills för ca 2 veckor sedan när jag testade med att installera en extra 512a ramminne. Nu har den börjat starta om sig , ibland frågar den om jag vill spara dokumenten jag jobbar med och ibland startar den bara om sig eller stänger av sig helt utan någon förvarning. Har tagit ut minnet, men proble
Läs hela trådstarten →jag har även norton av 2003, funkar det bättre`? sjukt att Norton AV orsakar omstarter...
Alcohol120% är ett program som fungerar som D-Tools, dock med ytterligare funktionalitet. Något alternativ känner jag inte till, dock kan det vara en idé att vara utan det ett tag för att se om det är där skon klämmer. Annars kan du ju åter installera det för vidare felsökning.
alright, danke för hjälpen 
en till fråga.. AVG är ju bara en trial version som senare kostar pengar! eller har jag fel nu? har du nån direktlänk till gratisprogrammet i sådana fall?
den kräver en licensnyckel, scheisse. har dom börjat ta betalt för sitt program kanske?
här finns gratisprogrammet! http://free.grisoft.com/
Avinstallerade Norton AV och lade in free-av.com-programmet som har fått bra recensioner.. datorn funkade i nån dag, men nu har den startat om sig igen..
ska fixa dumpfilerna..o postar strax
dump1:
Microsoft (R) Windows Debugger Version 6.4.0007.2
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\WINDOWS\Minidump\Mini052805-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*c:\websymbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
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: Sat May 28 10:43:44.109 2005 (GMT+2)
System Uptime: 0 days 0:03:43.821
Loading Kernel Symbols
......................................................................................................................................
Loading unloaded module list
...........
Loading User Symbols
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 10000050, {c9c754d2, 1, 80550ae2, 0}
Could not read faulting driver name
Unable to load image d347bus.sys, Win32 error 2
*** WARNING: Unable to verify timestamp for d347bus.sys
*** ERROR: Module load completed but symbols could not be loaded for d347bus.sys
Probably caused by : Pool_Corruption ( nt!ExDeferredFreePool+107 )
Followup: Pool_corruption
---------
0: kd> !analyze -v
*******************************************************************************
* *
* 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: c9c754d2, memory referenced.
Arg2: 00000001, value 0 = read operation, 1 = write operation.
Arg3: 80550ae2, If non-zero, the instruction address which referenced the bad memory
address.
Arg4: 00000000, (reserved)
Debugging Details:
dump2:
Microsoft (R) Windows Debugger Version 6.4.0007.2
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\WINDOWS\Minidump\Mini052805-02.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*c:\websymbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
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: Sat May 28 10:44:15.828 2005 (GMT+2)
System Uptime: 0 days 0:00:16.531
Loading Kernel Symbols
...............................................................................................................................
Loading unloaded module list
....
Loading User Symbols
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 19, {20, e1a0f848, e1a0fbc8, c70066e}
Probably caused by : ntkrnlmp.exe ( nt!ExFreePoolWithTag+2c1 )
Followup: MachineOwner
---------
0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
BAD_POOL_HEADER (19)
The pool is already corrupt at the time of the current request.
This may or may not be due to the caller.
The internal pool links must be walked to figure out a possible cause of
the problem, and then special pool applied to the suspect tags or the driver
verifier to a suspect driver.
Arguments:
Arg1: 00000020, a pool block header size is corrupt.
Arg2: e1a0f848, The pool entry we were looking for within the page.
Arg3: e1a0fbc8, The next pool entry.
Arg4: 0c70066e, (reserved)
Debugging Details:
Du verkar ju fortfarande ha daemon tools installerat:
f6b81d64 7c90eb94 badb0d00 0006e7fc ffffffff d347bus+0xd7ac
Andra dumpen kan man inte säga mycket om. För att få mer information än vad dumpen ger måste man aktivera Special Pool. Men då är vi inne på mer avancerad felsökning. Mest troligt är nämligen minnesdelen redan korrupt när nuvarande funktion exekveras.
alright, daemon tools är avinstallerat nu, hoppas det gör susen.
har ju iofs haft det installerat hur länge som helst så det låter ju lite skumt att det orsakar allt strul helt plötsligt.
men men, hoppas hoppas
fortfarande skit med datorn.. nu får jag upp ett felmeddelande som säger att datorn stänger av sig inom en minut. har haft detta för länge sedan men då var det ett virus som kunde avbrytas genom att skriva "shutdown -a" i kör. nu får man bort meddelandet men datorn startas ändå om efter en minut..
konstigt med alla dessa fel, eftersom datorn är helt nyformaterad!! här kommer ny dump:
Microsoft (R) Windows Debugger Version 6.4.0007.2
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\WINDOWS\Minidump\Mini052905-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*c:\websymbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
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 May 29 10:00:05.875 2005 (GMT+2)
System Uptime: 0 days 0:01:20.578
Loading Kernel Symbols
.............................................................................................................................
Loading unloaded module list
....
Loading User Symbols
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 10000050, {e1be1804, 1, 805505a1, 1}
Could not read faulting driver name
Probably caused by : win32k.sys ( win32k!FastGetProfileStringW+60 )
Followup: MachineOwner
---------
0: kd> !analyze -v
*******************************************************************************
* *
* 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: e1be1804, memory referenced.
Arg2: 00000001, value 0 = read operation, 1 = write operation.
Arg3: 805505a1, If non-zero, the instruction address which referenced the bad memory
address.
Arg4: 00000001, (reserved)
Debugging Details:
Blaster/Sasser. En viktig sak att komma ihåg efter formatering är att slå igång en brandvägg innan nätverkskabeln pluggas i. Kör fixen (på den länkade sidan) samt Windows Update.
http://securityresponse.symantec.com/avcenter/venc/data/w32.blaster.worm.removal.tool.html
här kommer dump2 , den startar fortfarande om sig 2 ggr.
Microsoft (R) Windows Debugger Version 6.4.0007.2
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\WINDOWS\Minidump\Mini052905-02.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*c:\websymbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
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 May 29 14:28:24.953 2005 (GMT+2)
System Uptime: 0 days 0:05:13.656
Loading Kernel Symbols
....................................................................................................................................
Loading unloaded module list
..........
Loading User Symbols
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 100000D1, {ffffffff, 2, 0, ffffffff}
Probably caused by : irda.sys ( irda!InitiateDiscoveryReq+d4 )
Followup: MachineOwner
---------
1: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high. This is usually
caused by drivers using improper addresses.
If kernel debugger is available get stack backtrace.
Arguments:
Arg1: ffffffff, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000000, value 0 = read operation, 1 = write operation
Arg4: ffffffff, address which referenced memory
Debugging Details:
nix , verkar inte va blaster/sasser. fix-programmet hittar inget.
Fixprogrammet? Har du testat http://windowsupdate.microsoft.com ?
jepp, jag har redan alla uppdateringar installerade..
Om lsass kraschar ( vilket gör att maskinen stängs ner inom 60 sekunder) så har du någon typ av virus på maskinen. Maskarna Sasser/Blaster ska du vara fri från om du kört WU OCH allt installerats ok.