» Poradna » Notebooky

Modrá obrazovka

Odpovědět  |  Zobrazit bez stromu  |  Upozornit redakci  |  nových odpovědí: 2/2
 |   |  Microsoft Windows 7 Chrome 22.0.1229.79  |  [83.208.142.---]

Zobrazuje se modrá obrazovka, bohuzel nestihnu topřečíst - ale zde přikládám minidumpy http://leteckaposta.cz/740169753, co s tím ???

Odpovědi na otázku

avatar
 | Microsoft Windows 7 Firefox 20.0

ake je cislo chybovej hlasky? pri bluescreene?A co s minidumpom?

Souhlasím  |  Nesouhlasím  |  Odpovědět
 |   |  Microsoft Windows XP IE 7.0  |  [194.228.13.---]

Crash Dump Analysis - programem WhoCrashed:--------------------------------------------------------------------------------On Sun 7.4.2013 12:35:14 GMT your computer crashedcrash dump file: C:\WINDOWS\Minidump\040713-66362-01.dmpThis was probably caused by the following module: dxgmms1.sys (dxgmms1+0x1986) Bugcheck code: 0x3B (0xC0000005, 0xFFFFF88004001986, 0xFFFFF880072A3BA0, 0x0)Error: SYSTEM_SERVICE_EXCEPTIONBug 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. A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: dxgmms1.sys . Google query: dxgmms1.sys SYSTEM_SERVICE_EXCEPTIONOn Sun 7.4.2013 12:21:37 GMT your computer crashedcrash dump file: C:\WINDOWS\Minidump\040713-19172-01.dmpThis was probably caused by the following module: ntoskrnl.exe (nt+0x75C40) Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80002CD2B45, 0xFFFFF880079EF180, 0x0)Error: SYSTEM_SERVICE_EXCEPTIONfile path: C:\WINDOWS\system32\ntoskrnl.exeproduct: Operační systém Microsoft® Windows®company: Microsoft Corporationdescription: NT Kernel & SystemBug 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 Sun 7.4.2013 12:12:18 GMT your computer crashedcrash dump file: C:\WINDOWS\Minidump\040713-19687-01.dmpThis was probably caused by the following module: ntoskrnl.exe (nt+0x75C40) Bugcheck code: 0x1 (0x779D138A, 0x0, 0xFFFF, 0xFFFFF88008059CA0)Error: APC_INDEX_MISMATCHfile path: C:\WINDOWS\system32\ntoskrnl.exeproduct: Operační systém Microsoft® Windows®company: Microsoft Corporationdescription: NT Kernel & SystemBug check description: This indicates that there has been a mismatch in the APC state index.The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time. On Fri 5.4.2013 6:00:29 GMT your computer crashedcrash dump file: C:\WINDOWS\Minidump\040513-24960-01.dmpThis was probably caused by the following module: ntoskrnl.exe (nt+0x35CE41) Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF80002FC4E41, 0xFFFFF88002FD9A18, 0xFFFFF88002FD9270)Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_Mfile path: C:\WINDOWS\system32\ntoskrnl.exeproduct: Operační systém Microsoft® Windows®company: Microsoft Corporationdescription: NT Kernel & SystemBug check description: This indicates that a system thread generated an exception which the error handler did not catch.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 Thu 4.4.2013 7:39:33 GMT your computer crashedcrash dump file: C:\WINDOWS\Minidump\040413-31137-01.dmpThis was probably caused by the following module: ntoskrnl.exe (nt+0x75C40) Bugcheck code: 0x50 (0xFFFFF6F850023588, 0x0, 0xFFFFF80002AA9501, 0x5)Error: PAGE_FAULT_IN_NONPAGED_AREAfile path: C:\WINDOWS\system32\ntoskrnl.exeproduct: Operační systém Microsoft® Windows®company: Microsoft Corporationdescription: NT Kernel & SystemBug check description: This indicates that invalid system memory has been referenced.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 Thu 4.4.2013 7:35:50 GMT your computer crashedcrash dump file: C:\WINDOWS\Minidump\040413-30732-01.dmpThis was probably caused by the following module: ntoskrnl.exe (nt+0x75C40) Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80002C01A9B, 0xFFFFF880028F2EA0, 0x0)Error: SYSTEM_SERVICE_EXCEPTIONfile path: C:\WINDOWS\system32\ntoskrnl.exeproduct: Operační systém Microsoft® Windows®company: Microsoft Corporationdescription: NT Kernel & SystemBug 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 Thu 4.4.2013 7:32:13 GMT your computer crashedcrash dump file: C:\WINDOWS\Minidump\040413-30045-01.dmpThis was probably caused by the following module: ntoskrnl.exe (nt+0x75C40) Bugcheck code: 0x19 (0x3, 0xFFFFFA8003F615E0, 0xFFFFFA8003F615E0, 0xF7FFFA8003F615E0)Error: BAD_POOL_HEADERfile path: C:\WINDOWS\system32\ntoskrnl.exeproduct: Operační systém Microsoft® Windows®company: Microsoft Corporationdescription: NT Kernel & SystemBug check description: This indicates that a pool header is corrupt.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. On Wed 3.4.2013 11:12:17 GMT your computer crashedcrash dump file: C:\WINDOWS\Minidump\040313-20030-01.dmpThis was probably caused by the following module: ntoskrnl.exe (nt+0x6F840) Bugcheck code: 0xA (0x0, 0x2, 0x1, 0xFFFFF80002A4B829)Error: IRQL_NOT_LESS_OR_EQUALfile path: C:\WINDOWS\system32\ntoskrnl.exeproduct: Operační systém Microsoft® Windows®company: Microsoft Corporationdescription: NT Kernel & SystemBug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.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 3.4.2013 7:39:50 GMT your computer crashedcrash dump file: C:\WINDOWS\Minidump\040313-23930-01.dmpThis was probably caused by the following module: ntoskrnl.exe (nt+0x6F840) Bugcheck code: 0x19 (0x3, 0xFFFFF8A008B0DEA0, 0xFFFFF8A008B0DEA0, 0xF7FFF8A008B0DEA0)Error: BAD_POOL_HEADERfile path: C:\WINDOWS\system32\ntoskrnl.exeproduct: Operační systém Microsoft® Windows®company: Microsoft Corporationdescription: NT Kernel & SystemBug check description: This indicates that a pool header is corrupt.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--------------------------------------------------------------------------------9 crash dumps have been found and analyzed. A third party driver has been identified to be causing system crashes on your computer. It is strongly suggested that you check for updates for these drivers on their company websites. Click on the links below to search with Google for updates for these drivers: dxgmms1.sys If no updates for these drivers are available, try searching with Google on the names of these drivers in combination the errors that have been reported for these drivers and include the brand and model name of your computer as well in the query. This often yields interesting results from discussions from users who have been experiencing similar problems.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.

Souhlasím  |  Nesouhlasím  |  Odpovědět



Určitě si přečtěte