tosiaan nyt rupesi ihmettyttään kun ostin aikoja sitten HD 5770 näyttiksen ja eka todettiin rikkinäiseksi huollossa, kun se tuli takasi niin samat ongelmat vaan jatkuivat ja laitoin sen takasi huoltoon mutta se oli ehjä tuote joten sama tuli takas.
Ainakin yksi bsod viittasi kovalevyyn (katsoin koodin perusteella) joten testasin sen eikä se ollu ainakaan rikki.
Tänään tuli tälläinen, tässä minidumb:
Microsoft (R) Windows Debugger Version 6.12.0002.633 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\Minidump\Mini032411-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
WARNING: Whitespace at end of path element
Symbol search path is: srv*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows Server 2008/Windows Vista Kernel Version 6002 (Service Pack 2) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 6002.18327.x86fre.vistasp2_gdr.101014-0432
Machine Name:
Kernel base = 0x82236000 PsLoadedModuleList = 0x8234dc70
Debug session time: Thu Mar 24 14:32:58.612 2011 (UTC + 2:00)
System Uptime: 0 days 0:01:56.363
Loading Kernel Symbols
...............................................................
................................................................
.................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck C1, {a6396e70, a639643c, 170190, 23}
Unable to load image \SystemRoot\System32\Drivers\sptd.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for sptd.sys
*** ERROR: Module load completed but symbols could not be loaded for sptd.sys
Probably caused by : ecache.sys ( ecache!EcDeviceIoCleanup+17 )
SPECIAL_POOL_DETECTED_MEMORY_CORRUPTION (c1)
Special pool has detected memory corruption. Typically the current thread's
stack backtrace will reveal the guilty party.
Arguments:
Arg1: a6396e70, address trying to free
Arg2: a639643c, address where bits are corrupted
Arg3: 00170190, (reserved)
Arg4: 00000023, caller is freeing an address where nearby bytes within the same page have been corrupted
joo tosiaan molemmilla muisti kammoilla 7h pyöritin testiä ilman yhtäkään error:ia
Edit. tässä uusin dumppi:
Microsoft (R) Windows Debugger Version 6.12.0002.633 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\Minidump\Mini032511-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
WARNING: Whitespace at end of path element
Symbol search path is: srv*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows Server 2008/Windows Vista Kernel Version 6002 (Service Pack 2) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 6002.18327.x86fre.vistasp2_gdr.101014-0432
Machine Name:
Kernel base = 0x8224b000 PsLoadedModuleList = 0x82362c70
Debug session time: Fri Mar 25 15:58:43.577 2011 (UTC + 2:00)
System Uptime: 0 days 0:59:45.440
Loading Kernel Symbols
...............................................................
................................................................
................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
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: 8242bdec, The address that the exception occurred at
Arg3: a28786dc, Trap Frame Arg4: 00000000
Debugging Details:
------------------
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - K sky osoitteessa 0x%08lx viittasi muistiin osoitteessa 0x%08lx. Muisti ei voi olla %s.
