Alle drivere der er problemer med, pånær én, er relateret til dit grafikkort. Du har Nvidia går jeg ud fra. Har du opdateret til den nyeste driver, evt. med en "fresh install"?
--
http://tinyCode.dk[...]

Den fortæller dig da at der er noget galt med driveren til dit grafikkort. Eller er det mig der har misforstået noget? Prøv at geninstaller din grafik driver, og tjek dine temperature på både GPU og CPU :-)
--
Hjemløs gamer, ses på hjørnet.

Som der bliver sagt. 1) opdater din GPU driver 2) hvis ikke #1 virker, så afinstaller og lav en frisk driveriinstall 3) hvis ikke dette har løst problemet, lav en frisk windows install 4) Tjek temperaturen på dit GFX (og resten af systemet) 5) hvis ikke dette løser problemet, overvej en RMA på dit gfx kort / system (hvis det er købt samlet, så self. samlet) Inden du opretter en RMA, kan du evt. teste med et andet grafikkort? (hvis ikke dit case er sealed hvis du har købt det som et samlet system, for så skal du ikke bryde det seal)
--
Jutus fortis tenax est - Klistermærker er ikke casemod

#0 Geninstaller Windows. Download alle de nye drivere og installer dem. Installer spil og programmer. Ny dumplog hvis problemet stadig er der. Grunden til at jeg ville geninstallere Windows, er fordi jeg gætter på at du ikke har geninstalleret i det 1½ år du har haft computeren.
--
Google først, spørg bagefter.

Har du skiftet dele i den? da det godt kan være med til at driverne ikke kan fatte hvad der sker. Men ja det er umiddelbart din GPU som de andre også siger. Så prøv det -Mastersell
--
LONG LIVE STATIONÆRE COMPUTERE!!!

Tusind tak for svar alle sammen og undskyld jeg først skriver tilbage nu... #1: Den er nu opdateret til den nyeste version, har også lavet en fresh install, men problemet fortsættter :-( #2: Den er opdateret til den nyeste version... #3: jeg tror jeg gør som punkt 3 på din liste og geninstallerer Windows... #4: det er korrekt, har ikke geninstalleret Windows siden jeg installerede det... #5: det eneste jeg har udskiftet er en ssd, samme dag som jeg skrev indlægget, men det er hverken blevet værre eller bedre med BSOD... Til jer alle sammen: findes der en måde hvorpå jeg kan geninstallere windows og stadig beholde bogmærker, programindstillinger, downloads, dokumenter, osv..? PFT
--

#6 Du fører alt din data over på en anden partition på harddisken eller på en ekstern usb pen/hdd. Så fører du det tilbage igen når Windows er installeret igen. Jeg er ret sikker på at version 314.22 ikke er nyeste version af Nvidia-driveren til dit grafikkort. Jeg kan finde denne Version: 334.89 - Release Date: Tue Feb 18, 2014 - men da du ikke skriver hvilket grafikkort du har, så er det svært at sige om du kan bruge den.
--
Google først, spørg bagefter.

Prøv at bruge display driver uninstaller fra guru3d og installer nyeste driver i fejlsikret tilstand: http://www.guru3d.com[...] Hvis altså du ikke allerede har gjort det ;)
--

