Forum Mjukvara Microsoft Windows Tråd

datorn dog

1
Skriv svar
Permalänk
Medlem
●

datorn dog

Hejsan! När jag spelade bf 3 så dog datan. När den startades om så kom det upp en ruta och de stog det så här när jag öppnade upp rutan.

Problemsignatur:
Problemhändelsens namn: BlueScreen
OS-version: 6.1.7600.2.0.0.256.1
Språkvariant-ID: 1053

Ytterligare information om problemet:
BCCode: 116
BCP1: FFFFFA800FAEC4E0
BCP2: FFFFF88010B19AE4
BCP3: FFFFFFFFC000009A
BCP4: 0000000000000004
OS Version: 6_1_7600
Service Pack: 0_0
Product: 256_1

Filer som hjälper till att beskriva problemet:
C:\Windows\Minidump\102911-15709-01.dmp
C:\Users\Hasan\AppData\Local\Temp\WER-20030-0.sysdata.xml

Läs vår sekretesspolicy online:
http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x041d

Om sekretesspolicyn online inte är tillgänglig kan du läsa vår sekretesspolicy offline:
C:\Windows\system32\sv-SE\erofflps.txt

vad är felet?

Visa signatur

Cooler Master Haf X // Intel I7 2600k // 2x Gtx 560 ti oc SLI // 16gb ddr3 Corsair Vengeance // Ocz 120gb ssd // Ocz 1250w psu // Cpu kylare Corsair H100 // Sabertooth P67

Redigera
Citera flera Citera
Permalänk
Medlem ★
●

Har du de senaste drivrutinerna till dina grafikkort? Just 560 Ti verkar vara extremt kinkigt med BF3 och jag ska hjälpa en polare med detta senare ikväll. Vissa forum rekommenderar att man ska uppdatera grafikkortets BIOS men det känns lite overkill.

Visa signatur

11600K@5.1 GHz + 32GB Corsair Vengeance RGB PRO 3200@3400 MHz + MSI RTX 2080 Super Gaming X Trio +
WDC Blue SN550 1TB + Black OEM SN730 500GB + Kingston A1000 480GB + A2000 500GB + NV2 1TB + 2TB R10 + RGB most of THE THINGS! + Corsair 4000D Airflow + 2*ZyXEL NSA326 2*3TB @ R1 + Netgear RN2100 4*3TB @ R10 + RN204 4*4TB @ R5 + Synology DS216j 2*4TB @ SHR R1 + DS418 4*8TB @ SHR R6 men just nu handikappad till en jävla Dell Latitude 7420 :'(

Redigera
Citera flera Citera
Permalänk
Medlem ★
●

Våre bra att veta vad för delar du har. Speciellt nätagget märke modell ålder

Visa signatur

Fractal r4 5volt. Amd 965 3.4 ghz Noctua DH 14 Asus M4N68T LE
Ssd diskar Samsung 850pro/intel 730 /320 Crucial m4 /8 tb mx500
Nätagg Corsair vx 450 = Seasonic m12d

Redigera
Citera flera Citera
Permalänk
Medlem
●

ladda ner detta program: http://www.resplendence.com/download/whocrashedSetup.exe

sedan installerar du och startar upp, klickar på -> Analyze

sedan postar du vad den sa.

Visa signatur

