Occasional BSOD during shutdown

[jeff032]

Occasionally my computer will BSOD during shutdown. Before the BSOD, it will stay on the shutting down screen for a couple of minutes. This time I didn't even see the BSOD - after staying on the shutting down screen, the screen went blank and eventually I just did a hard shut down. When I logged in, I received a dialog stating that the computer had BSOD'd.

zip file is attached

-Windows 7 Professional SP1 x64
-Not the original OS, from MSDNAA
-Age of system varies: graphics card - 2 months, CPU/motherboard/RAM - 6 months, power supply - 1 year, hard drives/network adapter/cdrom drive - 5 years
-Age of OS installation - less than 2 months, I had the issue on a previous installation of the same OS as well

 

[JaidynM]

It looks like you have some corrupt memory.

You should test your RAM using Memtest86+. Let it run until 6-8 passes have completed or errors have been found.
RAM - Test with Memtest86+

However, you should being by filling out your system specs.
http://www.sevenforums.com/tutorials/180324-system-info-see-your-system-specs.html

 

[jeff032]

After posting yesterday, I noticed my RAM timing was set to 9-9-9-28, while my RAM supports 8-8-8-24. I changed it to 8-8-8-24 and ran Memtest86+. So that's already finished 8 passes and it found no errors.

I think that this issue existed before I got the new RAM, but I'm not sure.

I also filled out some of my system specs.

Any other thoughts? Thanks.

 

[zigzag3143]

After posting yesterday, I noticed my RAM timing was set to 9-9-9-28, while my RAM supports 8-8-8-24. I changed it to 8-8-8-24 and ran Memtest86+. So that's already finished 8 passes and it found no errors.

I think that this issue existed before I got the new RAM, but I'm not sure.

I also filled out some of my system specs.

Any other thoughts? Thanks.

Be sure to do what JaidynM suggests first!

Just in passing. Make sure you arent overclocking/undervolting anything. Return everything to default.

 

[jeff032]

@zigzag3143
Are you suggesting that I revert the timings back to 9-9-9-28 and run memtest again? I would think that if memtest passed with 8-8-8-24, it would pass with 9-9-9-28, but I could run it again. Everything else is set to automatic.

@JaidynM
Why do you say that it looks like a memory corruption issue? Wouldn't that cause issues at times other than shutdown as well?

 

[zigzag3143]

It is much easier to find patterns, etc, when there are more than one crash.

We prefer you wait until you have at least two so that if one is corrupt the other probably wont be.



Yours is related to memory corruption but till we have more info we probably cant tell you why.



Anything that isnt the way it was before you started crashing should be changed back

 

[JaidynM]

@JaidynM
Why do you say that it looks like a memory corruption issue? Wouldn't that cause issues at times other than shutdown as well?

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000009F, {4, 258, fffffa800c40cb60, fffff80000b9c3d0}

*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : [B]memory_corruption[/B]

Followup: memory_corruption
---------

That's what your dump file tells us.