[problem] BSOD podczas włączania komputera.

Witam!

Mam problem z ostatnio bardzo częstymi Blue Screenami na nowym komputerze.

Specyfikacja techniczna:

Procesor AMD FX 6100
Ram 8GB 1333 mhz
Zasilacz - obecnie spalił mi się Modecom Feel2 i dostałem z gwarancji Feel'a (za co oczywiście napisałem stosowną wiadomość do sprzedawcy) - ale na to wychodzi że to nie wina zasilacza, bo obecnie wymieniłem Feela tego którego dostałem "z gwarancji" na innego Feela i problem jest nadal.

Dzisiaj 3 razy BSOD wyskoczył w tym samym - przy próbie dodania Max Payna do blokowanych wyjątków w zaporze ESETa, ale ani Max ani ESET do tego nic nie powinny mieć bo w komunikacie BSOD widzimy że problemem jest "ntoskrnl.exe" i nie mamy wypisanego procesu ESETowego albo MAXowego w "prawdopodobnej przyczynie"

Dodatkowo - jak jeszcze miałem podpiętego tego gwarancyjnie wymienionego Feela to próbowałem przetestować kompa w zakładce "Power Supply" to komputer wchodził w dziwny stan po około 5 minutach - dokładniej, tak jak by wszystkie urządzenia we / wy zostały pozbawione dostępu do prądu, a komputer nie reagował ani na przycisk reset, ani na przytrzymanie powera - musiałem go wyłączać przez wciśnięcie "0" na zasilaczu z tyłu.


Więcej dumpów: http://www.speedysha...2/minidumpy.rar

Przykładowy BSOD:

Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\Minidump\081712-20670-01.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\ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Windows 7 Kernel Version 7600 MP (6 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`02017000 PsLoadedModuleList = 0xfffff800`02254e50
Debug session time: Fri Aug 17 12:40:49.382 2012 (GMT+2)
System Uptime: 0 days 0:02:47.882
*********************************************************************
* 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\ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Loading Kernel Symbols
...............................................................
................................................................
.............
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
*																			 *
*					 Bugcheck Analysis								 *
*																			 *
*******************************************************************************Use !analyze -v to get detailed debugging information.
BugCheck 50, {fffff8a0051f6000, 0, fffff8000234d079, 0}***** 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									 ***
***																 ***
*************************************************************************
*************************************************************************
***																 ***
***																 ***
*** 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									 ***
***																 ***
*************************************************************************
*********************************************************************
* 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+								 *
*********************************************************************
*********************************************************************
* 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+								 *
*********************************************************************
Probably caused by : ntoskrnl.exe ( nt+336079 )Followup: MachineOwner
---------
5: kd> !analyze -v
*******************************************************************************
*																			 *
*					 Bugcheck Analysis								 *
*																			 *
*******************************************************************************PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced. This cannot be protected by try-except,
it must be protected by a Probe. Typically the address is just plain bad or it
is pointing at freed memory.
Arguments:
Arg1: fffff8a0051f6000, memory referenced.
Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
Arg3: fffff8000234d079, If non-zero, the instruction address which referenced the bad memory
address.
Arg4: 0000000000000000, (reserved)
Debugging Details:
------------------***** 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									 ***
***																 ***
*************************************************************************
*************************************************************************
***																 ***
***																 ***
*** 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									 ***
***																 ***
*************************************************************************
*********************************************************************
* 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+								 *
*********************************************************************
*********************************************************************
* 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+								 *
*********************************************************************ADDITIONAL_DEBUG_TEXT:
Use '!findthebuild' command to search for the target build information.
If the build information is available, run '!findthebuild -s ; .reload' to set symbol path and load symbols.
MODULE_NAME: ntFAULTING_MODULE: fffff80002017000 nt
DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bc600READ_ADDRESS: unable to get nt!MmSpecialPoolStart
unable to get nt!MmSpecialPoolEnd
unable to get nt!MmPoolCodeStart
unable to get nt!MmPoolCodeEnd
fffff8a0051f6000
FAULTING_IP:
nt+336079
fffff800`0234d079 410fb701	 movzx eax,word ptr [r9]MM_INTERNAL_CODE: 0
CUSTOMER_CRASH_COUNT: 1DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0x50CURRENT_IRQL: 0
LAST_CONTROL_TRANSFER: from fffff800021081e4 to fffff80002088f00STACK_TEXT:
fffff880`0bd19468 fffff800`021081e4 : 00000000`00000050 fffff8a0`051f6000 00000000`00000000 fffff880`0bd195d0 : nt+0x71f00
fffff880`0bd19470 00000000`00000050 : fffff8a0`051f6000 00000000`00000000 fffff880`0bd195d0 00000000`00000000 : nt+0xf11e4
fffff880`0bd19478 fffff8a0`051f6000 : 00000000`00000000 fffff880`0bd195d0 00000000`00000000 00000000`00000000 : 0x50
fffff880`0bd19480 00000000`00000000 : fffff880`0bd195d0 00000000`00000000 00000000`00000000 fffff880`0bd19500 : 0xfffff8a0`051f6000

STACK_COMMAND: .bugcheck ; kbFOLLOWUP_IP:
nt+336079
fffff800`0234d079 410fb701	 movzx eax,word ptr [r9]
SYMBOL_NAME: nt+336079FOLLOWUP_NAME: MachineOwner
IMAGE_NAME: ntoskrnl.exeBUCKET_ID: WRONG_SYMBOLS
Followup: MachineOwner
---------

Użytkownik happyy edytował ten post 17 08 2012 - 13:04

Zasilacz - obecnie spalił mi się Modecom Feel2 i dostałem z gwarancji Feel'a

Zasilacz który miałeś i ten co obecnie podłączyłeś znajdują się na czarnej liście zasilaczy na początek to pożycz od kogoś jakiś "markowy zasilacz" podłącz go i sprawdź czy BSOD-y będą nadal się pokazywały.

Użytkownik Tomasz6688 edytował ten post 18 08 2012 - 12:47

Wiem że zasilacze to syf, a pożyczyć nie mam skąd więc szukałem ewentualnej innej przyczyny.

Przyczyna jest jedna -> zasilacz do wymiany. Jeżeli po wymianie na "markowy zasilacz" problem będzie się pojawiał to będziemy szukali przyczyny gdzie indziej.