Bardzo częsty BlueScreen i reset komputera

Post18 mar 2011, 13:46

Godzina to za mało. Zostaw na noc, niech przejdzie po 10 godzin.

Post19 mar 2011, 09:37

Oto wynik po 11 godzinach skanowania: Dostępne tylko dla zarejestrowanych użytkowników

Uploaded with Dostępne tylko dla zarejestrowanych użytkowników

Wychodzi na to że to jednak nie wina pamięci.

Post19 mar 2011, 11:25

Czyli ram jest sprawny.
Jaki model i moc zasilacza masz?
Przeczyściłeś komputer? Jakie teraz są temperatury?

Post19 mar 2011, 12:27

Tracer MGB-400ATX-400W
Komputer przeczyściłem i temperatury są takie: Dostępne tylko dla zarejestrowanych użytkowników

Uploaded with Dostępne tylko dla zarejestrowanych użytkowników

Post19 mar 2011, 13:00

Tracer to nie jest dobry zasilacz, tutaj masz listę dobrych i złych zasilaczy: http://forum.hotfix.pl/sprzet-komputerowy/spis-dobrych-i-zlych-zasilaczy-t160.html. Proponuję podmienić go na jakiś markowy zasilacz i sprawdzić jak będzie sprawował się komputer. Choć najlepiej go po prostu wymienić, toć ten Tracer to tykająca bomba..

Post19 mar 2011, 13:17

Czyli te błędy mogą być spowodowane zasilaczem? Mogłabyś polecić jakiś dobry, tani zasilacz ponieważ ten komputer będzie używany głównie do pisania i przeglądania Internetu więc nie chce w niego inwestować jakiejś dużej kasy.

Post19 mar 2011, 13:25

Napisz ile pieniędzy jesteś w stanie wydać na zasilacz. Nie gwarantuję ani nie dam sobie uciąć głowy, że powodem jest w 100% zasilacz, ale bardzo często tak jest, zwłaszcza kiedy nic innego nie wskazuje błędu.

Post19 mar 2011, 13:44

Ok 100 zł jeśli by się dało kupić coś dobrego za taką cenę bo nie chcę dużo inwestować w starszy sprzęt.

Post19 mar 2011, 13:58

Troszkę drożej, ale bardzo dobry:
Dostępne tylko dla zarejestrowanych użytkowników

Poza tym do 100 zł:
Dostępne tylko dla zarejestrowanych użytkowników

Post19 mar 2011, 22:30

Dzięki za pomoc, zakupie nowy zasilacz, zobaczę co się będzie działo i dam znać na forum.

-- 19 mar 2011, 22:30 --

Mam jeszcze jedna pytanie: co oprócz zasilacza może być jeszcze przyczyną powstawania tych błędów bo po tych testach RAM i dysk jest wykluczony?

Post19 mar 2011, 22:45

Testy nie wskazują ani na dysk ani na ram.

Post20 mar 2011, 07:08

Podmień zasilacz jak problem nie ustąpi będziemy myśleć dalej. Wszystkie znaki na niebie i ziemi wskazują właśnie na elektrownie komputera. Jakby problem nadal występował to zobaczymy potem.

Post05 kwie 2011, 20:03

Witam, podmieniłem zasilacz na Fortrona ale niestety nadal występuje Bluescreen, oto raport z błędu:

Kod: Zaznacz cały

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


