[Markspoiss]

Product
Windows

Problem
Shut down unexpectedly

Date
2.02.2009 16:09

Status
Not Reported

Problem signature
Problem Event Name: BlueScreen
OS Version: 6.0.6001.2.1.0.256.1
Locale ID: 1061

Files that help describe the problem
Mini020209-01.dmp
sysdata.xml
Version.txt

Extra information about the problem
BCCode: be
BCP1: 981FEDB0
BCP2: 00911121
BCP3: CF8F07CC
BCP4: 0000000A
OS Version: 6_0_6001
Service Pack: 1_0
Product: 256_1


ehk oskab keegi nõu anda?

[A.S.]

[Markspoiss]

mingi siuke jutt siis tuli:

On Mon 2.02.2009 14:08:50 your computer crashed
This was likely caused by the following module: eamon.sys
Bugcheck code: 0xBE (0x981FEDB0, 0x911121, 0xCF8F07CC, 0xA)
Error: ATTEMPTED_WRITE_TO_READONLY_MEMORY
file path: C:\Windows\system32\drivers\eamon.sys
product: ESET Smart Security
company: ESET
description: Amon monitor

et nagu siis nod ei saand miskit mällu kirjutatud vms?:S

[A.S.]

Läks teine lolliks jah. Kui see kordub, siis võta plaani kas selle uuendamine või eemaldamine/väljavahetamine.
 

[Markspoiss]

selgeh tänud:)

mul siin mingi aeg pullis ka selle blue screeniga suht äkki:S ja siis juba hakkasin kahtlema et krt äkki miski riistvaraline kala sees et peab garantiisse vedama sunnikut hakkama:)

[A.S.]

Aga kes sul keelab mälu testida?
http://www.memtest.org/

E:
Temperatuure ka ikka jälginud oled, lihtsalt puhtinimlikust uudishimust või nii?
 

[Donut]

Lase NOD32 maha ja probleem lahendatud.

[Tomorrow]

[Betamax]

Vista SP1 on installitud?

[Donut]

[Tomorrow]

[pealuu]

lihtsalt mainin, et alati ei pea sellistel juhtudel tingimata antiviirus süüdlane olema. ei viitsinud tõlkima hakata:
Often you will see an antivirus driver named as the cause. For instance, after using !analyze –v, the debugger reports a driver for your antivirus program at the line "IMAGE_NAME". This may well be the case, but bear in mind that such a driver can be named more often than it is guilty. Here's why: For antivirus code to work it must watch all file openings and closings. To accomplish this, the code sits at a low layer in the operating system and is constantly working. In fact, it is so busy it will often be on the stack of function calls that was active when the crash occurred, even if it did not cause it. Because any third-party driver on that stack immediately becomes suspect, it will often get named. From a mathematical standpoint it is easy to see how it will so often be on the stack whether it actually caused a problem or not.

[Absona]

100% olen kindel, et NOD32 on süüdi. Kunagi kui mul Vista oli, siis oli sama jama aga tol aeg ei olnud vist veel Service Pack 1 olemas. Seega kui SP1 pole veel installitud arvutisse, siis on õige aeg peale installeerida ja alles siis NOD32 peale panna.

[pealuu]

kahtlustan, et
OS Version: 6_0_6001
Service Pack: 1_0
tähendavad vistat ja sp1'te.

[A.S.]

[pealuu]

[A.S.]

Eksimine on loomulikult võimalik, seda enam, et viirustõrje ju pidevalt seal sahmerdab. Aga dump faili pannakse mingil määral kirja ka see, mis toimus vahetult enne "pauku", seega on vähemalt teoreetiliselt tegeliku süüdlase valjaselgitamine võimalik. Full dump oleks sellisel juhul küll tunduvalt parem kui minidump.