Memtest

[Alfajk]

potreboval bych poradit,stahl jsem si http://www.goldmemory.cz (nebo by jste doporucili neco jinyho?) ,protoze potrebuju zjistit jestli jsou RAM ok,ale nevim co s tim,ani podle toho jejich navodu to nedam dohromady

chci to vypalit na cd (disketu totiz nemam),ale co vypalit? myslim si,ze to bude ten "rar"(se jmenem CDROM) co nejde rozbalit,ale pro jistotu se zeptam-lepsi nez spalit CD zbytecne

[Alfajk]

...tak uz jsem to asi dal dohromady,pak pisnu jak to dopadlo

[Alfajk]

nedopadlo to nijak,v biosu jsem dal: advanced bios features => first boot device - CD ROM a stejnak najeli normalni windows a test se nekonal(z duvodu ze dalsi bootovaci je HD) tudiz jsem udelal uz neco spatne pri vypaleni

tady maj navod:
1) Create a new folder
Example: C:\GM

2) Unzip all files from archive into that folder

3) Burn CDROM.ISO image to create stand-alone bootable CD-ROM.

je tam jeden rar (CDROM.iso) ,ten jsem teda vypalil a porad nic,co jsem na tom mohl udelat spatne? (kdyz se chci podivat do toho iso,pise to F:\CDROM.ISO: Nelze vytvořit )

[branda]

Na testování pamětí je osvědčený třeba Memtest86, ke stažení zde: http://www.stahuj.centrum.cz/utility_a_ ... memtest86/

[cernohous13]

Pokud máš F: opt.mechaniku, tak by na CD určitě neměl být soubor *.iso

ISO je obraz disku a vypaluje se takto
http://img7.imgup.eu/nero_iso.png

[Alfajk]

tak jsem to udelal a memtest se me podrail zprovoznit,nechal sem udelat 2 cely testy a ram vypadaj OK (0 chyb)...takze nevim cim muze bejt ten bsod zpusobenej
dik

[Alfajk]

jeste pridavam vypis pameti pri chybe

[Alfajk]

a jeste se me podarilo(mozna) rozlustit ten minidump,pro jistotu ho sem dam

Kód: Vybrat vše

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


Loading Dump File [C:\Documents and Settings\Admin.PC-PC\Plocha\Mini062209-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\windows\symbols*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_rtm.040803-2158
Machine Name:
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055c700
Debug session time: Mon Jun 22 21:26:16.562 2009 (GMT+2)
System Uptime: 0 days 0:31:28.294
Loading Kernel Symbols
...............................................................
................................................................
..
Loading User Symbols
Loading unloaded module list
.............
Unable to load image windrvNT.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for windrvNT.sys
*** ERROR: Module load completed but symbols could not be loaded for windrvNT.sys
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000008E, {c0000005, f7874703, ba449c70, 0}

Probably caused by : windrvNT.sys ( windrvNT+1703 )

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

1: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        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: f7874703, The address that the exception occurred at
Arg3: ba449c70, Trap Frame
Arg4: 00000000

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


EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - Instrukce na adrese 0x%08lx odkazovala na adresu pam

FAULTING_IP: 
windrvNT+1703
f7874703 668b08          mov     cx,word ptr [eax]

TRAP_FRAME:  ba449c70 -- (.trap 0xffffffffba449c70)
ErrCode = 00000000
eax=00000000 ebx=f7878142 ecx=00000000 edx=206b6400 esi=0012fb54 edi=ba449d64
eip=f7874703 esp=ba449ce4 ebp=ba449d04 iopl=0         nv up ei pl zr na pe nc
cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010246
windrvNT+0x1703:
f7874703 668b08          mov     cx,word ptr [eax]        ds:0023:00000000=????
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  DRIVER_FAULT

BUGCHECK_STR:  0x8E

PROCESS_NAME:  Re-MortalRO.exe

LAST_CONTROL_TRANSFER:  from f787823a to f7874703

STACK_TEXT:  
WARNING: Stack unwind information not available. Following frames may be wrong.
ba449d04 f787823a 00000000 00000000 3d737365 windrvNT+0x1703
ba449d48 8054060c 00000000 0012fb78 0012fb80 windrvNT+0x523a
ba449d48 7c90eb94 00000000 0012fb78 0012fb80 nt!KiFastCallEntry+0xfc
0012fb34 7c90e5e5 7c810e48 00000000 0012fb78 0x7c90eb94
0012fb88 00521760 00000000 00000000 00000000 0x7c90e5e5
0012fbb8 005217ef 00000000 0000002e 007748a0 0x521760
0012fbd4 0051daf0 011f8150 7c910738 00000000 0x5217ef
0012fc08 006b87ee 0070dd0c 7c910738 00000000 0x51daf0
0012ffa8 8061f142 0012ffe0 00695290 006c7738 0x6b87ee
0012ffc0 7c816d4f 7c910738 ffffffff 7ffde000 nt!CcPfBeginAppLaunch+0x190
0012fff0 00000000 00699eda 00000000 00000000 0x7c816d4f


STACK_COMMAND:  kb

FOLLOWUP_IP: 
windrvNT+1703
f7874703 668b08          mov     cx,word ptr [eax]

SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  windrvNT+1703

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: windrvNT

IMAGE_NAME:  windrvNT.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  409f405c

FAILURE_BUCKET_ID:  0x8E_windrvNT+1703

BUCKET_ID:  0x8E_windrvNT+1703

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

[Čarls]

Zkuste odinstalovat tuto hru vypadá že to má na svědomí Re-MortalRO http://re-mortalro.net/?page=10
Nebo jestli nevydali opravný Patch

[Alfajk]

ano,to ona to ma na svedomi,me by ale zajimalo jestli jde zjistit pri cem presne ta hra spadne,protoze pokud tu hru zapnu pres jinyho klienta,tak se aspon zapne do menu

je pravda ze vydali novej patch,ale me to spadne i s nim...

dokazete zjistit co presne je napsanyho v .exe? mam totiz dva (na prvni pohled) stejny klienty,od podobnejch serveru ktery spolu driv spolupracovali,ale jeden funguje a druhej spadne

[Čarls]

Bohužel Hry nehraji a tak vám moc neporadím

[Alfajk]

skoda...tohle je asi neresitelna zahada,ptal sem se na to uplne vsude a nikde nikdo nevi,kuli cemu to nefunguje

[stell]

zdravim
podla mna treba odcervit pc
windrvNT.sys-najst otestovat,

[Alfajk]

http://www.virustotal.com/cs/analisis/6 ... 1246109871 10/41

ale dle popisu " Misc/FolderLock " to mozna patri k programu Folder Lock kterej mam uz delsi dobu

[stell]

odinstaluj Folder Lock a budes mat po probleme,
potom napis,,,vidis ze nie je to koser,,,,