Blue screen.

Problema jau sena. Užvakar perrašė windows 7, patikrino HDD. Vakar išvaliau pc nuo dulkių. Bet visvien keičiant žaidimų (pvz cs 1,6) grafikas, ar paprastai juos žaidžiant, net žiūrint filmą per VLC gaunu blue screen. Gal kas žinot kaip išspręsti šitą error?

0x00000124 (0x00000000, 0x857F7024, 0xB2000000, 0x00060151)

0x00000124 (0x00000000, 0x857C9024, 0xB2000000, 0x00060151)

0x00000124 (0x00000000, 0x857E1024, 0xB2000000, 0x00060151)

0x00000124 (0x00000000, 0x857EE024, 0xB2000000, 0x00060151)

vaizdo plokstes driveriai naujausi?

vaizdo plokstes driveriai naujausi?

Taip :unsure:

Taip :unsure:

bandei ziuret kokios temperaturos vaizdo plokstes ir CPU? gal kartais perkaista? jei aukstos temperaturos patarciau pertept termo pasta

bandei ziuret kokios temperaturos vaizdo plokstes ir CPU? gal kartais perkaista? jei aukstos temperaturos patarciau pertept termo pasta

Gal žinai kaip patikrinti temperatūrą? :lol: Ir kokia maždaug turėtų būti normali?

Gal žinai kaip patikrinti temperatūrą? :lol: Ir kokia maždaug turėtų būti normali?

http://www.cpuid.com/downloads/hwmonitor/1.21-setup.exe

su sita programa pamatysi beveik visu pc daliu temperatura,jei nieko nedarant koks 40-50C tai nieko blogo.

jei pradejus ka nors daryti bus >85-90 tada jau negerai

"žaidimų (pvz cs 1,6) grafikas, ar paprastai juos žaidžiant, net žiūrint filmą per VLC gaunu blue screen. Gal kas žinot kaip išspręsti šitą error?"

Jei kompas nekaista, o taip tikrai tikėtina, tuomet problema bus tokia, kad kompo vaizdo plokštė "medinė" ir nėra ant Windows Vista/7 driverių, o tu rašai nuo XP sukurtus, štai ir problema. Norint vėl žaisti žaidimus - grįžti prie XP ir senesių arba atsisakai vaizdo plokštės tvarkyklių. Dar tikėtina, bet mažai procentų, kad užrašei ant Windows 7 numatytųjų XP driverius arba kokius kitus. Sekmės.

Sena, bet nėra baisiai medinė :D Kaip rodo Nvidia tinklapyje tai yra driveriai ant 7 windows :unsure:

Temperatūra išjungus daugelį programų:

Temperatūra po blue screen:

Čia temperatūra įjungus sims 3:

Prisek memory dump'ą (C:\windows\memory.dmp arba C:\windows\minidump). Užmesiu akį.

Prisek memory dump'ą (C:\windows\memory.dmp arba C:\windows\minidump). Užmesiu akį.

Daugiausiai 10MB galima prisegti per šį forumą, o su notepad neatidaro, nežinau kaip atkopijuoti :unsure: Iš minidump mažiau užima, bet neleidžia įkelti :D "Klaida Jūs neturite teisės įkelti tokio tipo failų".

P.S. Ačiū visiems už pagalbą! ^_^

EDIT: parsisiunčiau kažkokią programą, tai atidariau, bet man atrodo kažkas ne taip :D

Microsoft ® Windows Debugger Version 6.2.9200.16384 X86

Copyright © Microsoft Corporation. All rights reserved.

 

 

Loading Dump File [C:\Windows\MEMORY.DMP]

Kernel Summary Dump File: Only kernel address space is 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+ *

*********************************************************************

*** ERROR: Module load completed but symbols could not be loaded for ntkrpamp.exe

Windows 7 Kernel Version 7601 (Service Pack 1) MP (2 procs) Free x86 compatible

