Drug Lazar, dali ovo ima smisla?
(nekakva analiza please)
http://speedy.sh/5JRTF/Minidump.rar
Za pocetak makni Virtual Clone Drive i dobro se osiguraj da je NTFS zdrav i citav (chkdsk C: /f ili provjera&scan za bad sectore chkdsk C: /r /f)
Inace, BSOD je kao sto znas(?) REGISTRY_ERROR
Za pocetak makni Virtual Clone Drive i dobro se osiguraj da je NTFS zdrav i citav (chkdsk C: /f ili provjera&scan za bad sectore chkdsk C: /r /f)
Inace, BSOD je kao sto znas(?) REGISTRY_ERROR
-kasno je za spašavanje... (ok, treba probati, ali ne gine nova instalacija). Raspao se reg. Prvi error (ostali su posljedica).
-uobičajeni uzroci, RAM (ponekad memtest ne pokazuje problem, jedan po jedan eliminiraš..). Clone, RamDisk, kao i DT... kao i mixanje starih drivera (pogotovo ako nečeg nema za 7x64). Prvi sumnjivac je RAM, ali na AMDu (OC i unlock jezgre?) ..+ nestabilan chipset. Zato je OK za kućni PC, ne za radni.
btw, chkdsk /r
-kasno je za spašavanje... (ok, treba probati, ali ne gine nova instalacija). Raspao se reg. Prvi error (ostali su posljedica).
-uobičajeni uzroci, RAM (ponekad memtest ne pokazuje problem, jedan po jedan eliminiraš..). Clone, RamDisk, kao i DT... kao i mixanje starih drivera (pogotovo ako nečeg nema za 7x64). Prvi sumnjivac je RAM, ali na AMDu (OC i unlock jezgre?) ..+ nestabilan chipset. Zato je OK za kućni PC, ne za radni.
btw, chkdsk /r
Da, vulgarno receno RAM moze biti malo zilaviji i tako, pokvaren, moze korumpirati podatke na disku odnosno u ovom slucaju Registry. Prilikom OC-anja moze se cesto puta previdjeti dase i chipset (previse) zagrijava i to moze biti problem...
Prilikom OC-anja moze se cesto puta previdjeti dase i chipset (previse) zagrijava i to moze biti problem...
- to je oduvjek bio problem na AMDu (od kad je mem kontroler u CPU, osjetljivost-robustnost)... Pogotovo s kombinacijom kad user kaže ''.. pa do danas je radio OK''.. OCan, overvoltan itd. Naravno, tad je kompletan za smeće..
Više me brine ovaj konkretan Kihotyjev slučaj (tj DonKihotyjeva reputacija), jer je problem takav da je skoro neuhvatljiv (uzrok-greška), a on ga mora fixati.
Jedino rješenje je novi install (reinstall će nasljediti.. ipak možda prođe pa treba i to probati). Ali, bez otklanjanja uzroka, opet će se vratit Kihotiju na popravak i bit će 'loš majstor'... Zato je bavljenje politikom bolji posao, nema determinizma a zarada je OK, čak i kad ništa ne napraviš/ne znaš... :-))
EDIT: Mislim da dečki nisu skužili da se radi o mom PC-u.
Ovako, RAM sam više puta provjerio, od Corsaira, Kinstona, OCZa, Mushkina (koji ne radi dobro na ASRocku),
Apacera, Kingmaxa, itd itd. Nije problem.
Chipset je hladan kao led (ne prelazi 36°C, dok isti chipset na gigabyte ploči 990FXA-UD7 radi na 90°C pod opterećenjem - Gigabyte kaže da je to normalno i u granicama normale).
Napajanja promjenio dva radi sigurnosti (Corsair VX550 i LCPower 560W GP3), SSD uzeo novi OCZ 60GB umjesto Corsaira 60GB.
(zadnji FW 2.15 na OCZ-u, flashan, secure-erasean, opet force-flashan, kako OCZ traži)
Procesor zalockane jezgre, stavljen na stock 3.2GHz X2 555BE, opet BSoD.
Napravim novu instalaciju - opet BSoD i reboot.
Probam sve kvalitetne verzije BIOS-a za ploču:
1.50
1.48
1.47
1.35
1.30
Ista stvar.
Probam sa drugom grafikom - ista stvar.
Stavim BOX cooler (recimo da HR-02 možda svojom masom previše razvlači ploču, dakle problem u vodovima) - ista stvar.
OK, dakle problem u Windowsima.
Uzmem svoje ORIGINAL Windowse 7 Pro (ne ultimate krekane, nego ORIGINAL) - ista stvar.
Ok, googlam malo. Originalni win su u banani. Skinem Win 7 PRO skrpane sa SP1 - aktiviram svojim ključem - ista stvar.
Koja kifla više?
OK, googlam malo dalje, ono, i drugima se to dešava, ali na Win 8 svima sve radi OK. Pa dobro, odoh i ja probati Win 8 - nema BSoD-a.
Šta sad momci? Da se samoubijem iz nehaja?
Odlučio sam probati naći nekakvu modanu verziju Win 7 Pro (da mogu iskoristiti svoj ključ na njoj) - samo da isprobam dali će se i dalje dešavati.
Našao sam ovu verziju:
"7 Gamerz Pro" (samo zguglajte)
Prije nje sam instalirao bar 10ak verzija Win 7 - u uvjek sa piratom radi ok, sa originalnim nemodanim - BSoD.
Sa ovom verzijom za sada (kuc kuc u drvo) - sve radi OK - i ključ fino prošao aktivaciju.
Očito je M$ negdje nešto syebao sa SSD-om, i samo skrpani OS dobro radi sa AHCI-AMD driverima.
Da napomenem da na Intel platformi tih problema nema.
Procesor otključan X4 na 4GHz - sve šljaka normalno.
Procesor otključan X4 na 4GHz - sve šljaka normalno.
Hoces reci da piratska verzija koja u sebi ima nepotpisane drivere (gaming verzija, jel?) ne radi probleme vec ova originalna SP1?
Tako je - piratski OS radi OK, originalni OS radi probleme, makar CPU bio zaključan i neoverclockan. Čudno zar ne?
Ovo računalo ionako ne koristim na poslu, a i da mi dođe inspekcija doma - imam originalni medij i račun, po EULA mogu
si software koji kupim prilagoditi sebi kako mi paše. (a koristim Pro verziju, dakle onu za koju imam licencirani ključ - i aktivacija prolazi normalno)
-po opisanom, uzrok je killswitch koji se iz nekog razloga aktivira. Driveri AMD-AHCI-SSD nebi mogli biti objašnjenje (jer ih vjerojatno i sad koristiš).
- Nešto je u tvojoj aktivaciji ili kombinaciji instaliranog soft i podešavanjima 'sumnjivo' MSovim interesima, pa malo kilne reg. (piratski soft upravo neke od tih provjera isključije kao banalni wga).
Eto jednog od objašnjenja neuhvatljivim problemima. (Ili je ipak svizac, ili su u šumici... to nećemo saznati, osim da netko drugi, na drugi način, drugim softwareom, složi PiCeka D.Kyhu.). Pa sad mladići iz okolice rafinerije, mogu pohitati s CDima i okušati sreću, ako se ne varam, nagradni fond je stisak ruke, lajkanje i možd piva. -navalite :))
Moguće je.
U ovoj pajrat verziji ne postoji update KB971033, niti je instaliran niti mi ga nudi kao mogućnost instalacije.
Mogao bi opet vratiti Origigi Win, aktivirati ti ih normalno, ali bez da instaliram KB971033 (WGA checker).
Uvjek sam ga do sada instalirao, eto pitaj boga zašto, originalni OS pa mi ne smeta.
Tko zna... M$ je čudna biljka... Kažem, na W8 nema tih problema.
Mislio sam čak da je problem i zvučna kartica (X-Fi stara PCI kojoj origigi zvučni driveri nisu nešto,
pa koristim modane, ali probao sam dići OS bez kartice sa integriranom zvučnom - ista stvar).
Moguće je.
U Control Panel > Advanced System Properties > Environment Variables > User Variables for tvoje_ime > klik na New i unesi ovu varijablu devmgr_show_nonpresent_devices u Value unesi 1 [Restart, log off ili ubij explorer]
Sa ovim ce vidjeti mnogo jasnije u Device Manageru odnosno vidjet ces uredaje koji nisu prisutni i najbitnije, vidjet ces Non-Plug&Play uredaje (Driveri od Antivirusa na pr.)
[edit]
Sa ovim mi je bio cilj da vidis verzije od drivera za disk ili chipset odnosno napravis komparaciju sa piratski driverima i sa originalnim
==================================================
Dump File : 031412-25609-01.dmp
Crash Time : 14.3.2012. 10:32:28
Bug Check String : PFN_LIST_CORRUPT
Bug Check Code : 0x0000004e
Parameter 1 : 0x00000099
Parameter 2 : 0x000329d2
Parameter 3 : 0x00000000
Parameter 4 : 0x00560001
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+d1460
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7600.16905 (win7_gdr.111025-1503)
Processor : 32-bit
Crash Address : ntoskrnl.exe+d1460
Stack Address 1 : ntoskrnl.exe+e24a0
Stack Address 2 : ntoskrnl.exe+8589e
Stack Address 3 : ntoskrnl.exe+6bac9
Computer Name :
Full Path : C:\Windows\Minidump\031412-25609-01.dmp
Processors Count : 2
Major Version : 15
Minor Version : 7600
Dump File Size : 137.928
==================================================
==================================================
Dump File : 031312-24109-01.dmp
Crash Time : 13.3.2012. 22:28:08
Bug Check String : SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
Bug Check Code : 0x1000007e
Parameter 1 : 0xc0000005
Parameter 2 : 0x875be427
Parameter 3 : 0x87247b38
Parameter 4 : 0x87247710
Caused By Driver : Wdf01000.sys
Caused By Address : Wdf01000.sys+21427
File Description : Kernel Mode Driver Framework Runtime
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 1.9.7600.16385 (win7_rtm.090713-1255)
Processor : 32-bit
Crash Address : Wdf01000.sys+21427
Stack Address 1 : Wdf01000.sys+22d85
Stack Address 2 : Wdf01000.sys+15983
Stack Address 3 : cdrom.sys+1a02
Computer Name :
Full Path : C:\Windows\Minidump\031312-24109-01.dmp
Processors Count : 2
Major Version : 15
Minor Version : 7600
Dump File Size : 137.928
==================================================
==================================================
Dump File : 031312-28265-01.dmp
Crash Time : 13.3.2012. 21:02:47
Bug Check String : PAGE_FAULT_IN_NONPAGED_AREA
Bug Check Code : 0x00000050
Parameter 1 : 0x94bfd000
Parameter 2 : 0x00000000
Parameter 3 : 0x87c0a493
Parameter 4 : 0x00000000
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+5eb86
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7600.16905 (win7_gdr.111025-1503)
Processor : 32-bit
Crash Address : ntoskrnl.exe+5eb86
Stack Address 1 : ntoskrnl.exe+38948
Stack Address 2 : seehcri.sys+493
Stack Address 3 : seehcri.sys+37d5
Computer Name :
Full Path : C:\Windows\Minidump\031312-28265-01.dmp
Processors Count : 2
Major Version : 15
Minor Version : 7600
Dump File Size : 137.928
==================================================
==================================================
Dump File : 031312-23718-01.dmp
Crash Time : 13.3.2012. 21:00:35
Bug Check String : IRQL_NOT_LESS_OR_EQUAL
Bug Check Code : 0x0000000a
Parameter 1 : 0x765fffe8
Parameter 2 : 0x00000002
Parameter 3 : 0x00000001
Parameter 4 : 0x830d5681
Caused By Driver : halmacpi.dll
Caused By Address : halmacpi.dll+392d
File Description : Hardware Abstraction Layer DLL
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7600.16385 (win7_rtm.090713-1255)
Processor : 32-bit
Crash Address : ntoskrnl.exe+38b3b
Stack Address 1 : ntoskrnl.exe+93681
Stack Address 2 : ntoskrnl.exe+bdda6
Stack Address 3 : ntoskrnl.exe+229c7
Computer Name :
Full Path : C:\Windows\Minidump\031312-23718-01.dmp
Processors Count : 2
Major Version : 15
Minor Version : 7600
Dump File Size : 142.240
==================================================
==================================================
Dump File : 031312-26281-01.dmp
Crash Time : 13.3.2012. 1:37:41
Bug Check String : PFN_LIST_CORRUPT
Bug Check Code : 0x0000004e
Parameter 1 : 0x00000099
Parameter 2 : 0x00003eea
Parameter 3 : 0x00000000
Parameter 4 : 0x00160001
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+d1460
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7600.16905 (win7_gdr.111025-1503)
Processor : 32-bit
Crash Address : ntoskrnl.exe+d1460
Stack Address 1 : ntoskrnl.exe+e24a0
Stack Address 2 : ntoskrnl.exe+24e81
Stack Address 3 : ntoskrnl.exe+5dd1a
Computer Name :
Full Path : C:\Windows\Minidump\031312-26281-01.dmp
Processors Count : 2
Major Version : 15
Minor Version : 7600
Dump File Size : 142.240
==================================================
==================================================
Dump File : 031212-30437-01.dmp
Crash Time : 12.3.2012. 21:51:04
Bug Check String : IRQL_NOT_LESS_OR_EQUAL
Bug Check Code : 0x0000000a
Parameter 1 : 0x8dda7fe8
Parameter 2 : 0x00000002
Parameter 3 : 0x00000001
Parameter 4 : 0x830ca681
Caused By Driver : halmacpi.dll
Caused By Address : halmacpi.dll+392d
File Description : Hardware Abstraction Layer DLL
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7600.16385 (win7_rtm.090713-1255)
Processor : 32-bit
Crash Address : ntoskrnl.exe+38b3b
Stack Address 1 : ntoskrnl.exe+93681
Stack Address 2 : ntoskrnl.exe+bdda6
Stack Address 3 : ntoskrnl.exe+229c7
Computer Name :
Full Path : C:\Windows\Minidump\031212-30437-01.dmp
Processors Count : 2
Major Version : 15
Minor Version : 7600
Dump File Size : 142.240
==================================================
==================================================
Dump File : 031212-27046-01.dmp
Crash Time : 12.3.2012. 21:42:17
Bug Check String : PFN_LIST_CORRUPT
Bug Check Code : 0x0000004e
Parameter 1 : 0x00000099
Parameter 2 : 0x00004241
Parameter 3 : 0x00000002
Parameter 4 : 0x00038e1c
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+d1460
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7600.16905 (win7_gdr.111025-1503)
Processor : 32-bit
Crash Address : ntoskrnl.exe+d1460
Stack Address 1 : ntoskrnl.exe+e24a0
Stack Address 2 : ntoskrnl.exe+87da4
Stack Address 3 : ntoskrnl.exe+7d22a
Computer Name :
Full Path : C:\Windows\Minidump\031212-27046-01.dmp
Processors Count : 2
Major Version : 15
Minor Version : 7600
Dump File Size : 142.240
==================================================
==================================================
Dump File : 031212-23937-01.dmp
Crash Time : 12.3.2012. 11:21:31
Bug Check String : DRIVER_IRQL_NOT_LESS_OR_EQUAL
Bug Check Code : 0x000000d1
Parameter 1 : 0x801ba4d8
Parameter 2 : 0x00000002
Parameter 3 : 0x00000000
Parameter 4 : 0x9071a610
Caused By Driver : USBPORT.SYS
Caused By Address : USBPORT.SYS+8610
File Description : USB 1.1 & 2.0 Port Driver
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7600.16385 (win7_rtm.090713-1255)
Processor : 32-bit
Crash Address : ntoskrnl.exe+38b3b
Stack Address 1 : USBPORT.SYS+8610
Stack Address 2 : USBPORT.SYS+7fda
Stack Address 3 : USBPORT.SYS+9215
Computer Name :
Full Path : C:\Windows\Minidump\031212-23937-01.dmp
Processors Count : 2
Major Version : 15
Minor Version : 7600
Dump File Size : 180.568
==================================================
Pozdrav!
Evo ovo mi se par dana događa.
Prvo je to bilo ovako:
Upalim komp ucita windowse i restarta se i tako 2 puta i onda normalno radi.
Danas mi se dogodiilo da kad upalim komp ucitaju se windowsi i pojavi se taj BSOD,i tako cijelo vrijeme,odmah mi se pojavii!
Molim vas puno!
U Control Panel > Advanced System Properties > Environment Variables > User Variables for tvoje_ime > klik na New i unesi ovu varijablu devmgr_show_nonpresent_devices u Value unesi 1 [Restart, log off ili ubij explorer]
Sa ovim ce vidjeti mnogo jasnije u Device Manageru odnosno vidjet ces uredaje koji nisu prisutni i najbitnije, vidjet ces Non-Plug&Play uredaje (Driveri od Antivirusa na pr.)
[edit]
Sa ovim mi je bio cilj da vidis verzije od drivera za disk ili chipset odnosno napravis komparaciju sa piratski driverima i sa originalnim
Meni tog nema u CP-u..
Meni tog nema u CP-u..
Fakat..!!
Pogresio sam. Moje isprike. To je na desni klik na My Computer > Properties
imam bsod , piše driver_irql_not_less_or_equal , može li pomoć . HVALA
Microsoft (R) Windows Debugger Version 6.2.8229.0 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\Minidump\031812-46940-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\ntkrnlpa.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntkrnlpa.exe
*** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe
Windows 7 Kernel Version 7600 MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16905.x86fre.win7_gdr.111025-1503
Machine Name:
Kernel base = 0xe2a11000 PsLoadedModuleList = 0xe2b59810
Debug session time: Sun Mar 18 22:33:21.733 2012 (UTC + 1:00)
System Uptime: 0 days 10:16:33.592
*********************************************************************
* 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\ntkrnlpa.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntkrnlpa.exe
*** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe
Loading Kernel Symbols
...............................................................
................................................................
..............
Loading User Symbols
Loading unloaded module list
...........
TRIAGER: Could not open triage file : C:\Program Files\Windows Kits\8.0\Debuggers\x86\triage\oca.ini, error 2
TRIAGER: Could not open triage file : C:\Program Files\Windows Kits\8.0\Debuggers\x86\winxp\triage.ini, error 2
*******************************************************************************
Probably caused by : pacer.sys ( pacer+5c20 )
Followup: MachineOwner
---------
1: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
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 kernel debugger is available get stack backtrace.
Arguments:
Arg1: d8595000, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000001, value 0 = read operation, 1 = write operation
Arg4: d456e41b, address which referenced memory
Debugging Details:
------------------
***** Kernel symbols are WRONG. Please fix symbols to do analysis.
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands 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 ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands 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 ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands 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 ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands 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 ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands 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 ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands 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 ***
*** ***
*************************************************************************
TRIAGER: Could not open triage file : C:\Program Files\Windows Kits\8.0\Debuggers\x86\triage\modclass.ini, error 2
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands 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 ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands 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 ***
*** ***
*************************************************************************
ADDITIONAL_DEBUG_TEXT:
Use '!findthebuild' command to search for the target build information.
If the build information is available, run '!findthebuild -s ; .reload' to set symbol path and load symbols.
MODULE_NAME: pacer
FAULTING_MODULE: e2a11000 nt
DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bc916
WRITE_ADDRESS: unable to get nt!MmSpecialPoolStart
unable to get nt!MmSpecialPoolEnd
unable to get nt!MmPagedPoolEnd
unable to get nt!MmNonPagedPoolStart
unable to get nt!MmSizeOfNonPagedPoolInBytes
d8595000
CURRENT_IRQL: 0
FAULTING_IP:
+0
d456e41b 8801 mov byte ptr [ecx],al
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT
BUGCHECK_STR: 0xD1
LAST_CONTROL_TRANSFER: from d456e41b to e2a5786b
STACK_COMMAND: kb
FOLLOWUP_IP:
pacer+5c20
a6bc9c20 ?? ???
SYMBOL_STACK_INDEX: b
SYMBOL_NAME: pacer+5c20
FOLLOWUP_NAME: MachineOwner
IMAGE_NAME: pacer.sys
BUCKET_ID: WRONG_SYMBOLS
Followup: MachineOwner
---------
Ako moze tko analizirati ovaj minidump bio bih zahvalan.
To je vec osmi BSOD u 5-6 sati.
Najvise sumnjam u HDD, pa ako se moze izvuci koja informacija iz toga..
Ako moze tko analizirati ovaj minidump bio bih zahvalan.
To je vec osmi BSOD u 5-6 sati.
Najvise sumnjam u HDD, pa ako se moze izvuci koja informacija iz toga..
-imaš neko (novo) smeće, trojanac gMouUsb.sys vjerojatni uzrok (googlaj malo..). Ostatak je ntoskrnl+usb+hid možda nakon čišćenja prorade ili je sistem već za otpis (ponekad za nove viruse nema fixa neko vrijeme pa je praktičnije pribaviti liveCD i pripremiti se za format diska).
Probat cu ga jos sa Hitman-om skenirat, ako ne nade nista ide reinstall...
pozz,
Da li mi netko može pomoći u vezi BSOD-a koji mi se povremeno javlja, nije često ali recimo 1 u dva tjedna i onda dalje sve normalno radi.
uglavnom na kraju izbaci rečenicu:
technical information:
****Stop: 0x0000001E (OxFFFFFFFFc0000005,0xFFFFF800033BFAC0,0x000000000000,
0xFFFFFFFFFFFFFFFF)
Da li možda netko zna o čemu je riječ, pošto sam ja totalni laik što se toga tići.
thx
technical information:
****Stop: 0x0000001E (OxFFFFFFFFc0000005,0xFFFFF800033BFAC0,0x000000000000,
0xFFFFFFFFFFFFFFFF)
Nema puno pomoći od toga! Spakiraj i stavi Minidump (nalazi se u C:\Windows\Minidump folderu) na neki share servis (ovo je samo primjer ),pa će ti ga netko analizirati i reći gdje je problem!
A možeš i sam probati s ,recimo , BlueScreenView -om.
ile Crash Time Bug Check String Bug
*******************************
obrisano by Lazarus Long
*******************************
sry ali fakat se ne kužim baš u te stvari oko BSOD-a...
jel može netko nešto pročitati iz ovog gore u čemu je problem?
thx
sry ali fakat se ne kužim baš u te stvari oko BSOD-a...
Tvoj post sam morao preurediti zato sto to nije imao smisla (kopiranje sirovih minidump podataka)
Za pocetak, ako koristis Windows 7, u Start utipkaj Memory Check pokreni Windows Memory Diagnostic i pusti da se testiranje zavrsi. Za ovo ne treba imati nikakvih tehnickih predznanja. Na kraju ce ti biti javljeno da li imas problema sa RAM-om ili ne.
Dakle, osigurajmo se da li je RAM ispravan ili ne. Nakon toga idemo dalje
znam da sam ga fakat nadrobio post s tim svim podacima... ok thx probat ću danas navecer pa javim što je bilo.
Htio bi znati što je uzrokovalo ovaj problem ako je moguće.
Da ne postam ponovo ovdje isto stavio sam link na lock-anu temu...
http://www.bug.hr/forum/post/razni-hardverski-problemi/bsod-informacija/2800196.aspx
Htio bi znati što je uzrokovalo ovaj problem ako je moguće.
Da ne postam ponovo ovdje isto stavio sam link na lock-anu temu...
http://www.bug.hr/forum/post/razni-hardverski-problemi/bsod-informacija/2800196.aspx
Problem sa hibernacijom. U command prompt upisi ovo
powercfg /hibernate /size 100
i lupi Enter (:
Veli mi access denied. Heh :/
Veli mi access denied. Heh :/
Desni klik na command prompt i run as administrator
