New system New BSOD problem.

[thunderjeep]

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.

 

[zigzag3143]

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.

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
---------

 

[thunderjeep]

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.

 

[CarlTR6]

Thunderjeep, I will ask one of our hardware Guru's to take a look at this thread. I know they are going to want some additional information.

Please post your CPUZ, Mainboard, Memory, and SPD tabs. This will give everyone the basic info, Mainboard for the motherboard though the revision is usually not listed, Memory tab can indicate wrong OC attempts or wrong settings, confirmed by the SPD tab which is the JEDEC settings for the RAM. JEDEC is the industry standard that the RAM manufactures use to get stable settings for default.

For posting the information , enter 'Snipping tool' in the Start button > Search box, hit enter. Select the area you want to post and save to a convenient place. How to Post a Screenshot in Seven Forums

We will also need the voltage settings for the CPU, RAM and NB or equivalent. NB or memory controller is important. CPU voltage is listed on the CPU tab, RAM voltage is listed but it's not the actual voltage; it's the recommended voltage.

 

[thunderjeep]

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?

 

[CarlTR6]

If you suspect your mobo and it is under warranty, you have not jumped the gun at all. I hope the new mobo will solve your problem. It is possible that the hardware Guru's could have guided you in tuning your mobo to the RAM; but that is time consuming and a lot of trial and error. Please do update us after you get the new system up and running - and I hope you will be BSOD free.

Thank you very much for the update.

 

[Dave76]

I have to agree with Carl, the RAM can be adjusted to work on that motherboard, but it is a long process of testing and tuning.

The problem you have described is a very well known issue and affects just about everyone with an AMD CPU trying to run RAM at 1600MHz.

Read the info on this link, it explains the issue.
VERY IMPORTANT INFORMATION REGARDING AMD AM3 CPU's and RAM SPEEDS


The best way to solve this, until AMD solves it, is to run your RAM at 1333MHz.
Completely understand that if you decide to buy 1600MHz RAM, you want to run the RAM at 1600MHz.
As mentioned in the link above, this can be done but it is not an easy task. The perceptible difference in speed is negligible.

Be sure to get RAM that specifically states it is optimized for AMD CPU/motherboards.
There are many issues when trying to use Intel optimized RAM on an AMD system.

Let us know how the new components are working.

 

[thunderjeep]

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.

 

[Dave76]

This is a good video card stress test:
Video Card - Stress Test with Furmark

Can you let us know your new hardware?

 

[thunderjeep]

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)

 

[CarlTR6]

I see in your system event dump file that drivers are failing to load. this is a typical sequence; but different drivers are involved at different times.

Event[14]:
  Log Name: System
  Source: Microsoft-Windows-DistributedCOM
  Date: 2011-04-24T02:04:00.000
  Event ID: 10005
  Task: N/A
  Level: Error
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: Rich-PC
  Description: 
DCOM got error "1084" attempting to start the service ShellHWDetection with arguments "" in order to run the server:
{DD522ACC-F821-461A-A407-50B198B896DC}

Event[15]:
  Log Name: System
  Source: Microsoft-Windows-WER-SystemErrorReporting
  Date: 2011-04-24T02:03:57.000
  Event ID: 1001
  Task: N/A
  Level: Error
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: Rich-PC
  Description: 
The computer has rebooted from a bugcheck.  The bugcheck was: 0x0000001e (0xffffffffc0000005, 0xfffff80002d5256d, 0x0000000000000000, 0xffffffffffffffff). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 042411-21309-01.

Event[16]:
  Log Name: System
  Source: Service Control Manager
  Date: 2011-04-24T02:03:57.076
  Event ID: 7026
  Task: N/A
  Level: Error
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: Rich-PC
  Description: 
The following boot-start or system-start driver(s) failed to load: 
AsIO
discache
spldr
Wanarpv6

1. Update this Marvel driver using the link provided:

mv61xx.sys Thu Mar 19 23:48:21 2009 - Marvell Thor Windows Driver. Marvell: Support.

2. as ZigZag suggested, enable Driver Verifier. Follow the instructions in this tutorial: Driver Verifier - Enable and Disable. Upload any and all Driver Verifier enabled dumps.

3. As soon as you are able to boot in the normal mode, upgrade your OS by installing Service Pack 1: http://windows.microsoft.com/en-US/w...ice-pack-1-sp1

Windows 7 Kernel Version 7600 MP (6 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`02a1a000 PsLoadedModuleList = 0xfffff800`02c57e50
Debug session time: Sat Apr 23 20:20:13.941 2011 (GMT-4)
System Uptime: 0 days 0:00:21.252
Loading Kernel Symbols
...............................................................
................................................................
......
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000007E, {ffffffffc0000005, fffff80002d7a684, fffff88007a71358, fffff88007a70bb0}

Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_GLOBAL::DestroyOneAllocation+153 )

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

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: ffffffffc0000005, The exception code that was not handled
Arg2: fffff80002d7a684, The address that the exception occurred at
Arg3: fffff88007a71358, Exception Record Address
Arg4: fffff88007a70bb0, Context Record Address

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


EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

