Originally posted by: DopeFiend
Could you be more specific? What do you see at the top-left of the screen when it happens? If you can tell me/us that, then I/we might be able to figure out what's causing it.
If it happens just this once, then you should be okay, as Windows still has little glitches here and there that cause these kind of things every once in a while.
Originally posted by: Smilin
Originally posted by: DopeFiend
Could you be more specific? What do you see at the top-left of the screen when it happens? If you can tell me/us that, then I/we might be able to figure out what's causing it.
If it happens just this once, then you should be okay, as Windows still has little glitches here and there that cause these kind of things every once in a while.
Hehe. It is completely impossible for any software including Windows to generate that error. User mode, kernel mode, drivers etc. Impossible. I wouldn't trick you!
See if you have any other events in your system log that may give an indication as to what's up. Also check for event id 26s that are informational popups (memory could not be 'read' etc). Run a memory tester. If you have any events in the 50's range start looking at your drives. 5, 7, 9, 11, 15, 26, 50, 51, 55's all CAN be indicative of hardware problems although it's not 100% certain. With the hardware malfunction error (which is ALWAYS hardware) it becomes much more likely that other events are hardware related rather than software.
Hehe. It is completely impossible for any software including Windows to generate that error. User mode, kernel mode, drivers etc. Impossible. I wouldn't trick you!
Nnngh. That's a very good point. In my defence, I'm mildly sloshed and it's Friday night![]()
Originally posted by: bsobel
Hehe. It is completely impossible for any software including Windows to generate that error. User mode, kernel mode, drivers etc. Impossible. I wouldn't trick you!
Nnngh. That's a very good point. In my defence, I'm mildly sloshed and it's Friday night![]()
In your defense, it's actually kernel mode code in Windows which is generating that error message. It's not Windows, however, which is the cause of the error neccesitating the message
Bill
Originally posted by: Smilin
Originally posted by: bsobel
Hehe. It is completely impossible for any software including Windows to generate that error. User mode, kernel mode, drivers etc. Impossible. I wouldn't trick you!
Nnngh. That's a very good point. In my defence, I'm mildly sloshed and it's Friday night![]()
In your defense, it's actually kernel mode code in Windows which is generating that error message. It's not Windows, however, which is the cause of the error neccesitating the message
Bill
hm. Well true I spose. I like the sloshed defense anyway.![]()