New
#1
random bsod on new pc
im having problems with bsods. i built a new pc and this is spesifications
i5 2500k at default clock and voltage
gigabyte z77-ds3h
corsair vengeance lp 1600mhz cl9 2x4gb ram
msi 560ti twin frozrII oc edition
sandisk 120gb ultra ssd
seagate barracuda.12 500gb hdd
xilence 600w r3 gaming psu
razer blackwidow keyboard and deathadder 3.5g mouse
i tested my ram sticks for 10 passes with memtest86 with no error
stress my cpu and gpu for hours still nothing
i did scanned my hdds found nothing
switched slots on mb for ram and gpu still nothing changed.
tried driver verifier and diggin google for weeks. read all those threads. tried everything but this, posting mine.
i did a clean install win7 nothing happens.
when i m surfing on net, watching video or playing games i got bsod randomly.there is no spesific programs or hardwares i use on that situations.
also sometimes my pc keeps resetting itself after motherboard logo screen on startup. keeps resetting itself for about 5 or more times and it boots well after that.
there is lots of reports about ntoskrnl.exe and dxmmg1.sys. updated gpu, mb chipset driver, bios, firmwares etc.
i tried whocrashed and this is some reports
and an attachment for screenshot of whocrashed driver view
and there is my minidump files on attachment and skydrive.
http://sdrv.ms/W7weprCode:System Information (local) computer name: SERDAR-PC windows version: Windows 7 Service Pack 1, 6.1, build: 7601 windows dir: C:\Windows CPU: GenuineIntel Intel(R) Core(TM) i5-2500K CPU @ 3.30GHz Intel586, level: 6 4 logical processors, active mask: 15 RAM: 8543879168 total VM: 2147352576, free: 1950195712 Crash Dump Analysis Crash dump directory: C:\Windows\Minidump Crash dumps are enabled on your computer. On Wed 16.01.2013 15:53:39 GMT your computer crashed crash dump file: C:\Windows\Minidump\011613-4009-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0) Bugcheck code: 0xA (0x8, 0x2, 0x1, 0xFFFFF800024E6F93) Error: 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 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 which cannot be identified at this time. On Wed 16.01.2013 15:53:39 GMT your computer crashed crash dump file: C:\Windows\memory.dmp This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0) Bugcheck code: 0xA (0x8, 0x2, 0x1, 0xFFFFF800024E6F93) Error: IRQL_NOT_LESS_OR_EQUAL Bug 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 which cannot be identified at this time. On Tue 15.01.2013 11:22:20 GMT your computer crashed crash dump file: C:\Windows\Minidump\011513-4570-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0) Bugcheck code: 0x4A (0x77A1167A, 0x2, 0x0, 0xFFFFF8800B8B5B60) Error: IRQL_GT_ZERO_AT_SYSTEM_SERVICE 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 thread is returning to user mode from a system call when its IRQL is still above PASSIVE_LEVEL. The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time. On Fri 11.01.2013 17:59:27 GMT your computer crashed crash dump file: C:\Windows\Minidump\011113-4570-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0) Bugcheck code: 0x50 (0xFFFFFFFFFFFFFBA8, 0x0, 0xFFFFF800020FDBEC, 0x0) Error: PAGE_FAULT_IN_NONPAGED_AREA 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 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 which cannot be identified at this time. On Thu 10.01.2013 18:46:18 GMT your computer crashed crash dump file: C:\Windows\Minidump\011013-3931-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0) Bugcheck code: 0x34 (0x50853, 0xFFFFF880027AA178, 0xFFFFF880027A99D0, 0xFFFFF80002126269) Error: CACHE_MANAGER 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 problem occurred in the file system's cache manager. 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 which cannot be identified at this time. On Mon 07.01.2013 03:31:12 GMT your computer crashed crash dump file: C:\Windows\Minidump\010713-3900-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0) Bugcheck code: 0x50 (0xFFFFFFFFFFFFFBA8, 0x0, 0xFFFFF80002100BEC, 0x0) Error: PAGE_FAULT_IN_NONPAGED_AREA 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 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 which cannot be identified at this time. On Sat 05.01.2013 03:06:07 GMT your computer crashed crash dump file: C:\Windows\Minidump\010513-3993-02.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0) Bugcheck code: 0xA (0x0, 0x2, 0x1, 0xFFFFF800020DA288) Error: 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 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 which cannot be identified at this time. On Sat 05.01.2013 02:41:54 GMT your computer crashed crash dump file: C:\Windows\Minidump\010513-3993-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x7F190) Bugcheck code: 0x1E (0x0, 0x0, 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 which cannot be identified at this time. On Fri 04.01.2013 17:33:43 GMT your computer crashed crash dump file: C:\Windows\Minidump\010413-3993-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0) Bugcheck code: 0xA (0x2855444650, 0x2, 0x1, 0xFFFFF800020EAF93) Error: 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 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 which cannot be identified at this time. On Wed 02.01.2013 21:11:21 GMT your computer crashed crash dump file: C:\Windows\Minidump\010213-4586-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0) Bugcheck code: 0x19 (0x20, 0xFFFFFA8006BF93E0, 0xFFFFFA8006BFA100, 0x4D20010) Error: BAD_POOL_HEADER 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 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 which cannot be identified at this time. On Tue 18.12.2012 02:36:58 GMT your computer crashed crash dump file: C:\Windows\Minidump\121812-4602-01.dmp This was probably caused by the following module: dxgmms1.sys (dxgmms1+0x1DBF1) Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF88003BA3BF1, 0xFFFFF88009B13598, 0xFFFFF88009B12DF0) Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M 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 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 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. Conclusion 51 crash dumps have been found and analyzed. Only 15 are included in this report. 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 310.90 , 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.
Last edited by curautvaleas; 20 Jan 2013 at 11:57. Reason: forgot somethin