[Moderkort: ASUS Rog Strix Z390-F] - [CPU: Intel i7 9700k] - [Minnen: Corsair 16GB CL15 Vengeance] - [GPU: Palit Geforce RTX 2080 OC] - [SSD: Samsung EVO 120GB] - [PSU: Corsair AX1200] - [Skärm: ASUS 27" ROG Swift PG278QR] - [Skärm: Samsung SA700]

Redigera
Citera flera Citera
Permalänk
Medlem
●

Cooler Master Haf X // Intel I7 2600k // 2x Gtx 560 ti oc SLI // 16gb ddr3 Corsair Vengeance // Ocz 120gb ssd // Ocz 1200w psu // Cpu kylare Corsair H100 // Sabertooth P67

Skrivet av pompa_kumla:

Våre bra att veta vad för delar du har. Speciellt nätagget märke modell ålder

Gå till inlägget
Visa signatur

Cooler Master Haf X // Intel I7 2600k // 2x Gtx 560 ti oc SLI // 16gb ddr3 Corsair Vengeance // Ocz 120gb ssd // Ocz 1250w psu // Cpu kylare Corsair H100 // Sabertooth P67

Redigera
Citera flera Citera
Permalänk
Medlem
●

--------------------------------------------------------------------------------
Welcome to WhoCrashed HOME EDITION v 3.02
--------------------------------------------------------------------------------

This program checks for drivers which have been crashing your computer. If your computer has displayed a blue screen of death, suddenly rebooted or shut down then this program will help you find the root cause and possibly a solution.

Whenever a computer suddenly reboots without displaying any notice or blue screen of death, the first thing that is often thought about is a hardware failure. In reality, on Windows most crashes are caused by malfunctioning device drivers and kernel modules. In case of a kernel error, many computers do not show a blue screen unless they are configured for this. Instead these systems suddenly reboot without any notice.

This program will analyze your crash dumps with the single click of a button. It will tell you what drivers are likely to be responsible for crashing your computer. If will report a conclusion which offers suggestions on how to proceed in any situation while the analysis report will display internet links which will help you further troubleshoot any detected problems.

To obtain technical support visit www.resplendence.com/support

Click here to check if you have the latest version or if an update is available.

Just click the Analyze button for a comprehensible report ...

--------------------------------------------------------------------------------
Home Edition Notice
--------------------------------------------------------------------------------

This version of WhoCrashed is free for use at home only. If you would like to use this software at work or in a commercial environment you should get the professional edition of WhoCrashed which also allows analysis of crashdumps on remote drives and computers on the network and offers a range of additional features.

Click here for more information on the professional edition.
Click here to buy the the professional edition of WhoCrashed.

--------------------------------------------------------------------------------
System Information (local)
--------------------------------------------------------------------------------

computer name: HASAN-PC
windows version: Windows 7 , 6.1, build: 7600
windows dir: C:\Windows
CPU: GenuineIntel Intel(R) Core(TM) i7-2600K CPU @ 3.40GHz Intel586, level: 6
8 logical processors, active mask: 255
RAM: 17159041024 total
VM: 2147352576, free: 1949163520

--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

On Sat 10/29/2011 1:31:39 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\102911-15709-01.dmp
This was probably caused by the following module: nvlddmkm.sys (nvlddmkm+0xC3BAE4)
Bugcheck code: 0x116 (0xFFFFFA800FAEC4E0, 0xFFFFF88010B19AE4, 0xFFFFFFFFC000009A, 0x4)
Error: VIDEO_TDR_ERROR
file path: C:\Windows\system32\drivers\nvlddmkm.sys
product: NVIDIA Windows Kernel Mode Driver, Version 285.62
company: NVIDIA Corporation
description: NVIDIA Windows Kernel Mode Driver, Version 285.62
Bug check description: This indicates that an attempt to reset the display driver and recover from a timeout failed.
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: nvlddmkm.sys (NVIDIA Windows Kernel Mode Driver, Version 285.62 , NVIDIA Corporation).
Google query: nvlddmkm.sys NVIDIA Corporation VIDEO_TDR_ERROR

On Fri 10/28/2011 4:57:01 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\102811-15568-01.dmp
This was probably caused by the following module: nvlddmkm.sys (nvlddmkm+0xC3BAE4)
Bugcheck code: 0x116 (0xFFFFFA80115304E0, 0xFFFFF88008C3BAE4, 0xFFFFFFFFC000009A, 0x4)
Error: VIDEO_TDR_ERROR
file path: C:\Windows\system32\drivers\nvlddmkm.sys
product: NVIDIA Windows Kernel Mode Driver, Version 285.62
company: NVIDIA Corporation
description: NVIDIA Windows Kernel Mode Driver, Version 285.62
Bug check description: This indicates that an attempt to reset the display driver and recover from a timeout failed.
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: nvlddmkm.sys (NVIDIA Windows Kernel Mode Driver, Version 285.62 , NVIDIA Corporation).
Google query: nvlddmkm.sys NVIDIA Corporation VIDEO_TDR_ERROR

--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------

2 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:

nvlddmkm.sys (NVIDIA Windows Kernel Mode Driver, Version 285.62 , NVIDIA Corporation)

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.

Skrivet av Copsi:

ladda ner detta program: http://www.resplendence.com/download/whocrashedSetup.exe

sedan installerar du och startar upp, klickar på -> Analyze

sedan postar du vad den sa.

Gå till inlägget
Visa signatur

Cooler Master Haf X // Intel I7 2600k // 2x Gtx 560 ti oc SLI // 16gb ddr3 Corsair Vengeance // Ocz 120gb ssd // Ocz 1250w psu // Cpu kylare Corsair H100 // Sabertooth P67

Redigera
Citera flera Citera
Permalänk
Medlem
●

Aha okej men kan du höra av dig senare hur ni fixade felet uppskattas:)

