What is the deal with "Your ____ ran into a problem"?
-
To borrow from a post: @TimeBandit said in I'm getting tired of this npm shit:
@blakeyrat said in I'm getting tired of this npm shit:
Users deserve more respect than that.
Like this ?
This isn't the first time I've noticed this usage, "Your _____ ran into a problem." Is a "problem" now a physical object? As in (from the above), "Your computer ran into a [tree / truck / pothole / mudhole / rock / sign / cliff / lake]?" That kind of real, physical object?
We so PC now we can't say, "The operating system on your computer has failed?" So much so that we have to use "ran into a problem" as a euphemism for failed?
I swear I can hear the future exchanges now now:
- Cop: You shot sixteen people! Perp: Well, yeah, I ran into a problem.
- Investigator: The bridge you built collapsed. Architect: It ran into a problem.
- Adjuster: How did you total your car? Insured: Ran it into a problem.
is the deal?
-
Blergo ran into a problem
-
Maybe it's a regional thing, but "to run into" is pretty commonly used as a synonym for "to encounter". For example, "I ran into my old friend Joe last week." That doesn't mean that you physically collided with him.
-
@Dragnslcr said in What is the deal with "Your ____ ran into a problem"?:
Maybe it's a regional thing, but "to run into" is pretty commonly used as a synonym for "to encounter". For example, "I ran into my old friend Joe last week." That doesn't mean that you physically collided with him.
And that runs into money.
-
@CoyneTheDup said in What is the deal with "Your ____ ran into a problem"?:
We so PC now we can't say, "The operating system on your computer has failed?"
Why would you think it's about being PC? It's Microsoft's slightly cringeworthy attempt to sound all informal in things these days. Like outlook omitting "do you" when it says "Want to save your draft?"
-
@CoyneTheDup I don’t see what’s wrong with this — “running into a problem” is a normal expression.
OTOH, I do find the error message as a whole rather patronising. The big smiley at the top makes it look like some school kid wrote it, and the use of “we“ in the second sentence makes it come across as trying to appear human to make the computer less threatening. What’s wrong with something like, “Your PC ran into a problem and needs to restart. This will happen automatically in a few moments.”?
-
@Gurth said in What is the deal with "Your ____ ran into a problem"?:
What’s wrong with something like, “Your PC ran into a problem and needs to restart. This will happen automatically in a few moments.”?
Not aggressive enough.
"You touched something, didn't you. We warned you not to do that. Over and over, we warned you. But you did it anyway, and now you've broken it. We'll try to fix it for you but we're making no promises. What you have to do now is SIT THERE AND KEEP YOUR HANDS TO YOURSELF while we try to figure out how much permanent damage you've done.
"By the way, we're going to restart your PC, which will probably mean tying it up for two hours while we install updates afterwards. No, you can't go get a coffee. Sit down and shut up and maybe you'll finally learn something."
-
Although:
@flabdablet said in What is the deal with "Your ____ ran into a problem"?:
... No, you can't go get a coffee. We will be asking
stupidquestions during the process and there will be a test at the end so Sit down and shut up and maybe you'll finally learn something."...Adds piquancy
-
@CoyneTheDup said in What is the deal with "Your ____ ran into a problem"?:
We so PC now we can't say, "The operating system on your computer has failed?" So much so that we have to use "ran into a problem" as a euphemism for failed?
I would say it more of a 'weasel words' sort of doublespeak rather than the 'politically correct' type. Software vendors (especially MS) don't want to admit they ever fuck up like that, so they sort of backpedal on the severity of the 'problem'.
That having been said, the phrase itself is perfectly cromulent. It's the sort of thing people say quite often, it just sounds odd in this context because it is underplaying the developers' errors, and also because it's a lot less stilted and formal than the phrases previously used in error messages.
-
@Gurth said in What is the deal with "Your ____ ran into a problem"?:
the use of “we“ in the second sentence makes it come across as trying to appear human to make the computer less threatening
I see it as "we" meaning "Microsoft".
"This PC encountered a problem and needs to restart automatically. Microsoft is just collecting some error info first."
Not all bluescreens are software issues - maybe hardware is malfunctioning, which is not part of the OS but is part of the PC.
-
@LB_ Maybe it’s just me, but I prefer passive sentence for things like this. “Some data will be sent to Microsoft,” for instance. At least that way it doesn’t leave the impression that there’s a bunch of people somewhere looking specifically into my problem.
-
"This PC encountered a problem and needs to restart automatically. Some error info is just being collected first."
-
@LB_ For example.
-
@Jaloopa said in What is the deal with "Your ____ ran into a problem"?:
about being PC
@Jaloopa said in What is the deal with "Your ____ ran into a problem"?:
Microsoft
There's your answer.
Filed Under: I'm a PC...
-
99 problems, and now your bitch ran into one?
-
@LB_ said in What is the deal with "Your ____ ran into a problem"?:
I see it as "we" meaning "Microsoft".
Quite so. It's the royal "we", derived from an unshakable belief in the divine right of kings.
-
@lolwhat said in What is the deal with "Your ____ ran into a problem"?:
99 problems, and now your bitch ran into one?
Well, no, that one was all me on accident. She's never walked the same since that night...
-
@LB_ said in What is the deal with "Your ____ ran into a problem"?:
I see it as "we" meaning "Microsoft".
The usage of "we" seems pretty interesting. I think it's certainly indicative of the attitude Microsoft has towards your PC. That is, it isn't "yours", it's "ours".
:( We detected disallowed content on your computer (E_BL_PIRACY). Windows is removing detected blacklisted content... (100%) Finished! We will upload some metadata, and will restart your computer for you...
-
@LB_ said in What is the deal with "Your ____ ran into a problem"?:
Not all bluescreens are software issues - maybe hardware is malfunctioning, which is not part of the OS but is part of the PC.
Oh, yeah, and what's the odds of that? About 9400 software failures per hardware failure?I exaggerate of course, but crappy software yields failures...and there's sure a lot of crappy software. We are TD
... we have proof!@Gurth said in What is the deal with "Your ____ ran into a problem"?:
At least that way it doesn’t leave the impression that there’s a bunch of people somewhere looking specifically into my problem.
Which is an important impression to leave when there is, in fact, no one looking into anyone's problem.
@Dragnslcr said in What is the deal with "Your ____ ran into a problem"?:
Maybe it's a regional thing, but "to run into" is pretty commonly used as a synonym for "to encounter". For example, "I ran into my old friend Joe last week." That doesn't mean that you physically collided with him.
And, you're right, of course. But I didn't even think of that usage, in either case where I saw a message like this (the other was a product we made). I guess it was just so out of context I didn't make the connection.
I will continue to think it sounds stupid.
-
I don't like this screen either, partly because i agree that the “:( something bad happened :'(” text is annoying but also because it means that something bad happened to my computer, which i don't like
-
@Sumireko said in What is the deal with "Your ____ ran into a problem"?:
@LB_ said in What is the deal with "Your ____ ran into a problem"?:
I see it as "we" meaning "Microsoft".
The usage of "we" seems pretty interesting. I think it's certainly indicative of the attitude Microsoft has towards your PC. That is, it isn't "yours", it's "ours".
:( We detected disallowed content on your computer (E_BL_PIRACY). Windows is removing detected blacklisted content... (100%) Finished! We will upload some metadata, and will restart your computer for you...Sorry to burst the theory, but it's probably just to sound nicer. People react better to things that sound better (even if it ends up sounding stupid in the process), and this makes it sound like Microsoft is right there, helping you fix the issues.
ETA: Or if not helping to fix, at least commiserating.
-
While logically I understand this message is designed not to scare the target users of this software, it makes me furious with the patronizing tone and by not explaining the nature of the error, instead hiding behind "problems".
Also if the software can happily display those messages and collect statistics, then the "problem" does not seem serious and looks like a lame ecscuse.
-
@Adynathos said in What is the deal with "Your ____ ran into a problem"?:
While logically I understand this message is designed not to scare the target users of this software, it makes me furious with the patronizing tone and by not explaining the nature of the error, instead hiding behind "problems".
Also if the software can happily display those messages and collect statistics, then the "problem" does not seem serious and looks like a lame ecscuse.Oh I'm not saying you're wrong :) - it's extremely annoying to technical users. I can see why Microsoft is doing it though, even if it's annoying as f$%k to us....
You're right about that too - a BSOD doesn't just mean your cat videos didn't load, it means something is seriously f$^ked up somewhere, either in hardware, in which case you're screwed, or in software, possibly due to a bad driver or because your OS install is completely borked. It's a serious issue, and making it sound like less of a problem is the kind of thing that leads to crap like hard drive corruption due to constant BSOD...
-
@CoyneTheDup said in What is the deal with "Your ____ ran into a problem"?:
Oh, yeah, and what's the odds of that? About 9400 software failures per hardware failure?
Using the blakeydefinition of Drivers=Hardware,
I've not seen a software induced BSOD in Windows NT variants. Ever.I haven't seen a driver induced BSOD since early WinXP (though there were a lot of them in early-Vista, too. I never had one because I picked my hardware carefully)
All the rest have been hardware.
-
@Weng said in What is the deal with "Your ____ ran into a problem"?:
@CoyneTheDup said in What is the deal with "Your ____ ran into a problem"?:
Oh, yeah, and what's the odds of that? About 9400 software failures per hardware failure?
Using the blakeydefinition of Drivers=Hardware,
I've not seen a software induced BSOD in Windows NT variants. Ever.I haven't seen a driver induced BSOD since early WinXP (though there were a lot of them in early-Vista, too. I never had one because I picked my hardware carefully)
All the rest have been hardware.
I haven't bluescreened recently, but I did have a power outage a few days ago and my computer didn't bluescreen to protect itself, so I'm gonna go ahead and say that's a Windows bug.
-
@ben_lubar I rip the blue pin out of my analog monitor plug to prevent bsod
-
@groo Seems you can do that on DVI plug too. :P
-
@Weng my sister had Fallout 3 bluescreening her computer during a certain dialog, reliably. And she wasn't the only one, many people complained about it online, so if it was a hardware issue it was one specific condition triggered by the faulty driver, triggered by something that specific game did.
Or maybe it was a software failure. It is freaking Gamebyro after all...
-
@Sumireko said in What is the deal with "Your ____ ran into a problem"?:
The usage of "we" seems pretty interesting. I think it's certainly indicative of the attitude Microsoft has towards your PC. That is, it isn't "yours", it's "ours".
To be fair, that copy of Windows you’re using isn’t yours (see point 2a).
@sloosecannon said in What is the deal with "Your ____ ran into a problem"?:
Oh I'm not saying you're wrong :) - it's extremely annoying to technical users. I can see why Microsoft is doing it though, even if it's annoying as f$%k to us....
This kind of message isn’t really any less helpful than, say,
or
https://wpcf.neosmart.net/sites/5/2014/06/0x0000007B.png
or of course
-
@Weng said in What is the deal with "Your ____ ran into a problem"?:
I haven't seen a driver induced BSOD since early WinXP
I have a Game Boy flash cart with a driver that consistently BSODs anything newer than Vista every single time the cart is plugged. I had to run an XP VM and pass the USB through to it.
@sloosecannon said in What is the deal with "Your ____ ran into a problem"?:
ou're right about that too - a BSOD doesn't just mean your cat videos didn't load, it means something is seriously f$^ked up somewhere, either in hardware, in which case you're screwed, or in software, possibly due to a bad driver or because your OS install is completely borked. It's a serious issue, and making it sound like less of a problem is the kind of thing that leads to crap like hard drive corruption due to constant BSOD...
Yeah, I've ranted about it before. BSODs should be scary, full of technical gibberish and register dumps, so that the average user gets scared enough to call someone knowledgeable instead of just winging it. That the technical user doesn't feel patronized by Windows patting them on the head and saying "there, there, your PC did a booboo" is an added bonus.
-
@Maciejasjmj said in What is the deal with "Your ____ ran into a problem"?:
BSODs should be scary, full of technical gibberish and register dumps, so that the average user gets scared enough to call someone knowledgeable instead of just winging it.
Also, that's not a screen that ought to be seen by users often in the first place (or there's something else horribly wrong) so making it a bit scary and technical isn't a huge usability problem.
IIRC, the last time I saw a BSOD was when I was having thermal problems with some hardware.
-
@sloosecannon said in What is the deal with "Your ____ ran into a problem"?:
this makes it sound like Microsoft is right there, helping you fix the issues
Microsoft cares about you.
Microsoft wants to be near you.
Microsoft likes to watch you while you're sleeping.
-
@Maciejasjmj said in What is the deal with "Your ____ ran into a problem"?:
full of technical gibberish and register dumps
Exactly that - maybe the text can tell you whats happening maybe not - but at least you can search for it online and compare to other peoples' cases.
When I search using the error logs/messages from Linux I often find a solution online. The messages are not understandable, but at least have high enough entropy to be a good identifier :P
The single number or word given by Windows is not enough to confidently establish whether its the same or different error.
-
As for not seeing bluescreens much, My laptop is in for repair. I don't know what's broken, but Windows reliability monitor bottomed out. 12 or so bluescreens in a week will do that.
It does seem likely it's a hardware problem.
-
@Jaloopa said in What is the deal with "Your ____ ran into a problem"?:
Why would you think it's about being PC?
I've seen other instances of this sort of thing being PC, but in this case it just sounds like trying to deflect blame. "It's not our fault! There was a problem."
-
@Adynathos said in What is the deal with "Your ____ ran into a problem"?:
The messages are not understandable, but at least have high enough entropy to be a good identifier :P
The
Aiee, Killing interrupt handler Kernel panic: attempting to kill the idle task In interrupt handler - not syncingi.e. Linux equivalent of BSOD not so much though. Mainly because when things are going this bad, the code really has absolutely no clue what might have caused it.
-
@Bulb said in What is the deal with "Your ____ ran into a problem"?:
the code really has absolutely no clue what might have caused it
It does not know but different reasons will likely cause it to fail in different ways, so that when you search for
[what i was trying to do] + Aiee, Killing interrupt handleryou can find the answer.
-
@Tsaukpaetra said in What is the deal with "Your ____ ran into a problem"?:
@lolwhat said in What is the deal with "Your ____ ran into a problem"?:
99 problems, and now your bitch ran into one?
Well, no, that one was all me on accident. She's never walked the same since that night...
Filed under:
-
What happens when windows encounters this screen:
-
@flabdablet said in What is the deal with "Your ____ ran into a problem"?:
<clippy> It looks like you're trying to have sex. Would you like help? </clippy>Microsoft cares about you.
Microsoft wants to be near you.
Microsoft likes to watch you while you're sleeping.
-
@anotherusername said in What is the deal with "Your ____ ran into a problem"?:
@Tsaukpaetra said in What is the deal with "Your ____ ran into a problem"?:
@lolwhat said in What is the deal with "Your ____ ran into a problem"?:
99 problems, and now your bitch ran into one?
Well, no, that one was all me on accident. She's never walked the same since that night...
Filed under:
No! You've got it all wrong! She was sleeping in my bed and when I was stretching her foot was under mine in a bad position, something must have dislocated...
... Not really helping my case, am I?
-
In the same vein, this just popped up:
Changes? What changes? I did nothing! What do you want? WHY?
-
@Onyx said in What is the deal with "Your ____ ran into a problem"?:
In the same vein, this just popped up:
Changes? What changes? I did nothing! What do you want? WHY?
Windows has detected that you have moved your mouse. Please restart your computer for these changes to be applied.
-
@flabdablet said in What is the deal with "Your ____ ran into a problem"?:
Not aggressive enough.
"You touched something, didn't you. We warned you not to do that. Over and over, we warned you. But you did it anyway, and now you've broken it. We'll try to fix it for you but we're making no promises. What you have to do now is SIT THERE AND KEEP YOUR HANDS TO YOURSELF while we try to figure out how much permanent damage you've done.
"By the way, we're going to restart your PC, which will probably mean tying it up for two hours while we install updates afterwards. No, you can't go get a coffee. Sit down and shut up and maybe you'll finally learn something.""And pray you don't have a power blip, because if that happens then you will be proper fucked."
-
-
@flabdablet said in What is the deal with "Your ____ ran into a problem"?:
tying it up for two hours while we install updates afterwards
Maybe stop buying 486s.
-
@Weng said in What is the deal with "Your ____ ran into a problem"?:
@CoyneTheDup said in What is the deal with "Your ____ ran into a problem"?:
Oh, yeah, and what's the odds of that? About 9400 software failures per hardware failure?
Using the blakeydefinition of Drivers=Hardware,
I've not seen a software induced BSOD in Windows NT variants. Ever.I haven't seen a driver induced BSOD since early WinXP (though there were a lot of them in early-Vista, too. I never had one because I picked my hardware carefully)
All the rest have been hardware.
When my tablet ran Windows 8, its camera worked perfectly. After upgrading to Windows 10, it bluescreens every time the camera is used.
All signs point to a driver problem.
-
@FrostCat said in What is the deal with "Your ____ ran into a problem"?:
Maybe stop buying 486s.
but ... what else is going to power my Dialogic D/300? Or D/240 for you silly T1 yanks.
-
@Luhmann said in What is the deal with "Your ____ ran into a problem"?:
but ... what else is going to power my Dialogic D/300?
Given that your link shows a picture of a PCIe board, I'd say upgrade your add-in card too.
-
@FrostCat said in What is the deal with "Your ____ ran into a problem"?:
upgrade your add-in card
These cards are end-points for at least 1 E1 or T1 phone line, they easily cost more then the server they are in. In 2008 I did a project that included moving some ISA boards to new servers because the customer still considered looking for a sub-optimal solution with a freak server that still featured ISA slots was preferred above upgrading 20 cards.
We replaced the cards a few years later anyway ... but through a budgetary backdoor.
