Posts tagged ‘Microsoft Windows’

PS/2 keyboard one way to get your Windows 10 computer back after bricking


Everybody wants PS2. Still from The Professionals episode ‘Servant of Two Masters’.

I read this article in The Guardian, thinking: surely, after Microsoft rolled out some terrible updates, it wouldn’t be so stupid as to do one that bricks customers’ computers again? Especially after the bug was reported a month ago.
   The April update worked reasonably well, though I lost my wallpaper. But everything else was there, and I was using Vivaldi, which is a Chromium-based browser.
   Then I rebooted.
   That was it: my computer was bricked. The first boot, a very tiny rotating circle eventually appeared, but I couldn’t do anything except move the circle with my mouse. Subsequent reboots just resulted in a black screen—something, I must say, I had already encountered with an earlier Windows update that saw my having to take the PC back to the shop.
   I rebooted the computer three times to force it into recovery mode, but then there was another problem: neither mouse nor keyboard worked. It was as though USB was dead.
   Out of sheer luck I had a PS/2 keyboard that was unused, and after more forced reboots, I was able to use the old keyboard to look at various recovery options. Remember: no input device on USB works, and this was a bug that had surfaced with the last update in February.
   Forget system restore: the April update is a fresh OS, so there are no restore points.
   I had no choice but to roll back to the previous version I had installed.
   And here I am, back again, an hour wasted. It would probably be longer if I didn’t have an SSD.
   Microsoft, get your QC sorted, because this current model you’ve employed over the last few years simply does not work. I have spent more hours on these updates than with any OS you have ever rolled out, and that includes XP Service Pack 3 on a comparatively ancient system.
   And if you get stuck like I do, and like all those in The Guardian’s article did, I hope you still have a way of plugging in a PS/2 device and have an old-school keyboard lying around.

Tags: , , , , , , , ,
Posted in China, design, globalization, marketing, technology, USA | No Comments »

When Microsoft says your Windows 10 needs a reset or full reinstallation, they might be wrong


As many of you know, between around December 8 and February 2—dates during which I had Microsoft Windows 10’s fall Creators update without the January 31 cumulative patch—my computer suffered roughly three to six BSODs per day. Going on to Bleeping Computer was helpful, but Microsoft’s wisdom tended to be hackneyed and predictable.
   While I was lucky at Microsoft Answers and got a tech who wasn’t rehashing remarks from other threads, eventually he gave up and suggested I download the old spring Creators update, if that was the last version that was OK.
   I never had the time, and on February 2, I got the cumulative patch and everything has been fine since.
   It means, of course, that Microsoft had released a lemon at the end of 2017 and needed a big patch to deal with the problems it had caused. No word to their people on the forum though, who were usually left scratching their heads and concluding that the only option was a clean installation.
   I had bet one of the techs, however, that there was nothing wrong with my set-up, and everything to do with the OS. We know Windows is no longer robust because of the QC processes Microsoft uses, with each team checking its own code. That’s like proofreading your own work. You don’t always spot the errors.
   I said I could walk into any computer store and find that the display models were crashing as well.
   Last weekend, I did just that.
   Here are the Reliability Monitors of two Dell laptops running factory settings picked at random at JB Hi-fi in Lower Hutt.

Above: The Reliability Monitors of two display Dell laptops at JB Hi-fi in Lower Hutt, picked at random.

Above: My Reliability Monitor doesn’t look too bad by comparison—and suggests that it’s Microsoft, not my set-up, that was responsible for the multiple BSODs.

   The Monitors look rather like my own, not scoring above 2 out of 10.
   They are crashing on combase.dll for the most part, whereas mine’s crashing on ntdll.dll. Nevertheless, these are crashes that shouldn’t be happening, and a new machine shouldn’t have a reliability score that low.
   For those of you who suspect you have done nothing wrong, that your computer has always worked till recently, and you practise pretty good computer maintenance, your gut’s probably right. The bugs aren’t your fault, but that of slapdash, unchecked programming. I doubt you need full reinstallations. You may, however, have to put up with the bugs till a patch is released. It is the folly of getting an update too early—a lesson that was very tough to relearn this summer.

Tags: , , , , , , , , , , ,
Posted in New Zealand, technology, USA | No Comments »

The folly of Windows 10


Now that I’ve gone four days without a BSOD, it does appear Microsoft realized it had rolled out another lemon, and, nearly two months later, patched things. Goodness knows how many hours it has cost people worldwide—the forums have a lot of people reporting BSODs (maybe it’s confirmation bias, but I really don’t remember this many, ever). I posted this in a discussion entitled ‘Windows 10 is a nightmare!’, and the comments there make for sobering reading. A small number have had to purchase new computers; others report that the OS has made their computers unusable or that countless hours were spent trying to fix things. I can believe it. My addition:

