Witam bardzo serdecznie!
W ostatnich dniach, przy graniu w APB dosyć często wyskakuje mi blue screen…
Dokładnie gdzieś tak po paru minutach gry.
Czytałem, że problem może być spowodowany brakiem aktualnych sterowników, pobrałem lecz i to nie pomogło.
Inny sposób to wyłączenie audio w grze, on też zawiódł.
Więc kieruję do was prośbę o pomoc!
Jeżeli będzie coś jeszcze potrzebne to dajcie znać.
Informacje z BSV:
==================================================
Plik zrzutu : 031813-16140-01.dmp
Data wystąpienia błędu: 2013-03-18 22:02:40
Typ błędu : DRIVER_VERIFIER_DETECTED_VIOLATION
Kod błędu : 0x000000c4
Parametr 1 : 00000000`00000091
Parametr 2 : 00000000`00000002
Parametr 3 : fffff800`03048cc0
Parametr 4 : 00000000`00000000
Spowodowane przez sterownik: nvlddmkm.sys
Spowodowane przez adres: nvlddmkm.sys+1da743
Opis pliku :
Nazwa produktu :
Firma :
Wersja pliku :
Procesor : x64
Adres błędu : ntoskrnl.exe+75c40
Adres stosu 1 :
Adres stosu 2 :
Adres stosu 3 :
Nazwa komputera :
Pełna ścieżka : C:\Windows\Minidump\031813-16140-01.dmp
Liczba procesorów : 4
Wersja główna : 15
Wersja pomniejsza : 7601
Rozmiaru pliku ze zrzutem: 307 240
==================================================
Proszę logi z DBG:
Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C]
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 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 (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.18044.amd64fre.win7sp1_gdr.130104-1431
Machine Name:
Kernel base = 0xfffff800`02e49000 PsLoadedModuleList = 0xfffff800`0308d670
Debug session time: Mon Mar 18 22:01:26.875 2013 (UTC + 1:00)
System Uptime: 0 days 0:09:22.421
*********************************************************************
* 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 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 C4, {91, 2, fffff80003048cc0, 0}
***** 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***
******
*************************************************************************
Probably caused by : ntoskrnl.exe ( nt+75c40 )
Followup: MachineOwner
---------
P.S Ostatnio kupiłem kartę graficzną nVidie GeForce GTX650Ti (OverClocking) przy tym, że mam zasilacz o mocy tylko 320W więc nie wiem czy to przypadkiem nie może głównym skutkiem tego błędu, no ale w innych grach typu FarCry3, Assassins Creed 3 (najbardziej wymagających) przy maks detalach chodzi płynnie bez żadnych problemów.
P.SS Jeszcze jedna informacja, chyba dość ważna, nie posiadam sterowników do BIOS, ponieważ mam dosyć starą płytę główną i sterowniki do niego do win7 są tylko w wersji 32bit. No ale wydaje mi się, że to nie jest przyczyną tego błędu. Liczę na pomoc :C