Skrivet av ZaInT:

Har du de senaste drivrutinerna till dina grafikkort? Just 560 Ti verkar vara extremt kinkigt med BF3 och jag ska hjälpa en polare med detta senare ikväll. Vissa forum rekommenderar att man ska uppdatera grafikkortets BIOS men det känns lite overkill.

Gå till inlägget
Visa signatur

Cooler Master Haf X // Intel I7 2600k // 2x Gtx 560 ti oc SLI // 16gb ddr3 Corsair Vengeance // Ocz 120gb ssd // Ocz 1250w psu // Cpu kylare Corsair H100 // Sabertooth P67

Redigera
Citera flera Citera
Permalänk
Medlem
●

It is suggested you look for an update for the following driver: nvlddmkm.sys (NVIDIA Windows Kernel Mode Driver, Version 285.62 , NVIDIA Corporation).

Uppdatera dina drivar för grafikkortet

Visa signatur

[Moderkort: ASUS Rog Strix Z390-F] - [CPU: Intel i7 9700k] - [Minnen: Corsair 16GB CL15 Vengeance] - [GPU: Palit Geforce RTX 2080 OC] - [SSD: Samsung EVO 120GB] - [PSU: Corsair AX1200] - [Skärm: ASUS 27" ROG Swift PG278QR] - [Skärm: Samsung SA700]

Redigera
Citera flera Citera
Permalänk
Medlem
●

Det ska vara dom nyaste jag har jag uppdaterade igår till dom.

Skrivet av Copsi:

It is suggested you look for an update for the following driver: nvlddmkm.sys (NVIDIA Windows Kernel Mode Driver, Version 285.62 , NVIDIA Corporation).

Uppdatera dina drivar för grafikkortet

Gå till inlägget
Visa signatur

Cooler Master Haf X // Intel I7 2600k // 2x Gtx 560 ti oc SLI // 16gb ddr3 Corsair Vengeance // Ocz 120gb ssd // Ocz 1250w psu // Cpu kylare Corsair H100 // Sabertooth P67

Redigera
Citera flera Citera
Permalänk
Medlem ★
●
Skrivet av hasoo:

Aha okej men kan du höra av dig senare hur ni fixade felet uppskattas:)

Gå till inlägget

Vi gjorde inget åt det men efter googlande har jag kommit fram till att det finns 3 sätt.

1. Vänta på patch (enklast)
2. Underklocka grafikkortet (inte så svårt men om du är "nybörjare på datorer" är det kanske inte något du ska ge dig på)
3. Flasha grafikkortets BIOS (riskfyllt senast jag gjorde det, svårt och det hjälper inte för alla).

Jag rekommenderar de första två alternativen.

Visa signatur

