Lokalaskurar
Posts: 513 +0
Basically, my brother's computer (laptop, Toshiba Satellite C650D) is running Windows 7 Home (Premium), 64 bit legitimate.
(Btw, don't be worried of giving me "jargon-support" like; check the register-entry for halfdumped software keys and so on, I'm very experienced with computers )
He's had a BSOD... well... actually, 96 of them the last 5 days. (I checked the Windows log) - it says Kernel-power error, but I know that's just from every unsuccessful shutdown he's had...
Basically, about 75% of all his tries to boot results in the following STOP code:
0X0000000A
(0X0000000000000000,
0X0000000000000002,
0X0000000000000000,
0XFFFFF800032A8015)
And this message stays on-screen for as long as you don't press the start button.
But when the computer crashes from time to time, it displays an error message for exactly 5 seconds that is too hard to read at that speed (and every camera we have is too slow in order to snap the moment ).
But it ends with the STOP: 0x000000000002 - that, we can read.
It often happens after installations to the Program (x86) - folder.
So how will we go from here? The setup guide at the forum index did not cover this problem.
(Btw, don't be worried of giving me "jargon-support" like; check the register-entry for halfdumped software keys and so on, I'm very experienced with computers )
He's had a BSOD... well... actually, 96 of them the last 5 days. (I checked the Windows log) - it says Kernel-power error, but I know that's just from every unsuccessful shutdown he's had...
Basically, about 75% of all his tries to boot results in the following STOP code:
0X0000000A
(0X0000000000000000,
0X0000000000000002,
0X0000000000000000,
0XFFFFF800032A8015)
And this message stays on-screen for as long as you don't press the start button.
But when the computer crashes from time to time, it displays an error message for exactly 5 seconds that is too hard to read at that speed (and every camera we have is too slow in order to snap the moment ).
But it ends with the STOP: 0x000000000002 - that, we can read.
It often happens after installations to the Program (x86) - folder.
So how will we go from here? The setup guide at the forum index did not cover this problem.