Intermittant BSOD, always ntoskrnl.exe, checked ram, hdd, etc

[computron5000]

Hello computer gurus
I had this computer built back in may, and had several problems installing windows (hdd not found), eventually traced to a bad hdd, which they replaced, but some blue screens did not stop after that. I thought that I had tracked down most of the software issues, and actually had to hide a couple windows updates that were particularly problematic.

I have received a wide variety of BSODs, with the only commonality being that they all seem to reference ntoskrnl.exe, which made me suspect my RAM, but after running memtest for a ton (several days) of passes, I am not so sure.

I also tried running sfc, chkdsk and furmark, as well as virus scans (MSE).

One final note, the computer seems to stutter audio when loading large games, files, etc. Not sure if this is related but you would think with a fairly new computer this wouldn't be as prevalent

Dumps, specs, drivers, etc attached

EDIT: just thought that I would note that these are once every few days, although there was a large break where there were none in the last couple months till this week, I've been uninstalling anything that I have recently added to see if it will be fixed.

Thanks!

 

[FredeGail]

Hello Computron and welcome to Sevenforums.

Stuff we need

• A nfo file

  • To get this: Start Menu -> Type msinfo32 into the Search programs and files box -> When it opens, go to File, Save -> Save as msinfo32.nfo and save in a place you will remember -> Let it finish the process of gathering and saving the system info -> Right click the .nfo file, click send to compressed (zipped) folder -> Upload the .zip file here.

BSOD Analyse

Daemon Tools' drivers are known issues to Windows 7. That's all I see at the moment, if this won't fix your issues, we'll run driver verifier. But for now, uninstall Daemon Tools and make sure the sptd.sys driver is as good as gone.

intelppm.sys Tue Jul 14 01:19:25 2009 (4A5BC0FD)
RtNdPt60.sys Mon Jul 20 04:27:32 2009 (4A63D614)
amdxata.sys Fri Mar 19 17:18:18 2010 (4BA3A3CA)
HECIx64.sys Tue Sep 21 18:59:04 2010 (4C98E458)
iaStor.sys Fri May 20 18:52:24 2011 (4DD69C48)
Rt64win7.sys Tue Sep 27 16:50:33 2011 (4E81E2B9)
atpkns38.SYS Wed Dec 28 10:10:52 2011 (4EFADD1C)
EtronXHCI.sys Fri Jan 6 09:59:41 2012 (4F06B7FD)
EtronHub3.sys Fri Jan 6 09:59:47 2012 (4F06B803)
RTKVHD64.sys Tue Jan 17 12:14:33 2012 (4F155819)
sptd.sys Sat Mar 3 17:45:52 2012 (4F524AC0) [COLOR="Red"](known issues in Windows 7)[/COLOR]
MpFilter.sys Fri Mar 9 12:05:26 2012 (4F59E3F6)
nvlddmkm.sys Tue May 15 09:35:36 2012 (4FB20748)

intelppm.sys
RtNdPt60.sys
amdxata.sys
HECIx64.sys
iaStor.sys
Rt64win7.sys
atpkns38.SYS
EtronXHCI.sys
EtronHub3.sys
RTKVHD64.sys
sptd.sys
MpFilter.sys
nvlddmkm.sys

3: kd> lmvm sptd
start             end                 module name
fffff880`01076000 fffff880`011e9000   sptd       (deferred)             
    Image path: \SystemRoot\System32\Drivers\sptd.sys [COLOR="Red"]<-- location[/COLOR]
    Image name: sptd.sys
    Timestamp:        Sat Mar 03 17:45:52 2012 (4F524AC0)
    CheckSum:         0008CE54
    ImageSize:        00173000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Best Regards,
Frederik.

 

[computron5000]

Hey, thanks for replying
I uninstalled daemon tools a while ago after hearing it could be a problem, guess I missed the driver, that is gone now.
Here is the nfo, let me know if you need anything else. Haven't had a BSOD in a few days, but that never really means much

 

[FredeGail]

Alright, let's do some stress testing on your drivers.

Using Driver Verifier is an iffy proposition. Most times it'll crash and it'll tell you what the driver is. But sometimes it'll crash and won't tell you the driver. Other times it'll crash before you can log in to Windows. If you can't get to Safe Mode, then you'll have to resort to offline editing of the registry to disable Driver Verifier.

