New
#31
Ok we go one thing at a time, not to overwhelm you. Do the memory test.
I will even give you the basic instructions on how it is done.
http://www.geekstogo.com/forum/Guide...6-t246994.html
Ok we go one thing at a time, not to overwhelm you. Do the memory test.
I will even give you the basic instructions on how it is done.
http://www.geekstogo.com/forum/Guide...6-t246994.html
Very good on removing SPTD.sys. You have eliminated one definite problem.
This one is a stop error code of 7F.
The dump file blames memory corruption. It can be bad RAM; but there are several things that can cause memory corruption besides bad RAM.STOP 0x0000007E: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
Usual causes: Insufficient disk space, Device driver, Video card, BIOS, Breakpoint with no debugger attached, Hardware incompatibility, Faulty system service, Memory, 3rd party remote control
Richard's advice is spot on. Follow his suggestion and run memtest86+. One of us on the BSOD team will be here if you have questions or problems. Richard will probably get back to you before I do.Code:Microsoft (R) Windows Debugger Version 6.11.0001.404 X86 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [C:\Users\Owner\AppData\Local\Temp\Temp1_062910-18205-01.zip\062910-18205-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: SRV*c:\symbols*Symbol information Executable search path is: Windows 7 Kernel Version 7600 MP (4 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Personal Built by: 7600.16539.amd64fre.win7_gdr.100226-1909 Machine Name: Kernel base = 0xfffff800`02e4d000 PsLoadedModuleList = 0xfffff800`0308ae50 Debug session time: Tue Jun 29 10:43:19.296 2010 (GMT-4) System Uptime: 0 days 0:00:10.748 Loading Kernel Symbols ............................................................... ........................................... Loading User Symbols ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 7F, {8, 80050031, 6f8, fffff8800150835a} Probably caused by : memory_corruption Followup: memory_corruption --------- 0: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* UNEXPECTED_KERNEL_MODE_TRAP (7f) This means a trap occurred in kernel mode, and it's a trap of a kind that the kernel isn't allowed to have/catch (bound trap) or that is always instant death (double fault). The first number in the bugcheck params is the number of the trap (8 = double fault, etc) Consult an Intel x86 family manual to learn more about what these traps are. Here is a *portion* of those codes: If kv shows a taskGate use .tss on the part before the colon, then kv. Else if kv shows a trapframe use .trap on that value Else .trap on the appropriate frame will show where the trap was taken (on x86, this will be the ebp that goes with the procedure KiTrap) Endif kb will then show the corrected stack. Arguments: Arg1: 0000000000000008, EXCEPTION_DOUBLE_FAULT Arg2: 0000000080050031 Arg3: 00000000000006f8 Arg4: fffff8800150835a Debugging Details: ------------------ BUGCHECK_STR: 0x7f_8 CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: CODE_CORRUPTION PROCESS_NAME: System CURRENT_IRQL: 0 LAST_CONTROL_TRANSFER: from fffff80002ebcb69 to fffff80002ebd600 STACK_TEXT: fffff800`043dcd28 fffff800`02ebcb69 : 00000000`0000007f 00000000`00000008 00000000`80050031 00000000`000006f8 : nt!KeBugCheckEx fffff800`043dcd30 fffff800`02ebb032 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69 fffff800`043dce70 fffff880`0150835a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDoubleFaultAbort+0xb2 80000000`00000004 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : ndis!ndisMergeOffloadCapsAndRegistry+0xa STACK_COMMAND: kb CHKIMG_EXTENSION: !chkimg -lo 50 -db !ndis 20 errors : !ndis (fffff88001508017-fffff88001508f97) fffff88001508010 48 83 ec 20 4c 8b 42 *88 45 33 c9 4c 8b f1 48 8b H.. L.B.E3.L..H. ... fffff88001508090 c9 eb 59 66 3b f8 74 *71 0f b7 c7 41 0f b7 0c 40 ..Yf;.tq...A...@ ... fffff880015080d0 66 d1 e8 66 3b f0 75 *00 66 8b 54 24 60 45 33 c9 f..f;.u.f.T$`E3. ... fffff88001508150 0d a3 19 04 00 44 8b *58 b8 01 00 00 00 42 87 04 .....D.X.....B.. ... fffff88001508310 00 00 44 3b c6 72 14 *cc 8b c6 e8 71 0c fe ff c6 ..D;.r.....q.... ... fffff88001508350 48 89 5c 24 08 48 89 *f4 24 10 57 48 83 ec 20 80 H.\$.H..$.WH.. . ... fffff88001508390 ff ff 73 0c 21 42 30 *09 72 24 89 72 28 89 72 2c ..s.!B0.r$.r(.r, ... fffff88001508450 10 75 03 89 73 0c f6 *07 74 13 00 00 40 74 03 21 .u..s...t...@t.! ... fffff880015084d0 0e 73 05 33 c0 89 43 *cc 8b 4b 4c ba bb 00 00 c0 .s.3..C..KL..... ... fffff88001508610 3a a7 75 5c 66 39 42 *82 72 56 80 7a 01 01 72 50 :.u\f9B.rV.z..rP ... fffff88001508910 90 90 90 90 90 90 90 *10 90 90 90 90 90 90 90 90 ................ ... fffff88001508ad0 f6 05 15 14 04 00 04 *f4 65 8a 0d 9b 11 04 00 41 ........e......A ... fffff88001508b10 c0 41 0f 4f c9 88 0d *df 11 04 00 41 3a c9 75 1e .A.O.......A:.u. ... fffff88001508b50 48 89 5c 24 08 48 89 *ec 24 10 48 89 74 24 18 57 H.\$.H..$.H.t$.W ... fffff88001508b90 41 b8 4e 44 77 31 33 *49 8b d2 ff 15 d8 1b 03 00 A.NDw13I........ ... fffff88001508c50 41 0f b7 44 24 22 66 *09 45 22 41 0f b7 44 24 24 A..D$"f.E"A..D$$ ... fffff88001508c90 00 00 49 8d 94 24 38 *82 00 00 41 b8 04 02 00 00 ..I..$8...A..... ... fffff88001508d10 8b d9 bf 3c 04 00 00 *c8 8d 4c 24 20 48 8b d3 4c ...<.....L$ H..L ... fffff88001508d50 7b 02 89 43 0c 8b 44 *a4 30 bf 04 02 00 00 89 43 {..C..D.0......C ... fffff88001508f90 24 44 41 23 c8 89 43 *dc 8b 44 24 48 89 4b 58 89 $DA#..C..D$H.KX. MODULE_NAME: memory_corruption IMAGE_NAME: memory_corruption FOLLOWUP_NAME: memory_corruption DEBUG_FLR_IMAGE_TIMESTAMP: 0 MEMORY_CORRUPTOR: STRIDE FAILURE_BUCKET_ID: X64_MEMORY_CORRUPTION_STRIDE BUCKET_ID: X64_MEMORY_CORRUPTION_STRIDE Followup: memory_corruption ---------
Thanks rich46 for The Idiots guide lol it was easy to follow and to you carlTR6. I have downloaded file and burned it to disk I have verified that it has done as it should do unfortunately for me my grandson came in when I was out and turned on comp to go gaming before I had removed a stick of ram. The Memetest kicked in and when I returned home it had done 6 scans and was showing some 6348 Failures I don't know if this was due to having the 2 sticks of ram in so I will do another run tomorrow the correct way with 1 stick in for each test see if that shows as many failures thanks again guys be in touch but if the run done with 2 sticks in is anything like looks like I have a bad Ram Problem.
When you find a good stick, test that stick in each RAM slot to see if you have a bad slot on your motherboard.
Ok guys Update for you I ran the memtest one stick is ok other one is totally US sending it back under warranty I am using comp with just one stick and alls well up to now I will keep you informed on any further progress Many thanks again for your help.
You are very welcome. I am glad you found your problem. I hope you will be up and running at full strength soon.
Okay Guys replaced the memory stick under warranty been running now for 2 days without any crashes or blue screens all looking good. Once again Many Thanks for your help in my hour of need.