11600K@5.1 GHz + 32GB Corsair Vengeance RGB PRO 3200@3400 MHz + MSI RTX 2080 Super Gaming X Trio +
WDC Blue SN550 1TB + Black OEM SN730 500GB + Kingston A1000 480GB + A2000 500GB + NV2 1TB + 2TB R10 + RGB most of THE THINGS! + Corsair 4000D Airflow + 2*ZyXEL NSA326 2*3TB @ R1 + Netgear RN2100 4*3TB @ R10 + RN204 4*4TB @ R5 + Synology DS216j 2*4TB @ SHR R1 + DS418 4*8TB @ SHR R6 men just nu handikappad till en jävla Dell Latitude 7420 :'(

Redigera
Citera flera Citera
Permalänk
Medlem
●

Fixade biosen o de löste sig. Men brukar få ett fel medeland enu att de e fel med conetction:S eller hur de nu stavas hoppas du fattar vad jag menar hehe. den stänger bara av spelet så dyker rutan upp!

Skrivet av ZaInT:

Vi gjorde inget åt det men efter googlande har jag kommit fram till att det finns 3 sätt.

1. Vänta på patch (enklast)
2. Underklocka grafikkortet (inte så svårt men om du är "nybörjare på datorer" är det kanske inte något du ska ge dig på)
3. Flasha grafikkortets BIOS (riskfyllt senast jag gjorde det, svårt och det hjälper inte för alla).

Jag rekommenderar de första två alternativen.

Gå till inlägget
Visa signatur

Cooler Master Haf X // Intel I7 2600k // 2x Gtx 560 ti oc SLI // 16gb ddr3 Corsair Vengeance // Ocz 120gb ssd // Ocz 1250w psu // Cpu kylare Corsair H100 // Sabertooth P67

Redigera
Citera flera Citera
Permalänk
Medlem
●

Har också problem med mitt 560Ti så tänkte att jag kunde posta loggen från min dator med i hopp om lite hjälp.

System Information (local)
--------------------------------------------------------------------------------

computer name: AHLQVIST-PC
windows version: Windows 7 Service Pack 1, 6.1, build: 7601
windows dir: C:\Windows
CPU: AuthenticAMD AMD Phenom(tm) II X4 955 Processor AMD586, level: 16
4 logical processors, active mask: 15
RAM: 8589070336 total
VM: 2147352576, free: 1944842240

--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

On Wed 2011-11-02 19:41:21 GMT your computer crashed
crash dump file: C:\Windows\Minidump\110211-19359-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)
Bugcheck code: 0xD1 (0xFFFFFA0003084F32, 0x2, 0x8, 0xFFFFFA0003084F32)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
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 a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
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 which cannot be identified at this time.

On Wed 2011-11-02 18:49:21 GMT your computer crashed
crash dump file: C:\Windows\Minidump\110211-22468-01.dmp
This was probably caused by the following module: ndis.sys (ndis+0x8FC5A)
Bugcheck code: 0xD1 (0xFFFFE2000EDD7024, 0x2, 0x1, 0xFFFFF88001538C5A)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\ndis.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NDIS 6.20 driver
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
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 which cannot be identified at this time.

On Mon 2011-10-31 21:42:01 GMT your computer crashed
crash dump file: C:\Windows\Minidump\110111-21500-01.dmp
This was probably caused by the following module: dxgmms1.sys (dxgmms1+0x355C9)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF8800FDC55C9, 0xFFFFF88008457B20, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\drivers\dxgmms1.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: DirectX Graphics MMS
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 which cannot be identified at this time.

On Mon 2011-10-31 16:31:42 GMT your computer crashed
crash dump file: C:\Windows\Minidump\103111-20531-01.dmp
This was probably caused by the following module: portcls.sys (portcls+0x4304)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF880073C3304, 0xFFFFF88009C5EC70, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\drivers\portcls.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Port Class (Class Driver for Port/Miniport Devices)
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 which cannot be identified at this time.

On Mon 2011-10-31 12:39:20 GMT your computer crashed
crash dump file: C:\Windows\Minidump\103111-22953-01.dmp
This was probably caused by the following module: win32k.sys (win32k+0x16844)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF960000E6844, 0xFFFFF880057F9B50, 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 which cannot be identified at this time.

