BSOD After sleep

[Baloeb]

I have an emachines with a AMD 5450 video card that I've been having a couple problems with. It will go to sleep fine, but when you wake it up it goes to the blue screen and reboots. I've attached my zip file. Also, it will randomly shut down without warning sometimes. I don't know if it is a related problem, but it makes it hard to use as a media center. When it happens there isn't a warning, or blue screen. It's just off all of a sudden. Thank you for your help.

 

[koolkat77]

Welcome to SevenForums.

Sounds like your GPU is overheating. Download and install GPU z and post a screenshot from sensors tab.

For monitoring the heat/celsius of the system, use Speccy or HWMonitor:

• GPU-Z Video card GPU Information Utility
• Speccy System Information
• HWMonitor
• How to Upload and Post a Screenshot and File in Seven Forums

Here are some steps you should follow for troubleshooting a video card:

• How to troubleshoot video card problems

BTW: are you having two video cards installed?

Start Menu\Programs\AMD VISION Engine Control Center	Public:Start Menu\Programs\AMD VISION Engine Control Center	Public

Name	ATI Radeon HD 5450

I see ATI drivers as well as NVIDIA drivers installed. If you have an ATI video card you do not need to install NVIDIA drivers.

Driver	c:\windows\system32\drivers\atikmpag.sys (8.14.1.6290, 540.00 KB (552,960 bytes), 12/19/2012 11:32 AM)

Please remove these from control panel.

Start Menu\Programs\NVIDIA Corporation	Public:Start Menu\Programs\NVIDIA Corporation	Public
Start Menu\Programs\NVIDIA Corporation\NVIDIA Control Panel	Public:Start Menu\Programs\NVIDIA Corporation\NVIDIA Control Panel	Public

Perform a System File Check to check the integrity of all protected Windows 7 :

1. Click on the start rb:
2. Type CMD on Search
3. Left click and Run as Administrator
4. Type

   SFC /scannow

Full tutorial here:

• SFC /Scannow Command - System File Checker

Disk Check on your hard drive for file system errors and bad sectors on it.

• How to run Disk Check on Windows 7

Reduce items at start-up. Nothing except anti-virus is required plus improves the time for logging in windows.

• http://www.sevenforums.com/tutorials/1401-startup-programs-change.html
• http://www.sevenforums.com/tutorial...ation-conflicts-performing-clean-startup.html

Additional hardware check:

Take memtest. Run for 8 passes and test each stick in a know good slot for an additional 6 passes.

• http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html

   Note

Pay close attention to part 3 of the tutorial in order to rule out the faulty stick.

   Information

Errors are sometimes found after 8 passes.

   Tip

Do this test overnight, before going to bed.

If Memtest86+ does not find any errors with ram run Windows Memory Diagnostics for 7-8 passes following its tutorial:

• http://www.sevenforums.com/tutorials/715-memory-diagnostics-tool.html

Upload a screenshot of your hard disk using CrystalDiskInfo:

• CrystalDiskInfo Standard Edition
• How to Upload and Post a Screenshot and File in Seven Forums

Make a hard drive test from the hard drive manufacturers website:

• Hard Drive Diagnostic Procedure

Let us know the results.

 

[Baloeb]

Thanks for your help! I have suspected that gpu temp were causing the random shutdowns, but I didn't know how to test. It seems like temps would not cause the BSOD on sleep, though. I don't have 2 video cards, only the AMD. My computer uses nvidia ethernet and sata controllers, etc. Here are the results of the gpu z and speccy. This was taken not long after I turned on the computer. I'm running all the hardware tests now.

 

[Britton30]

I do see nVIDIA display service in the log, which isn't part of the chipset drivers. Use the Driver Sweeper link below my sig and remove any nVIDIA display drivers listed.

The sensor log is too convoluted to read positively but I don't think there are temps too hot, but could be wrong.
You could post snip of the GPUz sensor window.

 

[Baloeb]

OK, I've uninstalled the extra vido drivers and ran some hardware tests, which came back clean. I put it in sleep mode again, and this time it actually turned back on and looked like it was actually going to work for a few seconds before I got the BSOD. I put it in safe mode and got new logs, which I've attached here. Thanks for everyone's help!

 

[koolkat77]

Can you upload a snip from gpuz?

 

[koolkat77]

Can you explain what hardware test you ran?

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

Use !analyze -v to get detailed debugging information.

BugCheck 1A, {41790, fffffa8000dc87e0, ffff, 0}

Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+35084 )

Followup: MachineOwner
---------

kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

MEMORY_MANAGEMENT (1a)
    # Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 0000000000041790, A page table page has been corrupted. On a 64 bit OS, parameter 2
	contains the address of the PFN for the corrupted page table page.
	On a 32 bit OS, parameter 2 contains a pointer to the number of used
	PTEs, and parameter 3 contains the number of used PTEs.
Arg2: fffffa8000dc87e0
Arg3: 000000000000ffff
Arg4: 0000000000000000

Debugging Details:
------------------


BUGCHECK_STR:  0x1a_41790

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

PROCESS_NAME:  WerFault.exe

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from fffff80002ee8e10 to fffff80002e77c40

