BSOD random cause, thanks to ntoskrnl.exe

Hey y'all, been getting this BSOD problem since I built the computer and I cant quite figure it out. i know ntoskrnl.exe is causing it, or is the last item on the stack. I grabbed dmp file of it and uploaded it if anyone could help me that would be GREAT!

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.

Your crash dumps are not showing any finite probable cause. In such a situation, it is better to 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.

It blames to Deterministic Network Enhancer Miniport (c:\windows\system32\drivers\dne64x.sys).

Code:

BugCheck C4, {f6, 84, fffffa800caee210, fffff880077d6f50}

*** WARNING: Unable to verify timestamp for dne64x.sys
*** ERROR: Module load completed but symbols could not be loaded for dne64x.sys
Probably caused by : dne64x.sys ( dne64x+ff50 )

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

And it is extremely old.

Code:

fffff880`077c7000 fffff880`077f3000   dne64x   T (no symbols)           
    Loaded symbol image file: dne64x.sys
    Image path: \SystemRoot\system32\DRIVERS\dne64x.sys
    Image name: dne64x.sys
    Timestamp:        Tue Nov 11 06:31:24 2008 (4918D964)
    CheckSum:         000359DA
    ImageSize:        0002C000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Try to update it from DNE Support - Deterministic Networks - Citrix.

I ma seeing that the Cisco Systems VPN Adapter for 64-bit Windows is also very old. And it is disabled, perhaps? If it is not needed, uninstall it. Otherwise update it to the latest.

Let us know the results.

Heh, wow I wouldn't have even known where to go to find or fix half this stuff I usually get 1-2 BSOD's a day and I just built this computer maybe 3 months ago. I don't really want to mess with the VPN as it took me forever to get my school Linux servers to work with my computer. We have to remote connect specifically which took me forever to do.

I just updated the dne going restart and see if anything blows up.

--After restarting nothing went wrong, so I decided to turn on the verifier. Even with an SSD this took a while withe very driver but Microsoft ones selected. I'm going to run this for the next 24/12 hours depending on how long I can stand this lag. If no more BSOD's occur I will mark this solved if not. Ill post more dumps for you.

Thank you arc, your a life saver.

You are welcome mate.

Let us know for any further issue.

It is a stop 0x3B, caused by the display driver.

Code:

fffff880`09a2d528  fffff880`05bcca7bUnable 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+0xeba7b

Unfortunately the best known good driver version, 314.22 WHQL does not work with GTX 760. Try to clean install the latest version of the display driver, 331.65 WHQL. While doing the installation, choose the advanced option, check the clean install box, and install the display driver and PhysX only.

NVIDIA DRIVERS GeForce 331.65 Driver WHQL

Let us know the results.

Display issue again.

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.

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

Check if the Power Supply Unit (PSU) supplying adequate power to the computer or not.
eXtreme Power Supply Calculator

Is the computer hot? Report us the heat of the computer after a couple of hours of your normal usage. Upload a screenshot of the summery tab of Speccy.