I have to concur with the original poster: Windows 10 has been, hands-down, the most shockingly unreliable OS ever made, by anyone, anywhere.
   I have spent more time here for this OS than at any other time with Microsoft products—and Windows 10 has been terrible from day one.
   Most recently, I have had multiple BSODs per day since the fall Creators update was installed, and until Microsoft rolled out a patch at the end of January that finally fixed problems of its own making. If your computer is BSODing multiple times a day, with 800-plus events in the reliability monitor per week, then you can imagine how little work gets done. Things finally calmed down on February 2, when I received the cumulative update. You can see the thread for yourself here: I actually feel sorry for the MS tech who stepped in, because he’s solving problems a crap product with faults not of his own making. They won’t be bugs that are in his handbook. Looking at this part of the forum alone, BSOD comes up a lot in the subject lines, more than I ever remember. So it isn’t us, Microsoft, it’s you.
   Going right back to day one, I can’t believe how many threads I’m involved in. Windows 10 started up differently each day, as it would forget its own settings each day. Some days Cortana worked, other days it didn’t. Sometimes I had the UK keyboard (which I had never once installed), other days the US. In November 2015 I had to post a queryto ask how many hours it would take for a Windows 10 machine to shut down. That’s right, hours. At least that’s better than some of you who commented earlier who can’t get yours to start up.
   Initially, Cortana required fiddling with each day to get it to work. Notifications once went back in time—on a Saturday I began getting notifications from the previous Thursday. None from Friday though, they all vanished. Windows began forgetting my default browser and default PDF application, and no, you couldn’t fix either from the standard settings. The Anniversary update took 11 attempts to install on this PC—and one of them screwed things up so badly my PC was bricked and wound up at the shop, where I had to spend money to get it fixed urgently. (I joked at the time it was called Windows 10 because you needed more than 10 attempts to do anything.) It never installed on my laptop at all: by the time Creators spring came round, the one update that was compatible with my laptop, it had been through 40 unsuccessful update cycles.
   There’s still more that I can share, and you can probably find it via my profile. I would add more but on the original reply I actually hit a limit on these boxes. I guess Microsoft has a limit to how much bad news it can take from one user.
   Microsoft has actually changed its QC procedures for the worse—that is a matter of record—and you’d think after three years of abject failure they would switch back. We see the same hackneyed official responses here day in, day out. They need to spend more time getting things right before they ship their OSs, and spare their community people a lot of wasted hours with solutions that generally do not work. In my latest thread, I fixed it—yes, the tech helped a bit, but ultimately I had to listen to my gut and believe that MS had messed up. I was right, but wow, at a massive cost to my real job with days lost to being Microsoft’s unpaid technician.

   It is good, however, to come out the other side (knock on wood)—and despite the countless hours spent, I was once again right, and conventional wisdom was wrong. I’m not sure if that’s something to be that proud of. A healthy mistrust of big firms stands one in good stead nevertheless, and remember, every industry has thick people making stuff.

Tags: , , , , , , , ,
Posted in technology, USA | 2 Comments »

The path of least resistance: we humans aren’t discerning enough sometimes


