BSOD - što, zašto i kako

Zna li neko, već 2 dana surfam u potrazi za odgovorom ali ništa, nije valjda reinstall jedino rješenje ?

E caka je da on uopće ne radi dump memorije, buta sam već sa Hirensom i u MiniDump folderu nema ništa !

BTW, testira sam RAM i HDD i nije nađena nikakva greška !

To je prvo ta sam napravia a kako bi inače dozna o kjem je BSOD-u riječ, fora je da nema donje linije "Dumping Physical Memory", zadnaj linija je STOP code

Probaću

Ništa, u Registry-u su mi jednake vrijednosti ka i kod tebe ali on ne baca minidump-ove !

Reinstaliraj (stavi nove) drivere od grafičke kartice.

To je dio drivera za graficku. Obrisi ih u safe modu Driver sweeperom te restartaj komp i nanovo instaliraj.

Hvala na ovoj korisnoj stvari...Sigurno ce pomoci....

Molim nekog tko se razumije puno bolje nego ja da mi pomogne!!!

Radi se o Siemens Gigaset SE 461 WiMAX i radi u bridge modu, odnosno kao modem. Swicher mi je riješio problem na XP-u, a šta da radim sa Sedmicom? Driveri su svi kompletno up to date! Pazio sam i koje programe instaliram. Jel se može zamjenit router, za neki drugi model? Zvao sam Optimu, a oni nemaju pojma u čemu je problem! Dali se može vidit dmp file-ovima nešto više? Pozz

Pozdrav svima, upravo se registrirah, trebam pomoć kako slijedi

Danas mi se pojavio bsod na sekundu i restartao komp. Jedino što sam mogla napraviti je pričekati da se digne ponovo i win su mi sami napisali u prozorcicu error:

BCCode: 1000008e

BCP1: C0000005

BCP2: BF82DE77

BCP3: A4C11A40

BCP4: 00000000

OSVer:5_1_2600

SP: 3_0

Product: 256_1

Kada sam to prepisala , zagasila sam prozor i javila se vama!!

Imam Acer Aspire Notebook 5810T/5810TZ/5410T series, model je MS 2272.

Frend koji je IT strucnjak mi je skinuo Linux koji je bio gore (maknula sam ga jer nije imao graficko sucelje) i stavila original XP (odnosno Corporate edition, skoro kao original).

 Komp je novi, kupljen u ljeto 2009. kod nas.

Ali... ovo je drugi , isti takav. Naime, prvi koji je kupljen je radio par dana i ugasio se , nije se moglo ni u BIOS ući.. A prije nego se to dogodilo , glazba je jaaako zavlačila često i preskakala.. Ne stalno..Onda je crknnuo skroz. Odnesla ga na servis i dobila novi. Onda je glazba opet preskakala par dana , ali svako toliko, ne stalno. I sada 2,3, mjeseca nista i danas plavi ekran :(((

Što mi je raditi, help  

Inače, nemam ništa natrpano gore, nista skoro ne skidam, par filmova do sada, nemam wifi nego žični net vec jako dugo. Stalno upgrade-am antivirus, pokrecem ccleaner , aviru i 2 puta sam ga defragmentirala. nista novo nemam instalirano osim glary utilities što nikako ne bi trebalo biti problem... .. ..

TNX..

Bas sam napisala..jel se vidi ? Ako ne u poruci , onda u profilu...

Meni izbacuje plavi ekran

i ovo

KERNEL_STACK_INPAGE_ERROR

Technical information:

STOP : 0x00000077 (0xC000000E,0x00000000,0x04FCD000)

Evo ljudi molio bih pomoći :(,izludit će me a laptop mi treba za posao u petak već :(

HVALA SVIMA UNAPRIJED!

BSOD mi se pojavi ,i nakon restarta se normalno podigao sistem ,da li je to znak da ce se ponovo pojaviti ,ili moze da se ne pojavi?:D,hvala.

Nemam pojma sta da uradim radi prevencije ,napravio sam scan sa avirom,pa antimalvare-om,nije mi pokazao nikakve viruse!

  Ubaci instalacioni CD od Windows bootaj sa njega i uradi repair ili tako nesto

e ovako zadnja dva dana imam BSOD komp se restarta i poslije je sve normalno koristim win 7.Zašto mi je odjednom počeo BSOD?? Našao sam minidump datoteku ali neznam kaj s njom

uspio sam ju otvoriti

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

Loading Dump File [C:\Windows\Minidump\022010-26718-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 \SystemRoot\system32\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 7 Kernel Version 7600 MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16481.x86fre.win7_gdr.091207-1941
Machine Name:
Kernel base = 0x8303c000 PsLoadedModuleList = 0x8317b570
Debug session time: Sat Feb 20 20:18:52.868 2010 (GMT+1)
System Uptime: 0 days 2:11:33.852
*********************************************************************
* 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 \SystemRoot\system32\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
........
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000008E, {c0000005, 8325150e, 9679079c, 0}

*** WARNING: Unable to verify timestamp for tdrpm251.sys
*** ERROR: Module load completed but symbols could not be loaded for tdrpm251.sys
***** 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                                      ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    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                                      ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    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                                     ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    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 : tdrpm251.sys ( tdrpm251+2b5cf )

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

 Molim analizu minidumpa