Tech Support Forum banner
Status
Not open for further replies.

BSOD file

3K views 28 replies 3 participants last post by  jcgriff2 
#1 ·
#2 ·
My computer recently started NOT shutting down (occasionally) when I shut down. I click the shut down button and it starts logging off - but then a blue DOS looking screen pops up and the computer will re boot with a message saying something like "Windows has recovered from an unexpected shut down."

This happens about 1 in 10 times when I go to shut down. The other 9 out of 10 times it shuts down normal. I posted this in another area and I got a response to run the BSOD scan and post the results here.
 
#3 · (Edited)
Hi. . .

There are no memory dumps in the attached zip file.

Make sure that your system recovery settings are set up to generate a mini kernel memory dump file in the event of a system crash. You'll find the settings under "System" in Control Panel.

Luckily, the Event Viewer log told a different story. It recorded a total of 16 BSODs that occurred between 11 June 2017 and today - 20 July 2017.

Code:
[font=lucida console]The computer has rebooted from a bugcheck.  The bugcheck was: 0x0000007f ([color=red]0x0000000d[/color], 0x00000000, 0x00000000, 0x00000000). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 072017-20326-01.
The computer has rebooted from a bugcheck.  The bugcheck was: 0x0000007f ([color=red]0x0000000d[/color], 0x00000000, 0x00000000, 0x00000000). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 072017-19780-01.
The computer has rebooted from a bugcheck.  The bugcheck was: 0x0000007f ([color=red]0x0000000d[/color], 0x00000000, 0x00000000, 0x00000000). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 071817-23712-01.
The computer has rebooted from a bugcheck.  The bugcheck was: 0x0000007f ([color=red]0x0000000d[/color], 0x00000000, 0x00000000, 0x00000000). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 071617-21060-01.
The computer has rebooted from a bugcheck.  The bugcheck was: 0x0000007f ([color=red]0x0000000d[/color], 0x00000000, 0x00000000, 0x00000000). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 071517-20732-01.
The computer has rebooted from a bugcheck.  The bugcheck was: 0x0000007f ([color=red]0x0000000d[/color], 0x00000000, 0x00000000, 0x00000000). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 071417-24148-01.
The computer has rebooted from a bugcheck.  The bugcheck was: 0x0000007f ([color=red]0x0000000d[/color], 0x00000000, 0x00000000, 0x00000000). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 071417-24492-01.
The computer has rebooted from a bugcheck.  The bugcheck was: 0x0000007f ([color=red]0x0000000d[/color], 0x00000000, 0x00000000, 0x00000000). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 071017-26442-01.
The computer has rebooted from a bugcheck.  The bugcheck was: 0x0000007f ([color=red]0x0000000d[/color], 0x00000000, 0x00000000, 0x00000000). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 070917-22760-01.
The computer has rebooted from a bugcheck.  The bugcheck was: 0x0000007f ([color=red]0x0000000d[/color], 0x00000000, 0x00000000, 0x00000000). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 070317-21356-01.
The computer has rebooted from a bugcheck.  The bugcheck was: 0x0000007f ([color=red]0x0000000d[/color], 0x00000000, 0x00000000, 0x00000000). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 062617-20857-01.
The computer has rebooted from a bugcheck.  The bugcheck was: 0x0000007f ([color=red]0x0000000d[/color], 0x00000000, 0x00000000, 0x00000000). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 062517-22479-01.
The computer has rebooted from a bugcheck.  The bugcheck was: 0x0000007f ([color=red]0x0000000d[/color], 0x00000000, 0x00000000, 0x00000000). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 062517-27752-01.
The computer has rebooted from a bugcheck.  The bugcheck was: 0x0000007f ([color=red]0x0000000d[/color], 0x00000000, 0x00000000, 0x00000000). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 062017-21200-01.
The computer has rebooted from a bugcheck.  The bugcheck was: 0x0000007f ([color=red]0x0000000d[/color], 0x00000000, 0x00000000, 0x00000000). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 061817-21325-01.
The computer has rebooted from a bugcheck.  The bugcheck was: 0x0000007f ([color=red]0x0000000d[/color], 0x00000000, 0x00000000, 0x00000000). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 061117-21262-01.
[/font]
Notice the 1st parameter inside the parenthesis. Every one is 0x0000000d. Per Microsoft, its meaning -
"Windows cannot connect to the printer. Operation could not be completed > (error 0x0000000d)."
Your system files, specifically msinfo32, shows that you have an EPSON XP-640 Series printer installed. It does not matter whether the printer is accessed via wifi or whether you have it directly connected via USB cable. You have Epson software and drivers installed for the printing device.

I checked out the Epson support site and luckily they have new software/drivers for your model printer that was released just about a month ago (June 16, 2017).

Install the updated June 2017 package and see if the BSODs subside.

https://epson.com/Support/Printers/All-In-Ones/XP-Series/Epson-XP-640/s/SPT_C11CF50201

