BSOD Windows 7 x64

[studiovpc]

^
pa nema na tvojoj ploci marvell kontroler ti si vec na intelu, ako ti javlja gresku za ataport.sys to je bas driver odgovoran za hardove i za optiku, probaj da instaliras najnovije intelove pa onda da probas, druga stvar vrati sve na def u bios ali pogasi onaj Spread Spectrum gde god nadjes da ima, instaliraj driver po driver pa vidi sta zeza, meni doslo da razbijem komp kad je pocelo ovo da mi se desava a mogu da zamislim samo kako je tebi


@kobatz

haha sto ga forsiram, pa jbg budala sam, kao racunam da bolje 1T sad kad sam vratio sve kako fabricki kaze da je, ima onaj njen XMP profil, stavim njega memara mi radi brze kad testiram, write se podigao za 3 MB i copy, read je isti... znaci ja ****** eto hteo 1T ne znam iz kog razloga...

 

[Maverick78]

Ima neki Marvell 61xx SATA Driver i Marvell Yukon Gigabit Ethernet driver, mislim to je na CD-u koji je stigao uz plocu. I ja sam to sve instalirao u proslim Windowsima. Ne znam da li je to moglo da zeza.... Inace sada sam podigao Win 7 i nisam instalirao nikakve drajvere, koristim ove sto dodju uz Win7, jedino je naknadno instaliran drajver od graficke. Inace zasad drzim sve na defaultu i ugasio sam spread spectrum jos ranije. Sve je ostalo na auto trenutno, osim memorije koju sam manuelno postavio na 1066, 5-5-5-15, 2.1v, na toliko je i deklarisana.

 

[studiovpc]

nema bsod-ova vise, definitivno je memorija bila krivac, cisto da javim, 10 dana prodjose od poslednjeg bsod-a, ako se do sada nije pojavio nece ni sada...

 

[kljun]

ja imam problem s BSOD, vise njih. Kad upalim kompjuter, nece da podigne OS, nudi mi dve opcije,

1. Launch startup repair
i
2. Start windows normaly

kad pokrenem prvu opciju, dobijem

posle toga pokrenem drugu opciju, i dobijem

i tako jedno 5-6 puta, i onda pokrene windows, i windows radi par minuta i pojavi se BSOD.

u pitanju je windows 7 x64, ovo se do sada nije desavalo, nije se desavalo sa ovakvim errorima, javljao se bsod i ranije, ali se nisu javljali i ova dva. win je star neke dve nedelje.

 

[BigJoe]

^
Jel si vratio sve na default u BIOS-u?

 

[studiovpc]

hmmm ovakvi BSOD-ovi meni iskakali na Maxtor-u 160GB, sveze instaliran win masina neklokovana, sve na def i dobijao sam bas taj bsod, i posle par minuta ode maxtor u vecna lovista

 

[kljun]

^
Jel si vratio sve na default u BIOS-u?

nisam, u biosu sam samo namestao OC za CPU i ram, al to je bilo pre mozda 2-3 dana, a danas sam dobio ovaj error, probacu kad dodjem kuci

 

[BigJoe]

^
Možda nije bio stabilan OC, ntdlr.dll ume da strada od nestabilnosti...

 

[kljun]

oc cpu na 3.2 [def: 2.8], ram na 1600[def: 1333] i nije neki oc

ali moze biti i od toga, poludeo sam od svih ovih bsod, snimicu neku drugu verziju windowsa, pa cu videti

 

[FantomX]

tip: kupi dobar kuler za procesor

 

[studiovpc]

koliko vidim ove godine svima "zaposednuti" kompovi prvo bsod a onda kod mene poceo i sam da se pali, dok nisam skontao da mi ukljucen Wake On Lan heehehehe u pola noci kad me prepadne

 

[Maverick78]

nema bsod-ova vise, definitivno je memorija bila krivac, cisto da javim, 10 dana prodjose od poslednjeg bsod-a, ako se do sada nije pojavio nece ni sada...

Ni kod mene vise nema BSOD-ova... evo nekoliko dana radi sve ok, vratio sam i OC, i onaj disk WD 500GB za koji sam mislio da je uzrok BSOD-va i sve radi super kao i ranije. Ostavio sam drajvere koji dodju uz Win7 i sad je sve ok.