Product: WinNt, suite: TerminalServer SingleUserTS

Built by: 7601.17514.x86fre.win7sp1_rtm.101119-1850

Machine Name:

Kernel base = 0x82c0a000 PsLoadedModuleList = 0x82d54850

Debug session time: Thu Feb 21 02:25:16.594 2013 (UTC + 2:00)

System Uptime: 0 days 2:26:33.219

WARNING: Process directory table base 7EFA1280 doesn't match CR3 00185000

WARNING: Process directory table base 7EFA1280 doesn't match CR3 00185000

*********************************************************************

* 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+ *

*********************************************************************

*** ERROR: Module load completed but symbols could not be loaded for ntkrpamp.exe

Loading Kernel Symbols

...............................................................

................................................................

........................

Loading User Symbols

PEB is paged out (Peb.Ldr = 7ffdc00c). Type ".hh dbgerr001" for details

Loading unloaded module list

.......

*** ERROR: Symbol file could not be found. Defaulted to export symbols for halmacpi.dll -

*******************************************************************************

* *

* Bugcheck Analysis *

* *

*******************************************************************************

 

Use !analyze -v to get detailed debugging information.

 

BugCheck 124, {0, 85c04024, b2000000, 60151}

 

***** 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!_WHEA_ERROR_RECORD_HEADER ***

*** ***

*************************************************************************

*************************************************************************

*** ***

*** ***

*** 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!_WHEA_ERROR_RECORD_HEADER ***

*** ***

*************************************************************************

*** ERROR: Module load completed but symbols could not be loaded for PSHED.dll

*************************************************************************

*** ***

*** ***

*** 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: pshed!_WHEA_ERROR_RECORD_HEADER ***

*** ***

*************************************************************************

*************************************************************************

*** ***

*** ***

*** 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: pshed!_WHEA_ERROR_RECORD_SECTION_DESCRIPTOR ***

*** ***

*************************************************************************

*************************************************************************

*** ***

*** ***

*** 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: pshed!_WHEA_ERROR_RECORD_HEADER ***

*** ***

*************************************************************************

*************************************************************************

*** ***

*** ***

*** 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: pshed!_WHEA_ERROR_RECORD_HEADER ***

*** ***

*************************************************************************

*************************************************************************

*** ***

*** ***

*** 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: pshed!_WHEA_ERROR_RECORD_HEADER ***

*** ***

*************************************************************************

*************************************************************************

*** ***

*** ***

*** 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 ***

*** ***

*************************************************************************

*************************************************************************

*** ***

*** ***

*** 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 ***

*** ***

*************************************************************************

Probably caused by : GenuineIntel

 

Followup: MachineOwner

---------

Dar daugiau temperatūros užfiksavau :\

Ne prie ko cia tos temperaturos.

parsisiusk BlueScreenView ir spausk view -> HTML report - All items.

Susigeneruos bluescreen analizes raportas, ji ikelk, tada bus imanoma ka nors tau padeti.

Crash List.htm Tikiuos rodys :s jei reikia galiu screenais įmesti :)

Crash List

Created by using BlueScreenView

Dump File Crash Time Bug Check String Bug Check Code Parameter 1 Parameter 2 Parameter 3 Parameter 4 Caused By Driver Caused By Address File Description Product Name Company File Version Processor Crash Address Stack Address 1 Stack Address 2 Stack Address 3 Computer Name Full Path Processors Count Major Version Minor Version Dump File Size

022213-25187-01.dmp 2/22/2013 3:44:13 AM 0x00000124 0x00000000 0x85c1b024 0xb2000000 0x00060151 halmacpi.dll halmacpi.dll+efcd Hardware Abstraction Layer DLL Microsoft® Windows® Operating System Microsoft Corporation 6.1.7601.17514 (win7sp1_rtm.101119-1850) 32-bit ntkrnlpa.exe+def20 halmacpi.dll+efcd ntkrnlpa.exe+d1aec halmacpi.dll+f27f C:\Windows\Minidump\022213-25187-01.dmp 2 15 7601 160,488

