Częste BSOD'y

[taniu]

Od pewnego czasu ok. 2 tygodni mam problem z częstym pojawianiem się bsodów. Pojawiają się one podczas włączania gier takich jak: TSims2, Spore, Simcity 4 deluxe, Starecraft II brodwar, WarCraft III frozen trone, Swat4, oraz podczas przeglądania internetu, są one częste czasami 5-6 razy dziennie ale nie zawsze. Jak dobrze sobie przypominam zaczęło się to w grudniu po aktualizacji sterowników programem SLIMDRIVERS, potem była przerwa i zaczęło się dziać znowu aż do tej pory tak... Co muszę robić. Czyściłem komputer, rejestr CCleaner i system ninja. Jak usunąć ten problem pomóżcie.
PS. Format mija się z celem w moim przypadku.

[mint1991]

Polecam lekturkę do przeczytania -> http://www.hotfix.pl/bluescreen-bsod-sz ... mp-a17.htm

[taniu]

No właśnie natrafiłem na tą lekturkę wcześniej i zarejestrowałem się tutaj.Mam tylko trzy te zrzuty pamięci, ponieważ czyściłem komputer co i tak nie pomogło.
A oto i one:

Kod: Zaznacz cały

Loading Dump File [C:\WINDOWS\Minidump\Mini012112-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows XP Kernel Version 2600 (Service Pack 3) UP Free x86 compatible
Product: WinNt
Built by: 2600.xpsp_sp3_gdr.111025-1629
Machine Name:
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055b240
Debug session time: Sat Jan 21 13:13:26.484 2012 (GMT+1)
System Uptime: 0 days 1:06:12.049
Loading Kernel Symbols
...............................................................
................................................................
..
Loading User Symbols
Loading unloaded module list
............
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000007E, {c0000005, 804f38c4, f7a71ab0, f7a717ac}

Unable to load image \SystemRoot\System32\Drivers\aswMon2.SYS, Win32 error 0n2
*** WARNING: Unable to verify timestamp for aswMon2.SYS
*** ERROR: Module load completed but symbols could not be loaded for aswMon2.SYS
Probably caused by : aswMon2.SYS ( aswMon2+5f88 )

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

kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
This is a very common bugcheck.  Usually the exception address pinpoints
the driver/function that caused the problem.  Always note this address
as well as the link date of the driver/image that contains this address.
Some common problems are exception code 0x80000003.  This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG.  This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG.  This will let us see why this breakpoint is
happening.
Arguments:
Arg1: c0000005, The exception code that was not handled
Arg2: 804f38c4, The address that the exception occurred at
Arg3: f7a71ab0, Exception Record Address
Arg4: f7a717ac, Context Record Address

Debugging Details:
------------------


EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - Instrukcja spod "0x%08lx" odwo

FAULTING_IP:
nt!IoGetRequestorProcess+f
804f38c4 8b4044          mov     eax,dword ptr [eax+44h]

EXCEPTION_RECORD:  f7a71ab0 -- (.exr 0xfffffffff7a71ab0)
Cannot read Exception record @ f7a71ab0

CONTEXT:  f7a717ac -- (.cxr 0xfffffffff7a717ac)
Unable to read context, Win32 error 0n30

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  DRIVER_FAULT

BUGCHECK_STR:  0x7E

EXCEPTION_STR:  0x0

LAST_CONTROL_TRANSFER:  from 804fb655 to 804f38c4

STACK_TEXT: 
f7a71b78 804fb655 cb1ce886 f7a71c80 f50eaf88 nt!IoGetRequestorProcess+0xf
f7a71b84 f50eaf88 cb1ce886 02a9e8cb 0000085c nt!IoGetRequestorProcessId+0xd
WARNING: Stack unwind information not available. Following frames may be wrong.
f7a71c80 f50ebe12 860d7bf0 cb1ce886 f7a71cfd aswMon2+0x5f88
f7a71cff cb1cd080 cb1ce086 cb1ce886 6f12d086 aswMon2+0x6e12
f7a71d03 cb1ce086 cb1ce886 6f12d086 ffffff80 0xcb1cd080
f7a71d07 cb1ce886 6f12d086 ffffff80 000001ff 0xcb1ce086
f7a71d0b 6f12d086 ffffff80 000001ff 5b000000 0xcb1ce886
f7a71d0f ffffff80 000001ff 5b000000 00000003 0x6f12d086
f7a71d13 00000000 5b000000 00000003 271fe600 0xffffff80


FOLLOWUP_IP:
aswMon2+5f88
f50eaf88 ??              ???

SYMBOL_STACK_INDEX:  2

SYMBOL_NAME:  aswMon2+5f88

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: aswMon2

IMAGE_NAME:  aswMon2.SYS

DEBUG_FLR_IMAGE_TIMESTAMP:  0

STACK_COMMAND:  .cxr 0xfffffffff7a717ac ; kb

FAILURE_BUCKET_ID:  0x7E_aswMon2+5f88

BUCKET_ID:  0x7E_aswMon2+5f88

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



Kod: Zaznacz cały

Loading Dump File [C:\WINDOWS\Minidump\Mini012012-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Invalid directory table base value 0x0
Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:

"nt" was not found in the image list.
Debugger will attempt to load "nt" at given base 00000000.

Please provide the full image name, including the extension (i.e. kernel32.dll)
for more reliable results.Base address and size overrides can be given as
.reload <image.ext>=<base>,<size>.
Unable to load image nt, Win32 error 0n2
Unable to add module at 00000000
Debugger can not determine kernel base address
Windows XP Kernel Version 2600 (Service Pack 3) UP Free x86 compatible
Product: WinNt
Machine Name:
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055b240
Debug session time: Fri Jan 20 19:31:30.328 2012 (GMT+1)
System Uptime: 0 days 1:31:39.899

"nt" was not found in the image list.
Debugger will attempt to load "nt" at given base 00000000.

Please provide the full image name, including the extension (i.e. kernel32.dll)
for more reliable results.Base address and size overrides can be given as
.reload <image.ext>=<base>,<size>.
Unable to load image nt, Win32 error 0n2
Unable to add module at 00000000
Debugger can not determine kernel base address
Loading Kernel Symbols

Loading User Symbols
Loading unloaded module list
.........
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck C, {0, 0, 0, 0}

***** Debugger could not find nt in module list, module list might be corrupt, error 0x80070057.

Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )

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

kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

MAXIMUM_WAIT_OBJECTS_EXCEEDED (c)
Arguments:
Arg1: 00000000
Arg2: 00000000
Arg3: 00000000
Arg4: 00000000

Debugging Details:
------------------

***** Debugger could not find nt in module list, module list might be corrupt, error 0x80070057.


CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  DRIVER_FAULT

BUGCHECK_STR:  0xC

LAST_CONTROL_TRANSFER:  from 00000000 to 80533819

STACK_TEXT: 
f3e1fd14 00000000 00000000 00000000 00000000 0x80533819


STACK_COMMAND:  kb

SYMBOL_NAME:  ANALYSIS_INCONCLUSIVE

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: Unknown_Module

IMAGE_NAME:  Unknown_Image

DEBUG_FLR_IMAGE_TIMESTAMP:  0

BUCKET_ID:  CORRUPT_MODULELIST

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



Kod: Zaznacz cały

Loading Dump File [C:\WINDOWS\Minidump\Mini011912-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows XP Kernel Version 2600 (Service Pack 3) UP Free x86 compatible
Product: WinNt
Built by: 2600.xpsp_sp3_gdr.111025-1629
Machine Name:
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055b240
Debug session time: Thu Jan 19 20:45:49.375 2012 (GMT+1)
System Uptime: 0 days 5:15:56.953
Loading Kernel Symbols
...............................................................
................................................................
...
Loading User Symbols
Loading unloaded module list
.............
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000008E, {c0000005, bf805355, ec2c44c4, 0}

Unable to load image \SystemRoot\System32\nv4_disp.dll, Win32 error 0n2
*** WARNING: Unable to verify timestamp for nv4_disp.dll
*** ERROR: Module load completed but symbols could not be loaded for nv4_disp.dll
Probably caused by : nv4_disp.dll ( nv4_disp+248cd )

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

kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

KERNEL_MODE_EXCEPTION_NOT_HANDLED_M (1000008e)
This is a very common bugcheck.  Usually the exception address pinpoints
the driver/function that caused the problem.  Always note this address
as well as the link date of the driver/image that contains this address.
Some common problems are exception code 0x80000003.  This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG.  This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG.  This will let us see why this breakpoint is
happening.
Arguments:
Arg1: c0000005, The exception code that was not handled
Arg2: bf805355, The address that the exception occurred at
Arg3: ec2c44c4, Trap Frame
Arg4: 00000000

Debugging Details:
------------------


EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - Instrukcja spod "0x%08lx" odwo

FAULTING_IP:
win32k!SURFMEM::~SURFMEM+41
bf805355 ff30            push    dword ptr [eax]

TRAP_FRAME:  ec2c44c4 -- (.trap 0xffffffffec2c44c4)
Unable to read trap frame at ec2c44c4

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  DRIVER_FAULT

BUGCHECK_STR:  0x8E

LAST_CONTROL_TRANSFER:  from bf81b12f to bf805355

STACK_TEXT: 
ec2c4558 bf81b12f e3d06e80 e437d424 e437d424 win32k!SURFMEM::~SURFMEM+0x41
ec2c45d8 bf81cbfe bf9a9258 e1632008 bf8c530a win32k!bGetRealizedBrush+0x6aa
ec2c45f0 bf826dcf e437d424 00000000 e3d06e90 win32k!pvGetEngRbrush+0x1f
ec2c4650 bf0368cd e3d06e90 00000000 00000000 win32k!EngBitBlt+0x272
WARNING: Stack unwind information not available. Following frames may be wrong.
ec2c46e0 804e92b7 00000001 000004f0 c02f0780 nv4_disp+0x248cd
ec2c475c bf998d18 00000000 ec2c47b8 bf8050d3 nt!MiDispatchFault+0x13b
ec2c47b8 bf80be86 e437d424 ec2c483c ec2c489c win32k!`string'+0x104
ec2c4924 804de7be 0000007a 0012a574 0012a58c win32k!NtGdiFlushUserBatch+0x689
ec2c49ac 80566bfa ec2c4a34 7ffdf700 7ffdf6cc nt!KiFastCallEntry+0xca
ec2c4ae0 80566bc4 ec2c4b9c 80566bfa ec2c4b70 nt!KeUserModeCallback+0xef
ec2c4b3c 00000000 ec2c4bec ec2c4bf8 00000002 nt!KeUserModeCallback+0x87


STACK_COMMAND:  kb

FOLLOWUP_IP:
nv4_disp+248cd
bf0368cd ??              ???

SYMBOL_STACK_INDEX:  4

SYMBOL_NAME:  nv4_disp+248cd

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nv4_disp

IMAGE_NAME:  nv4_disp.dll

DEBUG_FLR_IMAGE_TIMESTAMP:  481c0584

FAILURE_BUCKET_ID:  0x8E_nv4_disp+248cd

BUCKET_ID:  0x8E_nv4_disp+248cd

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



Ps. Jak odczytać specyfikacje komputera- jaki program i co podać na forum.

[djkamil09061991]

Jeden zrzut wskazuje na problemy z avastem, tak więc odinstaluj go i zasinstaluj innego antywira lub przeinstaluj go.
A drugi zrzut wskazuje na sterownik od grafiki, odinstaluj aktualny sterownik i zainstaluj inny nie koniecznie najnowszy musi być nalepszy.

[taniu]

A to co jest?

Kod: Zaznacz cały

Loading Dump File [C:\WINDOWS\Minidump\Mini012412-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows XP Kernel Version 2600 (Service Pack 3) UP Free x86 compatible
Product: WinNt
Built by: 2600.xpsp_sp3_gdr.111025-1629
Machine Name:
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055b240
Debug session time: Tue Jan 24 18:03:40.187 2012 (GMT+1)
System Uptime: 0 days 4:18:47.777
Loading Kernel Symbols
...............................................................
................................................................
......
Loading User Symbols
Loading unloaded module list
.................
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 50, {cb868d21, 0, f3c1fb52, 0}


Could not read faulting driver name
Unable to load image \SystemRoot\system32\DRIVERS\ewusbmdm.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ewusbmdm.sys
*** ERROR: Module load completed but symbols could not be loaded for ewusbmdm.sys
Probably caused by : hardware ( asyncmac!AsyncPPPCompletionRoutine+5c )

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

Debugging Details:
------------------


Could not read faulting driver name

READ_ADDRESS:  cb868d21

FAULTING_IP:
asyncmac!AsyncPPPCompletionRoutine+5c
f3c1fb52 128b750c8b45    adc     cl,byte ptr [ebx+458B0C75h]

MM_INTERNAL_CODE:  0

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  DRIVER_FAULT

BUGCHECK_STR:  0x50

TRAP_FRAME:  f4f32a54 -- (.trap 0xfffffffff4f32a54)
ErrCode = 00000000
eax=00000103 ebx=85fb80ac ecx=86b7a4c8 edx=00000008 esi=85fb862f edi=85fb80b9
eip=f3c1fb52 esp=f4f32ac8 ebp=f4f32acc iopl=0         nv up ei ng nz na pe nc
cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010286
asyncmac!AsyncPPPCompletionRoutine+0x5c:
f3c1fb52 128b750c8b45    adc     cl,byte ptr [ebx+458B0C75h] ds:0023:cb868d21=??
Resetting default scope

MISALIGNED_IP:
asyncmac!AsyncPPPCompletionRoutine+5c
f3c1fb52 128b750c8b45    adc     cl,byte ptr [ebx+458B0C75h]

LAST_CONTROL_TRANSFER:  from 805241e0 to 80533846

STACK_TEXT: 
f4f329f0 805241e0 00000050 cb868d21 00000000 nt!KeBugCheckEx+0x1b
f4f32a3c 804e172b 00000000 cb868d21 00000000 nt!MmAccessFault+0x6f5
f4f32a3c f3c1fb52 00000000 cb868d21 00000000 nt!KiTrap0E+0xcc
f4f32acc f3c1fc7e 860f5630 00000000 85fe44cb asyncmac!AsyncPPPCompletionRoutine+0x5c
f4f32af4 804e3d48 00000000 85fb80b8 00000001 asyncmac!AsyncPPPCompletionRoutine+0x188
f4f32b24 f4bad894 86b7a3f0 86766be0 86b7a4a8 nt!IopfCompleteRequest+0xa2
WARNING: Stack unwind information not available. Following frames may be wrong.
f4f32b40 804e3807 00dd8650 85fe4338 85fe4338 ewusbmdm+0xf894
f4f32b50 f78fece4 85fe4338 86766950 85fb8008 nt!IopfCallDriver+0x31
f4f32b64 804e3807 85fe44c8 85fe4338 860f5630 Modem!UniRead+0x4a
f4f32b74 f3c1fdbf 85fb8008 860f5630 00000000 nt!IopfCallDriver+0x31
f4f32b8c f3c1fe4d 86d62680 85fe44cb 85fe4338 asyncmac!AsyncPPPRead+0x12f
f4f32ba4 804e3d48 00000000 85fe4338 860f5630 asyncmac!AsyncWaitMaskCompletionRoutine+0x5b
f4f32bd4 f78fa70c f4f32bfc f78fdd95 00000005 nt!IopfCompleteRequest+0xa2
f4f32bdc f78fdd95 00000005 85fe4338 00000000 Modem!RemoveReferenceAndCompleteRequest+0x3c
f4f32bfc f78fef1f 86b7a4a8 f4f32c64 00000001 Modem!UniRundownShuttledWait+0xa3
f4f32c2c f78ff7ce 86b7a400 00000002 00000002 Modem!UniPostProcessShuttledWaits+0x43
f4f32c94 804e3d48 86b7a3f0 85fe1200 00000002 Modem!UniSniffWaitComplete+0xe6
f4f32cc4 f4ba5d09 804e3621 86bff698 00000000 nt!IopfCompleteRequest+0xa2
f4f32ce0 f4ba3631 86bff698 01bff740 86bff7e4 ewusbmdm+0x7d09
f4f32dac 80579453 01bff698 00000000 00000000 ewusbmdm+0x5631
f4f32ddc 804f88fa f4ba308e 86bff698 00000000 nt!PspSystemThreadStartup+0x34
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16


STACK_COMMAND:  kb

FOLLOWUP_IP:
asyncmac!AsyncPPPCompletionRoutine+5c
f3c1fb52 128b750c8b45    adc     cl,byte ptr [ebx+458B0C75h]

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  asyncmac!AsyncPPPCompletionRoutine+5c

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: hardware

IMAGE_NAME:  hardware

DEBUG_FLR_IMAGE_TIMESTAMP:  0

FAILURE_BUCKET_ID:  IP_MISALIGNED_asyncmac.sys

BUCKET_ID:  IP_MISALIGNED_asyncmac.sys

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


Czy moglibyście mi powiedzieć co jest grane?? Już nie wytrzymuje...

[djkamil09061991]

Rozumiem że avast odinstalowany oraz sterownik do grafiki zmieniony na inną wersje? Jeśli tak to podaj SMART dysku:
sprzet-komputerowy/odczytanie-smart-programem-hd-tune-t512.html

[taniu]

Kod: Zaznacz cały

HD Tune Pro: WDC WD800BB-22JHC0 Health

ID                                  Current  Worst    ThresholdData     Status   
(01) Raw Read Error Rate            200      200      51       1227     ok       
(03) Spin Up Time                   161      153      21       2941     ok       
(04) Start/Stop Count               91       91       0        9090     ok       
(05) Reallocated Sector Count       199      199      140      7        warning 
(07) Seek Error Rate                200      200      51       0        ok       
(09) Power On Hours Count           82       82       0        13272    ok       
(0A) Spin Retry Count               100      100      51       0        ok       
(0B) Calibration Retry Count        100      100      51       0        ok       
(0C) Power Cycle Count              92       92       0        8796     ok       
(C2) Temperature                    107      82       0        36       ok       
(C4) Reallocated Event Count        197      197      0        3        warning 
(C5) Current Pending Sector         200      200      0        0        ok       
(C6) Offline Uncorrectable          200      200      0        0        ok       
(C7) Ultra DMA CRC Error Count      200      200      0        152      warning 
(C8) Write Error Rate               200      200      51       0        ok       

Health Status         : warning


[djkamil09061991]

Jest dużo błędów komunikacyjnych, wiec należałoby wymienić kabelek łączący dysk z płytą. Poczekaj na obszerniejszą diagnozę bardziej obeznanych w tym temacie