I came across a thread at Tedium where Christopher Marlow mentions Pandora Mail as an email client that took Eudora as a starting-point, and moved the game forward (e.g. building in Unicode support).
   As some of you know, I’ve been searching for an email client to use instead of Eudora (here’s something I wrote six years ago, almost to the day), but worked with the demands of the 2010s. I had feared that Eudora would be totally obsolete by now, in 2018, but for the most part it’s held up; I remember having to upgrade in 2008 from a 1999 version and wondering if I only had about nine years with the new one. Fortunately, it’s survived longer than that.
   Brana Bujenović’s Pandora Mail easily imported everything from Eudora, including the labels I had for the tables of contents, and the personalities I had, but it’s not 100 per cent perfect, e.g. I can’t resize type in my signature file. However, finally I’ve found an email client that does one thing that no other client does: I can resize the inbox and outbox to my liking, and have them next to each other. In the mid-1990s, this was one of Eudora’s default layouts, and it amazed me that this very efficient way of displaying emails never caught on. I was also heartened to learn from Tedium that Eudora was Apple co-founder Steve Wozniak’s email client of choice (‘The most important thing I use is Eudora, and that’s discontinued’). I’m in good company.
   However, this got me thinking how most users tolerate things, without regard, in my opinion, to what’s best for them. It’s the path of least resistance, except going down this path makes life harder for them.
   The three-panel layout is de rigueur for email clients today—all the ones I’ve downloaded and even paid good money for have followed this. Thunderbird, Mailbird, the oddly capitalized eM. All have had wonderful reviews and praise, but none allow you to configure the in- and outbox sizes. Hiri’s CEO says that’s something they’re looking at but right now, they’re not there, either. Twenty-plus years since I began using Eudora and no one has thought of doing this, and putting the power of customization with the user.
   But when did this three-panel layout become the standard? I can trace this back to Outlook Express, bundled with Windows in the late 1990s, and, if I’m not mistaken, with Macs as well. I remember working with Macs and Outlook was standard. I found the layout limiting because you could only see a few emails in the table of contents at any given time, and I usually have hundreds of messages come in. I didn’t want to scroll, and in the pre-mouse-wheel environment of the 1990s, neither would you. Yet most people put up with this, and everyone seems to have followed Outlook Express’s layout since. It’s a standard, but only one foisted on people who couldn’t be bothered thinking about their real requirements. It wasn’t efficient, but it was free (or, I should say, the licence fee was included in the purchase of the OS or the computer).
   ‘It was free’ is also the reason Microsoft Word overtook WordPerfect as the standard word processor of the 1990s, and rivals that followed, such as Libre Office and Open Office, had to make sure that they included Word converters. I could never understand Word and again, my (basic) needs were simple. I wanted a word processor where the fonts and margins would stay as they were set till I told it otherwise. Word could never handle that, and, from what I can tell, still can’t. Yet people tolerated Word’s quirks, its random decisions to change font and margins on you. I shudder to think how many hours were wasted on people editing their documents—Word can’t even handle columns very easily (the trick was usually to type things in a single column, then reformat—so much for a WYSIWYG environment then). I remember using WordPerfect as a layout programme, using its Reveal Codes feature—it was that powerful, even in DOS. Footnoting remains a breeze with WordPerfect. But Word overtook WordPerfect, which went from number one to a tiny, niche player, supported by a few diehards like myself who care about ease of use and efficiency. Computers, to me, are tools that should be practical, and of course the UI should look good, because that aids practicality. Neither Outlook nor Word are efficient. On a similar note I always found Quattro Pro superior to Excel.
   With Mac OS X going to 64-bit programs and ending support for 32-bit there isn’t much choice out there; I’ve encountered Mac Eudora users who are running out of options; and WordPerfect hasn’t been updated for Mac users for years. To a large degree this answers why the Windows environment remains my choice for office work, with Mac and Linux supporting OSs. Someone who comes up with a Unicode-supporting word processor that has the ease of use of WordPerfect could be on to something.
   Then you begin thinking what else we put up with. I find people readily forget or forgive the bugs on Facebook, for example. I remember one Twitter conversation where a netizen claimed I encountered more Facebook bugs than anyone else. I highly doubt that, because her statement is down to short or unreliable memories. I seem to recall she claimed she had never experienced an outage—when in fact everyone on the planet did, and it was widely reported in the media at the time. My regular complaints about Facebook are to do with how the website fails to get the basics right after so many years. Few, I’m willing to bet, will remember that no one’s wall updated on January 1, 2012 if you lived east of the US Pacific time zone, because the staff at Facebook hadn’t figured out that different time zones existed. So we already know people put up with websites commonly that fail them; and we also know that privacy invasions don’t concern hundreds of millions, maybe even thousands of millions, of people, and the default settings are “good enough”.
   Keyboards wider than 40 cm are bad for you as you reach unnecessarily far for the mouse, yet most people tolerate 46 cm unless they’re using their laptops. Does this also explain the prevalence of Toyota Camrys, which one friend suggested was the car you bought if you wanted to ‘tell everyone you had given up on life’? It probably does explain the prevalence of automatic-transmission vehicles out there: when I polled my friends, the automatic–manual divide was 50–50, with many in the manual camp saying, ‘But I own an automatic, because I had no choice.’ If I didn’t have the luxury of a “spare car”, then I may well have wound up with something less than satisfactory—but I wasn’t going to part with tens of thousands of dollars and be pissed off each time I got behind the wheel. We don’t demand, or we don’t make our voices heard, so we get what vendors decide we want.
   Equally, you can ask why many media buyers always buy with the same magazines, not because it did their clients any good, but because they were safe bets that wouldn’t get them into trouble with conservative bosses. Maybe the path of least resistance might also explain why in many democracies, we wind up with two main parties that attract the most voters—spurred by convention which even some media buy into. (This also plays into mayoral elections!)
   Often we have ourselves to blame when we put up with inferior products, because we haven’t demanded anything better, or we don’t know anything better exists, or simply told people what we’d be happiest with. Or that the search for that product costs us in time and effort. Pandora has had, as far as I can fathom, no press coverage (partly, Brana tells me, by design, as they don’t want to deal with the traffic just yet; it’s understandable since there are hosting costs involved, and he’d have to pay for it should it get very popular).
   About the only place where we have been discerning seems to be television consumption. So many people subscribe to cable, satellite, Amazon Prime, or Netflix, and in so doing, support some excellent programming. Perhaps that is ultimately our priority as a species. We’re happy to be entertained—and that explains those of us who invest time in social networking, too. Anything for that hit of positivity, or that escapism as we let our minds drift.

