New system New BSOD problem.

Just made a new system and I have never had issues this bad. The attachment does include the dump files from the utility provided by this site (thanks much) but i was not able to include a system health report. Every time i tried I would get an error stating windows could not locate that file path. Also I was suspecting it could be a bad install of my video card drivers. I used guru3d and wiped out the driver and reinstalled. That did not help. The system is fine for the most part in safe mode. Does not last but a few seconds when booted up normal before going to BSOD.

Is Windows 7 . . .
- x86 (32-bit) or x64 ? x64
- the original installed OS on the system? yes built the system not but a week ago.
- an OEM or full retail version? Its an OEM copy I purchased on-line. But dont get me wrong I installed it onto my system.
- OEM = came pre-installed on system
- Full Retail = you purchased it from retailer

- What is the age of system (hardware)? 1 week.
- What is the age of OS installation (have you re-installed the OS?) also 1 week.

sys specs
asus m4a89td pro usb3.0 mobo
g skill 1600 DDR3 2 gig (X4)
AMD phenom x6 clocked at 3.0 (no overcloking)
Saphire HD6870 x2
OCZ SSD 120g (OS is loaded on this guy)


I am really new to the error codes on BSOD and since I started having my problems have learned about these mem. dumps but defiantly dont have the knowledge to know where to start. Then I found this site. Thanks in advance for any help.

thunderjeep said:

Just made a new system and I have never had issues this bad. The attachment does include the dump files from the utility provided by this site (thanks much) but i was not able to include a system health report. Every time i tried I would get an error stating windows could not locate that file path. Also I was suspecting it could be a bad install of my video card drivers. I used guru3d and wiped out the driver and reinstalled. That did not help. The system is fine for the most part in safe mode. Does not last but a few seconds when booted up normal before going to BSOD.

Is Windows 7 . . .
- x86 (32-bit) or x64 ? x64
- the original installed OS on the system? yes built the system not but a week ago.
- an OEM or full retail version? Its an OEM copy I purchased on-line. But dont get me wrong I installed it onto my system.
- OEM = came pre-installed on system
- Full Retail = you purchased it from retailer

- What is the age of system (hardware)? 1 week.
- What is the age of OS installation (have you re-installed the OS?) also 1 week.

sys specs
asus m4a89td pro usb3.0 mobo
g skill 1600 DDR3 2 gig (X4)
AMD phenom x6 clocked at 3.0 (no overcloking)
Saphire HD6870 x2
OCZ SSD 120g (OS is loaded on this guy)


I am really new to the error codes on BSOD and since I started having my problems have learned about these mem. dumps but defiantly dont have the knowledge to know where to start. Then I found this site. Thanks in advance for any help.

One crash was blamed on your video but the majority were caused by some form of memory corruption (probably caused by a driver)

I would run memtest and driver verifier.

Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder or another ISO burning program. Memtest86.com - Memory Diagnostic

Boot from the CD, and leave it running for at least 5 or 6 passes.

Just remember, any time Memtest reports errors, it can be either bad RAM or a bad motherboard slot.

Test the sticks individually, and if you find a good one, test it in all slots.

I'd suggest that you first backup your stuff and then make sure you've got access to another computer so you can contact us if problems arise. Then make a System Restore point (so you can restore the system using the Vista/Win7 Startup Repair feature).

In Windows 7 you can make a Startup Repair disk by going to Start....All Programs...Maintenance...Create a System Repair Disc - with Windows Vista you'll have to use your installation disk or the "Repair your computer" option at the top of the Safe Mode menu .

Then, here's the procedure:
- Go to Start and type in "verifier" (without the quotes) and press Enter
- Select "Create custom settings (for code developers)" and click "Next"
- Select "Select individual settings from a full list" and click "Next"
- Select everything EXCEPT FOR "Low Resource Simulation" and click "Next"
- Select "Select driver names from a list" and click "Next"
Then select all drivers NOT provided by Microsoft and click "Next"
- Select "Finish" on the next page.