@studiovpc, vidim pominjes disk na kom si imao errore i da je ubrzo crkao. Ja imam jedan WD 500GB i HD Tune pod C7 (Ultra DMA CRC Error) pokazuje da ima jedan error u Data. Trenutno ga koristim kao storage i nadam se da nece da zvekne. Ne znam ni da li bi za ovo uracunali garanciju, jer HD Tune i WD Diagnostic kazu da je to problem sa kablovima. Probao vise kablova i isti se error pojavljuje i dalje. Na netu nadjoh da jedan ovakav error u zivotnom ciklusu HDD-a nije nista strasno, samo da se ne pocne povecavati. E sad, nisam ni sam siguan da li ce biti sve ok sa njim. Ako je neko imao neko iskustvo sa ovim bio bih zahvalan za pomoc. Izvinjavam se sto ovo pitam u ovoj temi, offtopic je, ali da ne otvaram novu samo zbog toga .

 

[studiovpc]

e pa pazi to ti sad zavisi vec od dobre volje prodavca, meni je recimo zamenjen tako Seagate 1.5 TB koji je poceo da prijavljuje reallocated sectore, pozvao prodavca (JoKa Atom Computers) resili smo to omdah, e sad crnjak najveci je sto je meni posle otkazao i zamenski hdd, ali to ne znam zasto, Hitachi 640GB znaci samo je izdahnuo bez ikakvih znakova, a ono za error za kabal sam imao na WD Blue 640GB eno ga hdd kod ortaka i dalje radi sa tim 1 errorom i vise nije podizao ni jedan

 

[Maverick78]

E ok, drago mi je da kod ortaka disk radi i dalje ok . Meni se isto nije povecavao broj errora, stoji taj jedan, a kad preskeniram HD Tune-om na errore, sve prodje super, nema bad sectora ili sta ja znam, sve kockice zelene .
Ne cima mi se sad oko garancije, jer nisam iz BG-a, moram da saljem, pa jos ako mi vrate, bezveze cimanje i postarina i tako to. Nadam se da ce biti ok, praticu ga uglavnom kako se ponasa.
Hvala ti na odgovoru

 

[kljun]

snimio novi os,win7 x64, i za sad radi, usput i podesio ovakav OC

intel i5 760
CPU: 180x20 [3.6GHz]
CPU Fan: max [19xx]
CPU Voltage: 1.2v
RealTemp

Mushkin 996959
RAM: 180x10 [1800MHz]
RAM latency: 8-8-8-24
RAM Voltage: 1.64v

interesuje me OC, da li valja, da li da nesto menjam? pokrenuo sam i prime, ali temperature idu preko

 

[studiovpc]

koja je inace default voltaza za CPU? nesto mi to deluje mnogo malo za 3.6, mada ajd ne znam koja je def

 

[kljun]

nem pojma

 

[voodoons]

Mozda zatreba nekom:
BlueScreenView v1.30
Copyright (c) 2009 - 2010 Nir Sofer
Web site: http://www.nirsoft.net

Spojler

Description
===========

BlueScreenView scans all your minidump files created during 'blue screen
of death' crashes, and displays the information about all crashes in one
table. For each crash, BlueScreenView displays the minidump filename, the
date/time of the crash, the basic crash information displayed in the blue
screen (Bug Check Code and 4 parameters), and the details of the driver
or module that possibly caused the crash (filename, product name, file
description, and file version).
For each crash displayed in the upper pane, you can view the details of
the device drivers loaded during the crash in the lower pane.
BlueScreenView also mark the drivers that their addresses found in the
crash stack, so you can easily locate the suspected drivers that possibly
caused the crash.



Versions History
================


* Version 1.30:
o Added 'Dump File Size' column.

* Version 1.29:
o You can now send the list of blue screen crashes to stdout by
specifying an empty filename ("") in the command-line of all save
parameters.
For example: bluescreenview.exe /stab "" > c:\temp\blue_screens.txt

* Version 1.28:
o Added 'Add Header Line To CSV/Tab-Delimited File' option. When
this option is turned on, the column names are added as the first
line when you export to csv or tab-delimited file.

* Version 1.27:
o Fixed issue: removed the wrong encoding from the xml string,
which caused problems to some xml viewers.

* Version 1.26:
o Fixed 'DumpChk' mode to work properly when DumpChk processing
takes more than a few seconds.

* Version 1.25:
o Added 'DumpChk' mode, which displays the output of Microsoft
DumpChk utility (DumpChk.exe). You can set the right path and
parameters of DumpChk in 'Advanced Options' window. By default,
BlueScreenView tries to run DumpChk from '%programfiles%\Debugging
Tools for Windows'
o The default MiniDump folder is now taken from
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CrashControl

