HTPC Gets Random BSODs when streaming to PS3

Hello Techhappy & Welcome to SevenForums!

BSOD Summary

Code:

Microsoft (R) Windows Debugger Version 6.12.0002.633 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\Frederik\AppData\Local\Temp\Rar$DI01.981\040411-18844-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Machine Name:
Kernel base = 0xfffff800`02a04000 PsLoadedModuleList = 0xfffff800`02c41e50
Debug session time: Tue Apr  5 01:58:22.964 2011 (UTC + 2:00)
System Uptime: 0 days 6:25:28.618
Loading Kernel Symbols
...............................................................
................................................................
.....................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 7F, {8, 80050031, 6f8, fffff80002a7eaf4}

Probably caused by : NETIO.SYS ( NETIO!CompareSecurityContexts+6a )

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

Your crash caused NETIO.sys which is some Network I/O Subsystem. Does this sound familiar to you? Any chance you could update it?

I found it here in your driver stack, the date is fine, but the driver itself might be corrupt.

Code:

Module Name:       tdx
Display Name:      NetIO Legacy TDI Support Driver
Driver Type:       Kernel 
Link Date:         11/20/2010 1:21:54 AM

It's logical though, you're streaming and this driver gets active.
I read something like there should be a hotfix for this you're experiencing. Could you search for updates in your Windows Update and see what appears? This NETIO.sys was been installed in your Windows Update most likely, if it's listing in those updates you can uninstall, you could try uninstalling it through that by using the instructions below.

Windows Update - Uninstall an Update

Best Regards,
FredeGail

techhappy said:

Yeah, I noticed the Netio.sys crash in windebug. So I'm guessing I need to update my network ethernet drivers? What's strange, is if you look at the other minidumps I included, that the problem seems to jump around, from memory corruption, to a cng.sys crash to netio.sys. So I'm kind of scratching my head, unsure of what the exact source of these BSOD's are, or if there are multiple causes.

As a side note, do you think that these sort of BSOD problems are minimized if you just buy a dell or hp system from the get go?

Yes, the Techhappy, is not as happy these days with all these BSODs, eeeeeeeeee......

Memory corruptions? I haven't seen one of those in your .dmp's.

I'd leave the system and just keeeeep uploading the .dmp's if any BSOD. I'd try to uninstall your NETIO.sys driver somehow. And then, leave it as it is.

By the way.. I did get the:

Code:

BugCheck 50, {ffffd800031fb6c0, 0, fffff8000305c9d8, 7}


Could not read faulting driver name
Probably caused by : cng.sys ( cng!GatherRandomKey+294 )

Followup: MachineOwner

Which is a Kernel Cryptography, Next Generation, also in Windows Update. It is digitally signed by Microsoft, and i'm not sure what the cause could be. But first, try uninstalling that Network Driver.

Edit: Strange, suddenly that Network Driver bug doesn't appear anymore on my monitor.

Best Regards,
FredeGail

techhappy said:

The dmp named 071311-21949-01.dmp lists memory corruption as the source. Woe is the BSOD, I guess I'll hang onto the system and upload any future BSODs that come along. I had similar random BSOD's on a custom AMD comp I put together last year.

Is this a trend with building custom comps these days? Do you think that buying comps from dell or hp would minimize bsod issues? My suspicion is that they probably test hardware and driver compatibility thoroughly on those comps to ensure stability, this whole nightmare that I'm going through with my custom builds is kind of turning me off from the scene. Maybe just my bad luck?

Don't give up already. Well, i'm having a custom build computer, and it works fine.

Regarding your memory_corruption, do a MemTest86+ to test your RAM sticks. Do it under these instructions:

RAM - Test with Memtest86+

Best Regards,
FredeGail