022113-22750-01.dmp 2/21/2013 10:54:18 PM 0x00000124 0x00000000 0x85ac7024 0xb2000000 0x00060151 halmacpi.dll halmacpi.dll+efcd Hardware Abstraction Layer DLL Microsoft® Windows® Operating System Microsoft Corporation 6.1.7601.17514 (win7sp1_rtm.101119-1850) 32-bit ntkrnlpa.exe+def20 halmacpi.dll+efcd ntkrnlpa.exe+d1aec halmacpi.dll+f27f C:\Windows\Minidump\022113-22750-01.dmp 2 15 7601 160,472

022113-24015-02.dmp 2/21/2013 10:45:56 PM 0x00000124 0x00000000 0x85c1a024 0xb2000018 0x06000e0f Unknown_Module_00000070 Unknown_Module_00000070+b4 32-bit C:\Windows\Minidump\022113-24015-02.dmp 2 15 7601 131,072

022113-22968-01.dmp 2/21/2013 9:39:28 PM 0x00000124 0x00000000 0x85bce024 0xb2000000 0x00060151 halmacpi.dll halmacpi.dll+efcd Hardware Abstraction Layer DLL Microsoft® Windows® Operating System Microsoft Corporation 6.1.7601.17514 (win7sp1_rtm.101119-1850) 32-bit ntkrnlpa.exe+def20 halmacpi.dll+efcd ntkrnlpa.exe+d1aec halmacpi.dll+f27f C:\Windows\Minidump\022113-22968-01.dmp 2 15 7601 160,480

022113-23156-01.dmp 2/21/2013 9:37:17 PM 0x00000124 0x00000000 0x85c0e024 0xb2000000 0x00060151 halmacpi.dll halmacpi.dll+efcd Hardware Abstraction Layer DLL Microsoft® Windows® Operating System Microsoft Corporation 6.1.7601.17514 (win7sp1_rtm.101119-1850) 32-bit ntkrnlpa.exe+def20 halmacpi.dll+efcd ntkrnlpa.exe+d1aec halmacpi.dll+f27f C:\Windows\Minidump\022113-23156-01.dmp 2 15 7601 154,528

022113-24453-01.dmp 2/21/2013 9:35:16 PM 0x00000124 0x00000000 0x85bf8024 0xb2000018 0x06000e0f halmacpi.dll halmacpi.dll+efcd Hardware Abstraction Layer DLL Microsoft® Windows® Operating System Microsoft Corporation 6.1.7601.17514 (win7sp1_rtm.101119-1850) 32-bit ntkrnlpa.exe+def20 halmacpi.dll+efcd ntkrnlpa.exe+d1aec halmacpi.dll+f27f C:\Windows\Minidump\022113-24453-01.dmp 2 15 7601 160,488

022113-24015-01.dmp 2/21/2013 7:58:03 PM 0x00000124 0x00000000 0x85c4f024 0xb2000018 0x06000e0f halmacpi.dll halmacpi.dll+efcd Hardware Abstraction Layer DLL Microsoft® Windows® Operating System Microsoft Corporation 6.1.7601.17514 (win7sp1_rtm.101119-1850) 32-bit ntkrnlpa.exe+def20 halmacpi.dll+efcd ntkrnlpa.exe+d1aec halmacpi.dll+f27f C:\Windows\Minidump\022113-24015-01.dmp 2 15 7601 160,416

022113-23718-01.dmp 2/21/2013 2:26:21 AM 0x00000124 0x00000000 0x85c04024 0xb2000000 0x00060151 halmacpi.dll halmacpi.dll+efcd Hardware Abstraction Layer DLL Microsoft® Windows® Operating System Microsoft Corporation 6.1.7601.17514 (win7sp1_rtm.101119-1850) 32-bit ntkrnlpa.exe+def20 halmacpi.dll+efcd ntkrnlpa.exe+d1aec halmacpi.dll+f27f C:\Windows\Minidump\022113-23718-01.dmp 2 15 7601 160,488