* Version 1.20:
o Added 3 new columns in the upper pane: Processors Count, Major
Version, Minor Version.
o Added 'Explorer Copy' option, which allows you to copy dump files
to the clipboard and then paste them into Explorer window.

* Version 1.15:
o Added option to view the blue screen list of multiple computers
on your network. The computer names are specified in a simple text
file. (See below).
o Added Combo-Box to easily choose the MiniDump folders available
in the hard-disks currently attached to your computer.
o Added 'Computer Name' and 'Full Path' columns.

* Version 1.11:
o Added /sort command-line option.

* Version 1.10:
o Added accelerator keys for allowing you to toggle between modes
more easily.
o Added command-line options for saving the crash dumps list to
text/csv/html/xml file.
o Added command-line option for opening BlueScreenView with the
desired MiniDump folder.
o Fixed focus problems when opening the 'Advanced Options' window.
o Added 'default' button to the 'Advanced Options' window.
o Added 'processor' column - 32-bit or x64.

* Version 1.05 - Added support for x64 MiniDump files.
* Version 1.00 - First release.



BlueScreenView Features
=======================


* Automatically scans your current minidump folder and displays the
list of all crash dumps, including crash dump date/time and crash
details.
* Allows you to view a blue screen which is very similar to the one
that Windows displayed during the crash.
* BlueScreenView enumerates the memory addresses inside the stack of
the crash, and find all drivers/modules that might be involved in the
crash.
* BlueScreenView also allows you to work with another instance of
Windows, simply by choosing the right minidump folder (In Advanced
Options).
* BlueScreenView automatically locate the drivers appeared in the crash
dump, and extract their version resource information, including product
name, file version, company, and file description.



System Requirements
===================


* BlueScreenView works with Windows XP, Windows Server 2003, Windows
Server 2008, Windows Vista, and Windows 7, as long as Windows is
configured to save minidump files during BSOD crashes. If your system
doesn't create MiniDump files on a blue screen crash, try to configure
it according to the followinf article: How to configure Windows to
create MiniDump files on BSOD
* BlueScreenView can read the MiniDump files of both 32-bit and x64
systems.



Using BlueScreenView
====================

BlueScreenView doesn't require any installation process or additional dll
files. In order to start using it, simply run the executable file -
BlueScreenView.exe
After running BlueScreenView, it automatically scans your MiniDump folder
and display all crash details in the upper pane.



Crashes Information Columns (Upper Pane)
========================================


* Dump File: The MiniDump filename that stores the crash data.
* Crash Time: The created time of the MiniDump filename, which also
matches to the date/time that the crash occurred.
* Bug Check String: The crash error string. This error string is
determined according to the Bug Check Code, and it's also displayed in
the blue screen window of Windows.
* Bug Check Code: The bug check code, as displayed in the blue screen
window.
* Parameter 1/2/3/4: The 4 crash parameters that are also displayed in
the blue screen of death.
* Caused By Driver: The driver that probably caused this crash.
BlueScreenView tries to locate the right driver or module that caused
the blue screen by looking inside the crash stack. However, be aware
that the driver detection mechanism is not 100% accurate, and you
should also look in the lower pane, that display all drivers/modules
found in the stack. These drivers/modules are marked in pink color.
* Caused By Address: Similar to 'Caused By Driver' column, but also
display the relative address of the crash.
* File Description: The file description of the driver that probably
caused this crash. This information is loaded from the version resource
of the driver.
* Product Name: The product name of the driver that probably caused
this crash. This information is loaded from the version resource of the
driver.
* Company: The company name of the driver that probably caused this
crash. This information is loaded from the version resource of the
driver.
* File Version: The file version of the driver that probably caused
this crash. This information is loaded from the version resource of the
driver.



Drivers Information Columns (Lower Pane)
========================================


* Filename: The driver/module filename
* Address In Stack: The memory address of this driver that was found in
the stack.
* From Address: First memory address of this driver.
* To Address: Last memory address of this driver.
* Size: Driver size in memory.
* Time Stamp: Time stamp of this driver.
* Time String: Time stamp of this driver, displayed in date/time format.
* Product Name: Product name of this driver, loaded from the version
resource of the driver.
* File Description: File description of this driver, loaded from the
version resource of the driver.
* File Version: File version of this driver, loaded from the version
resource of the driver.
* Company: Company name of this driver, loaded from the version
resource of the driver.
* Full Path: Full path of the driver filename.