Reboot the system and wait for it to crash to the Blue Screen. Continue to use your system normally, and if you know what causes the crash, do that repeatedly. The objective here is to get the system to crash because Driver Verifier is stressing the drivers out. If it doesn't crash for you, then let it run for at least 36 hours of continuous operation (an estimate on my part).

If you can't get into Windows because it crashes too soon, try it in Safe Mode.
If you can't get into Safe Mode, try using System Restore from your installation DVD to set the system back to the previous restore point that you created.

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\Windows_NT6_BSOD_jcgriff2\031911-14617-02.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;srv*e:\symbols
*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (6 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Machine Name:
Kernel base = 0xfffff800`02c53000 PsLoadedModuleList = 0xfffff800`02e90e50
Debug session time: Sat Mar 19 23:29:39.692 2011 (GMT-4)
System Uptime: 0 days 0:00:25.003
Loading Kernel Symbols
...............................................................
................................................................
.................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck A, {0, 2, 1, fffff80002cf036f}

Probably caused by : memory_corruption ( nt!MiReferenceControlArea+1ff )

Followup: MachineOwner
---------

2: 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: 0000000000000000, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000001, 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: fffff80002cf036f, address which referenced memory

Debugging Details:
------------------


WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff80002efb0e0
 0000000000000000 

CURRENT_IRQL:  2

FAULTING_IP: 
nt!MiReferenceControlArea+1ff
fffff800`02cf036f 488908          mov     qword ptr [rax],rcx

CUSTOMER_CRASH_COUNT:  2

DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP

BUGCHECK_STR:  0xA

PROCESS_NAME:  svchost.exe

TRAP_FRAME:  fffff88006f43720 -- (.trap 0xfffff88006f43720)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=0010000000000000
rdx=0000000080000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002cf036f rsp=fffff88006f438b0 rbp=fffff88002f64180
 r8=0000000000000000  r9=fffff88002f64180 r10=0000000000000000
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl zr na po nc
nt!MiReferenceControlArea+0x1ff:
fffff800`02cf036f 488908          mov     qword ptr [rax],rcx ds:00000000`00000000=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002cc2ca9 to fffff80002cc3740

STACK_TEXT:  
fffff880`06f435d8 fffff800`02cc2ca9 : 00000000`0000000a 00000000`00000000 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
fffff880`06f435e0 fffff800`02cc1920 : fffffa80`0a418010 fffffa80`099d35d0 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69
fffff880`06f43720 fffff800`02cf036f : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x260
fffff880`06f438b0 fffff800`02fbc451 : 00000000`00000000 00000000`00000002 00000000`01000000 00000000`00000000 : nt!MiReferenceControlArea+0x1ff
fffff880`06f43920 fffff800`02fb1d13 : fffff880`06f43b80 00000000`00000000 00000000`00000000 fffff880`06f43b78 : nt!MmCreateSection+0x285
fffff880`06f43b30 fffff800`02cc2993 : fffffa80`0a1deb60 00000000`00b6df98 fffff880`06f43bc8 00000000`00b6e248 : nt!NtCreateSection+0x162
fffff880`06f43bb0 00000000`7761fb5a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`00b6df78 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7761fb5a


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!MiReferenceControlArea+1ff
fffff800`02cf036f 488908          mov     qword ptr [rax],rcx

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  nt!MiReferenceControlArea+1ff

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP:  4cc791bd

IMAGE_NAME:  memory_corruption

FAILURE_BUCKET_ID:  X64_0xA_VRF_nt!MiReferenceControlArea+1ff

BUCKET_ID:  X64_0xA_VRF_nt!MiReferenceControlArea+1ff

Followup: MachineOwner
---------

Thanks so much for speedy reply. I was going to buy the Memtest86.com - Memory Diagnostic program but I was reading on their site about their product and it seems to be based on x86 systems. I know I am running x64, and perhaps this is a case of "I don't know what I need to know" but it would seem to me that a x86 mem. diag. would only be testing half the RAM allocated to a x64 system. Not sure if that is the case or not, maybe I am being foolish.
Now that you bring up the majority of my BSOD's resulting from RAM issues I think it might be important to note that several days ago I suspected bad RAM/ mobo RAM slots on this system. Since then I RMA the ram, mobo,and CPU for good measure. I received the new components yesterday. I do worry that my G SKILL ram ( model f3-12800cl9d-4gbrl) are not configured appropriately in the BIOS. When set to auto my BIOS sets the RAM speed at 1333MHZ and the voltage at anywhere from 1.45-1.5 V. G. SKILL says this model number should be at 1600MHZ and at 1.6v. I have configured my BIOS to run the RAM at the G. SKILL recommendations. I also tried to run the driver verifier utility. I was only able to set it up in safe mode and windows crashes way to fast (Im assuming with these mem. problems.) to get any useful information out of it. Does not seem any more stable though. Any help from this point would be greatly appreciated.

Thanks much for getting back with me Cartr6. Unfortunately though I will not be able to meet your request. I guess I am rather impatient, but allow me to explain. After my last post I began doing some research on the mobo. I found out that this board is plagued with memory problems and grounding problems to boot. So I figured I paid for a product it should work with RAM specified by the manufactured. The G. SKILL RAM I have is a listed RAM by ASUS for this board. So looking at this problem from outside of the trouble shooting mindset (got to defeat the problem, not necessarily figure out why there is a problem.) I have returned the mobo back to Newegg for a full refund. I have another system here running a ASUS M4A79XTD EVO 790X AM3 RT. Its cheaper, its running the exact same RAM I have, and much more reliable. I lose USB 3.0 but that is a small price for reliability. I will have the parts in 2 days. After I install the hardware I will come back to this post and let everyone know how things or going. I figure I am either going to be in the same boat or perhaps this will fix my problem. This approach may not ave been the optimal way of fixing the problem, but all my parts are still under warranty. So what you you think? perhaps I jumped the gun?

All right I got the new components. Got the New mobo. Important to note that this is not a replacement for the mobo I had but rather a different model that I know first hand works with the RAM I have. The system is up and running but nothing is ever easy right. My H70 water cooling system from Corseair failed while piceing the system together. I should have known better for buying into that foolish thing. Well you live and learn you know. I fortunately had a Zulman air cooled heat sink that has worked for a number of years and is really reliable. Had to reinstall windows tried booting it up and it BSOD on my almost instantly and said that the I/O drivers that were loading where mucking everything up. Made sence since it still had the old mobo drivers loaded up on there. So i decided for a clean install. That went just fine and i was lading all of my drivers on and ran into a snag for the ATI driver. Its gui would continuously crash. I ended up using the cmd promt to install it and that worked out well. The next boot up though the system BSOD before I got to log-in. I assumed it had to be the recently installed ATI drivers. I restarted again and here I am writing this. So I wonder about the stability of my current graphics driver. I have created a restore point just in case. I am going to stress my video drivers by running 4 instances of VLC media player running several different videos. I dont have any stressing software and i figured if anything will crash it this will. If it does crash I will make sure to use that utility that rips the mem dumps and I will post here again.

Hay guys, its me again coming to you live from windows safe mode with networking.....*sigh* Needless to say my makeshift stress test did the job. Lasted for a number of hours before it went BSOD with error code 1E. Tried bootting it up again this morning and it went to BSOD with the same error code before I could do anything. It would seem I am just fine in safe mode though. I have included the mem dump so if any one could decipher that I would be very grateful. Dave76 thank you much for the stress test link you have given me. I am sure to use it once I get things up and running. Also dave the only new hardware I have from the old configuration is a new heat sink but that should be negligible and the new mobo which is a ASUS m4a79xtd Evo. and just for continuity's sake I am going to post my system hardware here again with updated mobo and model numbers. Not really sure where to go from here guys. Willing to try anything.

ASUS m4a79xtd Evo
g skill 1600 DDR3 2 gig (X4) model number: f3-12800cl9d-4gbrl
AMD phenom x6 clocked at 3.0 (no overcloking) mdel number:x6 1075T
Saphire HD6870 x2
OCZ SSD 120g (OS is loaded on this guy)