dinnmuzz

Hi, I have finally run the ram test that was mentioned above,it took about 25 mins, went thru, passed OK no errors. 1. Should I let it go on and on,, 2, Where to from here, confused by reading comment about above dumps. Thanks

I am not up to speed on the first part copy below Memory dump of the entire system: 1. Create or set the following registry value: Key: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\i8042prt\Parameters Value: CrashOnCtrlScroll Type: REG_DWORD Data: 1 How do you do that? in real simple language for me as a beginner in this area. Step by Step lol Thanks guys for your help by the way..

How do I configure to do a kernal dump, and then get that info

I have a program that is video program that is Ezy.exe So that is not malware. Again this program has been there for years

I have a XP pro comp, has been running fine, nothing has been changed,I have updated to SP3 but crashes were happening before that. I have run dubug from Microsoft and results as follows. Microsoft ® Windows Debugger Version 6.9.0003.113 X86 Copyright © Microsoft Corporation. All rights reserved. Loading Dump File [C:\WINDOWS\Minidump\Mini062508-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: Windows XP Kernel Version 2600 (Service Pack 3) UP Free x86 compatible Product: WinNt, suite: TerminalServer SingleUserTS Built by: 2600.xpsp.080413-2111 Kernel base = 0x804d7000 PsLoadedModuleList = 0x805634c0 Debug session time: Wed Jun 25 00:24:15.937 2008 (GMT+12) System Uptime: 0 days 14:34:58.468 Loading Kernel Symbols .................................................................................................... ........................................ Loading User Symbols Loading unloaded module list ................................. ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 1000000A, {4, 1c, 0, 804e90b2} Probably caused by : win32k.sys ( win32k!GreReleaseSemaphore+a ) Followup: MachineOwner --------- kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* IRQL_NOT_LESS_OR_EQUAL (a) 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 a kernel debugger is available get the stack backtrace. Arguments: Arg1: 00000004, memory referenced Arg2: 0000001c, IRQL Arg3: 00000000, bitfield : bit 0 : value 0 = read operation, 1 = write operation bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status) Arg4: 804e90b2, address which referenced memory Debugging Details: ------------------ READ_ADDRESS: 00000004 CURRENT_IRQL: 1c FAULTING_IP: nt!KeReleaseSemaphore+14 804e90b2 8b5e04 mov ebx,dword ptr [esi+4] CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: DRIVER_FAULT BUGCHECK_STR: 0xA PROCESS_NAME: Ezy.exe LAST_CONTROL_TRANSFER: from 804e9134 to 804e90b2 STACK_TEXT: f2c78cdc 804e9134 00000000 00000000 0000708c nt!KeReleaseSemaphore+0x14 f2c78d0c bf80198c bf82e5d1 00000001 00000000 nt!ExReleaseResourceLite+0x6f f2c78d10 bf82e5d1 00000001 00000000 f2c78d60 win32k!GreReleaseSemaphore+0xa f2c78d58 804dd98f e66a39c8 0012f420 7c90e4f4 win32k!GreSaveDC+0x1fb f2c78d58 7c90e4f4 e66a39c8 0012f420 7c90e4f4 nt!KiFastCallEntry+0xfc WARNING: Frame IP not in any known module. Following frames may be wrong. 0012f420 00000000 00000000 00000000 00000000 0x7c90e4f4 STACK_COMMAND: kb FOLLOWUP_IP: win32k!GreReleaseSemaphore+a bf80198c ff2538cb98bf jmp dword ptr [win32k!_imp__KeLeaveCriticalRegion (bf98cb38)] SYMBOL_STACK_INDEX: 2 SYMBOL_NAME: win32k!GreReleaseSemaphore+a FOLLOWUP_NAME: MachineOwner MODULE_NAME: win32k IMAGE_NAME: win32k.sys DEBUG_FLR_IMAGE_TIMESTAMP: 48025f2a FAILURE_BUCKET_ID: 0xA_win32k!GreReleaseSemaphore+a BUCKET_ID: 0xA_win32k!GreReleaseSemaphore+a Followup: MachineOwner --------- This is the error log from event viewer, Cat (102) Type error Event 1003 Error code 1000008e, parameter1 c0000005, parameter2 8070194f, parameter3 f32c8420, parameter4 00000000. 0000: 53 79 73 74 65 6d 20 45 System E 0008: 72 72 6f 72 20 20 45 72 rror Er 0010: 72 6f 72 20 63 6f 64 65 ror code 0018: 20 31 30 30 30 30 30 38 1000008 0020: 65 20 20 50 61 72 61 6d e Param 0028: 65 74 65 72 73 20 63 30 eters c0 0030: 30 30 30 30 30 35 2c 20 000005, 0038: 38 30 37 30 31 39 34 66 8070194f 0040: 2c 20 66 33 32 63 38 34 , f32c84 0048: 32 30 2c 20 30 30 30 30 20, 0000 0050: 30 30 30 30 0000