Monitor death after hardware calibration.

NLAlston

Member
I have an HP-f2105 monitor that had served me faithfully - up until today. Yesterday, a previously ordered Spyder2Express hardware colorimeter monitor calibration device came in, and immediately sat down to calibrate my monitor. All seemed to go well, and my prints were coming out much better. I shut down the pc for the night, and - when I powered the computer up this morning - I found that all hell had broken loose. My monitor would NOT power up right. All that I could see was a very faint "Microsoft Corporation" at the lower mid-section of the screen. I must have powered down & back up (then pc) no less than five or six times, but the problem remained the same. Thinking that my new PC might have been problematic, I took it back to Best Buy to have it checked out. Powering it up into one of their monitors revealed no problems at all. So, the issue was with my monitor instead.

I will be sending this calibration unit back to the manufacturer, but wanted to know if anyone had an idea as to how I might be able to revive my monitor. I have tried everything I could, from the monitor's physical control buttons, but no action will bring about a favorable change in these circumstances.

I am really desperate, as I NEED my computer & monitor for my startup photography business.

Advanced thanks.
 
Well, it turns out - everyone - that the problem is not with my monitor, as previously thought. I just tried it on our children's computer, and it worked just fine. But I also tried their LCD monitor on my computer, and guess what? Yes...that's right - the same problem as with my monitor on my new PC. I don't know why the PC worked without issue, with the monitor at Best Buy - but won't work with any of the two monitors here. Really strange indeed.
 
Found out, today, what the problem was. My video card had to be reset. This had to be done at the place of purchase, as I could not see anything on the screen. I was also told that the Spyder2Express was a 32-bit application, which caused issues due to my new system being 64-bit. So, I will see if the manufacturer has an updated driver for 64-bit systems.
 
Back
Top