Multiple Different BSODs Custom PC

[Svyn]

Technical specs are on my profile for viewing if required.
I bought all the parts to this computer off of newegg.ca back in January 2014, been having multiple BSODs since that time. I've ran Memtest 3 different times overnight and haven't had 1 since issue yet. I've downloaded all the latest drivers off of manufacture websites and by using multiple software's to check for outdated drivers.

Examples of when these BSODs will occur:
Playing Skyrim, I have the game completely pimped out in 2k resolution, very demanding in some areas (Riften). BSOD will occur randomly throughout the game.
While playing Outlast, I've had BSOD's occur when the game tries to do an auto-save in demanding areas.
Witcher II, while playing in highly demanding areas, though BSOD was much less common on that game.
No games open, only Google Chrome on youtube or surfing webpages will also cause BSOD.
(Fixed) Used to have BSOD will computer was fully idle (I was AFK) it would happen approximately 1-2 hours into idle, I fixed that by modifying advanced power settings (HDD idle was at 20 minutes, changed to 60 minutes, no more idle BSODs).

Most common BSODs lately are:
System Service Exception + Variants
IRQL Not Less or Equal
Driver IRQL Not Less or Equal
System Thread Exception Not Handled

I've also tried switching my 2 RAM sticks into the other 2 RAM slots, and switching them a whole different amount of ways, never worked. Everytime these problems arise I always look online for fixes, but they never worked. All drivers are up-to-date (That I know of), I have all the latest Microsoft updates as well.

 

[Svyn]

Forgot to put in the dump files.

 

[Arc]

Hi Svyn.

Stress test the Graphics Card using Furmark.
Video Card - Stress Test with Furmark

Test your RAM modules for possible errors.
How to Test and Diagnose RAM Issues with Memtest86+
Run memtest for at least 8 passes, preferably overnight.
If it start showing errors/red lines, stop testing. A single error is enough to determine that something is going bad there.

Also, do you have access to any other GPU to apply and test with? If so, do it and see the situation.

Let us know the results.
____________________________________

BugCheck 1000007E, {ffffffffc0000005, fffff8800ffbbb80, fffff88003746598, fffff88003745df0}

Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_GLOBAL::PrepareDmaBuffer+fc8 )

Followup: MachineOwner
-----------------------------------
BugCheck 1000007E, {ffffffffc0000005, fffff80003692ac1, fffff880009a9898, fffff880009a90f0}

Probably caused by : memory_corruption ( nt!MmZeroPageThread+3c4 )

Followup: MachineOwner
-----------------------------------
BugCheck 50, {fffffa8015e00000, 0, fffff80003696bbb, 2}


Could not read faulting driver name
Probably caused by : ntkrnlmp.exe ( nt!ExAcquireResourceSharedLite+110 )

Followup: MachineOwner
------------------------------------
BugCheck A, {fffffa98005da4d8, 2, 1, fffff800037863bc}

Probably caused by : memory_corruption ( nt!MiRemoveLowestPriorityStandbyPage+1bc )

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

 

[Svyn]

After running FurMark for 15 minutes, the GPU only got up to 82 degrees, 99% load, 15% memory load, 69% fan speed.
I've used MemTest multiple times already, all with my RAM in different memory slots, no errors came up.
If you want me to test it again, I can.

 

[Arc]

If you want to do memtest86+ again, do it for at least 8 consecutive passes.

If it does not show any error, enable Driver Verifier to monitor the drivers.
Driver Verifier - Enable and Disable
Run Driver Verifier for 24 hours or the occurrence of the next crash, whichever is earlier.

   Information

Why Driver Verifier:
It puts a stress on the drivers, ans so it makes the unstable drivers crash. Hopefully the driver that crashes is recorded in the memory dump.

How Can we know that DV is enabled:
It will make the system bit of slow, laggy.

   Warning

Before enabling DV, make it sure that you have earlier System restore points made in your computer. You can check it easily by using CCleaner looking at Tools > System Restore.

If there is no points, make a System Restore Point manually before enabling DV.

   Tip

• If you fail to get on the Desktop because of DV, Boot into Advanced Boot Options > Safe mode. Disable DV there. Now boot normally again, and try following the instruction of enabling DV again.
• If you cannot boot in Safe mode too, do a System Restore to a point you made earlier.

Let us know the results, with the subsequent crash dumps, if any.

 

[Svyn]

Alright, I ran memtest for 5 passes, no errors.
When I ran driver verifier, it didn't even make it past the windows logo on start-up

It basically flickered to a BSOD and then restart itself, leaving no DMP file.
I did see that it was an IRQL Not Less or Equal error though, didn't see anything else.
I let it BSOD about 5 times before I did a system restore.

 