Loading Dump File [C:\WINDOWS\Minidump\Mini040511-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 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 XP Kernel Version 2600 (Service Pack 2) UP Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Machine Name:
Kernel base = 0x804d7000 PsLoadedModuleList = 0x805531a0
Debug session time: Tue Apr  5 19:51:15.484 2011 (GMT+2)
System Uptime: 0 days 0:17:21.050
*********************************************************************
* 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 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
..............
Unable to load image win32k.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 10000050, {b0e83bac, 0, bf818fbe, 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                                     ***
***                                                                   ***
*************************************************************************
*********************************************************************
* 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 : win32k.sys ( win32k+18fbe )

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

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: b0e83bac, memory referenced.
Arg2: 00000000, value 0 = read operation, 1 = write operation.
Arg3: bf818fbe, If non-zero, the instruction address which referenced the bad memory
   address.
Arg4: 00000000, (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                                     ***
***                                                                   ***
*************************************************************************
*********************************************************************
* 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: win32k

FAULTING_MODULE: 804d7000 nt

DEBUG_FLR_IMAGE_TIMESTAMP:  41107f7a

READ_ADDRESS: unable to get nt!MmSpecialPoolStart
unable to get nt!MmSpecialPoolEnd
unable to get nt!MmPoolCodeStart
unable to get nt!MmPoolCodeEnd
 b0e83bac 

FAULTING_IP: 
win32k+18fbe
bf818fbe 8b95f0feffff    mov     edx,dword ptr [ebp-110h]

MM_INTERNAL_CODE:  0

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  DRIVER_FAULT

BUGCHECK_STR:  0x50

LAST_CONTROL_TRANSFER:  from bf8174fb to bf818fbe

STACK_TEXT:  
WARNING: Stack unwind information not available. Following frames may be wrong.
afe83cbc bf8174fb e2386010 00000006 afe8403c win32k+0x18fbe
afe83cf4 bf817bce e22f5010 e2386010 e2cf7e04 win32k+0x174fb
afe83d80 bf81782e e2db4018 e22f5010 e2cf7e04 win32k+0x17bce
afe83de0 bf817d58 e2db4018 e22f5010 e2cf7e04 win32k+0x1782e
afe83e3c bf8181b3 e2db4018 e22f5010 e2cf7e04 win32k+0x17d58
afe83ea0 bf81859a afe83fc4 e2cf7e04 e22f5000 win32k+0x181b3
afe83fc8 bf817e3e 46010c2d 00000000 00000000 win32k+0x1859a
afe84110 8053c808 46010c2d 00000060 0117e534 win32k+0x17e3e
afe84124 7c90eb94 badb0d00 0117e3b4 bf816129 nt+0x65808
afe84128 badb0d00 0117e3b4 bf816129 00000000 0x7c90eb94
afe8412c 0117e3b4 bf816129 00000000 0000005a 0xbadb0d00
afe84130 bf816129 00000000 0000005a 0000003c 0x117e3b4
afe84134 00000000 0000005a 0000003c 00000001 win32k+0x16129


STACK_COMMAND:  kb

FOLLOWUP_IP: 
win32k+18fbe
bf818fbe 8b95f0feffff    mov     edx,dword ptr [ebp-110h]

SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  win32k+18fbe

FOLLOWUP_NAME:  MachineOwner

IMAGE_NAME:  win32k.sys

BUCKET_ID:  WRONG_SYMBOLS

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

Bardzo proszę o dalszą pomoc.

Strona WWW · Post05 kwie 2011, 23:04

Raport wskazuje na problem ze sterownikiem od grafiki, tak więc przeinstaluj go, nie koniecznie najnowszy musi być najlepszy.

Post06 kwie 2011, 00:49

Jakie pobrać te sterowniki mam Radeona 9550? Próbuje instalować różne sterowniki i bardzo często mi wywala Bluescreen albo komputer się resetuje bez Bluescreena.
I jeszcze raport z błędu podczas instalacji sterownika:

Kod: Zaznacz cały

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


Loading Dump File [C:\WINDOWS\Minidump\Mini040611-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 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 XP Kernel Version 2600 (Service Pack 2) UP Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Machine Name:
Kernel base = 0x804d7000 PsLoadedModuleList = 0x805531a0
Debug session time: Wed Apr  6 00:39:44.109 2011 (GMT+2)
System Uptime: 0 days 0:03:14.671
*********************************************************************
* 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 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
..............
Unable to load image win32k.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 10000050, {96538f7c, 0, bf8e4e32, 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                                     ***
***                                                                   ***
*************************************************************************
*********************************************************************
* 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 : win32k.sys ( win32k+e4e32 )

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

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: 96538f7c, memory referenced.
Arg2: 00000000, value 0 = read operation, 1 = write operation.
Arg3: bf8e4e32, If non-zero, the instruction address which referenced the bad memory
   address.
Arg4: 00000000, (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                                     ***
***                                                                   ***
*************************************************************************
*********************************************************************
* 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: win32k

FAULTING_MODULE: 804d7000 nt

DEBUG_FLR_IMAGE_TIMESTAMP:  41107f7a

READ_ADDRESS: unable to get nt!MmSpecialPoolStart
unable to get nt!MmSpecialPoolEnd
unable to get nt!MmPoolCodeStart
unable to get nt!MmPoolCodeEnd
 96538f7c 

FAULTING_IP: 
win32k+e4e32
bf8e4e32 8b4004          mov     eax,dword ptr [eax+4]

MM_INTERNAL_CODE:  0

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  DRIVER_FAULT

BUGCHECK_STR:  0x50

LAST_CONTROL_TRANSFER:  from bf8e4cca to bf8e4e32

STACK_TEXT:  
WARNING: Stack unwind information not available. Following frames may be wrong.
f2d77bfc bf8e4cca e10d7b28 00000000 e10d7b28 win32k+0xe4e32
f2d77c18 bf8464f3 e10d7b28 e10d7b28 856489f0 win32k+0xe4cca
f2d77c40 bf846599 e10d7b28 00000000 856489f0 win32k+0x464f3
f2d77c5c 805c6fd3 85840da0 00000000 856489f0 win32k+0x46599
f2d77d08 805c73f2 00000000 856489f0 00000000 nt+0xeffd3
f2d77d28 805c75cd 856489f0 00000000 f2d77d64 nt+0xf03f2
f2d77d54 8053c808 00000000 00000000 0007fecc nt+0xf05cd
f2d77d64 7c90eb94 badb0d00 0007fdd8 f72b3d98 nt+0x65808
f2d77d68 badb0d00 0007fdd8 f72b3d98 f72b3dcc 0x7c90eb94
f2d77d6c 0007fdd8 f72b3d98 f72b3dcc 00000000 0xbadb0d00
f2d77d70 f72b3d98 f72b3dcc 00000000 00000000 0x7fdd8
f2d77d74 f72b3dcc 00000000 00000000 00000000 0xf72b3d98
f2d77d78 00000000 00000000 00000000 00000000 0xf72b3dcc


STACK_COMMAND:  kb

FOLLOWUP_IP: 
win32k+e4e32
bf8e4e32 8b4004          mov     eax,dword ptr [eax+4]

SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  win32k+e4e32

FOLLOWUP_NAME:  MachineOwner

IMAGE_NAME:  win32k.sys

BUCKET_ID:  WRONG_SYMBOLS

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