Wątek zamknięty

Codzienne Bluescreeny "IRQL_NOT_LESS_OR_EQUAL"

 
Koks321
Nowy
Liczba postów: 2
Post: #1

Codzienne Bluescreeny "IRQL_NOT_LESS_OR_EQUAL"


Witam

Od miesiąca codziennie/co dwa dni wywala mi w/w BSOD. Przeszukałem google i każde forum żeby znaleźć rozwiązanie, ale niestety się nie udało. Odpaliłem memtesta i 0 errorów. Przeczytałem żeby odpalić CHKDSK/r, ale też nic nie znalazło ;/

Kod:
Microsoft (R) Windows Debugger Version 6.11.0001.402 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C: \Windows\Minidump\021314-71464-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 7601 (Service Pack 1) MP (6 procs) Free x64
Product:  WinNt, suite:  TerminalServer SingleUserTS
Built by:  7601.18247.amd64fre.win7sp1_gdr.130828-1532
Machine Name:
Kernel base = 0xfffff800`0320f000 PsLoadedModuleList = 0xfffff800`034526d0
Debug session time:  Thu Feb 13 03: 23: 06.702 2014 (GMT+1)
System Uptime:  0 days 16: 01: 48.888
*********************************************************************
* 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 D1, {fffff8004328f420, 2, 8, fffff8004328f420}

***** 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                                     ***
***                                                                   ***
*************************************************************************
*********************************************************************
* 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 :  ntoskrnl.exe ( nt+75bc0 )

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


Bardzo proszę o pomoc przy rozwiązaniu tego problemu, ponieważ sam sobie nie poradzę ;/


Specyfikacja komputera:
AMD FX-6100 3,3 Ghz OC na 4,4Ghz
GeForce 760 OC 2gb
Ram 2x8Gb
HDD 2Tb

Antywirus: Avast

Pozdrawiam

27.02.2014 19:39

Znajdź wszystkie posty użytkownika
irocket
Senior Moderator

Liczba postów: 2.337
Post: #2

RE: Codzienne Bluescreeny "IRQL_NOT_LESS_OR_EQUAL"


Wrzuć minidumpy, a nie wrzucasz źle zdebugowane, bez symboli, itp

27.02.2014 19:45

Znajdź wszystkie posty użytkownika
Koks321
Nowy
Liczba postów: 2
Post: #3

RE: Codzienne Bluescreeny "IRQL_NOT_LESS_OR_EQUAL"


http://speedy.sh/sd9uS/minidump.rar

27.02.2014 19:58

Znajdź wszystkie posty użytkownika
Wątek zamknięty

Podobne wątki
Wątek: Autor Odpowiedzi: Wyświetleń: Ostatni post
Windows 7 - Bluescreeny i crash'e gier. qudelzin 4 1.682 11.03.2016 16:23
Ostatni post: qudelzin
Windows 7 - ciągły restart i bluescreeny tiger85153 0 1.084 25.02.2015 20:32
Ostatni post: tiger85153
Bluescreeny w Windows 7 - pliki DMP do analizy maciej798 2 1.589 27.09.2014 18:25
Ostatni post: Maxim128
Rozwiązany Bluescreeny analiza - bluescreenview + minidump Fudal 1 1.811 12.08.2014 23:36
Ostatni post: thermalfake
Częste Bluescreeny i wyłaczanie się laptopa richie1989 6 1.521 03.05.2014 19:13
Ostatni post: thermalfake
Bluescreeny i crashe Chrome'a fckpoverty 0 992 04.04.2014 20:33
Ostatni post: fckpoverty
« Starszy wątek | Nowszy wątek »

Temat został oceniony na 0 w skali 1-5 gwiazdek.
Zebrano 1 głosów.