Exoit Geplaatst: 23 februari 2010 Rapport Geplaatst: 23 februari 2010 (bewerkt) Hallo lui, sinds dat ik windows 7 heb geïnstalleerd op mijn computer deed hij al raar. Hij bleef maar blue screens geven als ik even aan het gamen was en zelfs heel soms al ik aan het internetten was. Ik vind dit heel raar en natuurlijk stoort het mij. Al mijn hardware werkt gewoon en daar zijn geen problemen mee. Sinds het installeren van W7 tot nu zijn er al 41 BSOD's geweest, gewoon ongelofelijk! Voor het geval jullie mijn specs nodig hebben post ik die even. PC Specs: Rapport van Ruben Boerstoel's computerUitgevoerd op 2/23/2010, 12:43:28 PM [table=border] Computer|Fabrikant:|MICRO-STAR INTERNATIONAL CO.,LTD |Computermodel:|MS-7583 |Computernaam:|PC-RUBEN (in werkgroep WORKGROUP) |Systeemtype:|x64 (64-bits) systeem Moederbord|Fabrikant:|MICRO-STAR INTERNATIONAL CO.,LTD |Model:|P55-GD65 (MS-7583) |BIOS Fabrikant:|American Megatrends Inc. |BIOS Model:|Default System BIOS, versie V1.4 |Aansluitingen:|PCI1 (Vrij), PCI2 (Vrij), PCIE1 (Vrij), PCIE2 (Gebruikt), PCIE3 (Vrij), PCIE4 (Vrij), PCIE5 (Vrij) |Poorten:|J1A1 (Muis), J1A1 (Toetsenbord), J2A2 (USB), J2A2 (USB), J4A1 (Parallel), J2A1 (Serieel), J6A1 (Audio), J6A1 (Audio), J6A1 (Audio), J5A1 (USB), J5A1 (USB), J5A1 (Netwerk), J6B1 - AUX IN (Audio), J6B2 - CDIN (Audio), J6J2 - PRI IDE (Geen), J6J1 - SEC IDE (Geen), J4J1 - FLOPPY (Geen), J9H1 - FRONT PNL (Geen), J1B1 - CHASSIS REAR FAN (Geen), J2F1 - CPU FAN (Geen), J8B4 - FRONT FAN (Geen), J9G2 - FNT USB (Geen), J6C3 - FP AUD (Geen), J9G1 - CONFIG (Geen), J8C1 - SCSI LED (Geen), J9J2 - INTRUDER (Geen) Processor|Model:|Intel® Core i7 CPU 860 @ 2.80GHz (Octa Core) |Kloksnelheid:|2534 MHz |Socket & Cache(s):|CPU 1, 1024 KB L2 Cache, 8192 KB L3 Cache Geheugen|Grootte:|4087 MB RAM |Type(s):|2048 MB RAM (DDR, DIMM), 2048 MB RAM (DDR, DIMM) Hardeschijf|Bestandstype(s):|NTFS (C:), NTFS (E:), NTFS (F:) |Grootte:|1397.17 GB (97.56 GB (C:) + 368.10 GB (E:) + 931.51 GB (F:) ) |Vrije ruimte:|1169.00 GB (53.23 GB (C:) + 351.95 GB (E:) + 763.82 GB (F:) ) Stations|Type(s):|C: Local Fixed Disk, D: Onbekend, E: Local Fixed Disk, F: Local Fixed Disk |Model(len):|C: SAMSUNG HD502HI ATA Device IDE, D: Optiarc DVD RW AD-7240S ATA Device, E: WD 10EAVS External USB Device USB Geluidskaart|Fabrikant:|ATI Technologies Inc. |Model:|ATI High Definition Audio Device Videokaart|Model:|ATI Radeon HD 5700 Series |Beeldprocessor:|ATI display adapter (0x68B8) |Geheugengrootte:|1024 MB VRAM |Stuurprogramma:|atiu9p64 aticfx64 aticfx64 atiu9pag aticfx32 aticfx32 atiumd64 atidxx64 atidxx64 atiumdag atidxx32 atidxx32 atiumdva atiumd6a atitmm64, versie 8.690.3.1000 Beeldscherm|Fabrikant:|AG Neovo |Model:|H-W19 |Schermresolutie:|1440x900 (Breedbeeld 16:10 WXGA+) |Kleurdiepte:|32-bits |Frequentie:|60 Hz Muis|Fabrikant:|(Standard system devices) |Model:|USB Input Device |Aantal knoppen:|2 |Aansluiting:|USB Toetsenbord|Model:|Standard PS/2 Keyboard |Type:|Enhanced (101- or 102-key) |Functietoetsen:|12 Netwerkkaart|Model(len):|Realtek PCIe GBE Family Controller (Ethernet 802.3), Realtek PCIe GBE Family Controller (Ethernet 802.3) |Adressen:|IP: 192.168.1.81, MAC: 40:61:86:07:8B:E9, DHCP: 192.168.1.254 DirectX|Versie:|11.0 Besturingssysteem|Naam:|Microsoft Windows 7 Ultimate |Versie:|6.1.7600 |Service Pack:|Geen [/table] Gegenereerd door Flitskikker InfoTool (Versie 3.0.0.133) De meeste voorkomende crashes zijn: DirectX Graphics MMS & NT Kernel & System Ook zal ik die allemaal posten: Welcome to WhoCrashed Home Edition 2.00 -------------------------------------------------------------------------------- This program checks for drivers which have been crashing your computer. Whenever a computer suddenly reboots without displaying any notice or blue screen of death, the first thing that is often though 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, most computers do not show a blue screen unless they are configured to do so. Instead these systems suddenly reboot without any notice. This program does post-mortem crash dump analysis with the single click of a button. To obtain technical support visit www.resplendence.com/support To check if a newer version of this program is available, click here. 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. The professional edition of WhoCrashed also allows analysis of crashdumps on remote drives and computers on the network and offers more detailed analysis. -------------------------------------------------------------------------------- Analysis -------------------------------------------------------------------------------- Crash dump directory: C:\Windows\Minidump Crash dumps are enabled on your computer. On Tue 2/23/2010 8:29:26 PM your computer crashed This was likely caused by the following module: dxgmms1.sys Bugcheck code: 0x119 (0x7000000, 0xFFFFFA8006286410, 0xFFFFFA8003EDF010, 0xFFFFFA800702AD70) Error: VIDEO_SCHEDULER_INTERNAL_ERROR Dump file: C:\Windows\Minidump\022310-23134-01.dmp file path: C:\Windows\system32\drivers\dxgmms1.sys product: Microsoft® Windows® Operating System company: Microsoft Corporation description: DirectX Graphics MMS The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit may be another driver on your system which cannot be identified at this time. On Tue 2/23/2010 6:50:58 PM your computer crashed This was likely caused by the following module: npfs.sys Bugcheck code: 0xC2 (0x7, 0x1097, 0x0, 0xFFFFFA8003FA3650) Error: BAD_POOL_CALLER Dump file: C:\Windows\Minidump\022310-23353-01.dmp file path: C:\Windows\system32\drivers\npfs.sys product: Microsoft® Windows® Operating System company: Microsoft Corporation description: NPFS Driver The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit may be another driver on your system which cannot be identified at this time. On Tue 2/23/2010 12:38:50 PM your computer crashed This was likely caused by the following module: usbaudio.sys Bugcheck code: 0xC2 (0x7, 0x1097, 0x4CB1D10, 0xFFFFFA8006E8BB80) Error: BAD_POOL_CALLER Dump file: C:\Windows\Minidump\022310-24585-01.dmp file path: C:\Windows\system32\drivers\usbaudio.sys product: Microsoft® Windows® Operating System company: Microsoft Corporation description: USB Audio Class Driver The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit may be another driver on your system which cannot be identified at this time. On Tue 2/23/2010 11:35:33 AM your computer crashed This was likely caused by the following module: atikmpag.sys Bugcheck code: 0x3B (0xC0000005, 0xFFFFF880041B6957, 0xFFFFF8800A6F4F20, 0x0) Error: SYSTEM_SERVICE_EXCEPTION Dump file: C:\Windows\Minidump\022310-25958-01.dmp file path: C:\Windows\system32\drivers\atikmpag.sys product: AMD driver company: Advanced Micro Devices, Inc. description: AMD multi-vendor Miniport Driver On Tue 2/23/2010 11:09:09 AM your computer crashed This was likely caused by the following module: ntoskrnl.exe Bugcheck code: 0xC5 (0x800000008, 0x2, 0x1, 0xFFFFF80002FAC90D) Error: DRIVER_CORRUPTED_EXPOOL Dump file: C:\Windows\Minidump\022310-26816-01.dmp file path: C:\Windows\system32\ntoskrnl.exe product: Microsoft® Windows® Operating System company: Microsoft Corporation description: NT Kernel & System The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit may be another driver on your system which cannot be identified at this time. On Tue 2/23/2010 10:33:09 AM your computer crashed This was likely caused by the following module: dxgmms1.sys Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF88004FCD577, 0xFFFFF88002E068A8, 0xFFFFF88002E06100) Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M Dump file: C:\Windows\Minidump\022310-22947-01.dmp file path: C:\Windows\system32\drivers\dxgmms1.sys product: Microsoft® Windows® Operating System company: Microsoft Corporation description: DirectX Graphics MMS The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit may be another driver on your system which cannot be identified at this time. On Tue 2/23/2010 10:16:42 AM your computer crashed This was likely caused by the following module: dxgmms1.sys Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF88004F6CCF7, 0xFFFFF88005FDD6A8, 0xFFFFF88005FDCF00) Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M Dump file: C:\Windows\Minidump\022310-23478-01.dmp file path: C:\Windows\system32\drivers\dxgmms1.sys product: Microsoft® Windows® Operating System company: Microsoft Corporation description: DirectX Graphics MMS The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit may be another driver on your system which cannot be identified at this time. On Mon 2/22/2010 10:45:22 PM your computer crashed This was likely caused by the following module: ntoskrnl.exe Bugcheck code: 0x109 (0xA3A039D895BDB55E, 0x0, 0x9181686F392B97CA, 0x101) Error: CRITICAL_STRUCTURE_CORRUPTION Dump file: C:\Windows\Minidump\022210-23571-01.dmp file path: C:\Windows\system32\ntoskrnl.exe product: Microsoft® Windows® Operating System company: Microsoft Corporation description: NT Kernel & System The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit may be another driver on your system which cannot be identified at this time. On Mon 2/22/2010 10:36:29 PM your computer crashed This was likely caused by the following module: dxgmms1.sys Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF88004F90CEE, 0xFFFFF88005FDB6A8, 0xFFFFF88005FDAF00) Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M Dump file: C:\Windows\Minidump\022210-23025-01.dmp file path: C:\Windows\system32\drivers\dxgmms1.sys product: Microsoft® Windows® Operating System company: Microsoft Corporation description: DirectX Graphics MMS The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit may be another driver on your system which cannot be identified at this time. On Mon 2/22/2010 9:25:41 PM your computer crashed This was likely caused by the following module: ntoskrnl.exe Bugcheck code: 0xA (0x28, 0x2, 0x0, 0xFFFFF80002F01090) Error: IRQL_NOT_LESS_OR_EQUAL Dump file: C:\Windows\Minidump\022210-30841-01.dmp file path: C:\Windows\system32\ntoskrnl.exe product: Microsoft® Windows® Operating System company: Microsoft Corporation description: NT Kernel & System The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit may be another driver on your system which cannot be identified at this time. On Mon 2/22/2010 9:00:42 PM your computer crashed This was likely caused by the following module: ntoskrnl.exe Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80002ED7105, 0xFFFFF88007139CE0, 0x0) Error: SYSTEM_SERVICE_EXCEPTION Dump file: C:\Windows\Minidump\022210-25521-01.dmp file path: C:\Windows\system32\ntoskrnl.exe product: Microsoft® Windows® Operating System company: Microsoft Corporation description: NT Kernel & System The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit may be another driver on your system which cannot be identified at this time. On Mon 2/22/2010 8:58:50 PM your computer crashed This was likely caused by the following module: ntoskrnl.exe Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80002FB04EE, 0xFFFFF8800A963010, 0x0) Error: SYSTEM_SERVICE_EXCEPTION Dump file: C:\Windows\Minidump\022210-23212-01.dmp file path: C:\Windows\system32\ntoskrnl.exe product: Microsoft® Windows® Operating System company: Microsoft Corporation description: NT Kernel & System The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit may be another driver on your system which cannot be identified at this time. On Mon 2/22/2010 8:36:37 PM your computer crashed This was likely caused by the following module: ntoskrnl.exe Bugcheck code: 0xC5 (0x8, 0x2, 0x1, 0xFFFFF80002FA690D) Error: DRIVER_CORRUPTED_EXPOOL Dump file: C:\Windows\Minidump\022210-23758-01.dmp file path: C:\Windows\system32\ntoskrnl.exe product: Microsoft® Windows® Operating System company: Microsoft Corporation description: NT Kernel & System The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit may be another driver on your system which cannot be identified at this time. On Mon 2/22/2010 7:54:20 PM your computer crashed This was likely caused by the following module: ntoskrnl.exe Bugcheck code: 0x19 (0x3, 0xFFFFF8000300EA10, 0xFFFFF8000300EA10, 0xFFFFF8000308EA10) Error: BAD_POOL_HEADER Dump file: C:\Windows\Minidump\022210-30326-01.dmp file path: C:\Windows\system32\ntoskrnl.exe product: Microsoft® Windows® Operating System company: Microsoft Corporation description: NT Kernel & System The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit may be another driver on your system which cannot be identified at this time. On Mon 2/22/2010 7:47:41 PM your computer crashed This was likely caused by the following module: dxgmms1.sys Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF88004FAC577, 0xFFFFF880061C88A8, 0xFFFFF880061C8100) Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M Dump file: C:\Windows\Minidump\022210-31262-01.dmp file path: C:\Windows\system32\drivers\dxgmms1.sys product: Microsoft® Windows® Operating System company: Microsoft Corporation description: DirectX Graphics MMS The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit may be another driver on your system which cannot be identified at this time. On Mon 2/22/2010 5:51:35 PM your computer crashed This was likely caused by the following module: ntoskrnl.exe Bugcheck code: 0x1A (0x31, 0xFFFFFA80065A9690, 0xFFFFF8800C41F000, 0xFFFFF8A006B6F645) Error: MEMORY_MANAGEMENT Dump file: C:\Windows\Minidump\022210-25303-01.dmp file path: C:\Windows\system32\ntoskrnl.exe product: Microsoft® Windows® Operating System company: Microsoft Corporation description: NT Kernel & System The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit may be another driver on your system which cannot be identified at this time. On Mon 2/22/2010 5:30:50 PM your computer crashed This was likely caused by the following module: dxgmms1.sys Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF88004F75CF7, 0xFFFFF88005FC76A8, 0xFFFFF88005FC6F00) Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M Dump file: C:\Windows\Minidump\022210-13899-01.dmp file path: C:\Windows\system32\drivers\dxgmms1.sys product: Microsoft® Windows® Operating System company: Microsoft Corporation description: DirectX Graphics MMS The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit may be another driver on your system which cannot be identified at this time. On Mon 2/22/2010 2:43:47 PM your computer crashed This was likely caused by the following module: usbhub.sys Bugcheck code: 0xC5 (0x4008A, 0x2, 0x0, 0xFFFFF800030040BF) Error: DRIVER_CORRUPTED_EXPOOL Dump file: C:\Windows\Minidump\022210-16099-01.dmp file path: C:\Windows\system32\drivers\usbhub.sys product: Microsoft® Windows® Operating System company: Microsoft Corporation description: Default Hub Driver for USB The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit may be another driver on your system which cannot be identified at this time. On Mon 2/22/2010 2:07:19 PM your computer crashed This was likely caused by the following module: ntoskrnl.exe Bugcheck code: 0xC2 (0x7, 0x1097, 0x0, 0xFFFFF8A00278C220) Error: BAD_POOL_CALLER Dump file: C:\Windows\Minidump\022210-15787-01.dmp file path: C:\Windows\system32\ntoskrnl.exe product: Microsoft® Windows® Operating System company: Microsoft Corporation description: NT Kernel & System The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit may be another driver on your system which cannot be identified at this time. On Mon 2/22/2010 12:20:07 PM your computer crashed This was likely caused by the following module: ntoskrnl.exe Bugcheck code: 0x19 (0x3, 0xFFFFFA8007334780, 0xFFFFFA8007334780, 0xFFFFFA80073B4780) Error: BAD_POOL_HEADER Dump file: C:\Windows\Minidump\022210-17487-01.dmp file path: C:\Windows\system32\ntoskrnl.exe product: Microsoft® Windows® Operating System company: Microsoft Corporation description: NT Kernel & System The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit may be another driver on your system which cannot be identified at this time. On Mon 2/22/2010 12:17:01 PM your computer crashed This was likely caused by the following module: atipmdag.sys Bugcheck code: 0x3B (0xC0000005, 0xFFFFF88004AD7646, 0xFFFFF88008EAF7F0, 0x0) Error: SYSTEM_SERVICE_EXCEPTION Dump file: C:\Windows\Minidump\022210-16894-01.dmp file path: C:\Windows\system32\drivers\atipmdag.sys product: ATI Radeon Family company: ATI Technologies Inc. description: ATI Radeon Kernel Mode Driver On Mon 2/22/2010 11:38:50 AM your computer crashed This was likely caused by the following module: dxgmms1.sys Bugcheck code: 0x3B (0xC0000005, 0xFFFFF88004F6C53A, 0xFFFFF88007287B70, 0x0) Error: SYSTEM_SERVICE_EXCEPTION Dump file: C:\Windows\Minidump\022210-20748-01.dmp file path: C:\Windows\system32\drivers\dxgmms1.sys product: Microsoft® Windows® Operating System company: Microsoft Corporation description: DirectX Graphics MMS The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit may be another driver on your system which cannot be identified at this time. On Mon 2/22/2010 10:34:04 AM your computer crashed This was likely caused by the following module: ntoskrnl.exe Bugcheck code: 0xA (0x80008, 0x2, 0x0, 0xFFFFF80002E790AD) Error: IRQL_NOT_LESS_OR_EQUAL Dump file: C:\Windows\Minidump\022210-19328-01.dmp file path: C:\Windows\system32\ntoskrnl.exe product: Microsoft® Windows® Operating System company: Microsoft Corporation description: NT Kernel & System The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit may be another driver on your system which cannot be identified at this time. On Sun 2/21/2010 7:09:37 PM your computer crashed This was likely caused by the following module: ntoskrnl.exe Bugcheck code: 0xA (0x0, 0x2, 0x1, 0xFFFFF80002EB1D52) Error: IRQL_NOT_LESS_OR_EQUAL Dump file: C:\Windows\Minidump\022110-19203-01.dmp file path: C:\Windows\system32\ntoskrnl.exe product: Microsoft® Windows® Operating System company: Microsoft Corporation description: NT Kernel & System The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit may be another driver on your system which cannot be identified at this time. On Sun 2/21/2010 7:07:52 PM your computer crashed This was likely caused by the following module: ntoskrnl.exe Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80002E97F4F, 0xFFFFF8800937AEC0, 0x0) Error: SYSTEM_SERVICE_EXCEPTION Dump file: C:\Windows\Minidump\022110-18985-01.dmp file path: C:\Windows\system32\ntoskrnl.exe product: Microsoft® Windows® Operating System company: Microsoft Corporation description: NT Kernel & System The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit may be another driver on your system which cannot be identified at this time. On Sun 2/21/2010 7:06:30 PM your computer crashed This was likely caused by the following module: rt64win7.sys Bugcheck code: 0xD1 (0x8, 0x2, 0x1, 0xFFFFF88004F3B523) Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL Dump file: C:\Windows\Minidump\022110-17253-01.dmp file path: C:\Windows\system32\drivers\rt64win7.sys product: Realtek 8136/8168/8169 PCI/PCIe Adapters company: Realtek description: Realtek 8136/8168/8169 NDIS 6.20 64-bit Driver On Sun 2/21/2010 5:11:35 PM your computer crashed This was likely caused by the following module: dxgmms1.sys Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF88004820CEE, 0xFFFFF88005DC16A8, 0xFFFFF88005DC0F00) Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M Dump file: C:\Windows\Minidump\022110-17409-01.dmp file path: C:\Windows\system32\drivers\dxgmms1.sys product: Microsoft® Windows® Operating System company: Microsoft Corporation description: DirectX Graphics MMS The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit may be another driver on your system which cannot be identified at this time. On Sun 2/21/2010 4:56:11 PM your computer crashed This was likely caused by the following module: dxgmms1.sys Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF88004F54CEE, 0xFFFFF88005DCF6A8, 0xFFFFF88005DCEF00) Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M Dump file: C:\Windows\Minidump\022110-16692-01.dmp file path: C:\Windows\system32\drivers\dxgmms1.sys product: Microsoft® Windows® Operating System company: Microsoft Corporation description: DirectX Graphics MMS The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit may be another driver on your system which cannot be identified at this time. On Sun 2/21/2010 4:08:27 PM your computer crashed This was likely caused by the following module: afd.sys Bugcheck code: 0xD1 (0x8, 0x2, 0x1, 0xFFFFF88002CF51BD) Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL Dump file: C:\Windows\Minidump\022110-18189-01.dmp file path: C:\Windows\system32\drivers\afd.sys product: Microsoft® Windows® Operating System company: Microsoft Corporation description: Ancillary Function Driver for WinSock The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit may be another driver on your system which cannot be identified at this time. On Sun 2/21/2010 4:00:00 PM your computer crashed This was likely caused by the following module: dxgmms1.sys Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF88004F7DCEE, 0xFFFFF88005FC66A8, 0xFFFFF88005FC5F00) Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M Dump file: C:\Windows\Minidump\022110-18142-01.dmp file path: C:\Windows\system32\drivers\dxgmms1.sys product: Microsoft® Windows® Operating System company: Microsoft Corporation description: DirectX Graphics MMS The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit may be another driver on your system which cannot be identified at this time. On Sun 2/21/2010 11:54:18 AM your computer crashed This was likely caused by the following module: lvrs64.sys Bugcheck code: 0x19 (0x22, 0x80000, 0x0, 0x0) Error: BAD_POOL_HEADER Dump file: C:\Windows\Minidump\022110-22916-01.dmp file path: C:\Windows\system32\drivers\lvrs64.sys product: Logitech Webcam Software company: Logitech Inc. description: Logitech Kernel Audio Improvement Filter Driver On Sun 2/21/2010 11:28:55 AM your computer crashed This was likely caused by the following module: dxgmms1.sys Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF88004FD0CEE, 0xFFFFF88005DCD6A8, 0xFFFFF88005DCCF00) Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M Dump file: C:\Windows\Minidump\022110-28766-01.dmp file path: C:\Windows\system32\drivers\dxgmms1.sys product: Microsoft® Windows® Operating System company: Microsoft Corporation description: DirectX Graphics MMS The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit may be another driver on your system which cannot be identified at this time. On Sun 2/21/2010 11:24:26 AM your computer crashed This was likely caused by the following module: netio.sys Bugcheck code: 0xC5 (0x8, 0x2, 0x0, 0xFFFFF800030040BF) Error: DRIVER_CORRUPTED_EXPOOL Dump file: C:\Windows\Minidump\022110-29281-01.dmp file path: C:\Windows\system32\drivers\netio.sys product: Microsoft® Windows® Operating System company: Microsoft Corporation description: Network I/O Subsystem The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit may be another driver on your system which cannot be identified at this time. On Sun 2/21/2010 11:09:14 AM your computer crashed This was likely caused by the following module: ntoskrnl.exe Bugcheck code: 0xC5 (0x8, 0x2, 0x0, 0xFFFFF800030010BF) Error: DRIVER_CORRUPTED_EXPOOL Dump file: C:\Windows\Minidump\022110-28173-01.dmp file path: C:\Windows\system32\ntoskrnl.exe product: Microsoft® Windows® Operating System company: Microsoft Corporation description: NT Kernel & System The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit may be another driver on your system which cannot be identified at this time. On Sun 2/21/2010 10:47:42 AM your computer crashed This was likely caused by the following module: ntoskrnl.exe Bugcheck code: 0xA (0xFFFFF8A008153DC0, 0x0, 0x0, 0xFFFFF80002EFB241) Error: IRQL_NOT_LESS_OR_EQUAL Dump file: C:\Windows\Minidump\022110-26410-01.dmp file path: C:\Windows\system32\ntoskrnl.exe product: Microsoft® Windows® Operating System company: Microsoft Corporation description: NT Kernel & System The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit may be another driver on your system which cannot be identified at this time. On Sun 2/21/2010 5:47:53 AM your computer crashed This was likely caused by the following module: ntoskrnl.exe Bugcheck code: 0x19 (0x3, 0xFFFFFA80043C37C0, 0x1BAE0000089C00, 0xFFFFFA80043C37C0) Error: BAD_POOL_HEADER Dump file: C:\Windows\Minidump\022010-20701-01.dmp file path: C:\Windows\system32\ntoskrnl.exe product: Microsoft® Windows® Operating System company: Microsoft Corporation description: NT Kernel & System The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit may be another driver on your system which cannot be identified at this time. On Sun 2/21/2010 5:40:54 AM your computer crashed This was likely caused by the following module: dxgmms1.sys Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF88004820CEE, 0xFFFFF88005FC96A8, 0xFFFFF88005FC8F00) Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M Dump file: C:\Windows\Minidump\022010-19359-01.dmp file path: C:\Windows\system32\drivers\dxgmms1.sys product: Microsoft® Windows® Operating System company: Microsoft Corporation description: DirectX Graphics MMS The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit may be another driver on your system which cannot be identified at this time. On Sun 2/21/2010 5:35:12 AM your computer crashed This was likely caused by the following module: dxgmms1.sys Bugcheck code: 0x119 (0x7000000, 0xFFFFFA8005EB1410, 0xFFFFFA8004AF0AF0, 0xFFFFFA80040DF0E0) Error: VIDEO_SCHEDULER_INTERNAL_ERROR Dump file: C:\Windows\Minidump\022010-19624-01.dmp file path: C:\Windows\system32\drivers\dxgmms1.sys product: Microsoft® Windows® Operating System company: Microsoft Corporation description: DirectX Graphics MMS The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit may be another driver on your system which cannot be identified at this time. On Sun 2/21/2010 5:02:04 AM your computer crashed This was likely caused by the following module: rdyboost.sys Bugcheck code: 0x1A (0x1238, 0xFFFFFA8006FA36D0, 0x802, 0x0) Error: MEMORY_MANAGEMENT Dump file: C:\Windows\Minidump\022010-20935-01.dmp file path: C:\Windows\system32\drivers\rdyboost.sys product: Microsoft® Windows® Operating System company: Microsoft Corporation description: ReadyBoost Driver The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit may be another driver on your system which cannot be identified at this time. On Sun 2/21/2010 4:57:25 AM your computer crashed This was likely caused by the following module: dxgmms1.sys Bugcheck code: 0x50 (0xFFFFFFFFFFFFFFFF, 0x0, 0xFFFFF88004F57CEE, 0x0) Error: PAGE_FAULT_IN_NONPAGED_AREA Dump file: C:\Windows\Minidump\022010-18720-01.dmp file path: C:\Windows\system32\drivers\dxgmms1.sys product: Microsoft® Windows® Operating System company: Microsoft Corporation description: DirectX Graphics MMS The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit may be another driver on your system which cannot be identified at this time. -------------------------------------------------------------------------------- Conclusion -------------------------------------------------------------------------------- 41 crash dumps have been found on your computer. Only 40 could be analyzed. Note that it's not always possible to state with certainty whether a reported driver is really 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. Hopelijk kunnen jullie mij helpen en alvast bedankt, Exoit! Bewerkt: 24 februari 2010 door Thundercover Reageren
Exoit Geplaatst: 23 februari 2010 Auteur Rapport Geplaatst: 23 februari 2010 (bewerkt) windows legaal? Oops :$. Nu kunnen jullie me niet helpen toch? Bewerkt: 23 februari 2010 door Exoit Reageren
wesley123 Geplaatst: 23 februari 2010 Rapport Geplaatst: 23 februari 2010 ja, kopp hem maar legaal, dat is de oorzaak en dat had je dnek ik zelf ook wel kunnen bedenken Reageren
Exoit Geplaatst: 23 februari 2010 Auteur Rapport Geplaatst: 23 februari 2010 ja, kopp hem maar legaal, dat is de oorzaak en dat had je dnek ik zelf ook wel kunnen bedenken Is dat serieus de oorzaak? Haha, maar waarom doet het dit niet bij mijn broer dan? He wacht ik kan via een vriend de legale versie verkrijgen voor een tientje omdat zijn pa leraar is, dat ga ik nu METEEN doen! : D Reageren
Albert03 Geplaatst: 23 februari 2010 Rapport Geplaatst: 23 februari 2010 Toen ik BSOD's had (Met Vista legaal) was ik dagen bezig met een oplossing te bedenken, en ik dacht dat het lag aan: Kapot RAM, dus had ik een nieuw paartje RAM van 2GB gekocht. Maar ik had het probleem nog! Terwijl MemTest fouten gaf! Bleek dus dat de RAM-Slots op mijn moederbordje dood waren, nadat ik nieuw moederbordje had aangeschaft werkte het weer! Gebruik eens MemTest: http://hcidesign.com/memtest/download.html Lees de gebruikshandeling door, en laat 'm lopen. Als ie fouten geeft is: * Je RAM dood. * Er zit stof tussen moederbord en RAM * Moederbord dood. Reageren
Exoit Geplaatst: 23 februari 2010 Auteur Rapport Geplaatst: 23 februari 2010 (bewerkt) Toen ik BSOD's had (Met Vista legaal) was ik dagen bezig met een oplossing te bedenken, en ik dacht dat het lag aan: Kapot RAM, dus had ik een nieuw paartje RAM van 2GB gekocht. Maar ik had het probleem nog! Terwijl MemTest fouten gaf! Bleek dus dat de RAM-Slots op mijn moederbordje dood waren, nadat ik nieuw moederbordje had aangeschaft werkte het weer! Gebruik eens MemTest: http://hcidesign.com/memtest/download.html Lees de gebruikshandeling door, en laat 'm lopen. Als ie fouten geeft is: * Je RAM dood. * Er zit stof tussen moederbord en RAM * Moederbord dood. Bedankt voor de tip! Ik ga nu testen en over ongeveer 20 minutjes hoor je weer van me! Er staat namelijk dat je hem mu moet laten lopen voor ongeveer 20 minuten! Ok, of mijn RAM is stuk of mijn moederbord want hij geeft constant dit soort warnings tijdens het testen: Sorry, plaatje was te klein hopelijk nu leesbaar: Bewerkt: 23 februari 2010 door Exoit Reageren
Albert03 Geplaatst: 24 februari 2010 Rapport Geplaatst: 24 februari 2010 Dan zou ik eerst eens als je geen garantie meer hebt, het slot schoonmaken of doorblazen. Dan de test opnieuw doen, en als dat niet werkt het RAM testen op een andere PC, en dan zou het moederbord wel dood zijn. Reageren
Galiorix Geplaatst: 24 februari 2010 Rapport Geplaatst: 24 februari 2010 (bewerkt) * Je RAM dood. * Er zit stof tussen moederbord en RAM * Moederbord dood. Niet helemaal: tegenwoordig zit de memory controller in de processor (tenminste, bij de laatste serie i3, i5 en i7 processors van Intel, bij AMD al veel langer) dus het kan ook zijn dat de memory controller aan boord van je processor gewoon stuk is. Bij oudere Intel platformen zit de memory controller nog op het moederbord. Haal 1 van je geheugen reepjes uit je systeem en ga weer testen. Als je nog steeds errors krijgt wissel je de reepjes om en ga je weer testen. Geeft dat nog steeds errors dan zijn óf alle 2 de modules stuk of er is een ander probleem. Bewerkt: 24 februari 2010 door Galiorix Reageren
Exoit Geplaatst: 27 februari 2010 Auteur Rapport Geplaatst: 27 februari 2010 (bewerkt) Heel erg raar. Ik heb even mijn settings in de BIOS naar de default settings gereset en hij lijkt nu weer te werken, tot nu toe doet hij het nog erg goed! Iedereen hartstikke bedankt voor jullie hulp! Bewerkt: 27 februari 2010 door Exoit Reageren
Emaitroy Geplaatst: 27 februari 2010 Rapport Geplaatst: 27 februari 2010 Maar je hebt toch al een keer nieuw werkgeheugen gehad kan je dat nog 'n keer doen dan? Reageren
Sprunk Geplaatst: 27 februari 2010 Rapport Geplaatst: 27 februari 2010 Ik heb gister ook Windows opnieuw geïnstalleerd want ik had nog steeds de RC. Zoals bekend verloopt de RC maandag. Na het installeren van alle drivers kreeg ik na verloop van tijd ook telkens BSOD's. Mijn computer wilde alleen nog laden in safe mode. Wat blijkt nu, ik had een verkeerde driver geïnstalleerd. Die driver veroorzaakte waarschijnlijk alle BSOD's, want nu ik die driver verwijderd heb en de juiste heb geïnstalleerd krijg ik geen BSOD's meer. Wat ik hiermee wil zeggen is, kijk even of je de juiste drivers voor al je hardware hebt geïnstalleerd. Reageren
Exoit Geplaatst: 27 februari 2010 Auteur Rapport Geplaatst: 27 februari 2010 Ik heb gister ook Windows opnieuw geïnstalleerd want ik had nog steeds de RC. Zoals bekend verloopt de RC maandag. Na het installeren van alle drivers kreeg ik na verloop van tijd ook telkens BSOD's. Mijn computer wilde alleen nog laden in safe mode. Wat blijkt nu, ik had een verkeerde driver geïnstalleerd. Die driver veroorzaakte waarschijnlijk alle BSOD's, want nu ik die driver verwijderd heb en de juiste heb geïnstalleerd krijg ik geen BSOD's meer. Wat ik hiermee wil zeggen is, kijk even of je de juiste drivers voor al je hardware hebt geïnstalleerd. Is goed! Maar wat ik laatst had gelezen op een forum waar ik uit kwam omdat ik de BCcode van mijn BSOD invoerde in google is dat mijn geheugen waardes en dergelijke niet op de standaard instellingen staan waardoor 7 moeilijk gaat doen. Ik heb dus die BIOS gereset en tot nu toe doet hij het nog goed ! Reageren
Exoit Geplaatst: 28 februari 2010 Auteur Rapport Geplaatst: 28 februari 2010 Ik wilde even laten weten dat het probleem volledig is opgelost na het uitblazen van de slots en het resetten van mijn BIOS! Dankjulliewel! Reageren
Galiorix Geplaatst: 28 februari 2010 Rapport Geplaatst: 28 februari 2010 (bewerkt) Ik wilde even laten weten dat het probleem volledig is opgelost na het uitblazen van de slots en het resetten van mijn BIOS! Dankjulliewel! Ga er dus maar vanuit dat het door het resetten van de BIOS opgelost is. Het uitblazen van de slots vind ik zo´n onzin. Heb je ze door met je mond te blazen ze uitgeblazen? Bewerkt: 28 februari 2010 door Galiorix Reageren
Recommended Posts
Een reactie plaatsen
Je kan nu een reactie plaatsen en pas achteraf registreren. Als je al lid bent, log eerst in om met je eigen account een reactie te plaatsen.