Hello
i did like u said Usasma, here is your file.
And to you zigzag i havent been so much at the computer lately so i have to wait til next crash appear
Thank you very much guys for your time :)
There are numerous BSOD's listed in the MSINFO32 file
Please do the following to upload them with your next post:
Upload Dump Files:
Please go to C:\Windows\Minidump and zip up the contents of the folder. Then upload/attach the .zip file with your next post.
Left click on the first minidump file.
Hold down the "Shift" key and left click on the last minidump file.
Right click on the blue highlighted area and select "Send to"
Select "Compressed (zipped) folder" and note where the folder is saved.
Upload that .zip file with your next post.
If you have issues with "Access Denied" errors, try copying the files to your desktop and zipping them up from there. If it still won't let you zip them up, post back for further advice.
If you don't have anything in that folder, please check in C:\Windows for a file named MEMORY.DMP. If you find it, zip it up and upload it to a free file hosting service - then post the link to it.
Then, follow the directions here to set your system for Minidumps (much smaller than the MEMORY.DMP file): Set MiniDump
I did a recovery from a earlier date on windows 7 because i had 1 broken .dll file. So i only have 3 dumpies left. I hope these is enough for you to help :)
Thanks
No problem
these appear to have been caused by memory corruption. I would download memtestx86 and run for at least 5 passes
Run a system file check
type cmd in search>right click and run as admin>sfc /scannow
Let us know the results
Ken J+
Code:Microsoft (R) Windows Debugger Version 6.11.0001.404 X86 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [C:\Users\K\Desktop\New folder\010710-60793-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: SRV*d:\symbols*http://msdl.microsoft.com/download/symbols Executable search path is: Windows 7 Kernel Version 7600 MP (2 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Built by: 7600.16385.amd64fre.win7_rtm.090713-1255 Machine Name: Kernel base = 0xfffff800`02c53000 PsLoadedModuleList = 0xfffff800`02e90e50 Debug session time: Thu Jan 7 17:35:32.073 2010 (GMT-5) System Uptime: 0 days 0:00:52.977 Loading Kernel Symbols ............................................................... ................................................................ ................. Loading User Symbols ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 1000007E, {ffffffffc000001d, fffff880043af796, fffff88002ff67b8, fffff88002ff6010} Probably caused by : memory_corruption Followup: memory_corruption --------- 1: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e) 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: ffffffffc000001d, The exception code that was not handled Arg2: fffff880043af796, The address that the exception occurred at Arg3: fffff88002ff67b8, Exception Record Address Arg4: fffff88002ff6010, Context Record Address Debugging Details: ------------------ EXCEPTION_CODE: (NTSTATUS) 0xc000001d - {EXCEPTION} Illegal Instruction An attempt was made to execute an illegal instruction. FAULTING_IP: kbdclass!KeyboardClassGetWaitWakeEnableState+172 fffff880`043af796 49 ??? EXCEPTION_RECORD: fffff88002ff67b8 -- (.exr 0xfffff88002ff67b8) ExceptionAddress: fffff880043af796 (kbdclass!KeyboardClassGetWaitWakeEnableState+0x0000000000000172) ExceptionCode: c000001d (Illegal instruction) ExceptionFlags: 00000000 NumberParameters: 0 CONTEXT: fffff88002ff6010 -- (.cxr 0xfffff88002ff6010) rax=0000000000000000 rbx=0000000000000000 rcx=f880043ad2b00000 rdx=0000000000000000 rsi=0000000000000040 rdi=fffffa80081d81b0 rip=fffff880043af796 rsp=fffff88002ff69f0 rbp=fffffa80081d81b0 r8=0000000000000000 r9=fffff80002c83de0 r10=0000000000000101 r11=fffff88002ff6bb0 r12=fffffa800822a2a0 r13=0000000000000000 r14=0000000000000000 r15=0000000000000001 iopl=0 nv up ei pl zr na po nc cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010246 kbdclass!KeyboardClassGetWaitWakeEnableState+0x172: fffff880`043af796 49 ??? Resetting default scope CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: CODE_CORRUPTION BUGCHECK_STR: 0x7E PROCESS_NAME: System CURRENT_IRQL: 0 ERROR_CODE: (NTSTATUS) 0xc000001d - {EXCEPTION} Illegal Instruction An attempt was made to execute an illegal instruction. LAST_CONTROL_TRANSFER: from fffff880043aa0f9 to fffff880043af796 FAILED_INSTRUCTION_ADDRESS: kbdclass!KeyboardClassGetWaitWakeEnableState+172 fffff880`043af796 49 ??? STACK_TEXT: fffff880`02ff69f0 fffff880`043aa0f9 : 00000000`00000000 00000000`00000000 00000000`00000040 fffffa80`04901040 : kbdclass!KeyboardClassGetWaitWakeEnableState+0x172 fffff880`02ff6bc0 fffff880`043aa2e3 : fffffa80`0822a2a0 fffff800`02e685f8 fffffa80`081f01b0 00000000`00000000 : kbdclass!KeyboardStart+0x105 fffff880`02ff6c50 fffff800`02fbe527 : fffffa80`081d8060 fffffa80`04901040 fffffa80`08202c10 fffffa80`04901040 : kbdclass!KeyboardStartWorker+0x1f fffff880`02ff6c80 fffff800`02cd2161 : fffff800`02f20000 fffff800`030e2f90 fffff800`02e685f8 00000000`00000000 : nt!IopProcessWorkItem+0x23 fffff880`02ff6cb0 fffff800`02f68166 : 00000000`00000000 fffffa80`04901040 00000000`00000080 fffffa80`048f0040 : nt!ExpWorkerThread+0x111 fffff880`02ff6d40 fffff800`02ca3486 : fffff880`009e7180 fffffa80`04901040 fffff880`009f1f40 00000000`00000000 : nt!PspSystemThreadStartup+0x5a fffff880`02ff6d80 00000000`00000000 : fffff880`02ff7000 fffff880`02ff1000 fffff880`02ff69f0 00000000`00000000 : nt!KxStartSystemThread+0x16 CHKIMG_EXTENSION: !chkimg -lo 50 -d !kbdclass fffff880043af797 - kbdclass!KeyboardClassGetWaitWakeEnableState+173 [ 8b:8f ] 1 error : !kbdclass (fffff880043af797) MODULE_NAME: memory_corruption IMAGE_NAME: memory_corruption FOLLOWUP_NAME: memory_corruption DEBUG_FLR_IMAGE_TIMESTAMP: 0 MEMORY_CORRUPTOR: ONE_BIT STACK_COMMAND: .cxr 0xfffff88002ff6010 ; kb FAILURE_BUCKET_ID: X64_MEMORY_CORRUPTION_ONE_BIT BUCKET_ID: X64_MEMORY_CORRUPTION_ONE_BIT Followup: memory_corruption ---------
Hello again i couldnt make this memtestx 86 work on win 7 so i found another program called memtest. I dotn know if it will do the same work.
And also when i do this run as admin --> sfc /scannow , i get a black window that quickly closes.
Im testings a first time with this memtest (link : MemTest for Windows Download Page )
Hello. I did scan a couple of times but with this program it scans over 100% til i stoped it on 117%. So i would like some help finding a working memtest program because this one is a bit odd. Btw i didnt get any errors on this one. I also did a scan on sfc /scannow and after the scan was completed i didnt get any message or report on the scan..the window just closed so i assumed it was finished.
I sometimes reply a few days late because i thought the crashes stopped but the seem coming back more or less :), so i apologize for the late replies.
Thanks again
Quote