Crash Dump Driver Error
Windows 7: Event 45: The system could not sucessfully load the crash dump driver
Windows Crash Dump Analysis: Help From The Experts Driver errors can cause Windows to crash or hang. Fortunately, there are multiple ways OSR can help you.
Jan 13, 2014 Advanced Windows debugging and troubleshooting. In CLR languages, errors are modeled as exceptions and are represented as class objects derived from.
You ll have to have some working knowledge Device Manager Control Panel navigation and useage. If you re getting some error messages like: There are no active.
Why Crash. The Linux operating system originally lacked a built-in, traditional UNIX-like kernel crash dump facility. This was initially addressed by the Mission.
Microsoft is conducting an online survey to understand your opinion of the Technet Web site. If you choose to participate, the online survey will be presented to you when you leave the Technet Web site.
Would you like to participate.
The system could not sucessfully load the crash dump driver. Event ID 45
At the end of 2007 we talked about Bugchecks and why they happen. Today we re going to talk about the Crash Dump files themselves - the different types of dumps, how.
I tried those steps before but they did not help.
Even though I don t think posting the whole events would help, I have posted them probably I overlooked something. I dumped the events in csv so you can view them in excel.
Please let me know when you download the file
No problem. Could you fill in your system specs and let us know if you have a raid setup too while I ask for help.
I put in a call for help, will post when I here something.
System Manufacturer/Model Number Dude Build
CPU Intel R Core TM i5-3570K CPU OC 4.5GHZ Turbo
Motherboard MSI Z77A-G45 Gaming
Graphics Card MSI GTX 970 Gaming 4G
Sound Card Realtek High Definition
Monitor s Displays Dell S23O9W, HP L1710
Screen Resolution DELL-1920 x 1080 HP-1280 x1024
Hard Drives Crucial m4 256 SSD, WD 7200RPM 500GB X2
Internet Speed 50 down and 5 up
Other Info Logitech X-620 Speakers
System Manufacturer/Model Number Self Assembled
OS Microsoft Windows 10 Pro Insider Preview 64-bit
CPU Intel R Core TM i3-4130 CPU 3.40GHz
Motherboard Gigabyte Technology Co., Ltd. B85M-D3H
Memory Corsair Vengence 4GB x2 8.00GB Dual-Channel DDR3 798MHz
Graphics Card 2047MB GeForce GTS 450 ZOTAC International
Sound Card Onboard Realtek High Definition Audio
Monitor s Displays LG Flatron E2040T
Cooling Cooler Master Seidon 120V Plus
Hard Drives Western Digital 1 TB
Antivirus Windows Defender MBAM
Other Info Dell Studio 15 Laptop
Source: Microsoft-Windows-WER-SystemErrorReporting
The computer has rebooted from a bugcheck. The bugcheck was: 0x0000009f 0x0000000000000003, 0xfffffa8003d7a060, 0xfffff80000b9c3d8, 0xfffffa801100d160. A dump was saved in: C: Minidump 040613-17784-01.dmp. Report Id: 040613-17784-01.
So there is a BSOD for sure. And that is Hibernation/sleep related.
Follow it: Dump Files - Configure Windows to Create on BSOD
Go to Option Two, Point 2. Download the. reg file and merge it in registry by double clicking it.
Now put the computer in sleep and wait for another BSOD. When it occurred, search the. dmp files manually in the default path: C: Windows Minidump or SystemRoot Minidump. See if the crash dump is recorded or not hopefully it will be recorded. Post it following the Blue Screen of Death BSOD Posting Instructions.
Arc, this BSOD is pretty old as you can see from the date and it was caused by the hamachi drivers. I have had hamachi since 2011 and I have never had this problem but anyway I uninstalled it after that BSOD but the problem still exists and yea I deleted the dump file after debugging it otherwise you would have found it in the files I sent.
That was the last error event as per your event log.
And you already removed the zip so that I cannot have another look.
Edit: A 9F BSOD does not cause by Hamachi driver. It is a power state failure of a PnP device driver, either USB or PCI/PCIe.
System Manufacturer/Model Number Home made Desktop
CPU Intel i7-4820-E 4.625/vcore 1.3Vcore bios
Motherboard ASUS X79 Sabertooth
Memory G.SKILL Trident X Series-2400/16 Gb/I don t recommend G.Skil
Monitor s Displays Asus 27 LED LCD/VE278Q
Screen Resolution 1920-1080 or 1280-720 HDMI
Case Phanteks Enthoo Primo/4 case 140 fans
Cooling XSPC 360/240 Dual pump water cooling/2 radiators 10 fans p/p
Hard Drives INTEL SSD 530-250 Gb Sata 3.0/
Samsung 500 GB SSD external for backups.
Antivirus Microsoft Security Essentials/ Malwarebytes Premium
Browser I.E. 11 default/Firefox/ ISP Windstream
StarTech 5 1/4 ssd/hard drive sata hot swap bay.
StarTech 5 1/4 dual SSD hot swap
For posterity s sake I think I figured out what the problem is, it is one of many problems caused By Daemon tools. Apparently it happens when daemon tools is installed, for what ever reason it messes with hibernation and some how causes this error.
Heres a link to the information: Event ID: 45 Source: Ftdisk
Then i went hunting through the copy of the files uploaded, specifically the list of drivers and low and behold Daemon tools is installed.
System Manufacturer/Model Number Lenovo ThinkCenter, Custom Built PC, Acer Aspire V3-771G-9809
OS Windows 7 enterprise 64 bit, Windows 7 Pro 64 bit, Windows 8 64bit
CPU Core i5-2400, Athlon 64 X2 6400 , Core i7-3632QM
Memory 4GB, 4gb g.skill ddr2, 8gb
Graphics Card Radeon HD 4550 sgb, Radeon HD 4870, NVIDIA Geforce GT 650m
Monitor s Displays dual samsung 22 monitors
Case Antec Twelve Hundred V3 Black Steel ATX Full Tower
Cooling ASUS Silent Square Pro
Hard Drives 500GB, Western Digital WD Blue WD6400AAKS 640GB 7200 RPM 16MB Cache SATA 3.0Gb/s, 1TB
Displays information about blue screen crashes occured on your system. MiniDump Reader.
Intro: How to Analyze a BSOD Crash Dump. Blue screens of death can be caused by a multitude of factors. There are many tools on the internet that can analyze these.
Occasionally, my Windows XP SP2 laptop has had the Blue Screen of Death appear unexpectedly. It doesn t occur when any particular application is running, a.
Today I have to face a weird behavior in my laptop since a few of days ago. It only happens that when the computer goes to sleep, that is, stand-by, either by my.