STACK_TEXT:  
fffff880`07aa4828 fffff800`02ee8e10 : 00000000`0000001a 00000000`00041790 fffffa80`00dc87e0 00000000`0000ffff : nt!KeBugCheckEx
fffff880`07aa4830 fffff800`02eaa8e9 : 00000000`00000000 00000000`735cffff fffffa80`00000000 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x35084
fffff880`07aa49f0 fffff800`031932e1 : fffffa80`028a08c0 00000000`00000000 00000000`00000000 00000000`00000000 : nt!MiRemoveMappedView+0xd9
fffff880`07aa4b10 fffff800`031936ef : 0000007f`00000000 00000000`735c0000 fffffa80`00000001 fffffa80`05b125e0 : nt!MiUnmapViewOfSection+0x1b1
fffff880`07aa4bd0 fffff800`02e76ed3 : 00000000`00000000 00000000`735cc00c fffffa80`02659060 00000000`735c0000 : nt!NtUnmapViewOfSection+0x5f
fffff880`07aa4c20 00000000`76f615ba : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`001eb6c8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x76f615ba


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt! ?? ::FNODOBFM::`string'+35084
fffff800`02ee8e10 cc              int     3

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt! ?? ::FNODOBFM::`string'+35084

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  50e79935

FAILURE_BUCKET_ID:  X64_0x1a_41790_nt!_??_::FNODOBFM::_string_+35084

BUCKET_ID:  X64_0x1a_41790_nt!_??_::FNODOBFM::_string_+35084

Followup: MachineOwner
---------

Take memtest. Run for 8 passes and test each stick in a know good slot for an additional 6 passes.

• How to Test and Diagnose RAM Issues with Memtest86+

The goal is to test all the RAM sticks and all the motherboard slots.

Check your motherboard manual to ensure the RAM sticks are in the recommended motherboard slots. Some motherboards have very specific slots required for the number of RAM sticks installed.

If you get errors, stop the test and continue with the next step.

1. Remove all but one stick of RAM from your computer (this will be RAM stick #1), and run Memtest86 again, for 7 passes.

*Be sure to note the RAM stick, use a piece of tape with a number, and note the motherboard slot.
​

If this stick passes the test then go to step #3.

2. If RAM stick #1 has errors, repeat the test with RAM stick #2 in the same motherboard slot.

*If RAM stick #2 passes, this indicates that RAM stick #1 may be bad. If you want to be absolutely sure, re-test RAM stick #1 in another known good slot.
​

*If RAM stick #2 has errors, this indicates another possible bad RAM stick, a possible motherboard slot failure or inadequate settings.
​

3. Test the next stick of RAM (stick #2) in the next motherboard slot.

*If this RAM stick has errors repeat step #2 using a known good stick if possible, or another stick.
​

*If this RAM stick has no errors and both sticks failed in slot#1, test RAM stick #1 in this slot.
​

4. If you find a stick that passes the test, test it in all the other motherboard slots.

If Part 2 testing shows errors, and all tests in Part 3 show errors, you will need to test the RAM sticks in another computer and/or test other RAM in your computer to identify the problem.

In this way, you can identify whether it is a bad stick of RAM, a bad motherboard, or incompatibility between the sticks.

   Information

Errors are sometimes found after 8 passes.

   Tip

Do this test overnight, before going to bed.

• If Memtest86+ does not find any errors with ram run Windows Memory Diagnostics for 7-8 passes following its tutorial: How to Run the Memory Diagnostics Tool in Windows 7

 

[Baloeb]

OK, I had some time to work on the computer over the weekend. Some games were having trouble with the video card, so I had to uninstall and reinstall the AMD drivers. I also had time to run memtest. I just left it on over the weekend and there were no errors after 21 passes. I'm going to run the Windows memory diagnostics tool now. I just tried to put the computer to sleep again, and it would not come back on correctly still. Here are the GPU-Z screenshots I took before I put it to sleep, and the dump from after the computer came back on. Thanks again for the help you guys.

 

[Baloeb]

No errors with the Windows memory diagnostic either.

 

[koolkat77]

There are no dumps after 22nd of this month.
Configure the system to collect small memory dumps following this tutorial: http://www.sevenforums.com/tutorials/174459-dump-files-configure-windows-create-bsod.html

BIOS Version/Date	Phoenix Technologies, LTD P01-A4, 12/17/2009

Check for an update on the BIOS.

BTW, not always memtests find errors, sometimes you will have to test different RAM sticks on your motherboard.

 

[Dsprague]

The GPU temperature look rather high from your screen shot, try cleaning any suts out of your computer and seeing if it helps lower the temp somewhat.

 

[Baloeb]

Thanks for everyone's help. Sorry for the delay. OK, I've ended up completely uninstalling all display drivers and reinstalling the AMD drivers. I've also updated the bios. It still won't come out of sleep, but I don't get a BSOD anymore. Now it will turn back on, the lights are on on everything, but there isn't a picture at all. If I just let it sit there for a minute or two the computer turns off on its own. When I turn it back on it just starts up like normal, I don't get the boot menu anymore. I don't know if it will help because it seems like it didn't last time, but here is the newest zip. Also, I know my GPU temp is high, around 81, but I think I just need a new fan and it works when I'm using the computer, so I don't think that's the problem.

 

[koolkat77]

I don't know if it will help because it seems like it didn't last time, but here is the newest zip. Also, I know my GPU temp is high, around 81, but I think I just need a new fan and it works when I'm using the computer, so I don't think that's the problem.

Add a fan and let us know if it still happens.

 

[koolkat77]

Is there an update to this thread?