First of all, I carefully read the BSOD posting instructions... but haven't run the programme on my machine yet, because it refuses to start.
BUT, please bear with me a minute:
I think mine is a strange case: the same problem happened on two different computers I own, operating under different OS, only when connected to the same monitor (not at once).
I'll explain: I suffered a number of BSODs on my regular PC for a week (Acer OS Windows 7, regulardly updated) - initially after long periods of standby and/or power save, then at random, sometimes I couldn't even start the PC.
I did all I could, rebooted in safe mode, ran anti-virus scans, spyware scans, didn't find anything malignant, and I thought it seemed to be working again (well it worked for a whole day just doing the scans). Then crashed again, and again, and... So I gave up and though I'd use my small laptop until I had time to do something about it, just getting my work done at least.
My small laptop is mini MSI machine, running under Windows XP, totally different/independant, which I only use to work in the garden or on holiday etc..
It runs with a minimum of useful programmes and files. I soon connected it to my regular keyboard and mouse for comfort, and resumed work.
Then I thought - the MSI screen being impossibly "mini" - why not connect it to my regular 19" widescreen LCD monitor (Philips)?
Which I did. Thought I was very clever for a few minutes... until bang, BSOD (to be honest, I'm not sure whether it was black with strange characters or blue), but the laptop crashed.
Once past my initial "oh, not again" reaction, I unplugged the monitor (which had gone into "no signal/video input" before turning itself off), and looked more closely at the MSI... which looked "dead". And using the on/off switch (which, incidentally, is also the switch to exit powersave mode and return to Windows), I ressucitated it. The machine started again, looking just like it does when I switch it back on after a long period of standby. No error message, nothing, as if nothing had ever happened.
I've stuck to NOT using the big monitor since, and my little laptop is still perfectly fine (if a little small).
One last thing - in case it may be of use - when the main PC crashed, the blue LED that means it's running always remained lit, I had to force-switch it off (pressing the power switch until it went dead) every single time.
It never went really "dead" nor rebooted (like I've seen with previous PCs following BSODs).
Any idea? Could it be the monitor?
Please. Suggestions/diagnosis welcome.
PS: now I feel stupid because I've been writing from my mini-laptop connected to the big monitor the whole time hoping something would happen to help with the diagnosis, and it hasn't crashed... yet.
Next step, I'll download the JCGriff programme on the main PC if I manage to get it started (would it still work I I start it in safe mode?) and will let you know...
System spec info:
Is Windows 7 . . .
- x86 (32-bit) or x64 ? no sure, need to check when I can restart the machine
- the original installed OS on the system? YES
- an OEM or full retail version? OEM
- What is the age of system (hardware)? 1-2 years old (more or less)
- What is the age of OS installation (have you re-installed the OS?) - same as before: never re-installed it.
And the monitor is under 18 months old.