zamrzani PC u her , obcas BSOD
Napsal: 16 led 2013 18:09
Zdravim ,
pred dvema dny mne odesel zdroj a hdd , po vymnene zdroje a HDD dochazi k zamrzani her po cca 10 - 15 minutach , obcas k svevolnemu padu hry do vidli a nejhure k modre smrti
zde je vysledek WC :
computer name: CYKLO-DOMA
windows version: Windows 7 Service Pack 1, 6.1, build: 7601
windows dir: C:\Windows
CPU: GenuineIntel Intel(R) Core(TM)2 Duo CPU E8500 @ 3.16GHz Intel586, level: 6
2 logical processors, active mask: 3
RAM: 4294103040 total
VM: 2147352576, free: 1967542272
--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Wed 16.1.2013 16:12:58 GMT your computer crashed
crash dump file: C:\Windows\Minidump\011613-21808-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x705C0)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80002BF090D, 0xFFFFF88004A87D30, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Wed 16.1.2013 16:12:58 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: win32k.sys (win32k!EngCreatePalette+0x7BFC)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80002BF090D, 0xFFFFF88004A87D30, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\win32k.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Multi-User Win32 Driver
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.
On Wed 16.1.2013 15:47:22 GMT your computer crashed
crash dump file: C:\Windows\Minidump\011613-18018-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x705C0)
Bugcheck code: 0x4E (0x99, 0x6426D, 0x1, 0x11876D)
Error: PFN_LIST_CORRUPT
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that the page frame number (PFN) list is corrupted.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------
3 crash dumps have been found and analyzed. No offending third party drivers have been found. Consider configuring your system to produce a full memory dump for better analysis.
Read the topic general suggestions for troubleshooting system crashes for more information.
Note that it's not always possible to state with certainty whether a reported driver is actually responsible for crashing your system or that the root cause is in another module. Nonetheless it's suggested you look for updates for the products that these drivers belong to and regularly visit Windows update or enable automatic updates for Windows. In case a piece of malfunctioning hardware is causing trouble, a search with Google on the bug check errors together with the model name and brand of your computer may help you investigate this further.
prosim o radu co stim , skousel sem zatezove testy grafiky kdy se teplota procesoru grafarny dostala max na 81 stupnu a spotreba grafiky vzrostala na 125A,fanspeed vetraku na 76%
teplota procesoru compu 75 stupnu,teplota v cashe 27 stupnu , fansped procaku 1500, fanspeed vetraku v cash 1246 spodni , 1240 stredovy , 1120 horni
pred dvema dny mne odesel zdroj a hdd , po vymnene zdroje a HDD dochazi k zamrzani her po cca 10 - 15 minutach , obcas k svevolnemu padu hry do vidli a nejhure k modre smrti

zde je vysledek WC :
computer name: CYKLO-DOMA
windows version: Windows 7 Service Pack 1, 6.1, build: 7601
windows dir: C:\Windows
CPU: GenuineIntel Intel(R) Core(TM)2 Duo CPU E8500 @ 3.16GHz Intel586, level: 6
2 logical processors, active mask: 3
RAM: 4294103040 total
VM: 2147352576, free: 1967542272
--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Wed 16.1.2013 16:12:58 GMT your computer crashed
crash dump file: C:\Windows\Minidump\011613-21808-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x705C0)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80002BF090D, 0xFFFFF88004A87D30, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Wed 16.1.2013 16:12:58 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: win32k.sys (win32k!EngCreatePalette+0x7BFC)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80002BF090D, 0xFFFFF88004A87D30, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\win32k.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Multi-User Win32 Driver
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.
On Wed 16.1.2013 15:47:22 GMT your computer crashed
crash dump file: C:\Windows\Minidump\011613-18018-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x705C0)
Bugcheck code: 0x4E (0x99, 0x6426D, 0x1, 0x11876D)
Error: PFN_LIST_CORRUPT
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that the page frame number (PFN) list is corrupted.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------
3 crash dumps have been found and analyzed. No offending third party drivers have been found. Consider configuring your system to produce a full memory dump for better analysis.
Read the topic general suggestions for troubleshooting system crashes for more information.
Note that it's not always possible to state with certainty whether a reported driver is actually responsible for crashing your system or that the root cause is in another module. Nonetheless it's suggested you look for updates for the products that these drivers belong to and regularly visit Windows update or enable automatic updates for Windows. In case a piece of malfunctioning hardware is causing trouble, a search with Google on the bug check errors together with the model name and brand of your computer may help you investigate this further.
prosim o radu co stim , skousel sem zatezove testy grafiky kdy se teplota procesoru grafarny dostala max na 81 stupnu a spotreba grafiky vzrostala na 125A,fanspeed vetraku na 76%
teplota procesoru compu 75 stupnu,teplota v cashe 27 stupnu , fansped procaku 1500, fanspeed vetraku v cash 1246 spodni , 1240 stredovy , 1120 horni