BSODs on new build at random and while playing Skyrim

We do need the DMP file as it contains the only record of the sequence of events leading up to the crash, what drivers were loaded, and what was responsible.
Please attach the DMP files to your next post not to post one.

If you are overclocking STOP

You may be able to get the DMP files without crashing by booting into safe mode (F8) with networking.

To enable us to assist you with your computer's BSOD symptoms, upload the contents of your "\Windows\Minidump" folder. If empty (or non existent) please look in the following folders. C:\windows (the dmp should be called memory.dmp), and C:\windows\LiveKernelReports\Watchdog.

The procedure:

* Copy the contents of \Windows\Minidump to another (temporary) location somewhere on your machine.
* Zip up the copy.
* Attach the ZIP archive to your post using the "paperclip" (file attachments) button.
*If the files are too large please upload them to a file sharing service like "Rapidshare" and put a link to them in your reply.

To ensure minidumps are enabled:

* Go to Start, in the Search Box type: sysdm.cpl, press Enter.
* Under the Advanced tab, click on the Startup and Recovery Settings... button.
* Ensure that Automatically restart is unchecked.
* Under the Write Debugging Information header select Small memory dump (256 kB) in the dropdown box (the 256kb varies).
* Ensure that the Small Dump Directory is listed as %systemroot%\Minidump.
* OK your way out.
* Reboot if changes have been made.

sorry bout that, thought I had it attached. I only had 1 dump file available... looking at it with blue screen viewer it looks likes ntoskrnl.exe may be to blame but I can't seem to find any straightforward answers regarding this file

You can't find anything straight forward because that is an operating system file that often shows up in crashes due to the fact that it is one of the main processes for Windows to run. If that file were the actual cause, Windows would not run at all; it is usually blamed due to hardware problems with system or due to an underlying driver conflict. Blue Screen Viewer often blames OS processes and misses the true cause, which is why we use WinDbg.

Your crash points to memory problems or driver conflicts.

• If you are overclocking any hardware, please stop.
  
  
• Run the boot version of Memtest86+ paying close attention to Parts 2 and 3 of the tutorial. Also, in case Memtest86+ misses anything and comes up with no errors, run the extended version of the Windows Memory Diagnostics Tool for at least five passes. These you may want to run overnight since they take a long time to complete (run them an hour before bed each of the next two nights and check before going to sleep that they are still running).
  
     Warning

  Before you proceed with the following, answer these two questions: Are you still under warranty? Does your warranty allow you to open up the machine to check hardware? If you are unsure of the answers to these questions, contact your system manufacturer. WARNING: The steps that follow can void your warranty!!!
  
  For Part 3: If You Have Errors: If you swap any memory components, follow these steps for ESD safety:
  
  1. Shut down and turn off your computer.
  2. Unplug all power supplies to the computer (AC Power then battery for laptops, AC power for desktops)
  3. Hold down the power button for 30 seconds to close the circuit and ensure all power drains from components.
  4. Make sure you are grounded by using proper grounding techniques, i.e. work on an anti-static workbench, anti-static desk, or an anti-static pad. Hold something metallic while touching it to the anti-static surface, or use an anti-static wristband to attach to the anti-static material while working. If you do not have an anti-static workbench, desk, or pad, you can use your computer tower/case by finding a metal hold in it, such as a drive bay.
  
  Once these steps have been followed, it is safe to remove and replace components within your computer.
  
  
• An underlying driver may be incompatible\conflicting with your system. Run Driver Verifier to find any issues. To run Driver Verifier, do the following:
  
  a. Backup your system and user files
  b. Create a system restore point
  c. If you do not have a Windows 7 DVD, Create a system repair disc
  d. In Windows 7:

  • Click the Start Menu
  • Type verifier in Search programs and files (do not hit enter)
  • Right click verifier and click Run as administrator
  • Put a tick in Create custom settings (for code developers) and click next
  • Put a tick in Select individual settings from a full list and click next
  • Set up the individual settings as in the image and click next
    Attachment 214610
  • Put a tick in Select driver names from a list
  • Put a tick next to all non-Microsoft drivers.
  • Click Finish.
  • Restart your computer.

  
  
  If Windows cannot start in normal mode with driver verifier running, start in safe mode. If it cannot start in safe mode or normal mode, restore the system restore point using System Restore OPTION TWO.
  
  Thanks to zigzag3143 for contributing to the Verifier steps.
  If you are unable to start Windows with all drivers being verified or if the blue screen crashes fail to create .dmp files, run them in groups of 5 or 10 until you find a group that causes blue screen crashes and stores the blue screen .dmp files.
  The idea with Verifier is to cause the system to crash, so do the things you normally do that cause crashes. After you have a few crashes, upload the crash reports for us to take a look and try to find patterns.
  
  When you are ready to disable Verifier: Start Menu -> All Programs -> Accessories -> Right click Command Prompt -> Run as administrator -> Type the following command and then Enter:
  verifier /reset
  -> Restart your computer.

As I mentioned I've ran both memory tests as suggested as well as the disk and file checking utilities. I'm attaching the dump files created after using verifier to induce some crashes. Thanks for being patient!!

Which memchecks did you run. For how long? How many passes? More information would be great! :)

On the lines of more information: Please follow the https://www.sevenforums.com/crashes-d...tructions.html to provide us with your full crash reports.

writhziden said:

Which memchecks did you run. For how long? How many passes? More information would be great! :)

On the lines of more information: Please follow the https://www.sevenforums.com/crashes-d...tructions.html to provide us with your full crash reports.

After my last post I did a system restore because I was getting bsod while browsing and attempting to post to the forum. I'm sure this would affect the win_nt6 and system health reports mentioned in the steps u provided??

Most likely. When you are able to provide that information, let us know.


Crashes still indicate memory/drivers as the likely causes...


There was also a network related crash; it may be related to antivirus software or an old or corrupted network adapter driver. Hard to say without the full crash reports.

Mionet driver/WinpkFilter high performance packet filtering framework was blamed in one crash.

writhziden said:

Most likely. When you are able to provide that information, let us know.


Crashes still indicate memory/drivers as the likely causes...


There was also a network related crash; it may be related to antivirus software or an old or corrupted network adapter driver. Hard to say without the full crash reports.

I really appreciate your help, I got frustrated and didn't consider the logs I would need for a full diagnosis before I did the system restore. I seem to be stable now and will re-update in a few. I bsods return I will return with the info needed. On a side note I ran windbg myself and of course the system restore removed log files and reg entries that wouldnt allow wndbg to get all the info but it mentioned ndsird.sys as probable issue. Any ideas on this driver?

See my previous post. I edited it with info about that driver belonging to MioNet.