BSOD - što, zašto i kako

  Problem je vezan uz ATI drivere. Probaj ih ocistiti sa Driver Sweeperom i instaliraj samo ono najnuznije od ATI drivera (bez kontrol panela i slicno)

Od Avirinog drivera koji je zadužen za real-time skeniranje.

Nemoguće, nemam aviru...

Lijek?

Možeš preporučiti neke programe?

  Problem Event Name:    BlueScreen
  OS Version:    6.1.7600.2.0.0.256.1
  Locale ID:    1050

Additional information about the problem:
  BCCode:    7f
  BCP1:    0000000000000008
  BCP2:    0000000080050033
  BCP3:    00000000000006F8
  BCP4:    FFFFF80002C97EC0
  OS Version:    6_1_7600
  Service Pack:    0_0
  Product:    256_1

Files that help describe the problem:
  C:\Windows\Minidump\041811-35303-01.dmp
  C:\Users\TOSHIBA\AppData\Local\Temp\WER-66721-0.sysdata.xml

Read our privacy statement online:
 http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0409

If the online privacy statement is not available, please read our privacy statement offline:
  C:\Windows\system32\en-US\erofflps.txt                                     

kako da ovo popravim?? pl.

Sad mi se prije 3 minute desio BSOD ali nemogu da uploadam minidump,kaže mi da nemam ovlasti da to uradim.Kako da ga uploadam?

Evo uspjeo sam,nego mozes li mi molim te očitat taj minidump tj. odgovorit što to ga ruši?

Minidump:

http://bit.ly/gXNQtP

EDIT:I postaj mi sliku od tog programa u kojem si otvorio Minidump.

I što da sad s tim driverom napravim?

Avira mi je blokirala i isto mi se desavalo sa avirom.To mi se desilo odmah nakon što sam avast upadateao na verziju 6.0.1091

Evo i mog problema, stvarno više neznam u čemu je problem, mislim da do Windowsa nije....Ali od kada sam instalirao Aviru još češće se javlja BSOD, a nekad jednostavno zablokira, bez plavog ekrana i onda ga moram restartati.

Testirao sam memoriju sa Memtestom, jedno 5-6 sati i nije ništa našlo....

Da li imas prikopcano mozda neki eksterni USB disk ili stick? Ako jeste provjeri kako su mu podesenja za sleep u Power Options

Za pocetak iskljuci selective USB suspend

Ako nemas USB disk onda postupak znas...Memtest86+

  Ne pamtim tacno na koje mjesto ali postelaj da ti disk ne ide u sleep dok se ne koristi. Problem nastaje kada Windowsi zatraze disk a ovaj se ne umije probuditi i tada dobijes BSOD...ovako bi izgledalo primitivno objasnenje :)

SAVJET:

Ne znam koji su ti afiniteti ili potrebe da taj eksterni disk drzis non-stop ukljucen u PC ali trudi se da ga drzis iskljucen na USB kablu i prikopcavaj ga po potrebu

[edit]

Disk(ove) testiraj sa alatom od proizvodaca i to sa bootanjem necega. Ti alati, koji dolaze iz fabrike, su dovoljno rigorozni...vjeruj mi. Bed kod Memtesta je to sto testira cijeli memorijski subsistem tako da ce testirati i processor cache , memoriju na integriranoj graf. kartici i sve sto "pronade" :)

A mozda i nije bed posto gdje i da se nalazi, pokvarena memorija pravi probleme. Sretno

UMALO ZAORAVIH NAJBITNIJI DIO :)

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


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

Symbol search path is: C:\Windows\symbols
Executable search path is:
Windows 7 Kernel Version 7601 (Service Pack 1) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17514.x86fre.win7sp1_rtm.101119-1850
Machine Name:
Kernel base = 0x83007000 PsLoadedModuleList = 0x83151850
Debug session time: Fri Apr 29 21:16:35.934 2011 (UTC + 2:00)
System Uptime: 0 days 0:06:48.479
Loading Kernel Symbols
...............................................................
................................................................
..............................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000000A, {803853ac, 2, 0, 83080d76}

Probably caused by : ntkrpamp.exe ( nt!KiTimerExpiration+138 )

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

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

IRQL_NOT_LESS_OR_EQUAL (a)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high.  This is usually
caused by drivers using improper addresses.
If a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: 803853ac, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000000, bitfield :
    bit 0 : value 0 = read operation, 1 = write operation
    bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: 83080d76, address which referenced memory

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


READ_ADDRESS: GetPointerFromAddress: unable to read from 83171718
Unable to read MiSystemVaType memory at 831511a0
 803853ac

CURRENT_IRQL:  2

FAULTING_IP:
nt!KiTimerExpiration+138
83080d76 8b48fc          mov     ecx,dword ptr [eax-4]

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xA

PROCESS_NAME:  System

LAST_CONTROL_TRANSFER:  from 8307f00e to 83080d76

STACK_TEXT: 
807dfcdc 8307f00e 00006648 88385308 807c8800 nt!KiTimerExpiration+0x138
807dfd20 8307ee38 00000000 0000000e 00000000 nt!KiRetireDpcList+0xcb
807dfd24 00000000 0000000e 00000000 00000000 nt!KiIdleLoop+0x38


STACK_COMMAND:  kb

FOLLOWUP_IP:
nt!KiTimerExpiration+138
83080d76 8b48fc          mov     ecx,dword ptr [eax-4]

SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  nt!KiTimerExpiration+138

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrpamp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4ce78a09

FAILURE_BUCKET_ID:  0xA_nt!KiTimerExpiration+138

BUCKET_ID:  0xA_nt!KiTimerExpiration+138

Followup: MachineOwner

  Makni Daemon toolse