Hopefully this update will quiet the BSOD epidemic as I've never seen BSODs caused by a printer malfunction.

Regards. . .

jcgriff2

`
 
#4 ·
Thank you for your response. The Epson printer is brand new, (maybe a week old). Before that we had a Canon. The problem of the computer rebooting when I try to shut it down has been going on for months. We had the Cannon printer for 2 or 3 years so the problem didn't occur when we first got it, but started to occur a year or more after we got it. We replaced the Canon printer with the Epson printer last week - the problem was there before and is there now.

I'm not 100% sure what you're talking about as far as memory dump is concerned. I know very little about computers. This is what I found in control panel, and this is how I found it.

 
#5 ·
Hi. . .

Your system settings are correct. It's set for a "kernel memory dump" which should produce a full kernel dump (\windows\memory.dmp file) + mini kernel dumps (\windows\minidump folder).

Did you add RAM to the system? Doing so would mean that the page file base allocation size is now < installed physical RAM -- which would cause a no dump situation.

Here is a thread/sticky that should be helpful - http://www.techsupportforum.com/for...mp-files-being-produced-upon-bsod-816378.html

I don't know the reason why you're not producing dump files, but the page file is a good place to start.

Let's go ahead and delete and re-create the page file - https://www.sysnative.com/forums/wi...on-of-page-file-windows-10-8-1-8-7-vista.html

Regards. . .

jcgriff2

`

EDIT: Did you install the new Epson software/drivers?






`
 
#13 ·
I shut my computer down last night and it did the same reboot thing again. When it reboots back to my home screen I get this pop-up:



This computer is about 10 years old, maybe I should just look into getting another one. I hate to give up Windows 7; I like it. I don't know anything about 8 or 8.1. I do know my wife's laptop has Windows 10 on it and it sucks.

I don't know if this "Unexpected Shutdown" issue can be fixed or not.
 
#17 ·
The text output provided:
Code:
[FONT=Lucida Console]AllocatedBaseSize=3006
CurrentUsage=163
Description=C:\pagefile.sys
InstallDate=20170724205854.883200-420
Name=C:\pagefile.sys
PeakUsage=196
Status=
TempPageFile=FALSE[/FONT]
You can see that your page file base allocation size is 3006 MB, which is > than your 3 GB installed RAM.

Installation date (or create date) of the page file was July 24, 2017

The other numbers - Peak Usage = 196 MB -- the most amount of virtual memory used at one time since last re-boot

Current Usage = 163 MB -- self-explanatory

The best thing of all of this. . . We now know that you definitely have a page file!

Let's see if we can speed up your next BSOD by running Driver Verifier.


Please run Driver Verifier - http://www.techsupportforum.com/for...10-8-1-8-7-and-vista-bsod-related-473665.html

Let it run for at least 24 hours in the background. You can use the system while Driver Verifier is running, but you may notice some system slowness as Driver Verifier does utilize heavy system resources. Also, keep in mind that if Driver Verifier flags a 3rd party driver, it will BSOD your system immediately. Be sure to save any work as often as possible.

If Driver Verifier does BSOD your system, get the VERIFIER_ENABLED dump from \windows\minidump. The filenames contain dates, so it should be easy to find. Copy the dump out to Desktop or Documents; zip it up and attach to your next post. Windows WILL NOT allow you to zip the dump while it resides in \windows\minidump.

Regards. . .

jcgriff2

`
 
#22 ·
Hi. . .

Thank you for the files.

Update your M-Audio FireWire driver - M-Audio

That was the cause of the lone BSOD.

Your current driver is from 2009 -

Regards. . .

jcgriff2

`
I spent about 20 minutes trying several different ways to figure out how to update the driver. M-Audio's website doesn't even list the product I have, (M-Audio Fire Wire Solo). It's old - but not THAT old. I bought it new in 2012 or 2013. I ran the trouble shooting thing in Windows Device Manager and it said the driver was the most up to date available. I've never had trouble with it before so I'm not sure why it would suddenly start acting up.

Either way - I just disconnected it and uninstalled all the software. I guess time will tell if that resolved the issue or not.
 
#28 ·
I'm sure a new one would be as grossly overpriced as that one was. But I'm an old fart now. The "Sex, Drugs and Rock n Roll" part of my life is now becoming a distant memory. We've been raising our granddaughter since she was 8 months old, we adopted her when she turned 3, and last month was her 4th birthday. I've gotten rid of all the musical and digital recording gear I had over the years. I can't remember the last time I picked up my guitar. The only reason the M-Audio was still hanging around was because (I assumed) it worked and I was too lazy to crawl under the desk to unhook everything. Getting rid of it is not a loss.

Thanks for all your help. So far I haven't had another BSOD. Granted it's only been a few days and I haven't been on this computer much - but so far so good. Thanks.
 
Status
Not open for further replies.
You have insufficient privileges to reply here.
Top