[Golden]

Alright, I ran memtest for 5 passes, no errors.

You require a minimum of 8 passes for MemTest86+ - 5 passes is not enough to thoroughly test RAM

 

[Svyn]

Alright, I've been busy so I left Memtest up for a long time, it ended up having 28 passes and 0 errors.
Driver Verifier gives me the IRQL Not Less Or Equal and doesn't allow me to get passed the windows boot up logo.

 

[Arc]

Alright, I've been busy so I left Memtest up for a long time, it ended up having 28 passes and 0 errors.

That is a relieving news.

Driver Verifier gives me the IRQL Not Less Or Equal and doesn't allow me to get passed the windows boot up logo.

Disable driver verifier.

Then free up the startup. Windows does not need any other program to auto start with it, but the auto start programs often conflicts and causes various problems including BSODs.

1. Click on the Start button
2. Type “msconfig (without quotes), click the resulting link. It will open the System Configuration window.
3. Select the “Startup” tab.
4. Deselect all items other than the antivirus.
5. Apply > OK
6. Accept then restart.

Now enable driver verifier again. Hopefully this time the computer will crash after booting to windows and we will get the necessary crash dump.

 

[Svyn]

Alright, so I ended up getting to my desktop screen without any BSOD. So I let it run for approximately 24 hours, am I able to do normal tasks on that computer like gaming, streaming, etc.. Or do I just let it sit?

 

[Thedoctor44]

When you enable Driver Verifier just do whatever you would normally do if your computer was working. When it BSODs copy the dump files from C:/Windows/Minidump onto the desktop, zip them up to a compressed zip folder and upload them.

 

[Svyn]

Alright, it didn't BSOD while gaming, but it did BSOD after I finished gaming and was on youtube for a bit.
Disabled Verifier, posting log. (It's the last one on the list)

 

[Arc]

The BSOD points to wifi network driver.

BugCheck A, {8, 2, 0, fffff80003b06554}

[COLOR=Red]Probably caused by : nwifi.sys[/COLOR] ( nwifi!Dot11AllocateSendPacket+30 )

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

Your WiFi device is D-Link DWA-160 Xtreme N Dual Band USB Adapter(rev.B2); the driver is old.

fffff880`04200000 fffff880`0439c000   Dnetr28ux   (deferred)             
    Image path: \SystemRoot\system32\DRIVERS\Dnetr28ux.sys
[COLOR=Red]    Image name: Dnetr28ux.sys
    Timestamp:        Fri Sep 09 12:12:04 2011 [/COLOR](4E69B53C)
    CheckSum:         001A427D
    ImageSize:        0019C000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

And it is the latest available driver for this device, as per Support | D-Link UK

View attachment 311556

Still try to download and install the driver afresh. If the BSODs occur in the same way, use another USB WiFi adapter and see the situation.

 

[Svyn]

I uninstalled the D-Link software and only installed the driver straight off their website. I did that today
Right after I posted my last DMP logs last night I ended up getting another BSOD though, it was after I turned verifier off and rebooted. I ended up just going to bed though.
KMODE EXCEPTION NOT HANDLED was the error, DMP included.

 

[Thedoctor44]

I would enable Driver Verifier again for 24 hours. It seems there's another driver causing issues.

 

[Arc]

The KMODE EXCEPTION NOT HANDLED BSOD is not showing much more information about the BSOD, but the WiFi driver is as same as the earlier ones.

fffff880`04095000 fffff880`04231000   Dnetr28ux   (deferred)             
    Image path: \SystemRoot\system32\DRIVERS\Dnetr28ux.sys
[COLOR=Red]    Image name: Dnetr28ux.sys
    Timestamp:        Fri Sep 09 12:12:04 2011 [/COLOR](4E69B53C)
    CheckSum:         001A427D
    ImageSize:        0019C000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

It the BSODs continue to occur, IMHO it will be best to apply another adapter, on a test basis at least.

 

[Svyn]

Been running Driver Verifier for about 25 hours now and I just got a System Service Exception BSOD. Logs attached.

 

[Svyn]

No one posted a reply to my last BSOD, and I ended up getting different one while Verifier was running.
SYSTEM SERVICE EXCEPTION and
IRQL NOT LESS OR EQUAL
They are the last ones on the list, need to be checked.

 

[Arc]

Have you thought anything about the network adapter?

 

[Thedoctor44]

I agree with Arc, if you haven't updated your network driver it would be pointless making more suggestions as the network driver appears to be one of the culprits. Try updating the network driver again and if that doesn't work try using a different adapter.