At Tritech, many things have changed since even just one month ago. Here’s a spiffy list of such things. By the way, my new favorite word is “terse.” The magic of the word “terse” is that practically all of its synonyms not as terse as “terse.” It’s a self-fulfilling definition! ^_^ So, what’s been going on during my silence, you ask? Read on!
I changed my Sylvania G (original, non-Meso) netbook to Windows XP/Linux dual-boot to test some software I’m working on, and discovered that while Windows XP certainly does boot and run in general on the G, some kind of system timer or timing loop is severely out of whack! I wanted to use my little G as a portable gaming machine from the Windows XP install, and to my horror, ZSNES couldn’t decide what speed it wanted to run! Now, I’ve never had a single issue with ZSNES on any computer I’ve ever tried it on, even preferring the Windows port of it over the Linux native one, and not once has a problem existed with ZSNES that I couldn’t find an easy fix for, until now. I’ve been researching the matter and gathering evidence, and I may have a potential answer to the problem.
Remember our post about receiving a STOP 0x0000007E error after moving to an AMD processor from an Intel one? It turns out that the plot has thickened a bit more, and Windows XP SP3 can sometimes cause the same problem–and do so for the exact same reason: intelppm.sys! We’ve also figured out new ways to fix the problem that are easier than in our original post.
Greetings! This article has been moved to the Tritech Computer Solutions page called Fix for STOP 0x0000007E Blue Screen on AMD Platforms. Please update your links and bookmarks to reflect this change.
(If you get a STOP 0x0000007E error after upgrading to an AMD platform from an Intel platform, i.e. replacing an Intel-chipset motherboard with something like a VIA or AMD or nForce or ATI chipset for an Athlon64, here’s a little hint that’ll help you avoid a complete reinstall from scratch: It’s the “intelppm.sys” driver.)