Sysnative.com provides free professional Blue Screen of Death (BSOD) crash analysis and debugging support, expert malware analysis and removal advice, Windows Update help plus hardware and networking support for Windows OS.
If overclocking, please stop and rest the system to stock values while we're troubleshooting. Feel free to resume the overclock once the system is stabilized (once the BSOD's have stopped)
More info on the STOP 0x116 error here: http://www.carrona.org/bsodindx.html#0x00000116
More info on the STOP 0x117 error here: http://www.carrona.org/bsodindx.html#0x00000117
ATI troubleshooting (thanks to Cap'n Jack): http://support.amd.com/us/kbarticles...rmessages.aspx
Updated 10-14-2012 at 08:24 AM by usasma
I'm looking for suggestions on 2 things:
- adding info on software conflicts to the DRT (maybe a separate column in the database)?
- building a database of drivers that occur in memory dumps - and seeing if we can find relationships among drivers in specific crashes.
This came from this topic: http://www.sysnative.com/forums/show...nd-other-stuff
Please post any suggestions over in that
Just a quick post to let you know that I'm still around.
Lot's going on and I don't have much time to update things.
I'm still working on my website here: http://www.carrona.org/
My point here is that I can put up with an awful lot of sh*t (I spent 26 years in the military) - but there are certain things that I will not tolerate. One of those things is abusing people who can't defend themselves.
I firmly believe in the concept of "Noblesse oblige". For those not familiar with this, it's the obligation for one to act in the manner expected of the position that you're in. If you're a boss, you're obligated and expected to act as a boss should.
Updated 04-07-2012 at 08:29 AM by usasma
Just trying to firm up my "intent".........
My primary purpose/goal is to help users.
There is (IMO) a need for BSOD analysts to help users with their BSOD problems.
This differs from standard BSOD analysis in 2 ways:
- there is little need to disassemble instructions to see where a program/driver went wrong. It's enough (for our purposes) to know that the program was at fault. In most cases we don't even have the skills to repair the problem, relying