Lower Pane Modes
================

Currently, the lower pane has 4 different display modes. You can change
the display mode of the lower pane from Options->Lower Pane Mode menu.
1. All Drivers: Displays all the drivers that were loaded during the
crash that you selected in the upper pane. The drivers/module that
their memory addresses found in the stack, are marked in pink color.
2. Only Drivers Found In Stack: Displays only the modules/drivers that
their memory addresses found in the stack of the crash. There is very
high chance that one of the drivers in this list is the one that
caused the crash.
3. Blue Screen in XP Style: Displays a blue screen that looks very
similar to the one that Windows displayed during the crash.
4. DumpChk Output: Displays the output of Microsoft DumpChk utility.
This mode only works when Microsoft DumpChk is installed on your
computer and BlueScreenView is configured to run it from the right
folder (In the Advanced Options window).
You can get DumpChk from the installation CD/DVD of Windows or with
the installtion of Debugging Tools for Windows.



Crashes of Remote Network Computer
==================================

If you have multiple computers on your network and you have full
administrator access to them (e.g: you have access to \\ComputerName\c$),
you can also view the crashes of the other computers on your network
remotely. In order to do that, simply go to 'Advanced Options' (Ctrl+O)
and type the MiniDump folder of the remote computer, for example:
\\MyComp\c$\Windows\MiniDump.

Notice: If you fail to get full administrator access to the remote
computer, you should read the instructions in the following Blog post:
How to connect a remote Windows 7/Vista/XP computer with NirSoft
utilities.



Watching the crashes of multiple computers on your network
==========================================================

If you have a network with multiple computers, and you have full admin
access to these computers, you can view the blue screens list of all
these computers in one table, and easily detect computers with recurring
BSOD problems.

In order to use this feature, prepare a list of all computer names/IP
addresses that you want to inspect, and save it to a simple text file.
The computer names in the list can be delimited by comma, semicolon, tab
character, or Enter (CRLF).
Example for computer names list:

comp01
comp02
192.168.0.1
192.168.0.2
192.168.0.4

After you have a text file contains the computers list, you can go to
Advanced Options window (Ctrl+O), choose the second option and type the
computers list filename.



Command-Line Options
====================



/LoadFrom <Source>
Specifies the source to load from.
1 -> Load from a single MiniDump folder (/MiniDumpFolder parameter)
2 -> Load from all computers specified in the computer list file.
(/ComputersFile parameter)

/MiniDumpFolder <Folder>
Start BlueScreenView with the specified MiniDump folder.

/ComputersFile <Filename>
Specifies the computers list filename. (When LoadFrom = 2)

/LowerPaneMode <1 - 3>
Start BlueScreenView with the specified mode. 1 = All Drivers, 2 = Only
Drivers Found In Stack, 3 = Blue Screen in XP Style.

/stext <Filename>
Save the list of blue screen crashes into a regular text file.

/stab <Filename>
Save the list of blue screen crashes into a tab-delimited text file.

/scomma <Filename>
Save the list of blue screen crashes into a comma-delimited text file
(csv).

/stabular <Filename>
Save the list of blue screen crashes into a tabular text file.

/shtml <Filename>
Save the list of blue screen crashes into HTML file (Horizontal).

/sverhtml <Filename>
Save the list of blue screen crashes into HTML file (Vertical).

/sxml <Filename>
Save the list of blue screen crashes into XML file.

/sort <column>
This command-line option can be used with other save options for sorting
by the desired column. If you don't specify this option, the list is
sorted according to the last sort that you made from the user interface.
The <column> parameter can specify the column index (0 for the first
column, 1 for the second column, and so on) or the name of the column,
like "Bug Check Code" and "Crash Time". You can specify the '~' prefix
character (e.g: "~Crash Time") if you want to sort in descending order.
You can put multiple /sort in the command-line if you want to sort by
multiple columns.

Examples:
BlueScreenView.exe /shtml "f:\temp\crashes.html" /sort 2 /sort ~1
BlueScreenView.exe /shtml "f:\temp\crashes.html" /sort "Bug Check String"
/sort "~Crash Time"

/nosort
When you specify this command-line option, the list will be saved without
any sorting.



Translating BlueScreenView to other languages
=============================================