Tags: , , , , , , , , , , , , , , , , , , , , , , , , , , , ,
Posted in business, cars, culture, design, internet, politics, publishing, technology, USA | 2 Comments »

Windows 10, with the BSOD-prone Creators fall update, is calming down


I wonder if we have finally got there with Windows 10’s many BSOD crashes.
   Since my last post on the subject in late January, I have had a few more BSODs, but (knock on wood) things have been more stable for a few days. Then again, I haven’t pushed the computer quite as much. Here’s how the Reliability Monitor is looking:

Changes since my last post included adding lines to eudora.ini to switch Quicktime off, which seems to have stabilized that program, and brought the number of appcrash crash messages down.
   However, when I did get a BSOD a few days ago, it looked like this (again after using Explorer):

A post shared by Jack Yan 甄爵恩 (@jack.yan) on

   The memory dump revealed nothing new; it was the same as the one I saw when all this began (as far as I can make out).
   The big change seemed to have happened after I installed the Intel chipsets, and the number of crashes reduced from dozens to between seven and ten.
   I don’t think I have got to an absolute cure yet, but we are getting closer.
   The cumulative Windows update (KB4058258) released a couple of days ago may have helped, too—if it did, it showed that Microsoft had released a lemon with the fall Creators update and rushed to fix things. The number of fixes during the month of January alone suggested that they knew that the OS was iffy. That update was installed yesterday.

Tags: , , , , , , ,
Posted in technology | No Comments »

Windows Unreliability Monitor


Microsoft should rename Windows’ Reliability Monitor to Unreliability Monitor.
   This isn’t too unusual for Windows 10, is it?

   I’ve put Oracle Virtualbox and Cyberlink Power2Go back on, because it’s becoming more apparent that Windows 10 is incompatible with my hard drives in certain circumstances. It’s always when a drive (including a phone set up as a drive) is accessed that the system BSODs. It may also be a USB incompatibility. To be on the safe side, I have unplugged one of the two external drives I use.
   The Microsoft technician has finally given up and asked I do a clean install. As if I have the time—the last time I did that was on an Imac: it took days to get all the OS X updates and the software up and running again. Bwv848 at Bleeping Computer is, like me, determined. I’ll do a memtest (their latest suggestion) when I get a chance.
   Just another day using Windows 10 then.

PS.: Since the post: as my settings window would not come up (another fault of Creators fall), I deleted everything out of C:\Users\[username]\AppData\Local\Packages\Microsoft.MicrosoftEdge_8wekyb3d8bbwe. That was solved. I also went to Intel to download SetupChipset.exe. Not saying these are solutions to the original cause, and I was largely away from the computer for Sunday. However, I have a real suspicion that, because the computer often BSODs when Explorer (or something relying up on it) is open, there are hard-drive drivers that are failing despite, according to Device Manager, being up to date. One of the modules regularly affected is ntdll.dll, something the Reliability Monitor revealed.—JY

Tags: , , , , , , ,
Posted in technology, USA | 1 Comment »

Another program rendered incompatible with Windows 10’s fall Creators update