022013-26140-01.dmp 2/20/2013 11:59:13 PM 0x00000124 0x00000000 0x85c4a024 0xb2000000 0x00060151 halmacpi.dll halmacpi.dll+efcd Hardware Abstraction Layer DLL Microsoft® Windows® Operating System Microsoft Corporation 6.1.7601.17514 (win7sp1_rtm.101119-1850) 32-bit ntkrnlpa.exe+def20 halmacpi.dll+efcd ntkrnlpa.exe+d1aec halmacpi.dll+f27f C:\Windows\Minidump\022013-26140-01.dmp 2 15 7601 160,488

022013-28015-01.dmp 2/20/2013 11:25:52 PM 0x00000124 0x00000000 0x85c12024 0xb2000018 0x06000e0f halmacpi.dll halmacpi.dll+efcd Hardware Abstraction Layer DLL Microsoft® Windows® Operating System Microsoft Corporation 6.1.7601.17514 (win7sp1_rtm.101119-1850) 32-bit ntkrnlpa.exe+def20 halmacpi.dll+efcd ntkrnlpa.exe+d1aec halmacpi.dll+f27f C:\Windows\Minidump\022013-28015-01.dmp 2 15 7601 160,488

022013-30140-01.dmp 2/20/2013 11:52:41 AM 0x00000124 0x00000000 0x85818024 0xb2000000 0x00060151 halmacpi.dll halmacpi.dll+efcd Hardware Abstraction Layer DLL Microsoft® Windows® Operating System Microsoft Corporation 6.1.7601.17514 (win7sp1_rtm.101119-1850) 32-bit ntkrnlpa.exe+def20 halmacpi.dll+efcd ntkrnlpa.exe+d1aec halmacpi.dll+f27f C:\Windows\Minidump\022013-30140-01.dmp 2 15 7601 160,488

022013-32671-01.dmp 2/20/2013 6:03:21 AM 0x00000124 0x00000000 0x857ee024 0xb2000000 0x00060151 halmacpi.dll halmacpi.dll+efcd Hardware Abstraction Layer DLL Microsoft® Windows® Operating System Microsoft Corporation 6.1.7601.17514 (win7sp1_rtm.101119-1850) 32-bit ntkrnlpa.exe+def20 halmacpi.dll+efcd ntkrnlpa.exe+d1aec halmacpi.dll+f27f C:\Windows\Minidump\022013-32671-01.dmp 2 15 7601 160,432

022013-32031-01.dmp 2/20/2013 5:48:55 AM 0x00000124 0x00000000 0x857e1024 0xb2000000 0x00060151 halmacpi.dll halmacpi.dll+efcd Hardware Abstraction Layer DLL Microsoft® Windows® Operating System Microsoft Corporation 6.1.7601.17514 (win7sp1_rtm.101119-1850) 32-bit ntkrnlpa.exe+def20 halmacpi.dll+efcd ntkrnlpa.exe+d1aec halmacpi.dll+f27f C:\Windows\Minidump\022013-32031-01.dmp 2 15 7601 160,488

022013-27593-01.dmp 2/20/2013 1:53:47 AM 0x00000124 0x00000000 0x857c9024 0xb2000000 0x00060151 halmacpi.dll halmacpi.dll+efcd Hardware Abstraction Layer DLL Microsoft® Windows® Operating System Microsoft Corporation 6.1.7601.17514 (win7sp1_rtm.101119-1850) 32-bit ntkrnlpa.exe+def20 halmacpi.dll+efcd ntkrnlpa.exe+d1aec halmacpi.dll+f27f C:\Windows\Minidump\022013-27593-01.dmp 2 15 7601 160,440

