Crash Dumps, 000005 exceptions, and BSOD's after building comp

[ActivEcks]

Windows 7 Professional x64
Custom Built - My Own OS from Technet My Account
Hardware is mix between 4 months and 2 weeks old.

Basic Info:
*Core i5 2500k Unlocked (but not overclocked)
*Patriot G2 Series 16GB Quad-Channel(4 x 4GB) 240-Pin DDR3 SDRAM DDR3 1600 (PC3 12800) PGQ316G1600ELQK
*Nvidia Geforce 460 GTX
*Intel BOXDP67BGB3 LGA 1155 Intel P67
*Corsair Force Series GT CSSD-F120GBGT-BK 120GB SATA III SSD (have 500GB secondary Samsung SATA Platter drive for storage)

Problem #1:
Im getting BSOD's / Memory Crashes while playing games such as Tribes Ascend and Mass Effect 3.

Problem #2:
My ram was purchased as 1600MHz memory but the motherboard shows it as only 1333MHz and when I tried to set the clock to 1600MHz, windows crashed on boot.

Any and all help would be greatly appreciated.

 

[zigzag3143]

No idea on your mobo support for 1600 ram
These crashes were caused by memory corruption/exception (Cx05) probably a driver.
Please run these two tests to verify your memory and find which driver is causing the problem.

* If you are overclocking anything reset to default before running these tests.
In other words STOP!!!

* If you have a Raid update its Driver.



Memtest.

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

*Boot from the CD, and leave it running for at least 5-7 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.

Any errors are indicative of a memory problem.

If a known good stick fails in a motherboard slot it is probably the slot.

http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html






Driver Verifer

Using Driver Verifier is an iffy proposition.
Most times it'll crash and it'll tell you what the driver is.
But sometimes it'll crash and won't tell you the driver.
Other times it'll crash before you can log in to Windows.
If you can't get to Safe Mode, then you'll have to resort to offline editing of the registry to disable Driver Verifier.

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"
NOTE: You can use Low Resource Simulation if you'd like.
From my limited experimentation it makes the BSOD's come faster.
- 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.

If you are using win 8 add these
- Concurrency Stress Test
- DDI compliance checking

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

Reboot into Windows (after the crash) and turn off Driver Verifier by going back in and selecting "Delete existing settings" on the first page, then locate and zip up the memory dump file and upload it with your next post.


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.

Thanks to JGriff2 & Usasma.

Using Driver Verifier to identify issues with Windows drivers for advanced users

Driver Verifier

Using Driver Verifier (Windows Drivers)

 

[ActivEcks]

I finally got the blue screen with Verifier running. Here is the dump.

 

[ActivEcks]

Also worth noting, i was playing league of legends when this crash happened.

 

[writhziden]

Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [D:\Kingston\BSODDmpFiles\ActivEcks\042112-7971-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17790.amd64fre.win7sp1_gdr.120305-1505
Machine Name:
Kernel base = 0xfffff800`02e66000 PsLoadedModuleList = 0xfffff800`030aa650
Debug session time: Sat Apr 21 02:13:36.802 2012 (UTC - 6:00)
System Uptime: 0 days 6:01:33.082
Loading Kernel Symbols
...............................................................
................................................................
..........................
Loading User Symbols
Loading unloaded module list
..................
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000007E, {ffffffffc0000005, fffff8800418bcf7, fffff88003887568, fffff88003886dc0}

Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForPreparation+2b )

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

0: 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: fffff8800418bcf7, The address that the exception occurred at
Arg3: fffff88003887568, Exception Record Address
Arg4: fffff88003886dc0, 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: 
dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForPreparation+2b
fffff880`0418bcf7 0fba63540d      bt      dword ptr [rbx+54h],0Dh

EXCEPTION_RECORD:  fffff88003887568 -- (.exr 0xfffff88003887568)
ExceptionAddress: fffff8800418bcf7 (dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForPreparation+0x000000000000002b)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000000
   Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff

CONTEXT:  fffff88003886dc0 -- (.cxr 0xfffff88003886dc0)
rax=fffff8a008c0dad0 rbx=a4fff8a009f0ae50 rcx=fffffa800ecf7000
rdx=fffffa800f8f48b0 rsi=fffffa800ecf7000 rdi=fffffa800ecf7000
rip=fffff8800418bcf7 rsp=fffff880038877a0 rbp=fffffa800fd80038
 r8=fffffa800d89d001  r9=0000000000000000 r10=0000000000000000
r11=000000000000004f r12=fffffa800f8f48b0 r13=0000000000000001
r14=0000000000000000 r15=0000000000000001
iopl=0         nv up ei ng nz na po nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010286
dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForPreparation+0x2b:
fffff880`0418bcf7 0fba63540d      bt      dword ptr [rbx+54h],0Dh ds:002b:a4fff8a0`09f0aea4=????????
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  System

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

FOLLOWUP_IP: 
dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForPreparation+2b
fffff880`0418bcf7 0fba63540d      bt      dword ptr [rbx+54h],0Dh