It’s fast becoming apparent that Windows 10’s fall Creators update is a lemon, just like the original Windows 10.
   As those of you who have followed my posts know, my PC began BSODing multiple times daily, on average. There were brief interludes (it went for three days without a BSOD once, and yesterday it only BSODed once) but these (now) anomalies don’t really diminish my ‘three to six per day’ claim I made earlier by much.
   And it’s all to do with drivers. I won’t repeat earlier posts but the result was that drivers that came with Mozy, McAfee, Malwarebytes and Oracle Virtualbox caused these. In Mozy’s case, it was an old one. Same with McAfee, the remnants of a program that even their removal tool could not take out. Malwarebytes didn’t even show up in the installed programs’ list, and required another program. In Virtualbox’s case, there were both old and new drivers. They all had to be removed, in most cases manually, because removal procedures don’t seem to take them out. This is a failing, I believe.
   But with all these drivers gone, I still had a BSOD this morning. Four before lunch. The culprit this time was a CLVirtualDrive.sys driver that came with Cyberlink Power2Go, which came bundled when I replaced by DVD burner last year.
   And Cyberlink knows something is wrong with this driver. On December 13, two days after I began getting BSODs, it issued a patch for its latest version. Of course, it leaves those of us with older versions in the lurch, and I was surprised to find that the one it had issued for mine (years old) wouldn’t even run because I was on a bundled OEM edition.
   I’m crying foul. If your program is causing BSODs, then I feel it’s your responsibility to help us out. It shouldn’t matter if it’s a trial version, because this is a window into your business. This signals that Cyberlink doesn’t really want to offer a simple download to prevent users from losing hours each day to fixing their computers, even when they’re partly to blame for the problems.
   Let me say this publicly now: if any of our fonts cause system crashes like this, contact me and I will provide you with fresh copies with which you can upgrade your computer.
   I’m removing Power2Go as I write. It’s superfluous anyway: I only use it because it came as part of the bundle. Windows’ default burning works well enough for me.
   But there’s one thing that Cyberlink’s pages have confirmed: the fall Creators update has problems and it seems to me that it is incompatible with many earlier Windows drivers. We can lay a lot of these problems at Microsoft’s feet. Indeed, based on my experience, you could go far as to say that Windows 10 is now incompatible with many Windows programs.
   That’s all well and good if you have a new computer and the latest software, but what of those of us with older ones who will, invariably, have older drivers or upgraded from older systems?
   Are we now reaching an era where computing is divided between the haves and have-nots? It’s not as though decent new computers at the shops have got any cheaper of late.

Next part: click here.

Tags: , , , , , , , , ,
Posted in technology, USA | 2 Comments »

Mozy driver could have been behind 100–200 BSODs since the Windows 10 Creators fall update was installed


A post shared by Jack Yan 甄爵恩 (@jack.yan) on

Two very helpful people—bwv848 at Bleeping Computer and Sumit Dhiman at Microsoft—have taken me through the steps to figure out what was going on with my Windows 10 desktop computer, on which I’ve had between 100 and 200 BSODs since the Windows 10 Creators fall update arrived.
   Windows claimed that the error was a DRIVER_IRQL_NOT_LESS_OR_EQUAL in tcpip.sys, but we know that that wasn’t the cause of the crash.
   They had both got to the point where the Driver Verifier had to be run again. On the first attempt, the process had identified an Avira driver, although after removing and reinstalling the anti-virus program, the crashes continued. I had found other dodgy things in the Event Viewer, but solving them didn’t get rid of the BSODs.
   Now that I’m back from holiday—and with Windows 10 crashing one more time and costing me more work that hadn’t been backed up—I gave Driver Verifier one more go.
   I had been averse to it because of the crashes that resulted from it, and had a sense it would tell me the same thing it had in December.
   True to form, Windows wouldn’t even load and it BSODed during the boot. But this time, running Windbg on the dump file revealed something called mobk.sys (Mozy Change Monitor Filter Driver), part of a program called Mozy.
   I’ve never heard of Mozy, but it appears to be a back-up program. Checking my driver, it dates from April 2010 and was installed in 2012—around the time I bought the computer.
   It could well have been installed by me as part of a bundle, or by PB (the retailer).
   Mozy wasn’t helpful. They have a forum, but when you sign up to use it, you get to a page where they want to charge you US$109 for one of their plans. Personally, if I was making software, I’d want reports from people like me. It’s not as though the question was complex: I wanted to know if it made sense to delete the offending driver in safe mode, or maybe download a trial version of their program, then remove it, in the hope that the driver would be overwritten and deleted. It’s only been a couple of hours since I Tweeted them, so I don’t expect any replies till tomorrow.
   Rather than wait, I popped into safe mode and deleted mobk.sys from the system32\drivers folder.
   These errors are deeply frustrating and in direct contrast to the stability that my Imacs have exhibited. Even though I’ve tired of OS X, at least I wasn’t losing work because of three to six BSODs per day.
   The advice I can give to others is to create a system restore point, then run the Driver Verifier, and repeat the two processes until a culprit has been identified.
   There are a few silver linings to this: I got rid of certain software which might have been insecure, and the random resets were quite handy in “clearing” the PC sometimes when I was doing work on it remotely.
   I wonder what had changed in Windows between the spring and fall Creators updates that generated this very serious problem. I haven’t seen Windows crash this often since a dying laptop, on Vista, needed a fresh OS installation (it now runs Ubuntu). I’m still of the mind that Microsoft shipped a lemon, given that I’ve had no end of problems with this OS since it launched, from inconsistent behaviour (Windows 10 would originally be different each time it booted up, from Cortana settings to which keyboard it believed I was using), to very difficult updates (Anniversary took 11 attempts on this PC and never made it on to my laptop even after 40 attempts; it only updated to Creators because all other updates would fail).
   While I can understand that there was no way either Mozy or Microsoft could have checked on a 2010 driver for compatibility, and there are so many configurations of Windows out there, there’s still no escaping that Windows 10 could have shipped with fewer bugs. Happily, as it turned out, the troubleshooting procedures may have worked, even if things wound up taking a month.
   I’ll blog again if I’m wrong about Mozy.

