Programs for reading dump files, changing settings

C

Currency

New Member
I thought I had fixed my BSOD woes but have recently started getting them again. However, using either bluescreenview, and whocrashed I've noticed in recent months my system has not been saving the dump files, therefore the only information I have is that I see from the BSOD.

Perhaps I've messed up a setting somewhere under the advanced system settings tab?

I currently have it set to, small memory dump. According to my logs, I've not had any blue screens since 06/19/2013 but had another today related to, atikmpag.sys

The bsod was page fault in none paged area, 0x50

Video Driver: 12.104.0.0

Catalyst Version: 13.4

Video card is Sapphire 7870 XT

Thanks for any and all help, should also mention I have run memtest on each stick of memory for hours without any errors. 4x4GB
 
Last edited:
If the bluescreens still point to the ati driver then make sure its updated or you can always try an older driver. Also, what make and model of power supply are you using? Have you tried the card in a different computer? It could be a bad video card slot or just a bad card. You can use windows debugging tools to decipher bluescreens.

http://msdn.microsoft.com/en-us/windows/hardware/gg463009.aspx

And as far as you not having any files in your minidump folder, its possible that you are running a file cleaner such as Ccleaner that will empty the minidump folder.

If you can zip up your dump files when you see them, then attach them to your reply then I decipher what the bluescreens are.
 
http://www.newegg.com/Product/Product.aspx?Item=N82E16817371044
Antec Earthworks, 650 watt, 80 plus Bronze certified. Mine is exactly the same, just gray, not green.

Don't really have another system to test the card in, unless I toss my old motherboard, CPU, memory, with HDD, into a tower. I don't have a test bench, but should soon. My motherboard has three PCI-E slots, but only the first one running at X16.

http://www.gigabyte.us/products/product-page.aspx?pid=4168#sp

I had five old dump files I deleted, last one was dated over 10 weeks ago, for some reason it was not saving new ones or overwriting old ones. Not using any cleaning programs, use MS SE for firewall and scanning for viruses. Had really bad BSOD's from Norton 360, something I read about a recent windows update causing issues with most AV programs.

