R ransh New member Local time 7:55 PM Messages 1 Jun 28, 2015 #1 Hello, Can anyone help with the attached crash dump in windows 7 64-bit ? Thank you, Ran My Computer My Computer Computer typePC/DesktopOSwindows 7
GokAy New member Guru Gold Member VIP Local time 3:55 AM Messages 5,653 Location Maltepe - Istanbul Jun 28, 2015 #2 Follow http://www.sevenforums.com/bsod-help-support/96879-blue-screen-death-bsod-posting-instructions.html Make sure the zip file includes the dmp file/s. If not, configure a small memory dump - http://www.sevenforums.com/tutorials/174459-dump-files-configure-windows-create-bsod.html and wait/trigger another BSOD. then re-run the "Dm log collector" and attach the new report. Note: I tried to load the dmp file with WinDBG but got: Either you specified an unqualified symbol, or your debugger *** *** doesn't have full symbol information. Click to expand... Probably caused by : ntkrnlmp.exe ( nt!KiKernelCalloutExceptionHandler+e ) Click to expand... My Computer My Computer Computer typePC/DesktopComputer Manufacturer/Model NumberCustom BuildOSWindows 7 Ultimate x64 SP1CPUAMD Phenom 2 1090TMotherboardGigabyte GA-890FXA-UD5Memory2x8GB Kingston HyperX Fury Black 1600Mhz UngangedGraphics Card(s)MSI GTX 970 Gaming 4GSound CardRealtek On-Board HD 7.1 Audio / Logitech G35Monitor(s) Displays3xAcer GD245HQScreen Resolution1920x1080Hard DrivesSamsung 850 Pro 512GB SSD - OS / WD Caviar Black SATA 3 - 1 TBx2 - Dynamic RAID 0 / WD Caviar Green SATA 2 - 640GBx2 - Dynamic RAID 0 / WD Caviar Green SATA 2 - 640GB - Internal Backup / Seagate Barracude SATA 3 - 3TB - External Backup/ SyncPSUHighPower 1000WCaseCooler Master HAF 932CoolingNoctua NH-D14KeyboardLogitech G19MouseLogitech G500Internet Speed100/4 Mbit Cable (100GB quota)AntivirusZoneAlarm Extreme Security / MBAM Pro / MBAE Free / SAS FreeBrowserIE 11 - Firefox - ChromeOther InfoLogitech F710/ G27/ G940/ Z5500 // TrackIR 5 // Nvidia 3D Surround Vision
Follow http://www.sevenforums.com/bsod-help-support/96879-blue-screen-death-bsod-posting-instructions.html Make sure the zip file includes the dmp file/s. If not, configure a small memory dump - http://www.sevenforums.com/tutorials/174459-dump-files-configure-windows-create-bsod.html and wait/trigger another BSOD. then re-run the "Dm log collector" and attach the new report. Note: I tried to load the dmp file with WinDBG but got: Either you specified an unqualified symbol, or your debugger *** *** doesn't have full symbol information. Click to expand... Probably caused by : ntkrnlmp.exe ( nt!KiKernelCalloutExceptionHandler+e ) Click to expand...