Most recent dump file:
Code:
BugCheck 7F, {8, 80050033, 6f8, fffff8800147552a}
[COLOR=#ff0000][U][B]Probably caused by : memory_corruption[/B][/U][/COLOR]
Followup:[COLOR=#ff0000][U][B] memory_corruption[/B][/U][/COLOR]
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, [COLOR=#ff0000][U][B]EXCEPTION_DOUBLE_FAULT[/B][/U][/COLOR]
Arg2: 0000000080050033
Arg3: 00000000000006f8
Arg4: fffff8800147552a
BUGCHECK_STR: 0x7f_8
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: CODE_CORRUPTION
PROCESS_NAME: [COLOR=#ff0000][U][B]WifiSvc.exe[/B][/U][/COLOR]
CURRENT_IRQL: 0
LAST_CONTROL_TRANSFER: from fffff80002cd0b29 to fffff80002cd15c0
STACK_TEXT:
fffff880`009b8de8 fffff800`02cd0b29 : 00000000`0000007f 00000000`00000008 00000000`80050033 00000000`000006f8 : nt!KeBugCheckEx
fffff880`009b8df0 fffff800`02cceff2 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69
fffff880`009b8f30 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDoubleFaultAbort+0xb2
STACK_COMMAND: kb
CHKIMG_EXTENSION: !chkimg -lo 50 -db [COLOR=#ff0000][U][B]!ndis[/B][/U][/COLOR]
[COLOR=#ff0000][U][B]2 errors[/B][/U][/COLOR] : [COLOR=#ff0000][U][B]!ndis[/B][/U][/COLOR] (fffff88001475528-fffff880014755e0)
fffff88001475520 8b 8c 24 30 01 00 00 48 *31 cc e8 e1 da ff ff 48 ..$0...H1......H
...
fffff880014755e0 *03 48 8b 0d 28 fb 05 00 48 83 bf 10 02 00 00 00 .H..(...H.......
MODULE_NAME: [COLOR=#ff0000][U][B]memory_corruption[/B][/U][/COLOR]
IMAGE_NAME: [COLOR=#ff0000][U][B]memory_corruption[/B][/U][/COLOR]
FOLLOWUP_NAME: [COLOR=#ff0000][U][B]memory_corruption[/B][/U][/COLOR]
DEBUG_FLR_IMAGE_TIMESTAMP: 0
MEMORY_CORRUPTOR: STRIDE
FAILURE_BUCKET_ID: X64_[COLOR=#ff0000][U][B]MEMORY_CORRUPTION[/B][/U][/COLOR]_STRIDE
BUCKET_ID: X64_[COLOR=#ff0000][U][B]MEMORY_CORRUPTION[/B][/U][/COLOR]_STRIDE
Followup: [COLOR=#ff0000][U][B]memory_corruption[/B][/U][/COLOR]
DRIVERS to UPDATE:
Rt64win7.sys 2/26/2009 4:04 from here
Realtek bcmwlhigh664.sys 11/5/2009 19:27
scmndisp.sys 1/17/2007 2:48 The two drivers seem to be associated with your NETGEAR WNDA3100v2 N600 Wireless Dual Band USB Adapter and are relatively old go here and obtain the latest for your adapter
WNDA3100v2 follow the instructions by first uninstalling any previously installed driver software package remove the USB dongle and reboot and check for the presence of those two files to confirm that the uninstaller took those two drivers with it during the uninstall process, if not rename the .sys extensions to .OLD before attempting to install the latest driver software package.
Although your dump file would suggest problems with memory, the involvement of NDIS.SYS as well as WiFiSvc.exe makes me suspect it may still yet be a drive issues with your USB WiFi Dongle.
As an alternative you may want to take this device completely out of the diagnostic equation by removing it from your system and not installing any software package for the time being. Just as an temporary experiment to determine if it is fact the culprit.
If Blue Screens persist after completing the above, you'll probably want to
Download Memtest86+
from this location here. Burn the ISO to a CD and boot the computer from the CD from a cold boot after leaving it off for an hour or more.
Ideally let it run for at least 7 passes / 6-8 hours. If errors appear before that you can stop that particular test. Any time Memtest86+ reports errors, it can be either bad RAM or a bad Mobo slot. Perform the test RAM sticks individually as well as all possible combinations. When you find a good one then test it in all slots. Post back with the results.
See
this Guide to using Memtest 86+ Sometimes you'll find that when all memory slots on your motherboard are populated with 1333 (667Mhz) memory or faster you may very well have to tweak your memory voltage. Whether of not you will be able to do so or not will depend on your System BIOS and the available options and you computer or motherboard documentation should suggest
where to do this. The
how to do this is a bit of trial and error.
In my case the BIOS supported small increments. It started with the default setting of 1.5v and I bumped it incrementally until arriving at 1.6v and system stability.
If MemTest86+ shows errors when testing all memory in all slots then perhaps an easier experiment to determine if a memory voltage increase is required might be to reduce the number of installed modules by half leaving half the slots empty and the remaining slots populated according to the instructions provided in your motherboard manual.
Keep us posted
Regards
Randy