I sometimes get blue screens on startup, but every now and again I'll get one after my PC's been running for several hours. I never get any blue screens while gaming. However, if I stress my system with AIDA64, my display driver crashes every time preventing any tests at all. :(
 
If your system has a fatal error, it might not be able to do a screen dump. The settings for the type of dump are in the system property's control (hold windows key and press break/pause key) under the advanced/ system startup tabs. if it's your video card, you might be able to adjust the resources for the card in your cmos, I have had some success changing IRQ. Also check in the hardware device manager for any conflicts.
 
I've always seen the blue screen, made a mental note of why it happened and/or what caused it. I've watched the memory dump percentage until it completed, then pressed restart.

Event viewer shows the following bugchecks, and only three instances where my display driver stopped responding but was recovered.

Log Name: System
Date: 6/18/2013 1:14:19 AM
Description:
The computer has rebooted from a bugcheck. The bugcheck was: 0x0000001e (0xffffffffc0000005, 0xfffff880015ee66d, 0x0000000000000001, 0x000000000000ff8b). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 061813-13291-01.

Log Name: System
Date: 5/28/2013 12:11:17 AM
Description:
The computer has rebooted from a bugcheck. The bugcheck was: 0x00000050 (0xfffffa980784180b, 0x0000000000000000, 0xfffff80002e6e8c5, 0x0000000000000005). A dump was saved in: C:\Windows\MEMORY.DMP.

I'll shorten them up for the next ones.

05/26/2016 11:46:58PM 0x050 Dump was not saved, another error with same time stamp reads. "Unable to produce a minidump file from the full dump file."

The same thing repeats, yet I only have two that state a dump couldn't be saved, Event ID: 1005
 
http://support.microsoft.com/kb/275678 is a article from microsoft about the problem, sounds like a video driver issue. Try uninstalling the video driver and boot with default generic driver. If that works, try a older driver for your card. I have seen some systems that don't work with all video cards. Also have you checked the device manager for conflicts?
 
I've booted into safemode, removed the ATI drivers, restarted with default VGA drivers, installed fresh drivers, and so far everything is fine. I attempted to reply the other night but had major issues, three BSOD's, all different, and still no logs at all. Also had issues with one of those locking SATA cables which some how became loose on my SSD boot drive, easy fix but was annoying. Thought my refurbished SSD crapped out on me. Plans to upgrade it after I get a modular PSU.

I've removed all old logs, but still have event viewer details on them. I should mention I had the CPU running @ 4Ghz for a few days, but put it back to stock clocks, GPU has never been overclocked.

I'll update once I get a mini dump to share. Hopefully soon.
 
Last edited:
Had another BSOD a few minute ago and still no dump files. I've adjusted page files to system managed, although it says a dump may not be created since the size of the page file is either disabled or under 800MB's. Not sure, have to restart to save the settings. Will update with more information as it becomes available.

Edit: Further details,

Windows might not be able to record details that could help identify system errors because your current paging file is disabled or less than 800 megabytes. Click ok to return to the virtual memory settings window, enable paging file, and set the size to a value over 800 megabytes, or click cancel to change memory dump selection.

Performance options show.

Virtual memory; Total paging file size for all drives: 49033MB's. Changed setting to automatically manage paging file size for all drives instead of system managed size's. Error message appears to go away.

Current hard drives are as follows,
OS Boot SSD 120GB, 111GB W/37.8GB free
Primary Storage 2TB, 1.81TB W/1.56TB's free
Primary Backup 2TB, 1.81TB W/1.63TB's free

Not sure why system managed size's would be under 800MB's when it showed around 49GB's on the decimal system, not good with math so I can't tell you what 49,033MB's is in binary.
 
Last edited:
I'm still having issues with the system not writing dump files, I've done every single suggestion I have found online, including registry edits, changing settings, switching folders and so on.

I'm going to do a complete fresh install of 7 64bit and go from there, with all fresh drivers and so on. Annoyed with the issue, I just continue getting new, never before seen BSOD's.
 
Thank you John. I'm going to go through my entire driver list and attempt to get updates on everything. I'm on the fresh install of Windows, installed two drivers, Intel Lan and the video drivers.

Before I even restarted to, allow those changes to take affect, 0x50 page fault in none paged area, and no dump file. Are there any programs out that will list all the drivers on the system and what they are needed for?

I know who crashed shows a list, mine shows I have only 10 none Microsoft drivers installed, 110 are Microsoft drivers. I'm assuming some maybe default drivers which should be updated?
 
Last edited:
The only drivers that may need updates is the following.

Chipset
Audio
Video
Network/Lan
Wireless if applicable
USB 3.0
Card Readers

Microsoft provides generic drivers for cd/dvd drives and other hardware.
 
Updated all of those drivers from AMD's and gigabyte's websites. Everything has been fine for a few days, and tonight I return home to no working sound what so ever. Will create another thread regarding that before contacting gigabyte and requesting an RMA.

I have no dump files, and had three BS's tonight, 0x50, oxd1, and oxC something while attempting to combat the none working sound problem. Sigh! Sounds working again, and have this now but no minidump file.

On Sat 9/14/2013 7:41:03 AM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: Unknown (0x00000000)
Bugcheck code: 0x3B (0xC0000005, 0x0, 0xFFFFF880078C9EE0, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
A third party driver was identified as the probable root cause of this system error.
Google query: SYSTEM_SERVICE_EXCEPTION
 
Last edited:
Do me a favor, zip up that file and attach it to your next reply. I wanna see something.

C:\Windows\memory.dmp
 
johnb35 said:
Do me a favor, zip up that file and attach it to your next reply. I wanna see something.

C:\Windows\memory.dmp
Click to expand...

I cannot seem to get the dmp file small enough to attach it here, 19% compression ratio its still around 260MB's, there was no mini dump associated with the crash, just the full memory dump file. I will keep trying.

Missing security token, failed three times. :(
 
Last edited:
Well you won't be able to attach a file that big anyway. See if you can install debugging tools for windows and open that file and see it says what is wrong.
 
Alright, will look into that. I'm happy though I'm getting dump files again on crashes.

On Sun 9/15/2013 1:59:22 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\091513-12339-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75B80)
Bugcheck code: 0x50 (0xFFFFFA830A371E98, 0x0, 0xFFFFF800030996EB, 0x5)
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 that cannot be identified at this time.



That one happened after firefox stopped responding, I attempted to close it and boom. 0x50 page fault. This system is the first time I've ever seen that error before.
 
Zip up this file and attach it to your next post.

C:\Windows\Minidump\091513-12339-01.dmp
 
It said mainly memory corruption but also had issue with firefox. Have you ran memtest yet? If not, I would definitely do so now.
 
You must log in or register to reply here.
Back
Top