BSODs with multiple reasons

Hello, Dougyboy and welcome to seven forums. I will try to help with your problem. First I'd like you to fill out your system specs in as much detail as possible. Sometimes we need to look up a component and need the Manufacturer and model to do that. Also include your PSU and CPU cooling if possible and put them under the system specs you see in the bottom left of every post. These are the instructions I usually give, maybe they will help you.

Please fill out your System Specs

   Information

Your System Specs will help us to help you, and doing it in this manner will make them available to all helpers in every post and keep us from hunting for them. We ask that you fill them out in as much detail as possible including Desktop or Laptop, Model number if it is an OEM computer and all components with the Manufacturer and Model number if possible.

If you will go to your last post and click the 'System Specs' in the bottom left of the post, you will find a link to update your system specs. Please fill those out in as much detail as possible, making sure to click save at the bottom of the page. If you would like to know what we would like, you can click 'My System Specs' at the bottom left of this post to see mine. If you do not know what your components are, this will help you accomplish this task. System Info - See Your System Specs

Next I would like you to check and make sure your Firmware on your SSD is up to date.

The only things listed in your dump files were your graphics card.

Code:

 dxgmms1
start             end                 module name
fffff880`04756000 fffff880`0479c000   dxgmms1    (pdb symbols)          c:\symcache\dxgmms1.pdb\93AB163000A844D5BF442A979FB6FF991\dxgmms1.pdb
    Loaded symbol image file: dxgmms1.sys
    Mapped memory image file: c:\symcache\dxgmms1.sys\5164DC1346000\dxgmms1.sys
    Image path: \SystemRoot\System32\drivers\dxgmms1.sys
    Image name: dxgmms1.sys
    Timestamp:        Tue Apr 09 22:27:15 2013 (5164DC13)
    CheckSum:         00043C9B
    ImageSize:        00046000
    File version:     6.1.7601.18126
    Product version:  6.1.7601.18126
    File flags:       0 (Mask 3F)
    File OS:          40004 NT Win32
    File type:        3.7 Driver
    File date:        00000000.00000000
    Translations:     0409.04b0
    CompanyName:      Microsoft Corporation
    ProductName:      Microsoft® Windows® Operating System
    InternalName:     dxgmms1.sys
    OriginalFilename: dxgmms1.sys
    ProductVersion:   6.1.7601.18126
    FileVersion:      6.1.7601.18126 (win7sp1_gdr.130409-1534)
    FileDescription:  DirectX Graphics MMS
    LegalCopyright:   © Microsoft Corporation. All rights reserved

That is your DirectX delivered by Windows Update, Please make sure your updates are current. You can also either update your Direct X or make sure you have the latest version here How to install the latest version of DirectX I really believe this was a victim of the BSOD and not the cause, but making sure won't hurt.

The one mentioned in 2 of the dumps was

Code:

nvlddmkm
start             end                 module name
fffff880`0f2bd000 fffff880`0ff99000   nvlddmkm T (no symbols)           
    Loaded symbol image file: nvlddmkm.sys
    Image path: \SystemRoot\system32\DRIVERS\nvlddmkm.sys
    Image name: nvlddmkm.sys
    Timestamp:        Thu Oct 16 07:31:28 2014 (543FBAA0)
    CheckSum:         00C97F5B
    ImageSize:        00CDC000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

I would like you to update your driver. I believe you have the latest version, so you may be better off using an earlier version or if you want, you can reinstall that same one, but update it in this manner and see if it helps. NVIDIA Drivers - Avoid Problems

Try those and get back with us and let us know if you see any improvement. If you have another BSOD please upload the Blue Screen of Death (BSOD) Posting Instructions again in a new post.

The dump file is saying the same as the first one. But as you said, it says

Code:

VIDEO_MEMORY_MANAGEMENT_INTERNAL (10e)
The video memory manager encountered a condition that it can't recover from. By crashing,
the video memory manager is attempting to get enough information into the minidump such that
somebody can pinpoint what lead to this condition.
Arguments:
Arg1: 000000000000001f, The subtype of the bugcheck:
Arg2: fffff8a00ad75010
Arg3: 0000000000000000
Arg4: 00000000000ce974

You may try this test and see. http://www.majorgeeks.com/files/deta...ress_test.html

Dougyboy, The dump file is showing the same thing, just a different code number

Code:

nvlddmkm
start             end                 module name
fffff880`0f2c3000 fffff880`0ff9f000   nvlddmkm T (no symbols)           
    Loaded symbol image file: nvlddmkm.sys
    Image path: \SystemRoot\system32\DRIVERS\nvlddmkm.sys
    Image name: nvlddmkm.sys
    Timestamp:        Thu Oct 16 07:31:28 2014 (543FBAA0)
    CheckSum:         00C97F5B
    ImageSize:        00CDC000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Code:

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: fffff88004223eb0, The address that the exception occurred at
Arg3: fffff88002685548, Exception Record Address
Arg4: fffff88002684da0, Context Record Address

