ilovefuzz.com

Got new computers over the holiday break for most people who needed them in the office.
Some small glitches and such when first installing (Old softwares not communicating with other old software)
A little bit of learning curve but now everyone seems to be loving the new machines
with the exception of our Quality Manager.

His has been returned and restored fully once so far.
Gets blue screens every AM, can't work
Complains a ton.

Today I went to his office to confirm it was running before he got in, it was off. (This is a problem because I asked him to keep it on so outside IT could check a few things overnight). I turned it on and it worked as it should. When he got in, he claimed it wasn't working and I went to his office and he had blue screened it again. I have no idea how, but I now have the computer in an empty office working fine and can't duplicate the failure.

The day they brought back the restored computer he tried to vacuum his office and knocked the mouse cable loose. Is he trying to break the computer?

I honestly don't have another explanation.

He is not directly under me so I have limited actions I can take but he acknowledged that he turned it off last night on purpose because "that's not the issue". I have no idea what to do or how to prove he is jacking up a brand new machine intentionally or through constant human error.

Help me ILF!

sounds like its 100% user error. I assume you asked him what he was running before it blue-screened? does he have something running in the background he doesn't want you to find out about? why else would he shut it off at night?

So...person is a Quality Manager and can't figure out steps to reproduce the error???? Weak.

aedes wrote:So...person is a Quality Manager and can't figure out steps to reproduce the error???? Weak.

Yeah, it's a great mystery to him...again...not my department and not my call on him continuing to be employed here.

starmansam wrote:sounds like its 100% user error. I assume you asked him what he was running before it blue-screened? does he have something running in the background he doesn't want you to find out about? why else would he shut it off at night?

It's possible he is screwing around, this AM however it was running at 8:50 (when I started it) and blue screened by 9:10 (when he showed up and tried it) and I checked the activity and he had done absolutely nothing. The only thing I could figure is that he is banging it hard but that seems absurd.

Any way to install monitoring software on his PC so you can just "look" at the computer before he gets into work and see what the hell he's doing?

On the other hand, the QA is breaking things on purpose... so he is doing his job?

Give him his old computer back.

Lurker13 wrote:Give him his old computer back.

I Did but it's windows 7- unsupported

D.o.S. wrote:On the other hand, the QA is breaking things on purpose... so he is doing his job?

Yes he is absolutely doing his job, and not doing his job all at once.

hbombgraphics wrote:

D.o.S. wrote:On the other hand, the QA is breaking things on purpose... so he is doing his job?

Yes he is absolutely doing his job, and not doing his job all at once.

I'm also in QA, and it's baffling to me that they wouldn't be curious how they caused the error.

aedes wrote:

hbombgraphics wrote:

D.o.S. wrote:On the other hand, the QA is breaking things on purpose... so he is doing his job?

Yes he is absolutely doing his job, and not doing his job all at once.

I'm also in QA, and it's baffling to me that they wouldn't be curious how they caused the error.

He seems to think it's a conspiracy, I did 5 restarts including a few forced re-starts today and I can't duplicate the error.

I do think he likes being less efficient (not sure that is the best way to describe it)

Sounds like an id10T error

JonnyAngle wrote:Sounds like an id10T error

Agreed, most of the problems are located behind the keyboard, I thought about putting the new comp back with a hidden camera since he won't tell me what he is doing or come get me before it crashes.

update: Computer is working perfectly again today but someone from QA/Engineering office block claims they can hear him banging on his keyboard when it doesn't wake up fast enough. I have a theory that he is just super impatient.

QAM likes our Testing Manager quite a bit and thinks he is good with computers so the testing manager said he would confirm the machine is OK today.

I just need 1 PPAP closed out this morning and that is it and all he has to do is load in an IMDS number (he didn't even have to submit the IMDS I pay to outsource that)
as of 11AM PPAP is not done.

Computer perfect—human imperfect

frodog wrote:Computer perfect—human imperfect

Absolutely!


Trying to come up with a plan to monitor the machine when I put it back see what the error is and maybe have a teachable moment!!!!

And I finally got my PPAP!!!