Bluescreen windows vista

[Kusti]

Witam, piszę gdyż liczę na pomoc bo sam już niewiem co się dzieje.
Niedawno postanowiłem zainstalować sobie gre Total war : Shogun 2, wszystko ładnie pięknie tylko że przy włączaniu gry wyskakuj mi bluescreen.
Instalowałem na nowo gre, sterowniki do karty graficznej itp. i nic nie pomogło, wspomne zę jakieś 2 miesiące temu gra działała mi normalnie, i nie wiem czy jest to wina komputera czy może samej aplikacji.

System - Windows Vista Home Premium SP2 32 bity
Płyta główna - Foxconn G31MX-K
grafika - GeForce 9600 GT
procesor - Intel Pentium Dual-Core E5300
pamięć - 3 GB DDR2

Jeżeli zły dział to przepraszam.

[Mikou@j]

A kod błędu? Marka i moc zasilacza?

[Kusti]

Kod błędu :

0x00000124 (0x00000000, 0x855B1028, 0xB2000040, 0x00000800)

Co do zasilacza
MODECOM 500w

[Okocza]

MODECOM 500w

Modecom Feel? Modecom Volcano ? Wiele jest modeli zasilaczy Modecom.

[Kusti]

Modecom Feel

[Okocza]

I; II; III ?

[Kusti]

Modecom Feel 3 500w

[Mikou@j]

Wrzuć tutaj informacje z pliku minidump http://forum.idg.pl/minidump-i-narzedzie-debugging-tools-for-windows-t171701.html
Zasilacz nie najlepszej klasy, ale jeśli jest sprawny to powinien działać poprawnie.

[Kusti]

Oto treść

Microsoft (R) Windows Debugger Version 6.6.0003.5
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\Minidump\Mini102311-04.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: *** Invalid ***
****************************************************************************
* Symbol loading may be unreliable without a symbol search path. *
* Use .symfix to have the debugger choose a symbol path. *
* After setting your symbol path, use .reload to refresh symbol locations. *
****************************************************************************
Executable search path is:
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
Unable to load image \SystemRoot\system32\ntkrnlpa.exe, Win32 error 2
*** WARNING: Unable to verify timestamp for ntkrnlpa.exe
*** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe
Windows Vista Kernel Version 6002 (Service Pack 2) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Kernel base = 0x82414000 PsLoadedModuleList = 0x8252bc70
Debug session time: Sun Oct 23 13:22:46.564 2011 (GMT+2)
System Uptime: 0 days 0:05:16.375
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
Unable to load image \SystemRoot\system32\ntkrnlpa.exe, Win32 error 2
*** WARNING: Unable to verify timestamp for ntkrnlpa.exe
*** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe
Loading Kernel Symbols
.............................................................................................................................................................
Loading User Symbols
Loading unloaded module list
....
*** WARNING: Unable to verify timestamp for hal.dll
*** ERROR: Module load completed but symbols could not be loaded for hal.dll
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 124, {0, 855b1028, b2000040, 800}

***** Kernel symbols are WRONG. Please fix symbols to do analysis.

*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************

Followup: MachineOwner
---------