021913-28171-01.dmp 2/19/2013 9:08:27 PM 0x00000124 0x00000000 0x857f7024 0xb2000000 0x00060151 halmacpi.dll halmacpi.dll+efcd Hardware Abstraction Layer DLL Microsoft® Windows® Operating System Microsoft Corporation 6.1.7601.17514 (win7sp1_rtm.101119-1850) 32-bit ntkrnlpa.exe+def20 halmacpi.dll+efcd ntkrnlpa.exe+d1aec halmacpi.dll+f27f C:\Windows\Minidump\021913-28171-01.dmp 2 15 7601 160,440

021913-27000-01.dmp 2/19/2013 12:26:42 PM 0x00000124 0x00000000 0x857ed024 0xb2000018 0x06000e0f halmacpi.dll halmacpi.dll+efcd Hardware Abstraction Layer DLL Microsoft® Windows® Operating System Microsoft Corporation 6.1.7601.17514 (win7sp1_rtm.101119-1850) 32-bit ntkrnlpa.exe+def20 halmacpi.dll+efcd ntkrnlpa.exe+d1aec halmacpi.dll+f27f C:\Windows\Minidump\021913-27000-01.dmp 2 15 7601 131,072

021913-28062-01.dmp 2/19/2013 1:08:13 AM 0x00000124 0x00000000 0x85845024 0xb2000000 0x00060151 halmacpi.dll halmacpi.dll+efcd Hardware Abstraction Layer DLL Microsoft® Windows® Operating System Microsoft Corporation 6.1.7601.17514 (win7sp1_rtm.101119-1850) 32-bit ntkrnlpa.exe+def20 halmacpi.dll+efcd ntkrnlpa.exe+d1aec halmacpi.dll+f27f C:\Windows\Minidump\021913-28062-01.dmp 2 15 7601 160,488

021913-25625-01.dmp 2/19/2013 12:14:35 AM 0x00000124 0x00000000 0x85810024 0xb2000018 0x06000e0f halmacpi.dll halmacpi.dll+efcd Hardware Abstraction Layer DLL Microsoft® Windows® Operating System Microsoft Corporation 6.1.7601.17514 (win7sp1_rtm.101119-1850) 32-bit ntkrnlpa.exe+def20 halmacpi.dll+efcd ntkrnlpa.exe+d1aec halmacpi.dll+f27f C:\Windows\Minidump\021913-25625-01.dmp 2 15 7601 160,488

Crash List.htm Tikiuos rodys :s jei reikia galiu screenais įmesti :)

Gali buti ir gelezis

Bandyk praleisti memtest86

https://www.dropbox.com/s/w123fbbf5efj1as/memtest86plus-4.20.usb.installer.zip

tau sitas turetu isirasyti i USB, kai irasys biose nustatyk "Hard Drives" skiltyje savo USB. pasikraus automatiskai memtest, palauk iki kokiu 60% (kuo ilgiau tuo geriau) jei nemes jokiu raudonu erroru, tai reiskia su ramais viskas ok (jei iskart ismes errora, tai gali toliau ir nebeleisti memetesto - reiskia ramai yra pareje ir del to ir meta tuos halmacpi.dll errorus)

Bet pries leisdamas memtest86 patikrink ar tikrai turi atsinaujines visus draiverius, ar nera jokiu geltonu sauktuku device manageryje, ir pralesik scandiska, eik i start-> parasyk cmd -> chkdsk /f.

Ir isvis kada tau prasidejo tie melyni ekranai? Gal koki gelezi nauja idejei?

Problema jau tikrai sena metai+, vieną kartą nebeįsijungė pc, nešiau taisyti, tai sakė usb lizdas priekyje pc trumpina, tai atjungė. Kai darau chkdsk išmeta lentelę, kažką tikrina ir po to ji išsijungia. Dar tikrinau device manager, radau šauktuką:

