BSOD at start up

Hi Bryan, I'll find someone who is more adept at explaining the memory voltage tweaking than I can.

How about refreshing the information we have with a new run of the SF Diagnostic Tool (run as Administrator) and also please include CPUz images including all slots populated with memory from the SPD tab and export the HTML report from RAMMon. Links if needed are on the sticky that Elmer linked to already.

Here is the sf diagnostic and alll of the slots on the cpuz are the same so i only posted the one. Rammon file couldnt be uploaded so here u go RAMMon v1.0 Build: 1002 built with SysInfo v1.0 Build: 1019
PassMark (R) Software - www.passmark.com

Memory Summary For BRYAN-PC

Number of Memory Devices: 6 Total Physical Memory: 8182 MB (12288 MB) Total Available Physical Memory: 6101 MB Memory Load: 25%

Item	Slot #1	Slot #2	Slot #3	Slot #4	Slot #5	Slot #6
Ram Type	DDR3	DDR3	DDR3	DDR3	DDR3	DDR3
Standard Name	DDR3-1333	DDR3-1333	DDR3-1333	DDR3-1333	DDR3-1333	DDR3-1333
Module Name	PC3-10600	PC3-10600	PC3-10600	PC3-10600	PC3-10600	PC3-10600
Memory Capacity (MB)	2048	2048	2048	2048	2048	2048
Bus Clockspeed (Mhz)	666.67	666.67	666.67	666.67	666.67	666.67
Jedec Manufacture Name	Elpida	Elpida	Elpida	Elpida	Elpida	Elpida
Search Amazon.com	Search!	Search!	Search!	Search!	Search!	Search!
SPD Revision	1.0	1.0	1.0	1.0	1.0	1.0
Registered	No	No	No	No	No	No
ECC	No	No	No	No	No	No
DIMM Slot #	1	2	3	4	5	6
Manufactured	Year 0	Year 0	Year 0	Year 0	Year 0	Year 0
Module Part #	EBJ21UE8BDF0-DJ-F	EBJ21UE8BDF0-DJ-F	EBJ21UE8BDF0-DJ-F	EBJ21UE8BDF0-DJ-F	EBJ21UE8BDF0-DJ-F	EBJ21UE8BDF0-DJ-F
Module Revision	0x3020	0x3020	0x3020	0x3020	0x3020	0x3020
Module Serial #	0x190E2A70	0x180E2A70	0xE00D2A6F	0x230E2A71	0x200E2A70	0x1E0E2A71
Module Manufacturing Location	75	75	75	75	75	75
# of Row Addressing Bits	14	14	14	14	14	14
# of Column Addressing Bits	10	10	10	10	10	10
# of Banks	8	8	8	8	8	8
# of Ranks	2	2	2	2	2	2
Device Width in Bits	8	8	8	8	8	8
Bus Width in Bits	64	64	64	64	64	64
Module Voltage	1.5V	1.5V	1.5V	1.5V	1.5V	1.5V
CAS Latencies Supported	6 7 8 9	6 7 8 9	6 7 8 9	6 7 8 9	6 7 8 9	6 7 8 9
Timings @ Max Frequency	9-9-9-24	9-9-9-24	9-9-9-24	9-9-9-24	9-9-9-24	9-9-9-24
Minimum Clock Cycle Time, tCK (ns)	1.500	1.500	1.500	1.500	1.500	1.500
Minimum CAS Latency Time, tAA (ns)	13.125	13.125	13.125	13.125	13.125	13.125
Minimum RAS to CAS Delay, tRCD (ns)	13.125	13.125	13.125	13.125	13.125	13.125
Minimum Row Precharge Time, tRP (ns)	13.125	13.125	13.125	13.125	13.125	13.125
Minimum Active to Precharge Time, tRAS (ns)	36.000	36.000	36.000	36.000	36.000	36.000
Minimum Row Active to Row Active Delay, tRRD (ns)	6.000	6.000	6.000	6.000	6.000	6.000
Minimum Auto-Refresh to Active/Auto-Refresh Time, tRC (ns)	49.125	49.125	49.125	49.125	49.125	49.125
Minimum Auto-Refresh to Active/Auto-Refresh Command Period, tRFC (ns)	110.000	110.000	110.000	110.000	110.000	110.000
DDR3 Specific SPD Attributes
Write Recovery Time, tWR (ns)	15.000	15.000	15.000	15.000	15.000	15.000
Internal Write to Read Command Delay, tWTR (ns)	7.500	7.500	7.500	7.500	7.500	7.500
Internal Read to Precharge Command Delay, tRTP (ns)	7.500	7.500	7.500	7.500	7.500	7.500
Minimum Four Activate Window Delay, tFAW (ns)	30.000	30.000	30.000	30.000	30.000	30.000
RZQ / 6 Supported	Yes	Yes	Yes	Yes	Yes	Yes
RZQ / 7 Supported	Yes	Yes	Yes	Yes	Yes	Yes
DLL-Off Mode Supported	Yes	Yes	Yes	Yes	Yes	Yes
Maximum Operating Temperature (C)	95	95	95	95	95	95
Refresh Rate at Extended Operating Temperature Range	1X	1X	1X	1X	1X	1X
Auto-self Refresh Supported	No	No	No	No	No	No
On-die Thermal Sensor Readout Supported	No	No	No	No	No	No
Partial Array Self Refresh Supported	Yes	Yes	Yes	Yes	Yes	Yes
Thermal Sensor Present	No	No	No	No	No	No
Non-standard SDRAM Type	Standard Monolithic	Standard Monolithic	Standard Monolithic	Standard Monolithic	Standard Monolithic	Standard Monolithic
Module Type	UDIMM	UDIMM	UDIMM	UDIMM	UDIMM	UDIMM
Module Height (mm)	30	30	30	30	30	30
Module Thickness (front), (mm)	2	2	2	2	2	2
Module Thickness (back), (mm)	2	2	2	2	2	2
Module Width (mm)	133.5	133.5	133.5	133.5	133.5	133.5
Reference Raw Card Used	Raw Card B Rev. 0	Raw Card B Rev. 0	Raw Card B Rev. 0	Raw Card B Rev. 0	Raw Card B Rev. 0	Raw Card B Rev. 0
DRAM Manufacture ID	766	766	766	766	766	766
# of DRAM Rows	0	0	0	0	0	0
# of Registers	0	0	0	0	0	0
Register Manufacturer
Register Type
Register Revision	0	0	0	0	0	0