In order to translate BlueScreenView to other language, follow the
instructions below:
1. Run BlueScreenView with /savelangfile parameter:
BlueScreenView.exe /savelangfile
A file named BlueScreenView_lng.ini will be created in the folder of
BlueScreenView utility.
2. Open the created language file in Notepad or in any other text
editor.
3. Translate all string entries to the desired language. Optionally,
you can also add your name and/or a link to your Web site.
(TranslatorName and TranslatorURL values) If you add this information,
it'll be used in the 'About' window.
4. After you finish the translation, Run BlueScreenView, and all
translated strings will be loaded from the language file.
If you want to run BlueScreenView without the translation, simply
rename the language file, or move it to another folder.



License
=======

This utility is released as freeware. You are allowed to freely
distribute this utility via floppy disk, CD-ROM, Internet, or in any
other way, as long as you don't charge anything for this. If you
distribute this utility, you must include all files in the distribution
package, without any modification !



Disclaimer
==========

The software is provided "AS IS" without any warranty, either expressed
or implied, including, but not limited to, the implied warranties of
merchantability and fitness for a particular purpose. The author will not
be liable for any special, incidental, consequential or indirect damages
due to loss of data or any other reason.



Feedback
========

If you have any problem, suggestion, comment, or you found a bug in my
utility, you can send a message to [email protected]

 

[kljun]

juce sam snimio opet windows7 x64, i radio je neka dva sata, i dobih ovaj BSOD

Spojler

posle toga ne mogu da podignem sistem, upalim kompjuter, i odma pokrene system repair, ali on naravno nista ne uradi, i kao opciju jedino mi nudi da ugasim kompjuter. Pokrenem safe mode, isto pokrene system repair, pokrenem start windows normaly - isto ovaj se pojavi, i tako za svaku opciju.

Sumnjam na hard disk, pa bi mi trebao neki program preko kojeg mogu da vidim da li je hard ispravan ili ne, ako imate kakav slobodno javite

 

[studiovpc]

pa pise ti sta ti je izazvalo bsod, ovaj vsdatant.sys file, pogledaj na google-u sta je to pa ces znati sta je uzrok

 

[kljun]

nije mi to sada prioritet, snimao sam 3 razlcite verzije windowsa, i na svakoj je bio neki bsod, hteo bih samo da proverim hard disk


vezan je za zone alarm program, tacno je, jer sam snimao taj program i tad mi se pojavio BSOD, na prethodna dva sistema ga nisam snimao ali opet sam dobijao BSOD, vidim na netu da mnogi imaju s tim muku

 

[voodoons]

http://www.neuber.com/taskmanager/process/vsdatant.sys.html
Brisi taj ZoneAlarm

 

[kljun]

http://www.neuber.com/taskmanager/process/vsdatant.sys.html
Brisi taj ZoneAlarm

otiso je s windowsom

 

[Maverick78]

Ja ponovo u zadnjih par dana imam BSOD-ove... jednostavno ne mogu da skuzim sta me zeza. Tj. vidim da je ataport.sys i da bi to trebalo da je vezano za hardove. Imam u kucistu jedan WD 160GB i jedan WD 500GB. Za ovaj od 500GB mi HDTune javlja tu neku C7 gresku, pa mi je sistem na ovom WD 160GB. Probam da iskljucim taj od 500 i ostavim samo 160-ku i ista stvar. Povremeno se desi BSOD. Iskljucivao sam i rezac da vidim da nije do njega, posto je ataport.sys zaduzen za hardove i optiku, ali i dalje imam BSOD-ove. I kada nekako udjem u sistem, primjetim poneku anomaliju, tipa da nece Firefox da se upali, ili Internet Explorer ili neki drugi program. S druge strane igre mogu da odigram i po par sati da sve radi ok. Sumnjao sam i na ram, testirao par sati memtest-om x86 i nema errora. Da izludis... prvi put mi se desava da ne mogu da nadjem u cemu je stvar.... Doduse nisam probao sa drugim OS-om osim sa Win7. Mozda da probam XP pa da vidim sta ce da bude. Interesantno da instaliram Win normalno i on zna danima da radi ok, onda se desi prvi restart i nakon toga konstantni BSOD-ovi, najvise je uzrok ovaj ataport.sys. Bio bih zahvalan za bilo kakvu sugestiju, pomoc . Moze li biti da je nesto zveknulo na ploci?

Evo par komada od danas:

 

[voodoons]

jel ti vrela ploca, tj.chipset? koji ti je SB napon?