Which all started with the original cause

Code:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1000007E, {ffffffffc0000005, fffff88004223eb0, fffff88002685548, fffff88002684da0}
Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_GLOBAL::IsPagingOperationPending+4c )
Followup: MachineOwner

Please, if anything is overclocked please set everything at default values. I am not opposed to overclocking and am overclocked myself right now. However, it confuses things when trying to debug an issue.

Please go into BIOS and give me the values of your +12V, +5V and +3.3V Also the CPU and Motherboard temps.

Most graphics cards have a utility that will allow you to set a custom fan profile to keep the card at cooler temps. It will also be able to give you an on screen Display of several selected items, but I would like you to set it to be able to see the temp and fan speed of the GPU while gaming at all times.

Back in BIOS I would like you to see what your sata controller is set to )IDE, AHCI or Raid) also, Please see that the Frequency, Timings and Voltage are set to the Manufacturer's specs. Those will be written on a sticker on the side of the ram sticks themselves, if you don't know them. Then I would like you to set optimized defaults, confirm this, set your sata controller to what it is right now ( otherwise your system won't boot), Make sure your Ram timings, frequency and voltage are set to Manufacturer's specs, set the boot order, save and exit.

See if that helps any and please use utilities to keep watch on your CPU and GPU temps.

If you continue to have BSODs, please upload the files in a new post. Please also make sure your SSD is updated to the latest Firmware. I know you said you tried and can't do it. If you still can't, please call tech support of Plextor and they will help you do that.

If you don't have the utilities needed to keep watch on the CPU and GPU temps, I can suggest some.

Graphics cards are always the drivers, the card itself, the PSU or the motherboard. Physically, there is little involved. If you don't already have it, please download and install CPUz
CPU-Z CPUID - System & hardware benchmark, monitoring, reporting please post screenshots of the CPU, Mainboard, Memory and SPD tabs. On the SPD tabs, you can select each Dimm slot using a dropdown list in the upper left portion. I only need screenshots of the slots populated with Ram.

If after doing these things you continue having this issue, please remove the card and put it into another clot, to check if perhaps you have a bad PCIe slot. Please let me know of any changes.

Also, if you have any questions, please do not hesitate to ask. I do not mind explaining what we are doing or why I am asking you to do certain things. It's your computer and you can see exactly what is happening. I can't, so if you have any further details or information not already mentioned, please let me know. I have to depend on you for those details as I cannot see or hear what is actually happening.

Thanks mate,

This is a lot to consider but I'm on to it. I haven't overclocked anything, crikey I'm just trying to get this beastie stable at the moment lol. Both case sides are currently off for easy access while it is at this grumbling stage & I have a few methods of checking temps; all are moderate or better and thus not an issue. When installing the MB I had originally put the GPU in PCIe slot #2 and it had the same BSOD behavior so we've ruled out any misbehaving PCIe slots.

I've made some progress in identifying and fixing an Ethernet driver that may have been attributing to the BSOD's (Killer e220). It made you install some QOS software with the driver that was reported to cause issues but I found a work around online. Was hoping this to be the fix but I had yet another BSOD after performing this step (I've attached for you to see as again a different message).

SATA: set to AHCI in BIOS.
Voltages: 12v = 12.288, 5v = 5.040, 3.3v = 3.376

I've now started trouble shooting the RAM as you have instructed.

I've input the RAMs manufacturers specs (Command rate=2, 9,9,9,24) into the BIOS and also removed 2 sticks. I'll see how this goes over 24-48 hours and then swap over the other 2 RAM sticks.

Haven't seen a BSOD yet since setting up RAM in BIOS /fingers_crossed however I've had a game (WOW) crash several times while playing stating (fatal error #132 (0x85100084) & something about access violation and memory could not be read). I'm thinking the force is strong with you as your earlier hunch of the DirectX error being secondary might be right on the money.

I'll continue with the RAM testing & get back to you with the results and values once I have them.

Thanks again for your continued assistance.

It's still showing your graphics driver

Code:

nvlddmkm
start             end                 module name
fffff880`0f473000 fffff880`1014f000   nvlddmkm T (no symbols)           
    Loaded symbol image file: nvlddmkm.sys
    Image path: \SystemRoot\system32\DRIVERS\nvlddmkm.sys
    Image name: nvlddmkm.sys
    Timestamp:        Thu Oct 16 07:31:28 2014 (543FBAA0)
    CheckSum:         00C97F5B
    ImageSize:        00CDC000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

The killer Lan has caused a lot of people trouble and it' s difficult to find the right driver for it. make sure you set the timings frequency and Dram Voltage to Manufacturer's specs. If the problem is the ram, then nothing from the debugger will be correct. Your voltages look good. But, that is at idle. It is very difficult to see what they are under stress. Software is not accurate from my experience.

I suspect your ram should be set to 9-9-9-24 2T. The frequency and voltage has to be right.