This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
Hello
I'm having a pickle of a problem and I'm at a loss how to fix it.
Firstly, please see the following:
https://www.dropbox.com/s/hmtf7irjcwig4hr/042915-23275-01.zip?dl=0
This is the dump file attributed to my latest BSOD.
For the benefit of building a picture of what the problem is, I attach a further two dump files from BSOD's experienced yesterday and a few weeks back.
https://www.dropbox.com/s/j4pz7tqg7wfz9w7/040115-23415-01.zip?dl=0
https://www.dropbox.com/s/0ovv2igm7tq9yky/042715-23306-01.zip?dl=0
I experience these BSOD only when using FSX (Flight Simulator X) and not always in particularly 'stressy' types of environment (high density areas of scenery etc). I have searched the internet tirelessly looking for a fix and have undertaken the recommendations I have found including MEMtests, Virus scans (using Windows Security Essentials), System checks via CMD & updated GPU drivers. None of which seem to lead to a problem area.
Bizarrely, these BSOD don't occur every time I use FSX but do seem to rear their ugly head after a prolonged period of computer usage. Is my computer getting tired and rebooting in order to have a rest? A bit tongue in cheek but potentially.
Anyway, I would really appreciate some help from the experts on this issue because I'm at a loss where to go and would love to find a 'cure'.
Many thanks in advance for anyone who can offer some guidance.
Dave Potter
Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.
Dave
Click on the Start button and select Control Panel, Administrative Tools, Services. Locate Windows Event Log in the list. Check that it has started and that the StartUp type is Automatic. If it is not set to Automatic right click and select Properties, General tab. There is a box after StartUp type. The options are available on a drop down by clicking on the arrow down to the right of the box. Make the change and click on Apply and OK. Restart the computer and check whether it has started.
Hi there,
Just trying to provide you the Event Viewer files but when accessing the Event Viewer, I get an error stating that the Event Log Service is unavailable. Verify that the service is running.
I'm going to run the Driver Verifier for a few hours and see how it gets on.
Thanks
Dave
David
Verifier will only force the crash when the misbehaving driver is loaded. It will slow the computer down a tiny bit. I would leave it running and upload any new DMPS. I would also upload your event viewer logs
Please provide us with your Event Viewer administrative logs by following these steps:
Press the Win key + "R" and type eventvwr>enter
Expand Custom Views
Click Administrative Events
Right click Administrative Events
Save all Events in Custom View As...
Save them in a folder where you will remember which folder and save as Errors.evtx
Go to where you saved Errors.evtx
Right click Errors.evtx -> send to -> compressed (zipped) folder
Upload the .zip file to Onedrive or a file sharing service and put a link to it in your next post
*
**If you have updated to win 8.1 and you get the error message "**the system cannot find the file specified" it is a known problem. The work around is to edit the registry. If you are not comfortable doing this DONT. If you are, backup the key before you do
Press Win+"R" and input regedit
Navigate to:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\WINEVT\Channels.Delete "Microsoft-Windows-DxpTaskRingtone/Analytic"
Hi there
Firstly, please accept my sincere thanks for responding.
I have updated the driver as you suggested. It is now displaying a driver for 2009 which according to your notes is correct. For your information, I'm running Windows 7 64bit.
Now, I ran Driver Verifier using the wiki guide. It didn't blue screen on startup (which is a good sign I presume), it didn't blue screen when I ran some tasks but it did make the computer run pretty slowly. What I did manage to do was make the computer restart without prompting. This wasn't a BSOD, it just restarted. Therefore I have no dump file to provide you as it wasn't a Blue Screen.
I was doing some daft things to try and make it crash, loading up multiple intensive programs and I think in truth I just overloaded the computer. Is there anything I can provide you. Should I leave Driver Verifier running?
Alternatively, I can leave it off and on Saturday (the next time I plan to use FSX for a few hours), see if I get a BSOD.
Let me know your thoughts and thanks again for your guidance.
Dave
Dp
First you need to update a driver you have from 2005 called asacpi.sys. A huge cause of BSODS.
Second run driver verifier
The pre 2009 version of this driver is a known BSOD cause.
Please visit Asus tek computer inc. -support- drivers and download p7p55d le
Scroll down to the utilities category, then scroll down to the "atk0110 driver for windowsxp/vista/windows 7 32&64-bit" (it's about the 12th item down).
Download and install it.
Go to c:\windows\system32\drivers to check and make sure that the asacpi.sys file is date stamped from 2009 or 2010 (not before). If you are using Win 8 there is at least a 2012 version which is needed for that. If you cant find it on the ASUS site you can download it using windows update. Read about it here
These crashes were related to memory corruption (probably caused by a driver). Please run these two tests to verify your memory and find which driver is causing the problem. Please run verifier first. You do not need to run memtest yet unless you want to.
If you are over-clocking anything reset to default before running these tests.
In other words STOP!!! If you do not know what this means you probably are not
1-Driver verifier (for complete directions see our wiki here)
**2-Memtest. (**You can read more about running memtest here)
