random bsod on new pc

Page 1 of 2 12 LastLast

  1. Posts : 12
    win7 ultimate x64
       #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/W7wepr
    Code:
    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
      My Computer


  2. Posts : 2,573
    Win7 Ultimate X64
       #2

    The version of the nvidia drivers you are using dec12 are bugged we are seeing lots of errors lately relating to that specific driver there is a new version dated jan13 or rollback and try older version
      My Computer


  3. Posts : 12
    win7 ultimate x64
    Thread Starter
       #3

    im having this problem for 4 months i tried 5 drivers from newest to older ones. nothing happens.
      My Computer


  4. Posts : 1
    Windows Vista 64-bit (Ultimate) & Windows 7 64-bit (Ultimate)
       #4

    curautvaleas said:
    msi 560ti twin frozrII oc edition
    This caught my eye, try the 301.24 beta driver.
      My Computer


  5. Posts : 12
    win7 ultimate x64
    Thread Starter
       #5

    got fresh bsod after that old beta driver of nvidia. this time it says nvlddkm.sys
      My Computer


  6. Posts : 2,573
    Win7 Ultimate X64
       #6

    Have you been cleaning drivers after uninstalling current before installing next
    Drivers - Clean Left over Files after Uninstalling
      My Computer


  7. Posts : 12
    win7 ultimate x64
    Thread Starter
       #7

    i did it with driver sweeper and clean install.
      My Computer


  8. Posts : 2,573
    Win7 Ultimate X64
       #8

    Please run the MGADiag tool so we can have a look at your windows install
    Windows Genuine and Activation Issue Posting Instructions
      My Computer


  9. Posts : 12
    win7 ultimate x64
    Thread Starter
       #9

    Code:
    Diagnostic Report (1.9.0027.0):
    -----------------------------------------
    Windows Validation Data-->
    
    Validation Code: 0
    Cached Online Validation Code: N/A, hr = 0xc004f012
    Windows Product Key: *****-*****-Q6MMK-KYK6X-VKM6G
    Windows Product Key Hash: 289NoAWl2ZoVfuieux/315WkDIc=
    Windows Product ID: 00426-OEM-8992662-00173
    Windows Product ID Type: 2
    Windows License Type: OEM SLP
    Windows OS version: 6.1.7601.2.00010100.1.0.001
    ID: {388099CC-E18E-4CE9-9B31-738C5A2B2B71}(1)
    Is Admin: Yes
    TestCab: 0x0
    LegitcheckControl ActiveX: N/A, hr = 0x80070002
    Signed By: N/A, hr = 0x80070002
    Product Name: Windows 7 Ultimate
    Architecture: 0x00000009
    Build lab: 7601.win7sp1_gdr.120503-2030
    TTS Error: 
    Validation Diagnostic: 
    Resolution Status: N/A
    
    Vista WgaER Data-->
    ThreatID(s): N/A, hr = 0x80070002
    Version: N/A, hr = 0x80070002
    
    Windows XP Notifications Data-->
    Cached Result: N/A, hr = 0x80070002
    File Exists: No
    Version: N/A, hr = 0x80070002
    WgaTray.exe Signed By: N/A, hr = 0x80070002
    WgaLogon.dll Signed By: N/A, hr = 0x80070002
    
    OGA Notifications Data-->
    Cached Result: N/A, hr = 0x80070002
    Version: N/A, hr = 0x80070002
    OGAExec.exe Signed By: N/A, hr = 0x80070002
    OGAAddin.dll Signed By: N/A, hr = 0x80070002
    
    OGA Data-->
    Office Status: 109 N/A
    OGA Version: N/A, 0x80070002
    Signed By: N/A, hr = 0x80070002
    Office Diagnostics: 025D1FF3-364-80041010_025D1FF3-229-80041010_025D1FF3-230-1_025D1FF3-517-80040154_025D1FF3-237-80040154_025D1FF3-238-2_025D1FF3-244-80070002_025D1FF3-258-3
    
    Browser Data-->
    Proxy settings: N/A
    User Agent: Mozilla/4.0 (compatible; MSIE 8.0; Win32)
    Default Browser: C:\Program Files (x86)\Opera\Opera.exe
    Download signed ActiveX controls: Prompt
    Download unsigned ActiveX controls: Disabled
    Run ActiveX controls and plug-ins: Allowed
    Initialize and script ActiveX controls not marked as safe: Disabled
    Allow scripting of Internet Explorer Webbrowser control: Disabled
    Active scripting: Allowed
    Script ActiveX controls marked as safe for scripting: Allowed
    
    File Scan Data-->
    File Mismatch: C:\Windows\system32\wat\watadminsvc.exe[Hr = 0x80070003]
    File Mismatch: C:\Windows\system32\wat\npwatweb.dll[Hr = 0x80070003]
    File Mismatch: C:\Windows\system32\wat\watux.exe[Hr = 0x80070003]
    File Mismatch: C:\Windows\system32\wat\watweb.dll[Hr = 0x80070003]
    
    Other data-->
    Office Details: <GenuineResults><MachineData><UGUID>{388099CC-E18E-4CE9-9B31-738C5A2B2B71}</UGUID><Version>1.9.0027.0</Version><OS>6.1.7601.2.00010100.1.0.001</OS><Architecture>x64</Architecture><PKey>*****-*****-*****-*****-VKM6G</PKey><PID>00426-OEM-8992662-00173</PID><PIDType>2</PIDType><SID>S-1-5-21-2303262315-474085245-3065740533</SID><SYSTEM><Manufacturer>Gigabyte Technology Co., Ltd.</Manufacturer><Model>To be filled by O.E.M.</Model></SYSTEM><BIOS><Manufacturer>American Megatrends Inc.</Manufacturer><Version>F9</Version><SMBIOSVersion major="2" minor="7"/><Date>20120919000000.000000+000</Date></BIOS><HWID>C7B43A07018400FE</HWID><UserLCID>041F</UserLCID><SystemLCID>0409</SystemLCID><TimeZone>GTB Standard Time(GMT+02:00)</TimeZone><iJoin>0</iJoin><SBID><stat>3</stat><msppid></msppid><name></name><model></model></SBID><OEM><OEMID>_ASUS_</OEMID><OEMTableID>Notebook</OEMTableID></OEM><GANotification/></MachineData><Software><Office><Result>109</Result><Products/><Applications/></Office></Software></GenuineResults>  
    
    Spsys.log Content: 0x80070002
    
    Licensing Data-->
    Software licensing service version: 6.1.7601.17514
    
    Name: Windows(R) 7, Ultimate edition
    Description: Windows Operating System - Windows(R) 7, OEM_SLP channel
    Activation ID: 7cfd4696-69a9-4af7-af36-ff3d12b6b6c8
    Application ID: 55c92734-d682-4d71-983e-d6ec3f16059f
    Extended PID: 00426-00178-926-600173-02-1055-7601.0000-3112012
    Installation ID: 006240334400486935610381736614746332390306189133726506
    Processor Certificate URL: http://go.microsoft.com/fwlink/?LinkID=88338
    Machine Certificate URL: http://go.microsoft.com/fwlink/?LinkID=88339
    Use License URL: http://go.microsoft.com/fwlink/?LinkID=88341
    Product Key Certificate URL: http://go.microsoft.com/fwlink/?LinkID=88340
    Partial Product Key: VKM6G
    License Status: Licensed
    Remaining Windows rearm count: 3
    Trusted time: 20.01.2013 18:54:58
    
    Windows Activation Technologies-->
    HrOffline: 0x00000000
    HrOnline: N/A
    HealthStatus: 0x0000000000000000
    Event Time Stamp: N/A
    ActiveX: Not Registered - 0x80040154
    Admin Service: Not Registered - 0x80040154
    HealthStatus Bitmask Output:
    
    
    HWID Data-->
    HWID Hash Current: LAAAAAEAAQABAAEAAAACAAAAAQABAAEAln36jyBXcu5UJQJ9kLT0AeoHLnM=
    
    OEM Activation 1.0 Data-->
    N/A
    
    OEM Activation 2.0 Data-->
    BIOS valid for OA 2.0: yes
    Windows marker version: 0x20001
    OEMID and OEMTableID Consistent: yes
    BIOS Information: 
      ACPI Table Name	OEMID Value	OEMTableID Value
      APIC			ALASKA		A M I
      FACP			ALASKA		A M I
      HPET			ALASKA		A M I
      MCFG					
      SSDT			SataRe		SataTabl
      SSDT			SataRe		SataTabl
      SSDT			SataRe		SataTabl
      SLIC			_ASUS_		Notebook
      My Computer


  10. Posts : 12
    win7 ultimate x64
    Thread Starter
       #10

    LogisticsXLS said:
    curautvaleas said:
    msi 560ti twin frozrII oc edition
    This caught my eye, try the 301.24 beta driver.
    now i m using this driver for 3 days and i see artifacts in games which i never saw before.
      My Computer


 
Page 1 of 2 12 LastLast

  Related Discussions
Our Sites
Site Links
About Us
Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 02:08.
Find Us