Blog for hpHosts, and whatever else I feel like writing about ....

Thursday 31 May 2012

Sysnative.com: Need help with BSOD's?

At one time or another, most people who use the Windows operating system have experienced the dreaded "Blue Screen of Death" (BSOD) -- until Windows 8, a strange blue screen filled with numbers and codes, completely incomprehensible to most everyone.

Granted, there are occasions where a shutdown/restart or evoking "Last Known Good Configuration" appear to have resolved whatever issue caused the BSOD. More times than not, however, help is needed to trace the source of the problem. This is where Sysnative.com comes in to play.

Sysnative.com is the result of a vision of Microsoft MVP, John Griffith. John, known in forum communities as jcgriff2, specializes in Blue Screen of Death (BSOD) Kernel dump analysis. John also enjoys a reputation as an expert Windows forensic troubleshooter, typically sought by Windows Vista and Windows 7 owners after all else has failed.

John developed an application for use by analysts who assist computer users track down the source of the BSODs plaguing their computers. The contributions by many talented people who are involved in analyzing the data compiled by John's application have made the "jcgriff2 BSOD File Collection app" the tool of choice for kernel dump analysis.


Hat tip to Corrine for the heads up;

http://securitygarden.blogspot.co.uk/2012/05/sysnative-what-is-it.html

You can find sysnative.com here;

sysnative.com

For those unfamiliar, sysnative is also a lesser known folder present on x64 systems. Details from Microsoft at;

TechNet: File System Redirector http://technet.microsoft.com/en-us/subscriptions/aa384187(v=vs.85).aspx

Programming Guide for 64-bit Windows http://msdn.microsoft.com/en-us/library/bb427430(v=vs.85)

Best Practices for WOW64 (MS Word document) http://download.microsoft.com/download/A/F/7/AF7777E5-7DCD-4800-8A0A-B18336565F5B/wow64_bestprac.docx

A 32-bit application cannot access the system32 folder on a computer that is running a 64-bit version of Windows Server 2003 or of Windows XP http://support.microsoft.com/kb/942589

No comments: