New
#1
Crash/reboots on custom HTPC: ntoskrnl.exe ntkrnlmp.exe symptoms
Hi I built this custom htpc a few months ago and have experienced regular crashes/reboots. The system is based on an MSI Z97-GD65 mobo with i5-4690S processor in a fanless Streacom case designed for the purpose with extensive heatsinking. To ensure temperatures are not excessive I have kept the processor within the Streacom recommendations, nothing is overclocked and it uses only Intel's integrated graphics with no other video card. All components are new. The only "unusual" item has been an Asus Xonar STX sound PCI-e card. The system is used for TV (windows media center), as a Plex server and a Foobar server - not much else.
By way of troubleshooting, after the first few weeks I did a clean reinstall to remove any issues I might have caused as I iterated my way to the optimum setup, but this made no difference. I also replaced the PSU with no effect. I have run memtest on the memory - this produced 2 errors in the new "hammer test", but G-Skill apparently discount this test and when I run memtest86+ which does not include such a test it shows no errors. Temperatures are ok - typically 30-40 degrees C with occasional 50 (and up to 60 only when doing extreme tasks like Memtest) and the crashes do not seem to happen when anything intensive is going on.
I have been blaming the issue on the Asus Xonar STX sound card as google suggests some people find this causes BSOD issues and the Asus drivers are considered buggy and I had been using the alternative UNI drivers. I have therefore recently now removed the card and installed the mobo's built in realtek 1150 sound. However, I have already had one reboot.
These reboots can be while watching TV using Windows Media Center, or when updating a library in Plex, or simply when putting Flash video to full screen in Chrome browser.
Rather than attempt another clean rebuild with no more likelihood that I will eliminate the problem this time than last time, I would appreciate any help you folks can give me in tracking down the problem so I can fix it. I have now switched minidump reporting one but the last reboot had already resulted in a MEMORY.DMP file and one minidump file so I am attaching the requested zip file.
Thanks!