Bandyk paspausti Update Driver ant to geltono sauktuko, gal windows update ras tavo driveri, bet cia nemanau, kad tame yra problema, nes tie 0x124 bugcheckai yra daugiau susije su gelezim.

Siaip bandyk atsisiusti motinines driverius ir isirasyk kad butum tikras, jei nezinai koks modelis isijunk cpu-z ir pasiziurek (motherboard skiltis):

https://www.dropbox.com/s/3265hy0p1jfqirh/cpu-z_1.63-32bits-en.zip

Dar pabandyk praleisti prime95, pasirink small-FFT ir duok jam dirbti, jei mes melyna ekrana, tai reiskia kazkas negerai su procu.

https://www.dropbox.com/s/yaler0vs4wotrmc/p95v279.win32.zip

ar praleidai memtesta?

O ta chkdsk komanda greiciausiai prase taves perkrauti kompa ir paskui ji turejo pasileisti pries pasikraunant windowsams, nieko nespausk ir neisjunk jos, tegu prakaitina tavo harda

Paleidau memtest86 13min+ testino, bet jokiu erroru. Po to patikrinau motinines pavadinima (P5B-VM SE), bet kiek ieškojau, tiek neradau jai win 7 drivers, tik xp ir panašiai :| Tikrinau ir su prime95, nieko :(

Paleidau memtest86 13min+ testino, bet jokiu erroru. Po to patikrinau motinines pavadinima (P5B-VM SE), bet kiek ieškojau, tiek neradau jai win 7 drivers, tik xp ir panašiai :| Tikrinau ir su prime95, nieko :(

Siusk Vista driverius jei nerandi butent 7-iems - tikrai turetu tikti.

Siaip labai sunku pasakyti kas pas taves per problema, nes ta bluescreena inicijuoja grynai windowsiniai failai. Cia, kaip sakiau, piktas dalykas ir reiketu nepatingeti ir duoti streso savo geleziui, jei erroru neras, tai bent jau zinosi, kad su dalim viskas tvarkoj :)

Prime95 turi leisti ne 10min - leisk apie valanda ar kiek jis ten prasys, nesi bandes turbinti proco ar kazka panasaus?

Dar gali BIOSE patikrinti maitinblokio voltaza, gali buti, kad ir maitinimas hujovas yra

Siusk Vista driverius jei nerandi butent 7-iems - tikrai turetu tikti.

 

Siaip labai sunku pasakyti kas pas taves per problema, nes ta bluescreena inicijuoja grynai windowsiniai failai. Cia, kaip sakiau, piktas dalykas ir reiketu nepatingeti ir duoti streso savo geleziui, jei erroru neras, tai bent jau zinosi, kad su dalim viskas tvarkoj :)

 

Prime95 turi leisti ne 10min - leisk apie valanda ar kiek jis ten prasys, nesi bandes turbinti proco ar kazka panasaus?

 

Dar gali BIOSE patikrinti maitinblokio voltaza, gali buti, kad ir maitinimas hujovas yra

Praleidau pusantros valandos, viskas ok. O dėl voltažo, koks jis turi būti normalus? ;D

Praleidau pusantros valandos, viskas ok. O dėl voltažo, koks jis turi būti normalus? ;D

Eik i BIOSa ir paziurek Hardware Monitor skilty, ten turetu buti surasyta 12V 5V ir 3V ir salia keiciasi skaiciukai, tai tie kur keiciasi tur buti kuo arciau atitinkamai 12V 5V 3V, jei yra didelis skirtumas, tai ner gerai :)

Problema jau sena. Užvakar perrašė windows 7, patikrino HDD. Vakar išvaliau pc nuo dulkių. Bet visvien keičiant žaidimų (pvz cs 1,6) grafikas, ar paprastai juos žaidžiant, net žiūrint filmą per VLC gaunu blue screen. Gal kas žinot kaip išspręsti šitą error?

 

0x00000124 (0x00000000, 0x857F7024, 0xB2000000, 0x00060151)

