Search results

OK so this is more of a soapbox "rant" than an actual BSOD troubleshooting request. Now that I've run Windows 8, 8.1, Server 2012 and Server 2012 R2 on a bunch of different machines--all of which flawlessly run Windows 7 and Windows Server 2008 R2, I've made some observations about our little...

Hi John, Thank you for the thoughtful reply. I am tempted to rebuild the machine again with the Kingston, this time with Windows 8, and see if the problem returns. Unfortunately it's a fair amount of time and effort to do so, and since the machine is fully built exactly the way it was, except...

Thank you John for the very detailed and thorough explanation. I think part of the issue is that I'm running an OS (Windows 8.1) that isn't technically "public" yet. For those of us with MSDN, the bits are out there for us to play with, but as far as Microsoft and hardware vendors (HP included)...

OK your BSODs are all over the map. Of the three you just posted (the most recent zip had 3 in it), they're all different. The first is NTFS_FILE_SYSTEM, which can be caused by a variety of sources, but most often a failing disk or buggy drivers could be the culprit. A good way to rule out a...

I'm reluctant to call this an "intermittent" problem because it occurs with consistency--at least once per day, and always has the same error (0x133) at the same function (storport!RaidAdapterAcquireInterruptLock). The problem never occurred on the computer when it was just Windows 8; it's...

Do you have any USB devices connected? I took a look at your minidumps. The first is a SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M and the details it contains seem to closely resemble this post: Another BSOD while Idle thread... - Windows 7 Help Forums The second one is the...

Check out this step-by-step guide on resolving WHEA_UNCORRECTABLE_ERROR: What does the WHEA Uncorrectable Error Blue Screen mean in Windows? There's some good stuff there. It talks about running the Windows Memory Diagnostic, which can help rule out faulty memory. It also talks about ruling out...

You're getting the same error each time - WHEA_UNCORRECTABLE_ERROR, with a sub-code (parameter 1) indicating 0x0 Machine Check Exception. The explanation of WHEA_UNCORRECTABLE_ERROR is "A fatal hardware error has occurred. Parameter 1 identifies the type of error source that reported the error...

Secure Boot is a pain. It's very well-intentioned, but it makes booting from flash drives much more difficult. I find booting from flash to install Windows is much faster than using a CD/DVD, but UEFI and Secure Boot involves the extra step of disabling Secure Boot--with its glaring warnings...

It's been my experience that IRQL_NOT_LESS_OR_EQUAL is almost always driver related, and therefore could indicate a hardware problem. It's highly unlikely, although not impossible, a laptop vendor rolled out an OOB build that is quite buggy. In that case, there could be a lot of very unhappy...

Actually the BGA-413 is the package. FT1 is the socket type. List of AMD Accelerated Processing Unit microprocessors - Wikipedia, the free encyclopedia This sounds to be a pretty straightforward CPU replacement.

I'm normally pretty good at resolving BSODs but I've got one I can't quite solve. It occurs at least once a day, and it's the same BSOD with the same error code every time. Having an MSDN subscription, I was eager to try out the Windows 8.1 RTM bits, so I asked my wife if I could borrow her HP...