FAULTING_IP: 
nt!MiSectionDelete+24
fffff800`02d7a684 488b18          mov     rbx,qword ptr [rax]

EXCEPTION_RECORD:  fffff88007a71358 -- (.exr 0xfffff88007a71358)
ExceptionAddress: fffff80002d7a684 (nt!MiSectionDelete+0x0000000000000024)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000000
   Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff

CONTEXT:  fffff88007a70bb0 -- (.cxr 0xfffff88007a70bb0)
rax=ffeff8a000bdd940 rbx=0000000000000000 rcx=fffff8a0015ea5b0
rdx=00000000001d4a08 rsi=0000000000000001 rdi=fffff8a0015ea580
rip=fffff80002d7a684 rsp=fffff88007a71590 rbp=0000000000000000
 r8=0000000000000080  r9=fffff880009ea180 r10=0000000000002c01
r11=0000000000000000 r12=0000000000000001 r13=0000000000000001
r14=00000000ffffffff r15=0000000000000004
iopl=0         nv up ei ng nz na po nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010286
nt!MiSectionDelete+0x24:
fffff800`02d7a684 488b18          mov     rbx,qword ptr [rax] ds:002b:ffeff8a0`00bdd940=????????????????
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  csrss.exe

CURRENT_IRQL:  0

ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

EXCEPTION_PARAMETER1:  0000000000000000

EXCEPTION_PARAMETER2:  ffffffffffffffff

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002cc20e0
 ffffffffffffffff 

FOLLOWUP_IP: 
dxgmms1!VIDMM_GLOBAL::DestroyOneAllocation+153
fffff880`04320b2b 488b058665ffff  mov     rax,qword ptr [dxgmms1!_imp_g_loggerInfo (fffff880`043170b8)]

BUGCHECK_STR:  0x7E

LAST_CONTROL_TRANSFER:  from fffff80002a910b4 to fffff80002d7a684

STACK_TEXT:  
fffff880`07a71590 fffff800`02a910b4 : 00000000`00000000 00000000`00000000 fffffa80`06d2e790 00000000`00000001 : nt!MiSectionDelete+0x24
fffff880`07a715d0 fffff880`04320b2b : 00000000`00000000 fffff8a0`00e138b0 fffff8a0`015ef000 00000000`00000000 : nt!ObfDereferenceObject+0xd4
fffff880`07a71630 fffff880`0432f7b7 : 00000000`00000001 fffffa80`08cb9b10 00000000`00000000 00000000`00000174 : dxgmms1!VIDMM_GLOBAL::DestroyOneAllocation+0x153
fffff880`07a71710 fffff880`0430924b : fffffa80`08cb0820 00000000`00000004 fffffa80`08cb0820 fffff800`02bbf45c : dxgmms1!VIDMM_DMA_POOL::RemoveDmaBufferFromPool+0x117
fffff880`07a71760 fffff880`043091d3 : fffff8a0`015ac710 fffff8a0`015ef058 00000000`00000000 00000000`00000001 : dxgmms1!VIDMM_DMA_POOL::`scalar deleting destructor'+0x6b
fffff880`07a71790 fffff880`0425b3ed : 00000000`00000000 fffff8a0`015ac710 00000000`000007ff fffff8a0`015ef058 : dxgmms1!VidMmDestoryDmaPool+0x13
fffff880`07a717c0 fffff880`0425cd12 : fffff8a0`4b677844 fffff8a0`015ef000 00000000`00000001 00000000`00000000 : dxgkrnl!DXGCONTEXT::Destroy+0x16d
fffff880`07a71840 fffff880`0425c67e : fffff8a0`015ef000 fffff8a0`015ef068 00000000`00000000 fffff8a0`015ef068 : dxgkrnl!DXGDEVICE::Destroy+0x66
fffff880`07a71880 fffff880`04241815 : 00000000`fffffeda fffff8a0`00f04100 00000000`00000002 fffffa80`07f70000 : dxgkrnl!DXGDEVICE::~DXGDEVICE+0x1aa
fffff880`07a718f0 fffff880`04253f45 : 00000000`00000000 fffffa80`07f70000 00000000`40000000 fffff8a0`015ef000 : dxgkrnl!DXGADAPTER::DestroyDevice+0x1c9
fffff880`07a71920 fffff960`006396f9 : fffff900`c00c0020 fffff900`c00c0020 00000000`00000002 00000000`00000006 : dxgkrnl!DxgkCddDestroy+0x125
fffff880`07a71980 fffff960`00635e07 : ffffffff`fffffc4c ffffffff`fffd74f6 00000000`00000002 00000000`00000006 : cdd!CDDPDEV::DestroyDevice+0x75
fffff880`07a719b0 fffff800`02d2f166 : 00000000`03abf2c7 fffffa80`08cbab60 00000000`00000080 fffffa80`08c68b30 : cdd!PresentWorkerThread+0xa9b
fffff880`07a71d40 fffff800`02a6a486 : fffff880`03088180 fffffa80`08cbab60 fffff880`03093040 000002d0`00000007 : nt!PspSystemThreadStartup+0x5a
fffff880`07a71d80 00000000`00000000 : fffff880`07a72000 fffff880`07a6c000 fffff880`07a71170 00000000`00000000 : nt!KxStartSystemThread+0x16


SYMBOL_STACK_INDEX:  2

SYMBOL_NAME:  dxgmms1!VIDMM_GLOBAL::DestroyOneAllocation+153

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: dxgmms1

IMAGE_NAME:  dxgmms1.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bc578

STACK_COMMAND:  .cxr 0xfffff88007a70bb0 ; kb

FAILURE_BUCKET_ID:  X64_0x7E_dxgmms1!VIDMM_GLOBAL::DestroyOneAllocation+153

BUCKET_ID:  X64_0x7E_dxgmms1!VIDMM_GLOBAL::DestroyOneAllocation+153

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

Debug session time: Sat Apr 23 23:06:09.692 2011 (GMT-4)
System Uptime: 0 days 2:45:23.003
Loading Kernel Symbols
...............................................................
................................................................
...............
Loading User Symbols
Loading unloaded module list
..........
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1E, {0, 0, 0, 0}

Probably caused by : ataport.SYS ( ataport!IdeCompleteScsiIrp+62 )

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

5: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

KMODE_EXCEPTION_NOT_HANDLED (1e)
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.
Arguments:
Arg1: 0000000000000000, The exception code that was not handled
Arg2: 0000000000000000, The address that the exception occurred at
Arg3: 0000000000000000, Parameter 0 of the exception
Arg4: 0000000000000000, Parameter 1 of the exception

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


EXCEPTION_CODE: (Win32) 0 (0) - The operation completed successfully.

FAULTING_IP: 
+5fc0952f01bfdb50
00000000`00000000 ??              ???

EXCEPTION_PARAMETER1:  0000000000000000

EXCEPTION_PARAMETER2:  0000000000000000

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x1E

PROCESS_NAME:  System

CURRENT_IRQL:  2

EXCEPTION_RECORD:  fffff880030b05d8 -- (.exr 0xfffff880030b05d8)
ExceptionAddress: fffff88000e10d8c (Wdf01000!FxIoTarget::_RequestCompletionRoutine+0x0000000000000004)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000000
   Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff

TRAP_FRAME:  fffff880030b0680 -- (.trap 0xfffff880030b0680)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffff880030b0868 rbx=0000000000000000 rcx=0000000000000000
rdx=fffffa8008937460 rsi=0000000000000000 rdi=0000000000000000
rip=fffff88000e10d8c rsp=fffff880030b0810 rbp=fffffa8008937460
 r8=ffeffa8008937670  r9=fffffa8007b451b0 r10=000000171a9231b2
r11=fffff880030b0948 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na pe nc
Wdf01000!FxIoTarget::_RequestCompletionRoutine+0x4:
fffff880`00e10d8c 498b8890000000  mov     rcx,qword ptr [r8+90h] ds:dd20:ffeffa80`08937700=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002ab3c2e to fffff80002abbed0

STACK_TEXT:  
fffff880`030af6b8 fffff800`02ab3c2e : 00000000`00000000 00000000`00000000 fffff880`030afe30 fffff800`02ae8e28 : nt!KeBugCheck
fffff880`030af6c0 fffff800`02ae1bed : fffff800`02cc8c24 fffff800`02c01a3c fffff800`02a4a000 fffff880`030b05d8 : nt!KiKernelCalloutExceptionHandler+0xe
fffff880`030af6f0 fffff800`02ae9250 : fffff800`02c09b5c fffff880`030af768 fffff880`030b05d8 fffff800`02a4a000 : nt!RtlpExecuteHandlerForException+0xd
fffff880`030af720 fffff800`02af61b5 : fffff880`030b05d8 fffff880`030afe30 fffff880`00000000 fffffa80`074170d0 : nt!RtlDispatchException+0x410
fffff880`030afe00 fffff800`02abb542 : fffff880`030b05d8 00000000`00000000 fffff880`030b0680 fffffa80`0826e460 : nt!KiDispatchException+0x135
fffff880`030b04a0 fffff800`02ab9e4a : 00000000`00000001 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiExceptionDispatch+0xc2
fffff880`030b0680 fffff880`00e10d8c : 00000000`00000000 fffffa80`075c35c0 fffffa80`0826e460 fffffa80`08937460 : nt!KiGeneralProtectionFault+0x10a
fffff880`030b0810 fffff800`02aa6935 : fffff880`02f64180 fffffa80`06d3ab60 fffffa80`73556f49 fffffa80`093cec80 : Wdf01000!FxIoTarget::_RequestCompletionRoutine+0x4
fffff880`030b0840 fffff800`02abe516 : fffffa80`0893757b 00000000`00000000 00000000`00000000 fffffa80`08937460 : nt!IopUnloadSafeCompletion+0x55
fffff880`030b0870 fffff880`00c0941a : fffffa80`07b266a8 00000000`00000001 fffffa80`07b67010 00000000`00000000 : nt!IopfCompleteRequest+0x3a6
fffff880`030b0950 fffff880`00c09242 : fffffa80`07b67010 fffffa80`093d5f10 fffffa80`075d5400 fffff800`02bef2dd : ataport!IdeCompleteScsiIrp+0x62
fffff880`030b0980 fffff880`00c03e32 : 00000000`00000000 00000000`00000000 fffffa80`0826ae00 fffffa80`082b5501 : ataport!IdeCommonCrbCompletion+0x5a
fffff880`030b09b0 fffff880`00c0c7ed : fffffa80`07b251a0 fffffa80`07b67010 00000000`00000000 fffffa80`07b67010 : ataport!IdeTranslateCompletedRequest+0x236
fffff880`030b0ae0 fffff880`00c0c0ec : fffffa80`07b251a0 00000000`00000000 fffffa80`07b251a0 00000000`00000000 : ataport!IdeProcessCompletedRequests+0x4d5
fffff880`030b0c10 fffff800`02ac75dc : fffff880`03088180 00000006`c4e2a674 fffffa80`07b25050 fffffa80`07b25118 : ataport!IdePortCompletionDpc+0x1a8
fffff880`030b0cd0 fffff800`02ac46fa : fffff880`03088180 fffff880`03093040 00000000`00000000 fffff880`00c0bf44 : nt!KiRetireDpcList+0x1bc
fffff880`030b0d80 00000000`00000000 : fffff880`030b1000 fffff880`030ab000 fffff880`030b0d40 00000000`00000000 : nt!KiIdleLoop+0x5a


STACK_COMMAND:  kb

FOLLOWUP_IP: 
ataport!IdeCompleteScsiIrp+62
fffff880`00c0941a 8bc3            mov     eax,ebx

SYMBOL_STACK_INDEX:  a

SYMBOL_NAME:  ataport!IdeCompleteScsiIrp+62

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: ataport

IMAGE_NAME:  ataport.SYS

DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bc118

FAILURE_BUCKET_ID:  X64_0x1E_ataport!IdeCompleteScsiIrp+62

BUCKET_ID:  X64_0x1E_ataport!IdeCompleteScsiIrp+62

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

Kernel base = 0xfffff800`02a07000 PsLoadedModuleList = 0xfffff800`02c44e50
Debug session time: Sun Apr 24 07:59:42.358 2011 (GMT-4)
System Uptime: 0 days 0:01:00.669
Loading Kernel Symbols
...............................................................
................................................................
.................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1E, {ffffffffc0000005, fffff80002d5256d, 0, ffffffffffffffff}

Probably caused by : ntkrnlmp.exe ( nt!CmpKcbCacheLookup+1dd )

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

0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

KMODE_EXCEPTION_NOT_HANDLED (1e)
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.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff80002d5256d, The address that the exception occurred at
Arg3: 0000000000000000, Parameter 0 of the exception
Arg4: ffffffffffffffff, Parameter 1 of the exception

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


EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

FAULTING_IP: 
nt!CmpKcbCacheLookup+1dd
fffff800`02d5256d 418b45f4        mov     eax,dword ptr [r13-0Ch]

EXCEPTION_PARAMETER1:  0000000000000000

EXCEPTION_PARAMETER2:  ffffffffffffffff

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002caf0e0
 ffffffffffffffff 

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x1E

PROCESS_NAME:  svchost.exe

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from fffff80002ab8a17 to fffff80002a78f00

STACK_TEXT:  
fffff880`024ed268 fffff800`02ab8a17 : 00000000`0000001e ffffffff`c0000005 fffff800`02d5256d 00000000`00000000 : nt!KeBugCheckEx
fffff880`024ed270 fffff800`02a78542 : fffff880`024eda48 00000000`00000000 fffff880`024edaf0 fffff8a0`00023608 : nt! ?? ::FNODOBFM::`string'+0x460da
fffff880`024ed910 fffff800`02a76e4a : 00000000`00000001 fffff8a0`00000000 00000000`00000000 00000000`00000801 : nt!KiExceptionDispatch+0xc2
fffff880`024edaf0 fffff800`02d5256d : fffff880`024ee130 fffff880`024ee0d8 fffff880`024ee0f4 fffff880`024ee122 : nt!KiGeneralProtectionFault+0x10a
fffff880`024edc80 fffff800`02d51b28 : fffff880`024ede00 fffff880`00000001 fffff880`024ee208 fffff880`024ee220 : nt!CmpKcbCacheLookup+0x1dd
fffff880`024edd70 fffff800`02d4fd81 : fffff8a0`01a485d0 fffff880`024ee220 fffff880`024ee258 fffff880`024ee240 : nt!CmpBuildHashStackAndLookupCache+0x328
fffff880`024ee150 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!CmpParseKey+0x2a1


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!CmpKcbCacheLookup+1dd
fffff800`02d5256d 418b45f4        mov     eax,dword ptr [r13-0Ch]

SYMBOL_STACK_INDEX:  4

SYMBOL_NAME:  nt!CmpKcbCacheLookup+1dd

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bc600

FAILURE_BUCKET_ID:  X64_0x1E_nt!CmpKcbCacheLookup+1dd

BUCKET_ID:  X64_0x1E_nt!CmpKcbCacheLookup+1dd

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

0: kd> lmtsmn
start             end                 module name
fffff880`041aa000 fffff880`041e8000   1394ohci 1394ohci.sys Mon Jul 13 20:07:12 2009 (4A5BCC30)
fffff880`00e50000 fffff880`00ea7000   ACPI     ACPI.sys     Mon Jul 13 19:19:34 2009 (4A5BC106)
fffff880`02ccd000 fffff880`02d57000   afd      afd.sys      Mon Jul 13 19:21:40 2009 (4A5BC184)
fffff880`00fe4000 fffff880`00ffa000   AgileVpn AgileVpn.sys Mon Jul 13 20:10:24 2009 (4A5BCCF0)
fffff880`045db000 fffff880`045ef000   amdiox64 amdiox64.sys Thu Feb 18 10:17:53 2010 (4B7D5A21)
fffff880`01873000 fffff880`01888000   amdppm   amdppm.sys   Mon Jul 13 19:19:25 2009 (4A5BC0FD)
fffff880`01035000 fffff880`01040000   amdxata  amdxata.sys  Tue May 19 13:56:59 2009 (4A12F2EB)
fffff880`051f6000 fffff880`051fe000   ASACPI   ASACPI.sys   Wed Jul 15 23:31:29 2009 (4A5E9F11)
fffff880`02cc4000 fffff880`02cca000   AsIO     AsIO.sys     Mon Aug 03 03:03:16 2009 (4A768BB4)
fffff880`00fb1000 fffff880`00fba000   atapi    atapi.sys    Mon Jul 13 19:19:47 2009 (4A5BC113)
fffff880`00fba000 fffff880`00fe4000   ataport  ataport.SYS  Mon Jul 13 19:19:52 2009 (4A5BC118)
fffff880`04481000 fffff880`044a1000   AtihdW76 AtihdW76.sys Wed Nov 17 07:02:04 2010 (4CE3C43C)
fffff880`04878000 fffff880`0519f000   atikmdag atikmdag.sys Tue Mar 08 23:32:17 2011 (4D7702D1)
fffff880`04067000 fffff880`040b6000   atikmpag atikmpag.sys Tue Mar 08 23:17:42 2011 (4D76FF66)
fffff880`01986000 fffff880`0198d000   Beep     Beep.SYS     Mon Jul 13 20:00:13 2009 (4A5BCA8D)
fffff880`0183c000 fffff880`0184d000   blbdrive blbdrive.sys Mon Jul 13 19:35:59 2009 (4A5BC4DF)
fffff880`02789000 fffff880`027a7000   bowser   bowser.sys   Mon Jul 13 19:23:50 2009 (4A5BC206)
fffff960`00690000 fffff960`006b7000   cdd      cdd.dll      unavailable (00000000)
fffff880`01953000 fffff880`0197d000   cdrom    cdrom.sys    Mon Jul 13 19:19:54 2009 (4A5BC11A)
fffff880`00d3f000 fffff880`00dff000   CI       CI.dll       Mon Jul 13 21:32:13 2009 (4A5BE01D)
fffff880`018ed000 fffff880`0191d000   CLASSPNP CLASSPNP.SYS Mon Jul 13 19:19:58 2009 (4A5BC11E)
fffff880`00ce1000 fffff880`00d3f000   CLFS     CLFS.SYS     Mon Jul 13 19:19:57 2009 (4A5BC11D)
fffff880`010fe000 fffff880`01171000   cng      cng.sys      Mon Jul 13 19:49:40 2009 (4A5BC814)
fffff880`041e8000 fffff880`041f8000   CompositeBus CompositeBus.sys Mon Jul 13 20:00:33 2009 (4A5BCAA1)
fffff880`0660c000 fffff880`0661a000   crashdmp crashdmp.sys Mon Jul 13 20:01:01 2009 (4A5BCABD)
fffff880`02ca6000 fffff880`02cc4000   dfsc     dfsc.sys     Mon Jul 13 19:23:44 2009 (4A5BC200)
fffff880`02c97000 fffff880`02ca6000   discache discache.sys Mon Jul 13 19:37:18 2009 (4A5BC52E)
fffff880`018d7000 fffff880`018ed000   disk     disk.sys     Mon Jul 13 19:19:57 2009 (4A5BC11D)
fffff880`064d6000 fffff880`064f8000   drmk     drmk.sys     Mon Jul 13 21:01:25 2009 (4A5BD8E5)
fffff880`06626000 fffff880`0662f000   dump_atapi dump_atapi.sys Mon Jul 13 19:19:47 2009 (4A5BC113)
fffff880`0661a000 fffff880`06626000   dump_dumpata dump_dumpata.sys Mon Jul 13 19:19:47 2009 (4A5BC113)
fffff880`0662f000 fffff880`06642000   dump_dumpfve dump_dumpfve.sys Mon Jul 13 19:21:51 2009 (4A5BC18F)
fffff880`06600000 fffff880`0660c000   Dxapi    Dxapi.sys    Mon Jul 13 19:38:28 2009 (4A5BC574)
fffff880`040b6000 fffff880`041aa000   dxgkrnl  dxgkrnl.sys  Mon Jul 13 19:38:56 2009 (4A5BC590)
fffff880`0519f000 fffff880`051e5000   dxgmms1  dxgmms1.sys  Mon Jul 13 19:38:32 2009 (4A5BC578)
fffff880`02ba7000 fffff880`02bdd000   fastfat  fastfat.SYS  Mon Jul 13 19:23:28 2009 (4A5BC1F0)
fffff880`0108c000 fffff880`010a0000   fileinfo fileinfo.sys Mon Jul 13 19:34:25 2009 (4A5BC481)
fffff880`01040000 fffff880`0108c000   fltmgr   fltmgr.sys   Mon Jul 13 19:19:59 2009 (4A5BC11F)
fffff880`013e1000 fffff880`013eb000   Fs_Rec   Fs_Rec.sys   Mon Jul 13 19:19:45 2009 (4A5BC111)
fffff880`0189d000 fffff880`018d7000   fvevol   fvevol.sys   Mon Jul 13 19:22:15 2009 (4A5BC1A7)
fffff880`0158b000 fffff880`015d5000   fwpkclnt fwpkclnt.sys Mon Jul 13 19:21:08 2009 (4A5BC164)
fffff800`02fe4000 fffff800`0302d000   hal      hal.dll      Mon Jul 13 21:27:36 2009 (4A5BDF08)
fffff880`04800000 fffff880`04824000   HDAudBus HDAudBus.sys Mon Jul 13 20:06:13 2009 (4A5BCBF5)
fffff880`06529000 fffff880`06542000   HIDCLASS HIDCLASS.SYS Mon Jul 13 20:06:21 2009 (4A5BCBFD)
fffff880`06542000 fffff880`0654a080   HIDPARSE HIDPARSE.SYS Mon Jul 13 20:06:17 2009 (4A5BCBF9)
fffff880`0651b000 fffff880`06529000   hidusb   hidusb.sys   Mon Jul 13 20:06:22 2009 (4A5BCBFE)
fffff880`026c1000 fffff880`02789000   HTTP     HTTP.sys     Mon Jul 13 19:22:16 2009 (4A5BC1A8)
fffff880`015ef000 fffff880`015f8000   hwpolicy hwpolicy.sys Mon Jul 13 19:19:22 2009 (4A5BC0FA)
fffff880`04578000 fffff880`04587000   kbdclass kbdclass.sys Mon Jul 13 19:19:50 2009 (4A5BC116)
fffff880`0654b000 fffff880`06559000   kbdhid   kbdhid.sys   Mon Jul 13 20:00:20 2009 (4A5BCA94)
fffff800`00ba0000 fffff800`00baa000   kdcom    kdcom.dll    Mon Jul 13 21:31:07 2009 (4A5BDFDB)
fffff880`04598000 fffff880`045db000   ks       ks.sys       Mon Jul 13 20:00:31 2009 (4A5BCA9F)
fffff880`013b6000 fffff880`013d0000   ksecdd   ksecdd.sys   Mon Jul 13 19:20:54 2009 (4A5BC156)
fffff880`01560000 fffff880`0158b000   ksecpkg  ksecpkg.sys  Mon Jul 13 19:50:34 2009 (4A5BC84A)
fffff880`064f8000 fffff880`064fd200   ksthunk  ksthunk.sys  Mon Jul 13 20:00:19 2009 (4A5BCA93)
fffff880`065b8000 fffff880`065cd000   lltdio   lltdio.sys   Mon Jul 13 20:08:50 2009 (4A5BCC92)
fffff880`06574000 fffff880`06597000   luafv    luafv.sys    Mon Jul 13 19:26:13 2009 (4A5BC295)
fffff880`00cc0000 fffff880`00ccd000   mcupdate_AuthenticAMD mcupdate_AuthenticAMD.dll Mon Jul 13 21:29:09 2009 (4A5BDF65)
fffff880`06566000 fffff880`06574000   monitor  monitor.sys  Mon Jul 13 19:38:52 2009 (4A5BC58C)
fffff880`04587000 fffff880`04596000   mouclass mouclass.sys Mon Jul 13 19:19:50 2009 (4A5BC116)
fffff880`06559000 fffff880`06566000   mouhid   mouhid.sys   Mon Jul 13 20:00:20 2009 (4A5BCA94)
fffff880`00f97000 fffff880`00fb1000   mountmgr mountmgr.sys Mon Jul 13 19:19:54 2009 (4A5BC11A)
fffff880`027a7000 fffff880`027bf000   mpsdrv   mpsdrv.sys   Mon Jul 13 20:08:25 2009 (4A5BCC79)
fffff880`027bf000 fffff880`027eb000   mrxsmb   mrxsmb.sys   Mon Jul 13 19:23:59 2009 (4A5BC20F)
fffff880`02600000 fffff880`0264d000   mrxsmb10 mrxsmb10.sys Mon Jul 13 19:24:08 2009 (4A5BC218)
fffff880`0264d000 fffff880`02670000   mrxsmb20 mrxsmb20.sys Mon Jul 13 19:24:05 2009 (4A5BC215)
fffff880`019eb000 fffff880`019f6000   Msfs     Msfs.SYS     Mon Jul 13 19:19:47 2009 (4A5BC113)
fffff880`00eb0000 fffff880`00eba000   msisadrv msisadrv.sys Mon Jul 13 19:19:26 2009 (4A5BC0FE)
fffff880`010a0000 fffff880`010fe000   msrpc    msrpc.sys    Mon Jul 13 19:21:32 2009 (4A5BC17C)
fffff880`02c8c000 fffff880`02c97000   mssmbios mssmbios.sys Mon Jul 13 19:31:10 2009 (4A5BC3BE)
fffff880`015dd000 fffff880`015ef000   mup      mup.sys      Mon Jul 13 19:23:45 2009 (4A5BC201)
fffff880`00e00000 fffff880`00e46000   mv61xx   mv61xx.sys   Thu Mar 19 23:48:21 2009 (49C31205)
fffff880`0140e000 fffff880`01500000   ndis     ndis.sys     Mon Jul 13 19:21:40 2009 (4A5BC184)
fffff880`044e7000 fffff880`044f3000   ndistapi ndistapi.sys Mon Jul 13 20:10:00 2009 (4A5BCCD8)
fffff880`044f3000 fffff880`04522000   ndiswan  ndiswan.sys  Mon Jul 13 20:10:11 2009 (4A5BCCE3)
fffff880`0446c000 fffff880`04481000   NDProxy  NDProxy.SYS  Mon Jul 13 20:10:05 2009 (4A5BCCDD)
fffff880`02dcb000 fffff880`02dda000   netbios  netbios.sys  Mon Jul 13 20:09:26 2009 (4A5BCCB6)
fffff880`02d57000 fffff880`02d9c000   netbt    netbt.sys    Mon Jul 13 19:21:28 2009 (4A5BC178)
fffff880`01500000 fffff880`01560000   NETIO    NETIO.SYS    Mon Jul 13 19:21:46 2009 (4A5BC18A)
fffff880`01800000 fffff880`01811000   Npfs     Npfs.SYS     Mon Jul 13 19:19:48 2009 (4A5BC114)
fffff880`02c80000 fffff880`02c8c000   nsiproxy nsiproxy.sys Mon Jul 13 19:21:02 2009 (4A5BC15E)
fffff800`02a07000 fffff800`02fe4000   nt       ntkrnlmp.exe Mon Jul 13 19:40:48 2009 (4A5BC600)
fffff880`01213000 fffff880`013b6000   Ntfs     Ntfs.sys     Mon Jul 13 19:20:47 2009 (4A5BC14F)
fffff880`0197d000 fffff880`01986000   Null     Null.SYS     Mon Jul 13 19:19:37 2009 (4A5BC109)
fffff880`02da5000 fffff880`02dcb000   pacer    pacer.sys    Mon Jul 13 20:09:41 2009 (4A5BCCC5)
fffff880`00efa000 fffff880`00f0f000   partmgr  partmgr.sys  Mon Jul 13 19:19:58 2009 (4A5BC11E)
fffff880`00eba000 fffff880`00eed000   pci      pci.sys      Mon Jul 13 19:19:51 2009 (4A5BC117)
fffff880`00f80000 fffff880`00f87000   pciide   pciide.sys   Mon Jul 13 19:19:49 2009 (4A5BC115)
fffff880`00f87000 fffff880`00f97000   PCIIDEX  PCIIDEX.SYS  Mon Jul 13 19:19:48 2009 (4A5BC114)
fffff880`013d0000 fffff880`013e1000   pcw      pcw.sys      Mon Jul 13 19:19:27 2009 (4A5BC0FF)
fffff880`02ab7000 fffff880`02b5d000   peauth   peauth.sys   Mon Jul 13 21:01:19 2009 (4A5BD8DF)
fffff880`06499000 fffff880`064d6000   portcls  portcls.sys  Mon Jul 13 20:06:27 2009 (4A5BCC03)
fffff880`00ccd000 fffff880`00ce1000   PSHED    PSHED.dll    Mon Jul 13 21:32:23 2009 (4A5BE027)
fffff880`044c3000 fffff880`044e7000   rasl2tp  rasl2tp.sys  Mon Jul 13 20:10:11 2009 (4A5BCCE3)
fffff880`04522000 fffff880`0453d000   raspppoe raspppoe.sys Mon Jul 13 20:10:17 2009 (4A5BCCE9)
fffff880`0453d000 fffff880`0455e000   raspptp  raspptp.sys  Mon Jul 13 20:10:18 2009 (4A5BCCEA)
fffff880`0455e000 fffff880`04578000   rassstp  rassstp.sys  Mon Jul 13 20:10:25 2009 (4A5BCCF1)
fffff880`02c2f000 fffff880`02c80000   rdbss    rdbss.sys    Mon Jul 13 19:24:09 2009 (4A5BC219)
fffff880`019d0000 fffff880`019d9000   RDPCDD   RDPCDD.sys   Mon Jul 13 20:16:34 2009 (4A5BCE62)
fffff880`019d9000 fffff880`019e2000   rdpencdd rdpencdd.sys Mon Jul 13 20:16:34 2009 (4A5BCE62)
fffff880`019e2000 fffff880`019eb000   rdprefmp rdprefmp.sys Mon Jul 13 20:16:35 2009 (4A5BCE63)
fffff880`011bd000 fffff880`011f7000   rdyboost rdyboost.sys Mon Jul 13 19:34:34 2009 (4A5BC48A)
fffff880`065cd000 fffff880`065e5000   rspndr   rspndr.sys   Mon Jul 13 20:08:50 2009 (4A5BCC92)
fffff880`04824000 fffff880`04863000   Rt64win7 Rt64win7.sys Thu Aug 20 12:05:06 2009 (4A8D7432)
fffff880`01006000 fffff880`01035000   SCSIPORT SCSIPORT.SYS Mon Jul 13 20:01:04 2009 (4A5BCAC0)
fffff880`02b5d000 fffff880`02b68000   secdrv   secdrv.SYS   Wed Sep 13 09:18:38 2006 (4508052E)
fffff880`04056000 fffff880`04062000   serenum  serenum.sys  Mon Jul 13 20:00:33 2009 (4A5BCAA1)
fffff880`02dda000 fffff880`02df7000   serial   serial.sys   Mon Jul 13 20:00:40 2009 (4A5BCAA8)
fffff880`015d5000 fffff880`015dd000   spldr    spldr.sys    Mon May 11 12:56:27 2009 (4A0858BB)
fffff880`06400000 fffff880`06498000   srv      srv.sys      Mon Jul 13 19:25:11 2009 (4A5BC257)
fffff880`02a00000 fffff880`02a69000   srv2     srv2.sys     Mon Jul 13 19:25:02 2009 (4A5BC24E)
fffff880`02b68000 fffff880`02b95000   srvnet   srvnet.sys   Mon Jul 13 19:24:58 2009 (4A5BC24A)
fffff880`04596000 fffff880`04597480   swenum   swenum.sys   Mon Jul 13 20:00:18 2009 (4A5BCA92)
fffff880`01602000 fffff880`017ff000   tcpip    tcpip.sys    Mon Jul 13 19:25:34 2009 (4A5BC26E)
fffff880`02b95000 fffff880`02ba7000   tcpipreg tcpipreg.sys Mon Jul 13 20:09:49 2009 (4A5BCCCD)
fffff880`0182f000 fffff880`0183c000   TDI      TDI.SYS      Mon Jul 13 19:21:18 2009 (4A5BC16E)
fffff880`01811000 fffff880`0182f000   tdx      tdx.sys      Mon Jul 13 19:21:15 2009 (4A5BC16B)
fffff880`02c1b000 fffff880`02c2f000   termdd   termdd.sys   Mon Jul 13 20:16:36 2009 (4A5BCE64)
fffff960`00490000 fffff960`0049a000   TSDDD    TSDDD.dll    Mon Jul 13 20:16:34 2009 (4A5BCE62)
fffff880`0184d000 fffff880`01873000   tunnel   tunnel.sys   Mon Jul 13 20:09:37 2009 (4A5BCCC1)
fffff880`04400000 fffff880`04412000   umbus    umbus.sys    Mon Jul 13 20:06:56 2009 (4A5BCC20)
fffff880`064fe000 fffff880`0651b000   usbccgp  usbccgp.sys  Mon Jul 13 20:06:45 2009 (4A5BCC15)
fffff880`06642000 fffff880`06643f00   USBD     USBD.SYS     Mon Jul 13 20:06:23 2009 (4A5BCBFF)
fffff880`051e5000 fffff880`051f6000   usbehci  usbehci.sys  Mon Jul 13 20:06:30 2009 (4A5BCC06)
fffff880`04412000 fffff880`0446c000   usbhub   usbhub.sys   Mon Jul 13 20:07:09 2009 (4A5BCC2D)
fffff880`04863000 fffff880`0486e000   usbohci  usbohci.sys  Mon Jul 13 20:06:30 2009 (4A5BCC06)
fffff880`04000000 fffff880`04056000   USBPORT  USBPORT.SYS  Mon Jul 13 20:06:31 2009 (4A5BCC07)
fffff880`02a69000 fffff880`02a84000   USBSTOR  USBSTOR.SYS  Mon Jul 13 20:06:34 2009 (4A5BCC0A)
fffff880`00eed000 fffff880`00efa000   vdrvroot vdrvroot.sys Mon Jul 13 20:01:31 2009 (4A5BCADB)
fffff880`0198d000 fffff880`0199b000   vga      vga.sys      Mon Jul 13 19:38:47 2009 (4A5BC587)
fffff880`06646000 fffff880`067fd000   viahduaa viahduaa.sys Sat May 15 06:22:39 2010 (4BEE75EF)
fffff880`0199b000 fffff880`019c0000   VIDEOPRT VIDEOPRT.SYS Mon Jul 13 19:38:51 2009 (4A5BC58B)
fffff880`00f0f000 fffff880`00f24000   volmgr   volmgr.sys   Mon Jul 13 19:19:57 2009 (4A5BC11D)
fffff880`00f24000 fffff880`00f80000   volmgrx  volmgrx.sys  Mon Jul 13 19:20:33 2009 (4A5BC141)
fffff880`01171000 fffff880`011bd000   volsnap  volsnap.sys  Mon Jul 13 19:20:08 2009 (4A5BC128)
fffff880`02c00000 fffff880`02c1b000   wanarp   wanarp.sys   Mon Jul 13 20:10:21 2009 (4A5BCCED)
fffff880`019c0000 fffff880`019d0000   watchdog watchdog.sys Mon Jul 13 19:37:35 2009 (4A5BC53F)
fffff880`00c00000 fffff880`00ca4000   Wdf01000 Wdf01000.sys Mon Jul 13 19:22:07 2009 (4A5BC19F)
fffff880`00ca4000 fffff880`00cb3000   WDFLDR   WDFLDR.SYS   Mon Jul 13 19:19:54 2009 (4A5BC11A)
fffff880`02d9c000 fffff880`02da5000   wfplwf   wfplwf.sys   Mon Jul 13 20:09:26 2009 (4A5BCCB6)
fffff960`000f0000 fffff960`003ff000   win32k   win32k.sys   Mon Jul 13 19:40:16 2009 (4A5BC5E0)
fffff880`0486e000 fffff880`04877000   wmiacpi  wmiacpi.sys  Mon Jul 13 19:31:02 2009 (4A5BC3B6)
fffff880`00ea7000 fffff880`00eb0000   WMILIB   WMILIB.SYS   Mon Jul 13 19:19:51 2009 (4A5BC117)
fffff880`06597000 fffff880`065b8000   WudfPf   WudfPf.sys   Mon Jul 13 20:05:37 2009 (4A5BCBD1)
fffff880`02a84000 fffff880`02ab5000   WUDFRd   WUDFRd.sys   Mon Jul 13 20:06:06 2009 (4A5BCBEE)

Unloaded modules:
fffff880`0191d000 fffff880`0192b000   crashdmp.sys
    Timestamp: unavailable (00000000)
    Checksum:  00000000
fffff880`0192b000 fffff880`01937000   dump_ataport
    Timestamp: unavailable (00000000)
    Checksum:  00000000
fffff880`01937000 fffff880`01940000   dump_atapi.s
    Timestamp: unavailable (00000000)
    Checksum:  00000000
fffff880`01940000 fffff880`01953000   dump_dumpfve
    Timestamp: unavailable (00000000)
    Checksum:  00000000

 

[Dave76]

The below is a known issue that possibly might be causing your problems, actually pretty easy to change the RAM settings for testing purposes and easily changed back if this isn't effecting your system.

This is not a Gigabyte issue, it's an AMD issue.
Read the first link for an explanation of the issue and the second link for comments and user experiences.

There is a known issue with AMD CPUs integrated memory controllers having problems running RAM at 1600 MHz and above.

VERY IMPORTANT INFORMATION REGARDING AMD AM3 CPU's and RAM SPEEDS
Q&A for the topic VERY IMPORTANT INFORMATION REGARDING AMD AM3 CPU's & RAM....

Give it a try and let us know if it helps.

 

[thunderjeep]

Well I started again today excited about the new approaches i could take to trying to resolve my current computer woes. I believe I did what Dave76 suggested with RAM clock speeds. (see attached pics.) And once I was going to boot up into safe mode I was going to do what you said about the drivers CarlTR6. But unfortunately the system will not let me boot up into safe mode. It goes BSOD error code 7e before I can even get in. I figured I should try re-installing windows at this point but it BSOD'ed on me when attempting to load the initial files. So at that point I am worried its a hardware issue (again....) or improper hardware config. If there are another screen shoots of my BIOS that you guys think would help out just let me know and I will go get those. I am running several passed of windows mem. checker right now. Not sure what to do really after that. Man this all sounds really depressing I know, but I just wanted to say thank you to those trying to help me with this train wreak of a build.

 

[thunderjeep]

Well I was able to boot up into safe mode and CarlTR6 I tried updating that marvel driver but I already have the most up to date one. Its a raid driver. I don't have a raid in my system though all normal disks, no data i have is that important. So I disabled that device, I figure if i don't use it and might might be causing a problem might as well turn it off. I did not get it to start up normally with out crashing so i was not able to do driver verifier or patch it to OS service pack 1. I was able to get these dumps though. This might give some clues. Not really sure. I am not seeing any stability change wiht setting my ram clock speed from "AUTO" to "1333mhz" I am pretty sure this is helping somewhere but I think there is just to much else going on to see. I also checked my BIOS and I do indeed have the most current one available from ASUS.

 

[Dave76]

Don't bother with Windows mem checker, it is not very good.
Check this tutorial, there is a link to the free memtest86+ program, D/L it and burn to CD, DVD or put it on a bootable USB flash drive. This is the best RAM testing program available.
RAM - Test with Memtest86+

First, change the 'Enable clock to all DIMMs' to enable.

D/L CPUZ and post a snip of the CPU, Mainboard, Memory, and SPD tabs.

For posting the information , enter 'Snipping tool' in the Start button > Search box, hit enter. Select the area you want to post and save to a convenient place.
How to Post a Screenshot in Seven Forums

Go to the BIOS and tell me what the 'CPU/NB Voltage' and 'DRAM Voltage' are set at.
When you run more than 4GB RAM, four RAM cards or 2GB RAM cards, you will usually need an integrated memory controller voltage bump, which is the 'CPU/NB Voltage' setting in your BIOS. Since you have all of the above, change this voltage from the stock setting of 1.100v to 1.200v.
Run memtest86+ for at least 7 passes with all four RAM cards installed, best to run overnight. If you get any errors you can stop the test.


Another option would be to take out two of the RAM cards for testing purposes and see if that helps, this might let you check for other issues.
The RAM can be adjusted later.

The Marvell controller for RAID will also run non-RAID HDDs.
There should be different connection ports for this controller, if you're not using them then it shouldn't matter.
If you are using them, then you will know it, the HDD won't work anymore.

 

[thunderjeep]

Dave thanks much for your input. I have made the BIOS changes you have suggested, i have got a copy of memtest86+ on a usb drive, and I have some screen shots of cpuz. Had some problems wiht cpuz. I got an error message when starting it up, it looked like it could not find all of the drivers it needed. Makes sence since im in safe mode. And i think because of that most of my cpuz pages looks like the main board page.....blank. But i cant really get the system to boot up in normal mode yet. I will try agian after this post. incase I am wrong about the cpuz thing i have also included a screen shot of the error i get when i try to open the program.

 

[thunderjeep]

Well something wierd just happened guys I was able to boot up into noraml mode. It "feels" delicate, Dont have any real proof for that though. But I was able to fire up cpuz and get those screen caps you wanted. the snipping tool would crash everytime i tried to save from it so i took pics with my phone. I know wrong tool for the job but i dont know how long windows is going to be up before it crahed agian.

 

[Dave76]

For CPUZ try the 1.57 64bit (zip, No Installation) version, it should work in safe mode. This runs without installation on your system.

Have you installed all the motherboard drivers from the Asus site?
Graphics card drivers from AMD? Which version?
Which PSU do you have?

Did you install an Anti-Virus program?
If yes, which one?

Run memtest86+ for at least 7 passes with all four RAM cards installed, best to run overnight. If you get any errors you can stop the test.
This runs standalone from Windows, boot from the USB stick.

Let us know the results.

 

[thunderjeep]

Alright guys I am running a copy of memtest running off a USB drive. When I left for work it completed one pass wiht no errors. I am going to let it run for 24 hours and see the results. I left all 4 sticks of RAM in there. I figure if after 24 hours there are any error I can test the sticks 1 by 1. This made scence to me. Will post my results tommarow.

 

[Dave76]

Good plan.

Let us know the test results.