Series of BSODs: dxgmms1.sys, BHDrvx64.sys, PAGED_FAULT_IN_NONPAGE..

I understand your question.

The first dump - 101012 and its causes are:

Code:

STOP 0x0000007F: UNEXPECTED_KERNEL_MODE_TRAP 
Usual causes:  Memory corruption, Hardware (memory in particular), 
Overclocking failure, Installing a faulty or mismatched hardware 
(especially memory) or a failure after installing it, 
3rd party firewall, Device drivers, SCSI/network/BIOS updates needed, 
Improperly seated cards, Incompatible storage devices, Overclocking, 
Virus scanner, Backup tool, Bad motherboard, Missing Service Pack
BugCheck 7F, {8, 80050031, 6f8, fffff800020d575d}
Probably caused by : ntkrnlmp.exe ( nt!KiDoubleFaultAbort+b2 )

But your dump din't say anything like that, digging more in the dump din't give more information either. But we can see the usual causes and list you software which are famous for causing BSODs. You can see that the 7F bug check has Back up tool, Virus scanner and 3rd party firewall listed. I have never used Norton personally but I know that it has all the ones that are listed in red.

The second dump - 101412 stated some problems with the Nvidia Drivers but the bug checks usual causes are something else..and it's not necessary that the usual causes always match with whats there in the dump.

Code:

STOP 0x0000000A: IRQL_NOT_LESS_OR_EQUAL   
Usual causes:  Kernel mode driver, System Service, BIOS, Windows, 
Virus scanner, Backup tool, compatibility
------------------
fffff880`009a96f8  fffff880`05dab1f0Unable to load image \SystemRoot\system32\DRIVERS\nvlddmkm.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
 nvlddmkm+0xf61f0

Now the first crash that you had on 101712 shows the same problem with the Nvidia drivers but looks like there was something else bugging it there.

Code:

fffff880`10f64768  fffff880`066862dfUnable to load image \SystemRoot\system32\DRIVERS\nvlddmkm.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
 nvlddmkm+0xa612df

Code:

STOP 0x00000050: PAGE_FAULT_IN_NONPAGED_AREA  
Usual causes:  Defective hardware (particularly memory - but not just RAM), Faulty system service, Antivirus,  Device driver, NTFS corruption, BIOS
BugCheck 50, {fffff10021ec979c, 0, fffff8000210877f, 7}
Could not read faulting driver name
Probably caused by : memory_corruption

Antivirus yet again, but you'll see a red line that says "could not read faulting driver name" which could be the antivirus drivers irritating the graphic card drivers and that results in "memory corruption" but these lines are not always accurate or true. That's why we list the problematic software first, then look at hardware. But, if you want to run memtest86+, go ahead with it if you have time :)

Here's a strategy that may help:

Run for 8 passes and test each stick in a know good slot for an additional 6 passes.

The goal is to test all the RAM sticks and all the motherboard slots.

Check your motherboard manual to ensure the RAM sticks are in the recommended motherboard slots. Some motherboards have very specific slots required for the number of RAM sticks installed.

If you get errors, stop the test and continue with the next step.

1. Remove all but one stick of RAM from your computer (this will be RAM stick #1), and run Memtest86 again, for 7 passes.
Be sure to note the RAM stick, use a piece of tape with a number, and note the motherboard slot.
If this stick passes the test then go to step #3.

2. If RAM stick #1 has errors, repeat the test with RAM stick #2 in the same motherboard slot.
If RAM stick #2 passes, this indicates that RAM stick #1 may be bad. If you want to be absolutely sure, re-test RAM stick #1 in another known good slot.
If RAM stick #2 has errors, this indicates another possible bad RAM stick, a possible motherboard slot failure or inadequate settings.
3. Test the next stick of RAM (stick #2) in the next motherboard slot.
If this RAM stick has errors repeat step #2 using a known good stick if possible, or another stick.
If this RAM stick has no errors and both sticks failed in slot#1, test RAM stick #1 in this slot.
4. If you find a stick that passes the test, test it in all the other motherboard slots.

If Part 2 testing shows errors, and all tests in Part 3 show errors, you will need to test the RAM sticks in another computer and/or test other RAM in your computer to identify the problem.

In this way, you can identify whether it is a bad stick of RAM, a bad motherboard, or incompatibility between the sticks.

The second dump on 101712 just said HDAudBus.sys as probable cause, check for optional updates from windows updates in this case. Although I think its not really a cause as bug check 3D does not have usual causes listed.

Code:

STOP 0x0000003D: INTERRUPT_EXCEPTION_NOT_HANDLED 
Usual causes: None listed
BugCheck 3D, {fffff880020f6180, 0, 0, fffff88003849baa}
Probably caused by : HDAudBus.sys ( HDAudBus!READ_REGISTER_UCHAR+a )

Coming to the last dump of 101712, it finally revealed something to our face:

Code:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
STOP 0x00000050: PAGE_FAULT_IN_NONPAGED_AREA  
Usual causes:  Defective hardware (particularly memory - but not just RAM), Faulty system service, Antivirus,  Device driver, NTFS corruption, BIOS

BugCheck 50, {fffff8a0182d1ce9, 1, fffff88005a39638, 2}

Unable to load image \??\C:\ProgramData\Norton\{0C55C096-0F1D-4F28-AAA2-85EF591126E7}\NIS_19.1.0.28\Definitions\BASHDefs\20120928.001\BHDrvx64.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for BHDrvx64.sys
*** ERROR: Module load completed but symbols could not be loaded for BHDrvx64.sys

Could not read faulting driver name
Probably caused by : BHDrvx64.sys ( BHDrvx64+39638 )

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

BHDrvx64.sys is a driver from "Symantec Heuristics"
Source: Carrona.org

The bug checks usual causes are listed. Do I need to point out more?

Let us know memtest results, and if your system blue screens or not. Good luck :)

Walt110 said:

Wow, thank you very much for the detailed analysis, really appreciate it!

I'm going to proceed with the memory check and I will post back here when I have the results!

Also, on a side note, I am fairly convinced it was Norton, but the best test is to keep my MSE for a few weeks and put my computer through the ringer (playing games etc..).

Edit: Boo I can't give you more reputation. Oh well, +1 your rep, thank you again!

No problem. I appreciate that you appreciate me trying to help. :)
Will wait for the results from memtest. See you soon :)

So how did memtest go? Did the BSODs reoccur? :)

Alrighty, thanks for the update :)

Hi. Just looking for an update after 3 weeks. Have the BSOD-s reoccurred?
If not, let us know and mark the thread as solved.

If there are any other issues, you may create a new thread and link this one to it.

Good luck :)

Good to hear! Happy computing :)