<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Crash on Pieter Viljoen's Blog</title><link>https://blog.insanegenius.com/tag/crash/</link><description>Recent content in Crash on Pieter Viljoen's Blog</description><generator>Hugo</generator><language>en</language><lastBuildDate>Thu, 23 Aug 2012 22:09:49 +0000</lastBuildDate><atom:link href="https://blog.insanegenius.com/tag/crash/feed.xml" rel="self" type="application/rss+xml"/><item><title>Windows 8 VIDEO_TDR_FAILURE Madness</title><link>https://blog.insanegenius.com/2012/08/23/windows-8-video_tdr_failure-madness/</link><pubDate>Thu, 23 Aug 2012 22:09:49 +0000</pubDate><guid isPermaLink="false">https://blog.insanegenius.com/2012/08/23/windows-8-video_tdr_failure-madness/</guid><description>&lt;p&gt;I finally figured out why I kept on getting VIDEO_TDR_FAILURE BSOD&amp;rsquo;s when installing Windows 8 on my SuperMicro workstations. It turns out that the problem goes away when I use a PCIe slot associated with CPU #1, instead of a slot associated with CPU #2.&lt;/p&gt;
&lt;p&gt;Some history on my adventures with &lt;a href="http://windows.microsoft.com/en-US/windows/home"&gt;Windows 8&lt;/a&gt; and &lt;a href="http://www.supermicro.com/products/nfo/superworkstation.cfm"&gt;SuperMicro SuperWorkstations&lt;/a&gt;:&lt;br&gt;
I got &lt;a href="https://blog.insanegenius.com/2012/07/19/windows-8-and-server-2012-on-supermicro-results-in-acpi_bios_error-bsod/"&gt;ACPI_BIOS_ERROR BSOD&lt;/a&gt;&amp;rsquo;s while installing Windows 8, SuperMicro &lt;a href="https://blog.insanegenius.com/2012/07/30/supermicro-beta-bios-supports-windows-8-and-server-2012/"&gt;provided a Beta BIOS&lt;/a&gt; that resolved the problem.&lt;br&gt;
The Windows 8 &lt;a href="https://blog.insanegenius.com/2012/08/05/windows-8-install-hangs-booting-from-lsi-2308-sas-controller/"&gt;install hangs&lt;/a&gt; if installing to an SSD drive on an &lt;a href="http://www.lsi.com/products/storagecomponents/Pages/LSISAS2308.aspx"&gt;LSI 2308&lt;/a&gt; SAS controller, that issue is still unresolved, but can be worked around by connecting the SSD to the Intel SATA controller.&lt;br&gt;
I got &lt;a href="https://blog.insanegenius.com/2012/08/06/windows-8-install-crash-with-nvidia-quadro-5000/"&gt;VIDEO_TDR_FAILURE BSOD&lt;/a&gt;&amp;rsquo;s while installing Windows 8 with an NVidia Quadro 5000 graphics card, same with an ATI FirePro V7900 or an NVidia GeForce GTX 680 or an ATI HD 7970. And this post is about resolving that problem.&lt;/p&gt;</description></item><item><title>Windows 8 Install Crash With NVidia Quadro 5000</title><link>https://blog.insanegenius.com/2012/08/06/windows-8-install-crash-with-nvidia-quadro-5000/</link><pubDate>Mon, 06 Aug 2012 08:45:13 +0000</pubDate><guid isPermaLink="false">https://blog.insanegenius.com/2012/08/06/windows-8-install-crash-with-nvidia-quadro-5000/</guid><description>&lt;p&gt;I got Windows 8 RTM installed on my two SuperMicro SuperWorkstation machines, with a &lt;a href="https://blog.insanegenius.com/2012/08/05/windows-8-install-hangs-booting-from-lsi-2308-sas-controller/"&gt;bit of trouble&lt;/a&gt; along the way, but nothing I could not work around. But, I ran into a problem with NVidia Quadro 5000 cards causing a &lt;a href="http://msdn.microsoft.com/en-us/library/windows/hardware/ff557263(v=VS.85).aspx"&gt;VIDEO_TDR_FAILURE&lt;/a&gt; BSOD during the Windows 8 install process.&lt;/p&gt;
&lt;p&gt;I was running my two workstations with &lt;a href="http://amzn.to/LZehYW"&gt;ATI FirePro V7900&lt;/a&gt; graphics cards, but I decided I wanted a bit more rendering horsepower. I wanted a card that had a good balance between modern architecture, great 2D performance, good 3D performance, OpenCL or CUDA support, and reasonable power consumption. I found the &lt;a href="http://www.tomshardware.com/charts/workstation-graphics-2012/benchmarks,139.html"&gt;Tom&amp;rsquo;s Hardware Workstation Graphics 2012&lt;/a&gt; benchmark site to be very informative, and I decided that the &lt;a href="http://amzn.to/RrHg9L"&gt;NVidia Quadro 5000&lt;/a&gt; was a very good choice.&lt;/p&gt;</description></item><item><title>Debugging Windows 8 Install BSOD</title><link>https://blog.insanegenius.com/2012/07/20/debugging-windows-8-install-bsod/</link><pubDate>Fri, 20 Jul 2012 22:04:27 +0000</pubDate><guid isPermaLink="false">https://blog.insanegenius.com/2012/07/20/debugging-windows-8-install-bsod/</guid><description>&lt;p&gt;In my &lt;a href="https://blog.insanegenius.com/2012/07/19/windows-8-and-server-2012-on-supermicro-results-in-acpi_bios_error-bsod/"&gt;last post&lt;/a&gt; I described how to prevent Windows from automatically restarting when encountering a BSOD during the OS install process. This allowed me to see the &lt;a href="http://msdn.microsoft.com/en-us/library/windows/hardware/ff560114(v=vs.85).aspx"&gt;ACPI_BIOS_ERROR&lt;/a&gt; fault code while installing Windows 8 on my new SuperMicro workstation. The new &lt;a href="http://blogs.msdn.com/b/b8/archive/2011/09/20/reengineering-the-windows-boot-experience.aspx"&gt;Windows 8 BSOD page&lt;/a&gt; looks friendly, but no longer displays any error parameters other than the main fault code.&lt;/p&gt;
&lt;p&gt;In order to get additional details of the crash, I had to hook up a kernel debugger to the machine. Windows 8 adds &lt;a href="http://channel9.msdn.com/Events/BUILD/BUILD2011/HW-98P"&gt;USB3 and TCPIP&lt;/a&gt; kernel debug support, and I will describe how I used the TCPIP network option to capture details of the crash.&lt;/p&gt;</description></item><item><title>Windows 8 and Server 2012 on SuperMicro results in ACPI_BIOS_ERROR BSOD</title><link>https://blog.insanegenius.com/2012/07/19/windows-8-and-server-2012-on-supermicro-results-in-acpi_bios_error-bsod/</link><pubDate>Fri, 20 Jul 2012 00:59:01 +0000</pubDate><guid isPermaLink="false">https://blog.insanegenius.com/2012/07/19/windows-8-and-server-2012-on-supermicro-results-in-acpi_bios_error-bsod/</guid><description>&lt;p&gt;I ran out of disk space on my development workstation, all those VM images add up. The machine has four drive bays, and all four have 3TB drives. I can replace the 3TB drives with 4TB drives, but migrating the RAID5 array will be time consuming and risky. I can add an external SAS storage enclosure, but they do not power down when the machine goes to sleep. So I looked at buying a new machine with more drive bays.&lt;/p&gt;</description></item><item><title>CrashPlan Memory Utilization</title><link>https://blog.insanegenius.com/2012/07/15/crashplan-memory-utilization/</link><pubDate>Sun, 15 Jul 2012 22:39:14 +0000</pubDate><guid isPermaLink="false">https://blog.insanegenius.com/2012/07/15/crashplan-memory-utilization/</guid><description>&lt;p&gt;I&amp;rsquo;ve been using &lt;a href="http://www.crashplan.com/"&gt;CrashPlan&lt;/a&gt; as an online backup solution for quite some time, and it works really well.&lt;/p&gt;
&lt;p&gt;I like the fact that I can subscribe to the consumer plan, with almost 3.5TB of data backed up, and that the backup client installs on a server OS. Many of the other &amp;ldquo;unlimited&amp;rdquo; backup providers I tested have restrictions in place that make such a setup impossible.&lt;/p&gt;
&lt;p&gt;CrashPlan sends email notifications about backup status, and I noticed that something was wrong with the backup:
&lt;a href="https://blog.insanegenius.com/media/2012/07/crashplan-email_.png"&gt;&lt;img alt="CrashPlan.Email" loading="lazy" src="https://blog.insanegenius.com/media/2012/07/crashplan-email_thumb.png"&gt;&lt;/a&gt;&lt;/p&gt;</description></item><item><title>Trend Micro SafeSync, neat, but unreliable</title><link>https://blog.insanegenius.com/2010/12/31/trend-micro-safesync-neat-but-unreliable/</link><pubDate>Fri, 31 Dec 2010 22:17:00 +0000</pubDate><guid isPermaLink="false">https://blog.insanegenius.com/2010/12/31/trend-micro-safesync-neat-but-unreliable/</guid><description>&lt;p&gt;I wanted to write about &lt;a href="http://us.trendmicro.com/us/products/personal/safe-sync/"&gt;Trend Micro SafeSync&lt;/a&gt;, but it reminded me of my &lt;a href="http://en.wikipedia.org/wiki/Streamload"&gt;Streamload&lt;/a&gt; experience, and I ended up writing &lt;a href="https://blog.insanegenius.com/2010/12/will-your-online-backup-or-sync-and.html"&gt;this&lt;/a&gt; instead. This time I am really going to write about SafeSync.&lt;/p&gt;
&lt;p&gt;SafeSync is another online backup and sync and share application. Actually, they offer both online storage through a mapped drive, and syncing folders online, this makes it unique compared to many existing offerings.&lt;/p&gt;
&lt;p&gt;I have used almost all online backup and sync and share type applications out there, my favorite remains &lt;a href="http://www.dropbox.com/"&gt;DropBox&lt;/a&gt;. SafeSync used to be &lt;a href="http://en.wikipedia.org/wiki/Humyo"&gt;Humyo&lt;/a&gt;, before being acquired by Trend. I used Humyo when they were in Beta, it was just ok, but between then and now their product seems to have come a long way.&lt;/p&gt;</description></item><item><title>Zotac ZBOXHD-ID11 4GB RAM</title><link>https://blog.insanegenius.com/2010/05/18/zotac-zboxhd-id11-4gb-ram/</link><pubDate>Wed, 19 May 2010 02:46:00 +0000</pubDate><guid isPermaLink="false">https://blog.insanegenius.com/2010/05/18/zotac-zboxhd-id11-4gb-ram/</guid><description>&lt;p&gt;In this post I describe my experience while upgrading the BIOS, in order to support 4GB of memory.&lt;/p&gt;
&lt;p&gt;This is the third post in a &lt;a href="https://blog.insanegenius.com/2010/05/zotac-zbox-mini-pc-zboxhd-id11.html"&gt;series of posts related to the Zotac ZBOX ZBOXHD-ID11&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;Summary:&lt;br&gt;
- 4GB is supported after upgrading the BIOS.&lt;br&gt;
- BIOS has to be updated using less than 4GB, else ID11 fails to post.&lt;/p&gt;
&lt;p&gt;[Update: 20 May 2010]&lt;br&gt;
After writing this post, the machine started bluescreen / BSOD crashing.&lt;br&gt;
Mostly MEMORY_MANAGEMENT / 0x0000001A errors, with occasional 0x000000BE and 0x0000003B crashes.&lt;br&gt;
When I initially installed the 4GB RAM, I ran &lt;a href="http://www.memtest.org/"&gt;memtest&lt;/a&gt; for one cycle, and the RAM tested fine. I just reran memtest, and it is reporting the memory as bad.&lt;br&gt;
I replaced the memory with a new stick, I ran memtest overnight, and everything seems back to normal.&lt;br&gt;
I hope it was just a bad stick, and not the ID11 that killed the memory.&lt;/p&gt;</description></item></channel></rss>