Most recent dump file:

Code:

BugCheck 7F, {8, 80050033, 6f8, fffff8800147552a}
Probably caused by : memory_corruption
Followup: memory_corruption
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: 0000000080050033
Arg3: 00000000000006f8
Arg4: fffff8800147552a
BUGCHECK_STR:  0x7f_8
CUSTOMER_CRASH_COUNT:  1
DEFAULT_BUCKET_ID:  CODE_CORRUPTION
PROCESS_NAME:  WifiSvc.exe
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 !ndis
2 errors : !ndis (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: 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

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

hi, sorry for the long reply. been out of town and busy. anyways, updated netgear, uninstalled it, still no luck. and can u be a little more specific on the mem test? i downloaded one of them (not sure if right one) and then burned it and booted from cd but nothing happened. do i burn the zip file, one of the folders in the zip, or just one of the iso files? and if so which one theres 2? thanks for the help

Memtest86+ 4.20.

Download either of these, depending on whether you have 7-zip installed (first option):
Download - Pre-Compiled Bootable ISO (.gz)
Download - Pre-Compiled Bootable ISO (.zip)

Open the zip, and use ImgBurn to create a CD from the iso file, Do not just copy the iso onto a CD. Then:

Run Memtest86+ overnight, after your computer has been off for about an hour or two so it has a cold start. Ideally let it run for at least 7 passes / 6-8 hours. If errors appear before that you can stop that particular test.
Note!! Any time Memtest86+ reports errors, it can be either bad RAM or a bad Mobo slot. Test RAM sticks individually. When you find a good one then test it in all slots. Post back with the results.

Memtest86+ 4.20 Download.

Guide to using Memtest86+

alright so i finally found the time and decided not to be lazy. i ran the test and this came up

seeing as there was almost 400 errors, i dont think thats too good. so what do i do next? do i have to take out every stick and see whats the faulty one? is this my fault, or the manufacturers? i bought it from dell and have had it for about a year and a half. angers me its already failing

I have a couple of questions about this;
1. Did you change the voltages at all, not just for the memory but for anything else?
2. Did you remove the memory at all?
3. Did you do a hard reset of the bios including pulling the battery?
4. Did you try to OC this system?

I noticed on your CPUZ SS that the voltage was 1.5v, that seems a tad high. Memory voltage should be no more than 1.5v either. If these are not adjustable on your board then I suspect you have a PSU issue that overvolted your memory and possibly your CPU. If you can access voltage settings through the bios I would recommend setting them at auto (if possible). If not take the unit back to Dell and have them check the system, you may end up needing to buy new RAM, but make sure the PSU is working correctly before installing it.

No to all of those. How does one change the voltage settings?

It would be on a page called voltage in the Bios. I think you were running a Dell rig right? If thats the case the settings are usually not adjustable.