So, I'd suggest that you first backup your stuff and then make sure you've got access to another computer so you can contact us if problems arise.
Then make a System Restore point (so you can restore the system using the Vista/Win7 Startup Repair feature) - and create a System Repair Disc (Win7) if you don't have a full installation DVD.
You can do this by going to Start...All Programs...Maintenance...Create a System Repair Disc (don't forget to test the disc to make sure it works).

For Vista, you can download the repair discs from different websites. If unable to locate them, shoot me a PM and I'll point you to them.
For Win8, BSOD's are different - and we'll have to adjust how we do this with them.

Also, to ensure that you can recover, here's another couple of additional steps:
- Get to the Safe Mode menu (rapidly tap F8 just before the Windows splash screen comes up). Scroll down to and select "Disable automatic restart on System Failure"
- Get the RED information from this picture (in particular we will need the name of the file that the error occurred in):
Picture of a BSOD

Then, here's the procedure to run Driver Verifier:
- Go to Start and type in "verifier" (without the quotes) and press Enter
- Select "Create custom settings (for code developers)" and click "Next"
- Select "Select individual settings from a full list" and click "Next"
- Select everything EXCEPT FOR "IRP Logging", "Force Pending I/O Requests" and "Low Resource Simulation" and click "Next" ("Special Pool" may be able to be used depending on amount of RAM and errors being seen. In situations with small amounts of RAM, DO NOT select it),
- Select "Select driver names from a list" and click "Next"
Then select all drivers NOT provided by Microsoft and click "Next"
- Select "Finish" on the next page.

Reboot the system and wait for it to crash to the Blue Screen. Continue to use your system normally, and if you know what causes the crash, do that repeatedly. The objective here is to get the system to crash because Driver Verifier is stressing the drivers out. If it doesn't crash for you, then let it run for at least 36 hours of continuous operation (an estimate on my part).

Reboot into Windows (after the crash) and locate the memory dump file. If present, turn off Driver Verifier by going back in and selecting "Delete existing settings" on the first page. Then, zip up the memory dump file(s) and upload them with your next post. If no dump files were generated, post back for further suggestions.

If you can't get into Windows because it crashes too soon, try it in Safe Mode.
If you can't get into Safe Mode, try using System Restore from your installation DVD to set the system back to the previous restore point that you created.

If that doesn't work, post back and we'll have to see about fixing the registry entry off-line:

Delete these registry keys to stop Driver Verifier from loading (works in XP, Vista, Win7):
        HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\VerifyDrivers
        HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\VerifyDriverLevel

Best Regards,
Frederik.

 

[computron5000]

Finally got something, bluescreenview blames dxgkrnl.sys, ntoskrnl.exe, nvlddmkm.sys on a 0x3b system service exception
I doubt its going to be my NVIDIA drivers since I've reinstalled them from various sources numerous times, but I'm open to suggestions. Attached is the minidump file.

note: this occured while watching some pretty low-fi video on vlc

edit: after semi-random clicking of google links, I've tried http://www.sevenforums.com/crashes-debugging/190306-bsod-nvlddmkm-sys-dxgkrnl-sys-help.html

will try post 2 of http://www.sevenforums.com/crashes-...x64-nvlddmkm-sys-dxgkrnl-sys-dxgmms1-sys.html if it still crashes before I hear back from anyone

 

[FredeGail]

Umm, I think you've gotten the upload wrong.
Are you able to zip the dumps and attack them?

Best Regards,
Frederik.

 

[computron5000]

woops, thats what happens when you try to do anything at like 4 in the morning

edit: got another one, this time with ntfs.sys, also attached

I think I will try memtesting my RAM individually, can't remember if I have or not

 

[FredeGail]

We usually ask people to do this command to check if Windows is corrupted. It's the most common used one to check if the Windows files are corrupted. If it'll find errors, it'll restore them.

   Tip

If you're having a custom customization layer on your Aero, it's likely to get restored to default.

Press Start | search 'cmd' | Right-click it
| open as Admin | type SFC /SCANNOW

http://www.sevenforums.com/tutorials/1538-sfc-scannow-command-system-file-checker.html

Best Regards,
Frederik.

 

[computron5000]

scan said that it didnt find any integrity violations, but my screen did go black and come back a couple times during the test. Also, my bios had my ram set to 1333 (on auto) when they are 1600, that was weird

 

[FredeGail]

I'm sorry I should have linked you the Daemon Tools uninstaller of course. You can try to run it even if you uninstalled it already. Sptd.sys might still be hanging.

DuplexSecure - Downloads

Also did the bios ram voltage change recently?

Best Regards,
Frederik.

 

[computron5000]

cant say that I've ever checked the voltage, its been on auto forever. the timing has always been set to auto, and therefore 1333, I never really clued into the fact that my ram was 1600 until i was memtesting it and saw the label on the ram itself. I just recently changed that to 1600 manually, hasn't caused any problems yet.

 

[FredeGail]

cant say that I've ever checked the voltage, its been on auto forever. the timing has always been set to auto, and therefore 1333, I never really clued into the fact that my ram was 1600 until i was memtesting it and saw the label on the ram itself. I just recently changed that to 1600 manually, hasn't caused any problems yet.

It may have fixed your issues maybe. Voltages is a manner of problems and solutions for sure. Use your computer as usual and see if it's crashing.

Best Regards,
Frederik.

 

[computron5000]

Alright, thanks for the help!

 

[FredeGail]

Alright, thanks for the help!

You're welcome, nice effort on your side.
Return if your issues proceeds.

Best Regards,
Frederik.

 

[computron5000]

Well that didn't take long at all, got a 0x109 with ntoskrnl.exe blamed, dump attached

 

[FredeGail]

Well that didn't take long at all, got a 0x109 with ntoskrnl.exe blamed, dump attached

Is your verifier enabled/disabled?

 

[computron5000]

enabled, should I just turn it off?

 

[FredeGail]

enabled, should I just turn it off?

Yes please.

Verifier will always find something to crash on whatever computer in my experiences. Not on all, but many.

Best Regards,
Frederik.

 

[computron5000]

turned off verifier, still got a blue screen.
blames nvlddmkm.sys, dxgkrnl.sys and ntoskrnl.exe again

 

[FredeGail]

1. Fresh up the DirectX files
2. Reinstall your Graphics Driver within a clean install. By that you're making sure that there's no leftover files.
   1. Try to do a clean install of the Graphic Driver, the tutorial below meets the requirements of not having left-over files afterwards.
      
      i) Make your way to Nvidia Drivers - Download NVIDIA Drivers and download the latest driver for your card, save it to your desktop for instance.
      ii) Uninstall the Graphic driver you currently have and all its extensions (do not reboot yet)
      iii) Download Driver Sweeper
      iv) Get to safe mode (without network) and search for Driver Sweeper in your rb:
      v) Select all the Nvidia components and analyse them
      vi) Clean them, head into Windows without internet and install the driver you downloaded previously.

Best Regards,
Frederik.