PS. (January 18): After 24-plus hours with no crashes, I got another one, with the same message. Following my own advice, I ran the driver verifier again. Windbg pointed this time to Oracle Virtualbox. I intentionally ran an older version of this because since 2015, no newer version would work due to its hardening feature. Faced with no choice but to update, it had the same error which, finally, I traced to Mactype. This was the error, for those searching:

The virtual machine ‘Windows XP’ has terminated unexpectedly during startup with exit code -1073741819 (0xc0000005). More details may be available in ‘C:\Users\User\VirtualBox VMs\Windows XP\Logs\VBoxHardening.log’.

Result Code:
E_FAIL (0x80004005)
IMachine {85cd948e-a71f-4289-281e-0ca7ad48cd89}

The key is to insert these three lines into Mactype.ini:


   The error also picked up that there were McAfee drivers left behind from what should have been a full removal. I ran mcpr.exe, found in a thread with the ever-helpful Peter (Exbrit on the McAfee forums). Mcpr.exe did not remove the three drivers, so I took them out manually (despite this going against expert advice): mfeclnrk.sys, mfencbdc.sys and mfencrk.sys. There was also a driver from Malwarebytes, which I downloaded after expert advice in the wake of the damage done by Facebook and its forced download in 2016. Malwarebytes had to be removed with a program called mb-clean as it didn’t show up in the Windows 10 programs’ list.
   One important point: when the system restored itself after the latest crash, it appeared the old mobk.sys reinstalled itself into system32\drivers. I removed it again in safe mode. I’ve since created multiple restore points so hopefully none of the now-removed drivers resurface to cause problems again.
   I am very happy that I’m running the latest Virtualbox, too, since posting in 2015 resulted in no solid leads. It’s why I’m posting all of this stuff, in the hope others find it useful.—JY

P.PS. (January 22): No crashes for three days, I update both the Microsoft and Bleeping Computer threads with the good news, and within nine minutes, bam! Oracle VM Virtualbox is to blame again, if the driver verifier is accurate. That was yesterday. Today, I attempted to remove the program from the Windows Control Panel. Merely removing it caused three BSODs for three attempts, literally within minutes of each other. I booted into safe mode once, tried to remove it (I couldn’t), then back to the regular mode. I was then able to remove Virtualbox. I have since reinstalled it—let’s see what happens next.—JY

P.P.PS. (January 23): Two BSODs this afternoon, still so very disappointed software is this unreliable today. Removing a networking driver from Virtualbox has made no difference. Same error as before. I haven’t re-run driver verifier, but I have now updated MacType to the latest version and double-checked the ini file changes are still there.—JY

P.P.P.PS. (January 24): MacType update did nothing. Bwv848 recommends removing Oracle Virtualbox altogether. I may have to do that, and reinstall it only when I need it, and see what happens. Sumit at Microsoft has given up for the time being.—JY

P.P.P.P.PS. (January 25): After one more crash despite some tweaking of the power options last night, I removed Oracle Virtualbox this morning. There were five remaining drivers that removal did not address, two from the latest version (VBoxNetAdp6.sys and VBoxNetLwf.sys) and three from the old one (VBoxNetAdp.sys, VBoxNetFlt.sys and VBoxUSB.sys). I manually removed them. No crashes since, though I will be interested to know if reinstalling, without any of the old drivers present, will make a difference.—JY

