dwwin.exe DLL initialization failed.
The application failed to initialize because the window station is shutting down.
Except, the window station (what? is this English?) is not shutting down, which is the entire problem.
The system cannot end this program because it is waiting for a response from you.
Oh, that's nice. It's my fault. Meanwhile this program has not been open for hours and only needing a response from me because it failed to close properly or completely and has been hiding in the background, ready to rear its ugly head now.
Adobe acrord32.exe application error
The instruction at "0x5ad71531" referenced memeory at "0x00000014" the memory could not be "read"
Cute, tell me about some random line of code and random bit of memory. This is entirely unhelpful. If you had a countdown timer (like, oh, I don't know, my Mac) that just shut down 120 seconds after being told to, come hell or high water, I wouldn't have to deal with this bullshit.
If my time is worth $20 per hour, and I spend 3 minutes a day dealing with this, and I work 250 days a year, that's $1 per day, or $250 per year, or $750 over the lifespan of a computer (assuming it is amortised over three years). Can someone please explain how it is more efficient to save a hundred dollars on a PC just to have staff waste hour upon hour of time trying to make the goddamn system work?
No comments:
Post a Comment