Hej Jacob Er der ikke en automatisk måde at eksportere og derefter importere det jeg gerne vil gemme..? Bruger pt. Crashplan på min Mac og der kan man vælge hvad man vil backe up og derefter importere igennem Overførselsassistent... havde ikke fået lagt den nyeste dumplog ud, her er den (mit GFX er forresten et MSI GTX 560TI): System Information (local) computer name: MARC-PC windows version: Windows 7 Service Pack 1, 6.1, build: 7601 windows dir: C:\Windows Hardware: MS-7758, MSI, Z77A-G43 (MS-7758) CPU: GenuineIntel Intel(R) Core(TM) i5-3570K CPU @ 3.40GHz Intel586, level: 6 4 logical processors, active mask: 15 RAM: 8538484736 total VM: 2147352576, free: 1915707392 Crash Dump Analysis Crash dump directory: C:\Windows\Minidump Crash dumps are enabled on your computer. On Tue 04-03-2014 13:44:46 GMT your computer crashed crash dump file: C:\Windows\Minidump\030414-3946-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0) Bugcheck code: 0xFC (0xFFFFF900C0217AA8, 0xF4F000017A51E863, 0xFFFFF8800D9CD090, 0x2) Error: ATTEMPTED_EXECUTE_OF_NOEXECUTE_MEMORY 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 attempt was made to execute non-executable memory. 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. There is a possibility this problem was caused by a virus or other malware. The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time. On Tue 04-03-2014 13:44:10 GMT your computer crashed crash dump file: C:\Windows\Minidump\030414-4056-01.dmp This was probably caused by the following module: Unknown () Bugcheck code: 0x0 (0x0, 0x0, 0x0, 0x0) Error: CUSTOM_ERROR A third party driver was identified as the probable root cause of this system error. Google query: CUSTOM_ERROR On Tue 04-03-2014 13:44:10 GMT your computer crashed crash dump file: C:\Windows\Minidump\030414-4945-01.dmp This was probably caused by the following module: win32k.sys (win32k+0xB4293) Bugcheck code: 0x3B (0xC000001D, 0xFFFFF960000F4293, 0xFFFFF88009B95280, 0x0) Error: SYSTEM_SERVICE_EXCEPTION file path: C:\Windows\system32\win32k.sys product: Microsoft® Windows® Operativsystem company: Microsoft Corporation description: Win32-flerbrugerdriver 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 Tue 04-03-2014 13:43:50 GMT your computer crashed crash dump file: C:\Windows\Minidump\030414-3900-01.dmp This was probably caused by the following module: Unknown () Bugcheck code: 0x0 (0x0, 0x0, 0x0, 0x0) Error: CUSTOM_ERROR A third party driver was identified as the probable root cause of this system error. Google query: CUSTOM_ERROR On Sat 08-03-2014 19:21:22 GMT your computer crashed crash dump file: C:\Windows\Minidump\030814-4305-01.dmp This was probably caused by the following module: win32k.sys (win32k+0x12AE54) Bugcheck code: 0x3B (0xC0000005, 0xFFFFF9600016AE54, 0xFFFFF8800AE3EEF0, 0x0) Error: SYSTEM_SERVICE_EXCEPTION file path: C:\Windows\system32\win32k.sys product: Microsoft® Windows® Operativsystem company: Microsoft Corporation description: Win32-flerbrugerdriver 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 Sat 08-03-2014 19:21:22 GMT your computer crashed crash dump file: C:\Windows\memory.dmp This was probably caused by the following module: win32k.sys (win32k+0x12AE54) Bugcheck code: 0x3B (0xC0000005, 0xFFFFF9600016AE54, 0xFFFFF8800AE3EEF0, 0x0) Error: SYSTEM_SERVICE_EXCEPTION file path: C:\Windows\system32\win32k.sys product: Microsoft® Windows® Operativsystem company: Microsoft Corporation description: Win32-flerbrugerdriver 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 Sat 08-03-2014 00:41:10 GMT your computer crashed crash dump file: C:\Windows\Minidump\030814-3868-01.dmp This was probably caused by the following module: nskernel.sys (NSKernel+0x126EF) Bugcheck code: 0x3B (0xC0000005, 0xFFFFF88002AE26EF, 0xFFFFF8800C4B67B0, 0x0) Error: SYSTEM_SERVICE_EXCEPTION file path: C:\Windows\system32\drivers\nskernel.sys product: BullGuard company: BullGuard Ltd. description: BullGuard Behaviour Monitor 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. 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: nskernel.sys (BullGuard Behaviour Monitor, BullGuard Ltd.). Google query: BullGuard Ltd. SYSTEM_SERVICE_EXCEPTION On Sat 08-03-2014 00:33:59 GMT your computer crashed crash dump file: C:\Windows\Minidump\030814-3806-01.dmp This was probably caused by the following module: afd.sys (afd+0x53719) Bugcheck code: 0xD1 (0xF100000, 0x2, 0x1, 0xFFFFF880029A5719) Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL file path: C:\Windows\system32\drivers\afd.sys product: Microsoft® Windows® Operativsystem company: Microsoft Corporation description: Ancillary Function Driver for WinSock 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 that cannot be identified at this time. On Thu 06-03-2014 23:22:47 GMT your computer crashed crash dump file: C:\Windows\Minidump\030714-5553-01.dmp This was probably caused by the following module: nvlddmkm.sys (nvlddmkm+0x16A8D4) Bugcheck code: 0x1000007E (0xFFFFFFFFC000001D, 0xFFFFF8800316C8D4, 0xFFFFF880092F3038, 0xFFFFF880092F2890) Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M file path: C:\Windows\system32\drivers\nvlddmkm.sys product: NVIDIA Windows Kernel Mode Driver, Version 334.89 company: NVIDIA Corporation description: NVIDIA Windows Kernel Mode Driver, Version 334.89 Bug 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. 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 334.89 , NVIDIA Corporation). Google query: NVIDIA Corporation SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M On Thu 06-03-2014 16:06:28 GMT your computer crashed crash dump file: C:\Windows\Minidump\030614-4820-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0) Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF88002720E00, 0x0, 0x0) Error: KMODE_EXCEPTION_NOT_HANDLED 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 program 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. Conclusion 17 crash dumps have been found and analyzed. Only 10 are included in this report. 2 third party drivers have 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 334.89 , NVIDIA Corporation) nskernel.sys (BullGuard Behaviour Monitor, BullGuard Ltd.) 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.
--

Det kan osse være din harddisk bootsector der er fucked, hvis geninstall af Windows ikke virker, så prøv evt. med en bootdisk der kan 'gendanne' din harddisk som var den helt fresh. F.eks. Acronis Bootdisk kan dette (koster penge) men sikkert osse mange andre.
--
Athlon II X4 620 @3 Ghz | Radeon 5770 | Intel X25 SSD | Windows 8.1

#9 Der findes sikkert utallige backup-programmer, men jeg kan ikke hjælpe dig med det, da jeg ikke bruger disse programmer. Hvis du er bange for at miste noget, kan du boote på en linux livecd og så føre hele dit c drev (windowsprtition) over på en ekstern disk. Så har du det hele liggende. Nvidia 334 driveren er også til dit kort, så start med at insstallere den.
--
Google først, spørg bagefter.