P.P.P.P.P.PS. (January 26): Got to its first crash by 11.45 a.m. Driver verifier now blames CLVirtualDrive.sys. Found one user on Virtualbox’s forum who had the DRIVER_IRQL_NOT_LESS_OR_EQUAL crash but the mod doesn’t like me helping out (very protective people, who don’t like their favourite software criticized). A system restore saw Oracle Virtualbox return, even though I made a restore point long after I deleted it. Let’s see what CLVirtualDrive.sys is. Four BSODs before noon. Man from Mozy got back to me—the first contact other than on Twitter—because they wound up spamming me and never responded to my original support question. Amazing how a few events—including Facebook’s forced download in 2016—have directly led to this time-wasting point in 2018.—JY

Enough postscripts. The next episode of the saga is here.

Tags: , , , , , , , , , , , , ,
Posted in technology, USA | 3 Comments »

Solving my BSODs with Windows 10 Creators fall update—it’s not the usual culprits


Amazingly, Microsoft Windows 10 Creators fall update arrived last week on my desktop PC, and it took all of 25 minutes to do (running a Crucial 525 Gbyte SSD). (Add an extra 35 minutes for me to put my customizations back in.) This is in contrast to the Anniversary update, which took 11 attempts over many months, including one that bricked my desktop PC and necessitated repairs back at PB Technologies.
   However, I began getting regular BSODs, with the error message ‘Driver_IRQL_not_less_or_equal’ (all in caps), saying that tcpip.sys was the system file affected. An analysis of the minidump file using Windmp revealed that the cause was netio.sys (add ‘Netio!StreamInjectRequestsToStack+239’ if you want the full line).
   There were few people with a similar issue, though I can always count on people in the industry who help—usually it’s folks like Cyrus McEnnis, whom I have known since we were in the third form at Rongotai College, or Aaron Taylor, or, in this case, Hayden Kirk of Layer3, who pointed me in the right direction (that it was either hardware or drivers).
   First up, Windows Update isn’t any help, so let’s not waste any time there.
   Secondly, Device Manager was no help, either. Getting Windows to find updated drivers doesn’t necessarily result in the latest ones being downloaded. If the file that was crashing was tcpip.sys, then it does hint at something afoot with the TCP/IP, i.e. the networking.
   I couldn’t solve it through a virus scan, since a full one would never complete before I got another BSOD. (In fact, one BSOD knocked out Avira, and it had to be reinstalled.)
   It wasn’t Nvidia Control Panel, which was a regular culprit that people pointed to. I did remove and reinstall, just to be on the safe side, but that didn’t fix the problems.
   I had used the ‘Update driver’ option in the Device Manager for my network adapter, the Realtek PCIe GBE Family Controller #2, and while it did update, it wound up on version 1.
   Without much to lose, I decided to feed in the full name of the adapter to look for drivers. Realtek’s website took me here, where I selected the Win10 Auto Installation Program.
   This installed a driver that was version 10, and last updated on December 1, 2017, according to Realtek’s website (the driver is dated October 3, 2017).
   So far I’ve been BSOD-free, and things appear to have settled down.
   If you’re interested, I filed a bug report at Bleeping Computer, and my dump files are there.
   Also remarkable is that my Lenovo laptop, which had attempted to install various Windows 10 updates for over a year, and failing each time (I estimate over 40 attempts, as usually I let it run most times I turn that laptop on; as of April 18 it was at 31 attempts). That laptop was on near-factory settings, so the fact no Windows update would work on it was ridiculous. (I’ve even seen this at shops, where display laptops have Windows update errors.)
   Again, there’s plenty of advice out there, including the removal of Avira as the antivirus program. I tried that a few times over the first 31 attempts. It made no difference.
   I am happy to report that over the weekend, the spring Creators Update actually worked, using the Update tool, and the only alteration I made to Avira was the removal of its System Speedup program.
   And as of this morning, the same computer wound up with the newer fall update.
   There haven’t been BSODs there but to me it confirms that Microsoft’s earlier updates were incredibly buggy, and after two years they’ve managed to see to them.
   I can report that the advice on the Microsoft forums didn’t work and I never needed to result to using the ISO update methods. The cure seemed to be patience and allowing multiple attempts. Since Windows 10 behaves differently each time you boot it up anyway, one of those times might have been compatible with the update patches.
   Hopefully the above helps those who have been struggling with getting their Windows 10s to update. I’d advise against attempting some of the more extreme solutions, especially if your gut or your logic tells you that you shouldn’t need to go to those lengths just to update, when easier solutions worked perfectly fine when you were on Windows XP or Windows 7.

