 SOLVED:PC blue screening 0_o  |
Paranoia
tHeY'Re WatChInG mE!
Registration Date: 12-01-2007
Posts: 934
Location: Essex
Race in game: Absorber
Clan: HERP-DERP
 |
|
|
04-20-2012 18:55 |
|
|
Foxy
Viking
Registration Date: 05-02-2009
Posts: 582
Location: Wales
Race in game: Absorber
Clan: BOS + S.S.
|
|
| RE: PC blue screening 0_o |
     |
Few questions.
Is this the first time you used this MW3.
If so is it disk or download and where did you get it from also is it preowned or new if disk?
__________________
[20:01] <stimpuki> ur best gunner on srrver atm
[20:01] <Foxy9> really? not mortis or grind?
[20:02] <stimpuki> mortis is to old now and grind is hll
|
|
|
04-20-2012 19:48 |
|
|
Sapling
Triple Ace
Registration Date: 05-28-2011
Posts: 168
Location: Latvia
Race in game: Absorber
Clan: BoS - SAN
|
|
Do you have Daemon Tools / Alcohol 120 installed ?
|
|
|
04-20-2012 19:52 |
|
|
bloodDevil
Junior Member
Registration Date: 01-22-2012
Posts: 12
Location: Underworld
Race in game: Cultist
|
|
WHEA_UNCORRECTABLE_ERROR is usually a hardware problem.
WHEA = Windows Hardware Error Architecture
I read something ages ago if i remember right NTOSKRNL.EXE could be a problem with the keyboard.
Hope this helps.
__________________
IGN: bloodDevil
|
|
|
04-20-2012 19:55 |
|
|
bloodDevil
Junior Member
Registration Date: 01-22-2012
Posts: 12
Location: Underworld
Race in game: Cultist
|
|
NTOSKRNL.EXE is missing or corrupt.
Cause
Keyboard issue
Miscellaneous corruption
Corrupt boot.ini file.
Missing boot.ini file.
Missing or corrupt ntoskrnl.exe file.
Windows NT installed on a partition bigger then 7.8GB
Corrupted hard disk drive or severely corrupted Windows.
__________________
IGN: bloodDevil
|
|
|
04-20-2012 20:38 |
|
|
Sapling
Triple Ace
Registration Date: 05-28-2011
Posts: 168
Location: Latvia
Race in game: Absorber
Clan: BoS - SAN
|
|
Are you overclocking ? Probably not but just in case if you are, better stop that dirty habit.
But apart from antiviruses who have been known to be the cause of BSODs on Windows 7, there's a good chance that this doesn't really come from your hardware.
The only problem with RAM is that even 6 hour long stress tests can bring back "false positives" as they might still be damaged but the stress tests doesn't always detect it. It can skip over it and you could run the test 100 times and still not see it.
As for why I was asking about Alcohol 120 and Daemon is because their boot files have a tendancy to get registered much earlier than any other files in the boot sequence and they usually end up taking unwanted resources that frequently cause BSODs once you launch applications such as MW3. This is a problem with the Windows 7 boot sequence that has yet to be fixed.
In regards to the hardware in itself, if the problem comes from it, I have read everything you wrote and I understand your drivers are up to date.
Now, that being said, there are two types of drivers that are often forgotten and lead to BSODs.
1 - Motherboard drivers, cause number one in BSODs.
2 - if you are running a RAID, than these drivers usually don't update automatically and you might have to do this manually.
See if any of this helps.
Finally, as I mentionned earlier, antiviruses can often generate these errors 0x124, especially Norton so if you have anything Symantec related, best remove that.
| quote: |
Originally posted by bloodDevil
NTOSKRNL.EXE is missing or corrupt.
Cause
Keyboard issue
Miscellaneous corruption
Corrupt boot.ini file.
Missing boot.ini file.
Missing or corrupt ntoskrnl.exe file.
Windows NT installed on a partition bigger then 7.8GB
Corrupted hard disk drive or severely corrupted Windows. |
You seem to have amazing google skills.
This post has been edited 1 time(s), it was last edited by Sapling: 04-20-2012 20:49.
|
|
|
04-20-2012 20:48 |
|
|
|