On Mon 2011-10-17 19:47:22 GMT your computer crashed
crash dump file: C:\Windows\Minidump\101711-21859-01.dmp
This was probably caused by the following module: hal.dll (hal+0x12A3B)
Bugcheck code: 0x124 (0x0, 0xFFFFFA8006FCC028, 0xB669C000, 0x135)
Error: WHEA_UNCORRECTABLE_ERROR
file path: C:\Windows\system32\hal.dll
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Hardware Abstraction Layer DLL
Bug check description: This bug check indicates that a fatal hardware error has occurred. This bug check uses the error data that is provided by the Windows Hardware Error Architecture (WHEA).
This is likely to be caused by a hardware problem problem. This problem might be caused by a thermal issue.
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 which cannot be identified at this time.

On Wed 2011-10-12 10:32:30 GMT your computer crashed
crash dump file: C:\Windows\Minidump\101211-21500-01.dmp
This was probably caused by the following module: hal.dll (hal+0x12A3B)
Bugcheck code: 0x124 (0x0, 0xFFFFFA8006F1B028, 0xF26AC000, 0x175)
Error: WHEA_UNCORRECTABLE_ERROR
file path: C:\Windows\system32\hal.dll
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Hardware Abstraction Layer DLL
Bug check description: This bug check indicates that a fatal hardware error has occurred. This bug check uses the error data that is provided by the Windows Hardware Error Architecture (WHEA).
This is likely to be caused by a hardware problem problem. This problem might be caused by a thermal issue.
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 which cannot be identified at this time.

The following dump files were found but could not be read. These files may be corrupt:
C:\Windows\Minidump\110211-27390-01.dmp

Redigera
Citera flera Citera
Permalänk
Medlem
●

Har du fått ngt vettigt svar av folk på andra trådar?

Skrivet av Ahlqvist162:

Har också problem med mitt 560Ti så tänkte att jag kunde posta loggen från min dator med i hopp om lite hjälp.

System Information (local)
--------------------------------------------------------------------------------

computer name: AHLQVIST-PC
windows version: Windows 7 Service Pack 1, 6.1, build: 7601
windows dir: C:\Windows
CPU: AuthenticAMD AMD Phenom(tm) II X4 955 Processor AMD586, level: 16
4 logical processors, active mask: 15
RAM: 8589070336 total
VM: 2147352576, free: 1944842240

--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

On Wed 2011-11-02 19:41:21 GMT your computer crashed
crash dump file: C:\Windows\Minidump\110211-19359-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)
Bugcheck code: 0xD1 (0xFFFFFA0003084F32, 0x2, 0x8, 0xFFFFFA0003084F32)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
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 a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
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 which cannot be identified at this time.

On Wed 2011-11-02 18:49:21 GMT your computer crashed
crash dump file: C:\Windows\Minidump\110211-22468-01.dmp
This was probably caused by the following module: ndis.sys (ndis+0x8FC5A)
Bugcheck code: 0xD1 (0xFFFFE2000EDD7024, 0x2, 0x1, 0xFFFFF88001538C5A)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\ndis.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NDIS 6.20 driver
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
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 which cannot be identified at this time.

On Mon 2011-10-31 21:42:01 GMT your computer crashed
crash dump file: C:\Windows\Minidump\110111-21500-01.dmp
This was probably caused by the following module: dxgmms1.sys (dxgmms1+0x355C9)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF8800FDC55C9, 0xFFFFF88008457B20, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\drivers\dxgmms1.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: DirectX Graphics MMS
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 which cannot be identified at this time.

On Mon 2011-10-31 16:31:42 GMT your computer crashed
crash dump file: C:\Windows\Minidump\103111-20531-01.dmp
This was probably caused by the following module: portcls.sys (portcls+0x4304)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF880073C3304, 0xFFFFF88009C5EC70, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\drivers\portcls.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Port Class (Class Driver for Port/Miniport Devices)
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 which cannot be identified at this time.

On Mon 2011-10-31 12:39:20 GMT your computer crashed
crash dump file: C:\Windows\Minidump\103111-22953-01.dmp
This was probably caused by the following module: win32k.sys (win32k+0x16844)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF960000E6844, 0xFFFFF880057F9B50, 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 which cannot be identified at this time.