BUGCHECK_STR:  0x7E

LAST_CONTROL_TRANSFER:  from fffff88004188ed3 to fffff8800418bcf7

STACK_TEXT:  
fffff880`038877a0 fffff880`04188ed3 : 00000000`00000000 fffffa80`0fbfb010 00000000`0000004d 00000000`00000000 : dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForPreparation+0x2b
fffff880`038877d0 fffff880`041a365d : 00000000`00000000 fffff8a0`08f194f0 fffffa80`00000000 fffffa80`0d89d010 : dxgmms1!VIDMM_GLOBAL::PrepareDmaBuffer+0x43f
fffff880`038879a0 fffff880`041a3398 : fffff800`00b96080 fffff880`041a2d00 fffffa80`00000000 fffffa80`00000000 : dxgmms1!VidSchiSubmitRenderCommand+0x241
fffff880`03887b90 fffff880`041a2e96 : 00000000`00000000 fffffa80`0ed530b0 00000000`00000080 fffffa80`0df64410 : dxgmms1!VidSchiSubmitQueueCommand+0x50
fffff880`03887bc0 fffff800`0317cfda : 00000000`01cdae3d fffffa80`0eb9ea10 fffffa80`0c71c9e0 fffffa80`0eb9ea10 : dxgmms1!VidSchiWorkerThread+0xd6
fffff880`03887c00 fffff800`02ed39c6 : fffff800`03057e80 fffffa80`0eb9ea10 fffff800`03065cc0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`03887c40 00000000`00000000 : fffff880`03888000 fffff880`03882000 fffff880`03887540 00000000`00000000 : nt!KxStartSystemThread+0x16


SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForPreparation+2b

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: dxgmms1

IMAGE_NAME:  dxgmms1.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4ce799c1

STACK_COMMAND:  .cxr 0xfffff88003886dc0 ; kb

FAILURE_BUCKET_ID:  X64_0x7E_dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForPreparation+2b

BUCKET_ID:  X64_0x7E_dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForPreparation+2b

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

The crash was not Driver Verifier Enabled, but it points to DirectX/graphics card problems.

• You should disable Verifier for the time being: Start Menu -> All Programs -> Accessories -> Right click Command Prompt -> Run as administrator -> Type the following command and then Enter:
  verifier /reset​
  -> Restart your computer.
  
  
• Try re-installing DirectX using the Download: DirectX Redist (June 2010) - Microsoft Download Center - Download Details and see how the system responds.
  
  Follow the steps for Diagnosing basic problems with DirectX. To re-install your display card drivers as outlined in the DirectX link, use the following steps.
  
  1. Download the latest drivers for your display card(s)
  2. Click Start Menu
  3. Click Control Panel
  4. Click Uninstall a program
  5. For NVIDIA:
     • Uninstall the NVIDIA Graphics Driver (this should uninstall all NVIDIA software and drivers)
     • Restart your computer
     • Make sure NVIDIA 3D Vision Driver, NVIDIA 3D Vision Video Player, NVIDIA HD Audio Driver, and NVIDIA PhysX System Software are not still listed under Uninstall a program through Control Panel
     • If any remain of the above, uninstall one at a time
     • If asked to restart after uninstalling any of the above, do so, and continue uninstalling any remaining NVIDIA items until all are removed
  6. For AMD:
     • Uninstall AMD Catalyst Install Manager if it is listed (this should remove all AMD graphics software and drivers)
     • If AMD Catalyst Install Manager is not listed, use the following method to uninstall the graphics drivers:
       1. Click Start Menu
       2. Right Click My Computer/Computer
       3. Click Manage
       4. Click Device Manager from the list on the left
       5. Expand Display adapters
       6. Do the following for each adapter (in case you have multiple display cards)
          • Right click the adapter
          • Click Uninstall (do not click OK in the dialog box that pops up after hitting Uninstall)
          • Put a tick in Delete driver software for this device (if this option is available, otherwise just hit OK) and hit OK
       7. Restart your computer after uninstalling drivers for all display cards
       8. Install the latest driver for the display cards once Windows starts
       
       Alternatively:
       1. Login as an adminstrative user
       2. Click Start Menu
       3. Click Control Panel
       4. Click Hardware and Sound
       5. Click Device Manager (the last link under Devices and Printers)
       6. Expand Display adapters
       7. Do the following for each adapter (in case you have multiple display cards)
          • Right click the adapter
          • Click Uninstall (do not click OK in the dialog box that pops up after hitting Uninstall)
          • Put a tick in Delete driver software for this device (if this option is available, otherwise just hit OK) and hit OK
  7. Restart your computer after uninstalling drivers for all display cards
  8. Install the latest driver for the display cards once Windows starts