|
Share this page
Quick links
Add feed 
|
|
The Persuader
My personal blog, started in 2006. No paid or guest posts, no link sales.
Posts tagged ‘errors’
05.08.2020
With the new season of Alarm fĂŒr Cobra 11: die Autobahnpolizei nearly upon us, I decided Iâd pop into my Facebook group (Iâm still an admin) to see what had been happening. Iâve been there a few times this week and I have discovered some of the siteâs latest features.
Groups: these now have three posts. Thatâs it. Three. It doesnât matter how long they have been running, Facebook doesnât want you to be bothered by history or anything so stupid. Therefore, after the third post (fourth if youâve just posted something), youâve reached the end. Saves heaps on the server bills, since I guess theyâre not as rich as they would have us believe.
(This bug has been around for years but now itâs the norm, so maybe they eventually figured out it was a cost-saving feature.)
On groups: welcome to the end of Facebook. This is the last post.
Comments: donât be silly, you shouldnât be able to comment. This is a great way for Facebook to cut down on dialogue, because they can then just propagate nonsense before an election. We know where Zuckâs biases are, so they want to be a broadcaster and publisher. You can select the word âReplyâ in the reply box, you just canât type in it. (Again, an old bug, but it looks like itâs a feature. Iâm still able to like things, although on many previous occasions over the last decade or more that feature was blocked to me.)
Commenting: they let me have one reply, but replying to someone who has replied to you? Forget it, it’s impossible.
In the reply box, you can highlight ‘Reply’ but you can’t type in there. That would be too much to ask.
Notifications: these never load, had haven’t done for a long time. Remember the ad preferencesâ page? They donât load, either, so Facebook has now extended the âcircleâ to notifications. If you donât see notifications, you wonât need to continue a threadânot that you could, anyway, since they donât let you comment.
If you knew what your notifications were, you might stay longer and post stuff that makes sense. No, Facebook is for people who want to spread falsehoods among themselves. You have no place here.
Messages: why not roll out the same spinning circle here, too? They should never load, either, because, frankly, email is far more efficient and everyone should just give up on using Facebookâs messaging service.
Time to go back to email: if you were ever silly enough to rely on Facebook for messaging, then you’re out of luck.
I once thought that I encountered bugs on Facebook because I was a heavy user, but as I havenât even touched my wall since 2017, this cannot be the reason. I also used to say their databases were âshot to hellâ, which could be the case. And I still firmly believe I encounter errors because Iâm more observant than most people. Remember, as Zuckâs friend Donald Trump says, if you do more testing, youâll find more cases.
I’ve even found the “end” of Instagram, at the point where nothing will show any more.
The end of Instagram: when you can find the limit to the service.
No one’s posting much these days. In the early 2010s, there’d be no way I’d ever get to see the end of my friends’ updates.
Solution: donât use Facebook. And definitely don’t entrust them with your personal data, including your photosâeven if you trust them, they’ll potentially get lost. From what I can tell, the site’s increasing inability to cope suggests that its own technology might fail them before the US government even gets a chance to regulate! Andâthe above topics asideâit may be time to regulate Facebook and pull in the reins.
Tags: 2010s, 2020, 2020s, bug, bugs, computing, error, errors, Facebook, Instagram, privacy, technology, trust
Posted in internet, politics, technology, USA | No Comments »
23.08.2019
I really should not have wasted my time with Google, as My Business (see yesterday’s post) reminded me just why I donât use the siteâitâs not only the privacy issues, but the fact that things donât work as advertised, which has always been the case with Google.
Youâve already seen that itâs impossible for me to add my businessâs address to Google My Business. Thatâs not a huge surprise, since the last time I had Google Earth, they didnât even know that the White House was at 1600 Pennsylvania Avenue NW, Washington, DCâand that was version 5 of their software. If these folks donât even know where their own president is, I canât expect them to deal with Tawa.
However, we do have an address in Manhattan, so I attempted to add that. After all, it seemed I was verified, or at least close to being verified, so why not get around the existing entryâs non-verification (as it goes through the process of sending a postcard, and, frankly, no one at the office can be botheredâthey feel about Google much the same way as I).
There was no difference: Google still wanted to send a postcard, so I thought I should delete the entry.
Well, you canât. There isnât anything in the documentation that says itâs this hard. Following their own instructions, I delete the location, and nothing happens.
Seems simple enough: Google says I should select ‘Remove location’.
Google wants me to confirm. I click ‘Remove’.
Like a lot of US Big Tech, they make it appear that they’re busy doing something âŠ
⊠when in fact, nothing is being done.
Maybe I should go in and edit it, as perhaps Google canât deal with three businesses called Lucire.
Good luck with that. I click on the entry and just get taken to a page where I am asked to select an account. I only have one, so I click on it three times, and I get taken back to the My Business home page with the four locations on it.
Clicking on the last entry goes to this page. Click my email address three times, and you’ll go back to the start.
And ad infinitum. You can attempt to do this as many times as you like, but it is impossible to delete a location, contrary to what Google claims, it is impossible to edit some locations, contrary to what Google claims.
Itâs no wonder the Dashboard was so full of discrepancies because, like Facebook, like Twitter, like Amazon, their databases are probably shot to hell, and nothing works as they say they do. I may be a layman on such subjects but it appears the more they add, the more the house of cards collapses.
I suspect some of these errors are intentionalâwe know Google intentionally programs in more pages so they can claim increased page-views to their site (e.g. if you click on an image in the Google image search, they take you to an intermediate page firstâ10 years ago, they took you straight to the page)âso by offering a website that is SNAFU, youâre forced to increase the page-view count. (Of course, if we do holding pages and forwarding pages to our sites, Google penalizes us.) When such obvious inefficiencies are introduced, you know that the reasons arenât all kosher.
So there you are: even if you wanted to delete an entry (and I was sorely tempted to yesterday), Google won’t let you.
Google: deceitful and useless. And a total waste of time. I’m so glad I don’t use this site in any real wayâapart from the time it sucked over the last 24 hours.
Tags: 2019, bugs, errors, Google, technology, USA
Posted in business, globalization, publishing, technology, USA | No Comments »
23.07.2019
Iâve found some forum entries about this, but they date back to the beginning of the decade. I alerted Jetstar to this in March, and the problem has worsened since then.
Basically, I canât book online, and I donât know why. Consequently, I booked one flight with Air New Zealand and only managed, after huge effort, to get the other (for a colleague) with Jetstar.
Back in March, I couldnât book with Vivaldi, but I was able to switch to Firefox. I let Jetstar know.
Now, this strategy does not work.
Before you suggest it, cookies and caches have been cleared.
Hereâs what happens after Iâve selected the cities and the dates, and I go to select times. Letâs begin with Vivaldi on Windows, which is based on Chromium (which, as we know, is what Chrome, the browser Jetstar suggests you use, is based on):
Switching to Firefox now results in this:
Switching to Edge on the same PC gives this:
Fortunately, I also own Macs, so hereâs what Firefox for Mac returns:
The only browser that works with the Jetstar website: Safari on Mac. As I’ve sold my Ubuntu laptop, I was unable to test using that OS.
Not many people would go to that effort, and while Jetstarâs Twitter staff (after some pushing from me in DMs) said they would refer it on, I donât expect anything to happen.
Maybe Chrome would work, but Iâm not ever going to download it to find out. Why invite Google on to your computer? But if that is the case, it seems foolish to limit yourself to such an invasive browser. My experience is that whatever is blocking me from booking with Jetstar (some may argue that this is a good thing), it is expanding across browsers.
Tags: 2019, airline, Aotearoa, Apple, Apple Macintosh, bugs, Chrome, Chromium, ecommerce, errors, Jetstar, Microsoft Edge, Microsoft Windows, New Zealand, technology, travel, Twitter, Vivaldi, web browser, web development, website
Posted in business, design, internet, technology | No Comments »
10.05.2018
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: 2018, bugs, computing, errors, media, Microsoft, Microsoft Windows, technology, The Guardian
Posted in China, design, globalization, marketing, technology, USA | No Comments »
25.04.2018
Updated in a follow-up post: click here.
Since Facebook bought Instagram, itâs been getting buggier, of course.
Iâve complained about Instagram uploading a series of posts in a totally different order to what I had (which, on ANZAC Day, made it difficult for anyone to follow the story I was trying to tell on my account when the order is 2, 1, 5, 4, 3, 6, 7).
Video (2) was an interesting one, because Instagram allowed me to post something that was 2 minutes, 6 seconds long, which it had never done before (or since).
I thought it odd at the time but given that it was twice as long as normal, I didnât complain. It allowed me to show more of the Air Force band performing ‘Au e ihuâ (Soldierâs Hymn).
I did complain about one particular video featuring our national anthem which Instagram would say was loading, then on checking again, it would vanish. I made three attempts over a two-hour period before it âstuckâ (video no. 3 in the sequence above). I had to wonder if Instagram was picking up the music and flagging it as a copyright violation: after all, YouTube flags static as copyright violations (hat tip to Retrorechercher).
Above: Instagram says these two are loading, but the one featuring our national anthem (the top one) kept vanishing. It never made it on to my account without three attempts.
This morning, on checking the stats, I noticed that no one had viewed the longer video, and, after asking some friends on Twitter, learned that Instagram blocked anyone from seeing it. Itâs like shadow-banning on Twitter: you can see your own stuff, but no one else can. Try it for yourselfâhere’s the link Instagram claims it’s at.
Look at the eighth post down. On my account (top), I can see it. When logged in as someone else (above), I can’t. Instagram’s version of shadow-banning?
Above: What my friend Happyfishmedia saw when clicking through to the link Instagram gave me.
I can still play it straight from Instagram on the web and on my phone.
You can give the MP4 a shot here (and note the URL, which is an Instagram one, and the duration). The thumbnail is here.
However, I canât embed the video the normal way, and any link that it lets me share results in a 404. It all feels very familiar, because this is the sort of bug that Facebook used to cook up, e.g. on days when you couldnât post, like, comment or share, or tag yourself in a photograph.
I might save the two-minute-long video separately in case thereâs a way you can tell that it was edited inside Instagram.
To sum up: Instagram will not load content in the same order you do (we already know this); it will permit much longer videos that exceed one minute, but if they let it through, no one will ever see it except you.
We also know that Facebook will pump through any advertising on to Instagram, even in categories you have expressly asked not to be shown.
There you have it, Instagram in 2018.
PS., April 25, 1.19 a.m. GMT: I’ve just tried a 2 minute 50 second video, and it appears it is visible. For how long, I don’t know. Check it out here, or, if the embed’s visible below, have a look.
P.PS., 1.59 a.m. GMT: Looks like four minutes is fine, too. While the first one is still invisible, it does appear Instagram has lifted the one-minute limit, and that’s not something I can find documented anywhere. Still, I’m grateful, because it makes far more sense to show two- to four-minute vids.
P.P.PS., 8.54 a.m. GMT: Just tried one at seven minutes, and it’s hidden. Seems Instagram is very inconsistent on what it shows and what it doesn’t. Link is here (it won’t work) and the MP4 is here.
Tags: 2018, Aotearoa, bugs, errors, Facebook, Instagram, New Zealand, technology, Wellington, Whanganui-a-Tara
Posted in interests, internet, New Zealand, Wellington | 2 Comments »
27.01.2018
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: 2018, bugs, computing, errors, Microsoft, Microsoft Windows, software, technical support
Posted in technology, USA | 1 Comment »
26.01.2018
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: 2018, bugs, computing, customer service, equality, errors, ethics, Microsoft, Microsoft Windows, software
Posted in technology, USA | 2 Comments »
17.01.2018
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)
Component:
MachineWrap
Interface:
IMachine {85cd948e-a71f-4289-281e-0ca7ad48cd89}
The key is to insert these three lines into Mactype.ini:
[UnloadDll]
VirtualBox.exe
VBoxSvc.exe
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: 2010, 2017, 2018, Apple, Avira, bug, bugs, error, errors, Microsoft, Microsoft Windows, Oracle, PB Technologies, software
Posted in technology, USA | 3 Comments »
11.12.2017
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: 2017, Aotearoa, Avira, bugs, errors, Microsoft, Microsoft Windows, New Zealand, Nvidia, Realtek, software, tech support, technology, Wellington
Posted in design, technology, USA | 2 Comments »
08.07.2017
I bought Steven Parissienâs The Life of the Automobile: a New History of the Motor Car, which started off as a good history. Iâm 300-odd pages in now and the mistakes are really worrying. Thereâs also a shocking lack of editing (one part repeated, albeit in different language, and spelling and grammatical mistakes) in the parts I’ve got to now; it’s as though the editor got tired after the first 10 chapters and stopped caring. But the biggest errors are factual.
I am astonished to learn, for instance, that Harley Earl was responsible for the concept of the Ford Thunderbird (p. 255), that Triumph TR7 production was transferred to Speke in 1982 (p. 293, though Parissien later contradicts himself with the correct fact), and that John Z. de Lorean was a protĂ©gĂ© of Lee Iacocca (p. 309). I really have no idea how, but as far as I know, de Lorean was never at Ford, and he had a Chrysler stint long before Iacocca got there. I also never knew that âIn 1968 the Toyota Corolla became the first Japanese car to be manufactured in the USâ (p. 314; that was the year it went on sale there, and from memory the Corolla didn’t get built there till the NUMMI deal in the 1980s) or that the Opel Ascona C was also sold as the Opel Vectra (p. 337). The Italian Job was released in 1969, not 1967 (p. 224).
I am frustrated with this bookâand now it makes me wonder if the stuff earlier on, which I know less about, was accurate.
I can understand an editor not grasping the subject as well as the author but there is less excuse in professional publishing for the other problems. Maybe there are few professional proofreaders left, now that spellchecks have been around for a generation or more. I was prepared to recommend this book even a week ago and tolerated the spelling and grammar, but these factual mistakes are worse than what can be found in Wikipedia, and I often label parts of that site as fiction.
PS. (September 17): How much worse can it get, as I continued through? A lot.
On p. 320, we get an admission that Parissien was wrong on p. 314: the Honda Accord was the first Japanese-branded car to be made Stateside. At least an earlier error was corrected. But they begin again on p. 321: Parissien claims the V30 Toyota Camry dominated the US mid-size car market (it was never sold outside Japan; he’s thinking of the XV10, or the Japanese-market Scepter, which was badged Camry). Correcting his error on p. 322, the Camry was not specifically targeted at the US; it was Toyota’s attempt to create an efficient car from the ground up, and it was not done in 1980, but 1982 (the 1980 Celica Camry was not sold outside Japan). The Paykan deal was cemented long before George Turnbull got to Iran (p. 324), though local content rose in the 1970s for it to be truly Iranian-made and Parissien might mean the shifting of the engine tooling there, if I’m being generous. There is only one world, not multiple ones (also p. 324), unless Parissien knows something about parallel universes that the rest of us don’t. Surely Chrysler managed to launch its T-115 minivan (Dodge Caravan, Plymouth Voyager) before Renault launched the Espace (p. 330), and the Triumph Acclaim was never called the ‘Ronda’ (p. 334), though its successor was.
On p. 360, in a single paragraph, Parissien makes several errors. The MG 6 launched as a five-door car, not his claimed four. There is no such thing as the Roewe 150, in China or elsewhere. The MG 3 has five doors and is not a three-door counterpart to the 6. The five-door MG 6 launched not in 2011, but in 2010, and the Magnette name was only used in the UK for the four-door. The founder of Chrysler was Walter Chrysler, not Walther (p. 364). The Lancia Delta only became a Chrysler in the UK and Ăire, as far as I know (p. 365), and remained a Lancia in most countries. The Belgian designer is Dirk van Braeckel, not van Braeckl (p. 368); Mercedes-Benz never bought an 18·53 per cent stake in Volkswagen (p. 369); and CitroĂ«n’s BX was not the last car in that range to have ‘pneumatic suspension’ (p. 372). The Malibu was not a Saturn, but a Chevrolet (p. 375), and Buick was never sold off (p. 376). The Ford Mondeo did not replace the Telstar in all Asian markets (p. 377), and it shared far more than the ‘windscreen, front doors and rear’ with the Contour and Mystique (in fact, the rear was not shared, though there were common engines, platform, and plenty more). It’s not entirely certain that the US market judged the Contour to be too small (p. 378), but there was a lack of marketing (which would have made an even better story than the one Parissien writes about). Ford subsequently filled the Contour’s niche with the smaller Focus Stateside. The CD338 Fusion was never sold in Australia (also p. 378). Ford never resurrected the Taunus in Germany under Alan Mulally (p. 381)âthis invention is incredible. VAZ did follow up the 2101 with something similar after it ended production in 1983 (not 1984, p. 382), viz. the 2105, which was about as similar as one could get to the 2101.
On p. 384, Parissien claims Acura’s Legend sales were ‘disappointing’, after saying they were ‘beginning to sell rather well’ 50 pp. before. The Hindustan Ambassador was not based on the 1954 Morris Oxford (p. 389): that car was actually the Hindusthan Landmaster. The Ambassador was based on the 1957 Morris Oxford III, and was in production from 1959, not 1958. The Red Flag (or Hongqi) marque was not reborn on an Audi A6 (p. 391), but the marque had been used on a version of the Audi 100 C3 from 1988, and no Hongqi bore an AudiâChryslerâHongqi brand name. The Chinese company is Dongfeng, not Dongfen (p. 391), and Parissien’s claim that the Everus was sold in the west (p. 392) is news to me, as I am sure it is to its own management. I’ll stop there for now.
P.PS. (September 18): Some bedtime reading, or should I say error-finding, last night. On p. 394, Toyota and Aston Martin did not jointly develop the Cygnet: Toyota developed the IQ in 2008, and Aston Martin converted that car to become its Cygnet, and ‘hot hatch’ is a very optimistic description for a city car. Toyota did not launch the Cygnet in 2008 as Parissien claims, nor did it have a say in what customers were expected to purchase the Cygnet: it was aimed specifically at existing Aston Martin owners, not ‘Toyota and Aston expected initial demand to be limited to those who already owned an Aston Martin sports car.’ It was certainly no ‘eccentric experiment’ of Toyota, but of Aston Martin. Volvo never made a model called the A40 (p. 395), and I bet Nissan is surprised to find that the original Qashqai was designed ‘at the firm’s Milan design centre’ (p. 397) when it was designed in London. Maserati never launched a Jeep-based SUV called the Kubang (p. 397), but it did have a concept of that name, and the Levante appeared in 2016 after the book was published. There is no such car as the Porsche Cajun, and if Parissien refers to the smaller Porsche crossover, then that is called the Macan, and it has five doors, not the claimed three (p. 397). The Volkswagen New Beetle was not on a Polo platform (p. 399), but a Golf one, as was its successor (though a newer Golf); and Ford would dispute that its Mustang is a sedan (p. 401). If J Mays’s first name is J (as footnoted), then there is no need to refer to him as ‘J. Mays’ (p. 401). The Ford Ka’s name is not derived from StreetKa (p. 402): that was a model spun off from the Ka in 2002; and some would regard the Mk II model was being superior to the Fiat 500 on which it is based (especially as Fiat adopted some of the changes for its own model). I have yet to see a Smart with a Mercedes-Benz three-pointed star or marque anywhere, unlike Parissien who seems to think they are badged Mercedes (p. 403), and a Smart SUV does not exist unless Parissien is reporting again from his parallel universe (p. 403). There is also no such car as the Kia Exclusive (p. 410).
Tags: 1950s, 1980s, 2010s, 2013, BL, book, car, car design, car industry, cars, errors, Ford, GM, Harley Earl, history, John Z. de Lorean, Lee Iacocca, Opel, publishing, UK, USA
Posted in cars, design, interests, publishing, UK, USA | 1 Comment »
|