On Mon 2011-10-17 19:47:22 GMT your computer crashed
crash dump file: C:\Windows\Minidump\101711-21859-01.dmp
This was probably caused by the following module: hal.dll (hal+0x12A3B)
Bugcheck code: 0x124 (0x0, 0xFFFFFA8006FCC028, 0xB669C000, 0x135)
Error: WHEA_UNCORRECTABLE_ERROR
file path: C:\Windows\system32\hal.dll
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Hardware Abstraction Layer DLL
Bug check description: This bug check indicates that a fatal hardware error has occurred. This bug check uses the error data that is provided by the Windows Hardware Error Architecture (WHEA).
This is likely to be caused by a hardware problem problem. This problem might be caused by a thermal issue.
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 which cannot be identified at this time.

On Wed 2011-10-12 10:32:30 GMT your computer crashed
crash dump file: C:\Windows\Minidump\101211-21500-01.dmp
This was probably caused by the following module: hal.dll (hal+0x12A3B)
Bugcheck code: 0x124 (0x0, 0xFFFFFA8006F1B028, 0xF26AC000, 0x175)
Error: WHEA_UNCORRECTABLE_ERROR
file path: C:\Windows\system32\hal.dll
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Hardware Abstraction Layer DLL
Bug check description: This bug check indicates that a fatal hardware error has occurred. This bug check uses the error data that is provided by the Windows Hardware Error Architecture (WHEA).
This is likely to be caused by a hardware problem problem. This problem might be caused by a thermal issue.
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 which cannot be identified at this time.

The following dump files were found but could not be read. These files may be corrupt:
C:\Windows\Minidump\110211-27390-01.dmp

Gå till inlägget
Visa signatur

Cooler Master Haf X // Intel I7 2600k // 2x Gtx 560 ti oc SLI // 16gb ddr3 Corsair Vengeance // Ocz 120gb ssd // Ocz 1250w psu // Cpu kylare Corsair H100 // Sabertooth P67

Redigera
Citera flera Citera
Permalänk
Medlem
●
Skrivet av hasoo:

Har du fått ngt vettigt svar av folk på andra trådar?

Gå till inlägget

Jag har faktiskt inte frågat någonstans. Ska prova att formatera datorn imorgon och installera alla drivrutiner från scratch så att säga. Löser inte det problemet så får vi väl vänta på patch från Nvidia.

Redigera
Citera flera Citera
Permalänk
Medlem
●

Formatera inte! har gjort det och det händer inget utan samma problem uppstår men det var en här på swec som sa att han uppdaterade moderkortets bios och att det löste sig atm hoppas att de håller bara ska göra det jag med tänkte jag.

Skrivet av Ahlqvist162:

Jag har faktiskt inte frågat någonstans. Ska prova att formatera datorn imorgon och installera alla drivrutiner från scratch så att säga. Löser inte det problemet så får vi väl vänta på patch från Nvidia.

Gå till inlägget
Visa signatur

Cooler Master Haf X // Intel I7 2600k // 2x Gtx 560 ti oc SLI // 16gb ddr3 Corsair Vengeance // Ocz 120gb ssd // Ocz 1250w psu // Cpu kylare Corsair H100 // Sabertooth P67

Redigera
Citera flera Citera
Permalänk
Medlem
●
Skrivet av hasoo:

Formatera inte! har gjort det och det händer inget utan samma problem uppstår men det var en här på swec som sa att han uppdaterade moderkortets bios och att det löste sig atm hoppas att de håller bara ska göra det jag med tänkte jag.

Gå till inlägget

Jag har senaste biosversionen till mitt moderkort och det har ju inte löst något problem, hittar inte heller några biosuppdateringar till grafikkortet? Msi Twin frozr har jag iaf.

Senast redigerat
Redigera
Citera flera Citera
1
Skriv svar
Senaste nyheterna
Hårdvara
Mjukvara
Övrigt
Nytt i forumet
Datorkomponenter
System
Ljud, bild och kommunikation
Spel och mjukvara