PS., December 12: After a day without crashes post-driver-update, they returned the following day. Investigations are ongoing … I’ve updated the Bleeping Computer link page.

P.PS.: Updated a remote-access program as well as Java (which hadn’t updated despite it having been set to automatic updates). During the former, I had another BSOD as it tried to shut down various network services. Wish I wrote down what they were. However, it does point at a networking issue. Also I saw some hackers in Latvia and the Netherlands try to get in to the system and blocked their IPs. Coincidentally, they had not attempted anything yesterday, which was the day I didn’t have BSODs.

P.P.PS.: Event Viewer revealed those hackers were really going for it. Hayden says it was a ‘port exhaustion hack’, which does, logically, affect TCP/IP. I’ve replaced the remote desktop program, though Java 8 wound back on the desktop because of another program I run. The PC has stayed on since the afternoon, so hopefully that is that. It does mean a day wasted on IT—and it does seem worrying that Windows 10 Creators fall has potentially more holes by default, or somehow falls over more easily when attacked. Those attacks had always come, but they never resulted in BSODs. It was, overall, more robust in updating but it may have some other problems, if the last few days are any indication.
   The external HD was also moved to another USB port. There could be a connection to USBs, as it crashed once after my partner unplugged her phone, and on another occasion I distinctly heard the external HD activate just before a BSOD.

P.P.P.PS.: The above never solved it, but one month on, this might have done the trick.

It didn’t do the trick. Here’s the next part.

Tags: , , , , , , , , , , , , ,
Posted in design, technology, USA | 2 Comments »

Capricious Cortana


I have never seen a program as inconsistent as Microsoft’s Cortana.
   We were always taught that computers were very logical, that they all followed a certain set of code each time.
   Not so Cortana, which has had more different behaviours than anything I have ever seen.
   When I run into technical issues, it’s the fault of certain parties for failing to anticipate the behaviour of ordinary people or for adopting a head-in-the-sand position to bugs that are very real or crooked company policies. These have been covered many times on this blog, such as Six Apart’s old Vox site refusing to accept a log-in, or Facebook ceasing to allow likes and comments; and then there’s the human dishonesty that drove Google’s failures on Blogger and Ads Preferences Manager.
   This still fits into those categories, as Microsoft’s engineers on its forums are peddling standard responses, none of which actually work. One even damaged my start menu and forced a system restore.
   The bugs are so varied, and that to me is strange. Normally bugs will take one form and one form only. Address that, and your problem is solved.
   However, Cortana has done the following.

Day 1. Refused to work, with Windows saying US English was not supported (curious, given it’s an American program). I downloaded the UK English language pack. Worked perfectly for the rest of the day. How novel.

Day 2. Refused to work, but prompted me to set up again, and then it worked.

Day 3. Cortana becomes deaf. No prompts to set up again, but I do it anyway. It works again.

Day 4. I play with the microphone settings (by ‘play’ I mean clicking on a setting but not actually changing it) and Cortana would work intermittently.

Day 5. Cortana would not work except at night, and I play the movie quiz.

Day 6. Cortana claims my Notebook is inaccessible because I am offline. Clearly I wasn’t offline because I was doing stuff online.

Day 7, daytime. Cortana refuses to answer and sends all queries to Bing. The Notebook screen just displays animated ellipses.

Day 7, evening. Cortana works after I plug in my headphones (which has a microphone). After I unplug it, my regular webcam microphone starts picking up my voice again. Cortana works again.

Day 8. Cortana hears me say ‘Hey, Cortana,’ but then just goes to ‘Thinking’ for minutes on end. It might display, ‘Something’s not right. Try again in a little bit,’ after all that. Apparently Cortana still cannot retrieve my interests because I am ‘offline,’ which is amazing that I’m posting to this blog right now.

   The microphones work with other programs. And browsing the Windows forums, this has been going on since July. The November service pack was supposed to have fixed a lot of issues, but clearly not.
   I’ll be fascinated to see what it does tomorrow. But I am tired of the BS that their techs are dishing out as “solutions”. I’m being reminded why I don’t use Word or Outlook: because I have a short fuse when it comes to crap.

PS.: Day 9, same as day 8. Day 10, asked a few set-up questions (again) and it works, though ‘Thinking’ still came up for a few seconds on the first go. Day 11, worked without intervention (amazing!). Day 12, see day 7 (evening).—JY

Tags: , , , , , , ,
Posted in India, internet, technology, USA | 2 Comments »