0x00000124 (0x00000000, 0x857C9024, 0xB2000000, 0x00060151)

0x00000124 (0x00000000, 0x857E1024, 0xB2000000, 0x00060151)

0x00000124 (0x00000000, 0x857EE024, 0xB2000000, 0x00060151)

bijau prikalbėt nesąmonių, tad parašysiu kaip rekomendacinio pobūdžio. turėjau panašią problemą, kai žiūrint ar žaidžiant triokšt ir išmeta blue screen. finale paaiškėjo, kad buvo kalta viena iš dviejų RAM modulių ( pas mane 2 DDR3 po 4 GB ). kadangi pas mane garantinis, plokštelę sutvarkė ir kolkas jokių problemų, pfu pfu pfu

Eik i BIOSa ir paziurek Hardware Monitor skilty, ten turetu buti surasyta 12V 5V ir 3V ir salia keiciasi skaiciukai, tai tie kur keiciasi tur buti kuo arciau atitinkamai 12V 5V 3V, jei yra didelis skirtumas, tai ner gerai :)

Pas mane tie skaičiukai nesikeičia, skiriasi iki 0,2. :/

Laguna, testinau jau ramus :|

Pas mane tie skaičiukai nesikeičia, skiriasi iki 0,2. :/

 

Laguna, testinau jau ramus :|

Nezinau nei ka cia daugiau ir patarti:)

Mmm, gal kazko BlueScreenView neuzfiksavo, atsisiusk:

https://www.dropbox.com/s/x3kbp7cgm8sm1vf/T-303WCP.rar

Spausk Analyze, ir vel prisek sugeneruota raporta. Nepamenu tik kaip issaugoti raporta, nes pas manes blue screen nemeto, tai net neturiu dump failu kompe :)

Ieskok kazka panasaus i save report, save log file ir pan.

Be to patikrink ar jokie metaliukai nesiliecia pas tave prie motinines plokstes, sakei USB trumpino, tai gal koks varztukas prie kontaktu liecias ar panasiai

Nezinau nei ka cia daugiau ir patarti:)

Mmm, gal kazko BlueScreenView neuzfiksavo, atsisiusk:

https://www.dropbox.com/s/x3kbp7cgm8sm1vf/T-303WCP.rar

 

Spausk Analyze, ir vel prisek sugeneruota raporta. Nepamenu tik kaip issaugoti raporta, nes pas manes blue screen nemeto, tai net neturiu dump failu kompe :)

 

Ieskok kazka panasaus i save report, save log file ir pan.

 

Be to patikrink ar jokie metaliukai nesiliecia pas tave prie motinines plokstes, sakei USB trumpino, tai gal koks varztukas prie kontaktu liecias ar panasiai

Dabar prisiminiau, kad nesenai valant pc nuėmiau aušintuvą, kad pilnai išvalyti, tada pamačiau, kad jis kažkoks prisviles, tai nuvaliau ir atgal uždėjau. Gali būti, kad ten buvo kokia izoliuojanti medžiaga? (Geltona, kur pažymėjau, ant tos vietos aušintuvas)

Dabar prisiminiau, kad nesenai valant pc nuėmiau aušintuvą, kad pilnai išvalyti, tada pamačiau, kad jis kažkoks prisviles, tai nuvaliau ir atgal uždėjau. Gali būti, kad ten buvo kokia izoliuojanti medžiaga? (Geltona, kur pažymėjau, ant tos vietos aušintuvas)

Greiciausiai termoizoliacine pasta nuvalei (pilka tokia buvo?) :) Jei teip - tai nereikia jos valyti, o kaip tik turi nusipirkti uz kelis lt is kompu daliu parduotuves ir labai nedaug uztepti tarp radiatoriaus ir proco dangcio.

Nebuvai pacio procesoriaus islupes? Siaip temperaturos pas tave neblogos, tai karsti gali atmesti, bet nors ir kaistu procas blue screenu nemestu