Unregelmässig Kernel Power 41, Task 63 shutdown

[IPCNightmare]

Unregelmässig Kernel Power 41, Task 63 shutdown

Hello,

first of all sorry for posting in the wrong language. Today the error shutdowns were that often that I have only a view minutes to post before the next shutdown happens. So I did it in my native language. Will translate it now, maybe it takes some times (next shutdown will happen ).

TRANSLATION:
Since a few weeks, I have not reproducable shutdowns from the Type Kernel Power 41. They happen to different times. Sometimes while the system boots (also before Windows starts), then during the normal work in windows and also when I shut down the Computer normally.

What have I done to solve the problem:
I have changed the main memory and the hard disk. Because I want to be sure, that I have no problem with a driver or so.
After these steps I contacted DELL. They came three times and changed the motherboard, the second board inside my laptop and the display. But without succes. The problem still exists.
The only thing that helps was to deactivate the optimus video settings inside BIOS. But "helps" doesn't mean no more shutdowns. They only happen now approximately once a day.

Can someone help me? I attached the SF DIAGNOSTIC LOG.

Greetings Thomas.

***********************German Verion******************************************

Hallo zusammen,

ich habe nun seit einigen Wochen täglich, jedoch nicht sauber reproduzierbare abstürtze des Typs Kernel Power 41. Diese Abstürtze treten teilweise beim booten (noch vor dem starten von Win7), teilweise während der Arbeit in Windows und teilweise beim herunterfahren auf.
Ich habe bereits Arbeitsspeicher und Festplatte ohne Erfolg selbst getauscht. Von DELL wurden mir bereits zweimal das Mainboard, einmal das Zusatzboard und zu guter Letzt das Display getauscht. Ergebnis war das es nicht besser wurde. Was eine Besserung brachte war die Deaktivierung der Optimus Grafikeinstellungen im BIOS. Dies bedeutete aber nicht das es keine abstürtze gab. Vielmehr waren es nun maximal einer am Tag.

Habt ihr eine Idee? Anbei der SF DIAGNOSTIC LOG.

Gruß Thomas

 

[Arc]

Windows 7 Help Forums - Forum Rules

   Note

12) This is an English based site. Please only post in English, or provide an English translation in your posts.

 

[IPCNightmare]

Hello

I did the translation. Sorry for that.

Greetings Thomas

 

[essenbe]

IPCNightmare, The posting instructions file had no dumps in it. Please make sure your computer is set for Small Memory dumps. This will tell you how to do that.http://www.sevenforums.com/tutorials/174459-dump-files-configure-windows-create-bsod.html

Also, just so you know how this system works, if you answer in a new post, we get notified. If you edit a previous post we don't get notified. So, Please always respond with a new post, otherwise we won't know you answered.

After configuring you computer for small memory dumps, please fill out your system specs in as much detail as possible and put them where these instructions tell you to. That is so that they will be available no matter where you are and we don't have to go hunt for them. The details such as Manufacturer and model number is important. We often have to go look up the specs on a component and can't do that without those details. So, if you would

Please fill out your System Specs​

   Information

Your System Specs will help us to help you, and doing it in this manner will make them available to all helpers in every post and keep us from hunting for them. We ask that you fill them out in as much detail as possible including Desktop or Laptop, Model number if it is an OEM computer and all components with the Manufacturer and Model number if possible.

If you will go to your last post and click the 'System Specs' in the bottom left of the post, you will find a link to update your system specs. Please fill those out in as much detail as possible, making sure to click save at the bottom of the page. If you would like to know what we would like, you can click 'My System Specs' at the bottom left of this post to see mine. If you do not know what your components are, this will help you accomplish this task. http://www.sevenforums.com/tutorials/180324-system-info-see-your-system-specs.html​

Also, when you finish the above, please open a elevated command prompt ( click start, type cmd in the search box, right click on the cmd entry and select run as administrator) in the black box that opens, copy/paste sfc /scannow. If you decide to type it, notice the space between the sfc and the /. It is a system file checker which will scan your system files and attempt to correct any missing or corrupt files. What we want are the results to say windows found no integrity violations. If it says files were found but could not be repaired, close the box, reboot and run it again, after opening the administrative command prompt. You may have to reboot and run it three times for it to repair all system files. If it can't repair them after 3 reboots, let us know.

If you don't mind please look in device manager and see if anything has a yellow icon on it. And please go to control panel, add/remove programs and post a screenshot of it. If it takes 2 or 3 screenshots, that's OK. this will tell you how to upload screenshots here. http://www.sevenforums.com/tutorials/9733-screenshots-files-upload-post-seven-forums.html Basically the same way you uploaded the diagnostic files.

 

[IPCNightmare]

HI

after my holidays a Dell technician once again was in the office and changed most parts from my Laptop. But today again I got a bluescreen. The new SF Diagnostic Scan is attached as a .rar file.

@essenbe: I did sfc /scannow without any negative result.
I will also add the installed programms as screenshot.


Thank you
Thomas

 

[essenbe]

IPCNightmare Looking at your dump files, it seems you have more than one problem. The dump file lists

 nvlddmkm
start    end        module name
9aa0d000 9b31a000   nvlddmkm T (no symbols)           
    Loaded symbol image file: nvlddmkm.sys
    Image path: [COLOR=red]nvlddmkm.sys[/COLOR]
    Image name: nvlddmkm.sys
    Timestamp:        [COLOR=red]Mon Oct 28 16:43:08 2013[/COLOR] (526EDA6C)
    CheckSum:         008DED3D
    ImageSize:        0090D000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e

That is your Graphics card But further analysis reveals this about it

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
[COLOR=red]VIDEO_TDR_FAILURE (116)[/COLOR]
Attempt to reset the display driver and recover from timeout failed.
Arguments:
Arg1: 8bc23008, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: 9ab1ed5a, The pointer into responsible device driver module (e.g. owner tag).
Arg3: 00000000, Optional error code (NTSTATUS) of the last failed operation.
Arg4: 0000000d, Optional internal context dependent data.

Which is usually with laptops and is extremely difficult to fix. It's a TDR error which is a Time Delay and Response error. In laptops that have switchable graphics, the manufacturer's implementation of it is when it switches from internal graphics to the dedicated card, the time it takes it to do it is too long for Windows, so Windows assumes there is a Graphics failure and shuts down. The usual fix is to disable one or the other. The dedicated graphics card gives better graphics and enables you to play games the internal one won't. Most people (me included) disable the on chip graphics and use the dedicated card for everything. That has a trade off though. It can seriously reduce your battery life. But, it is the only fix I have ever found that works because it stops the switching back and forth. In your case the dedicated Nvidia graphics driver is way out of date and could use an update. That may help and you could try that first. It is better if you could update it from Dell's site. It seems that each vendor manipulate the switching part and alter their drivers to fit that and the latest drivers from Nvidia don't always help.

You seem to have an update problem also. I will post some code, only to show you what I'm talking about. It's the Windows Update log that shows your updates. The only reason I am posting a small part of the code is to show you what I am talking about,

2014-10-16 09:46:10:457 1280 18a8 DnldMgr ***********  DnldMgr: New download job [UpdateId = {E6893137-6F73-4108-B3FA-04AA659D4EF6}.200]  ***********
2014-10-16 09:46:10:457 1280 18a8 DnldMgr FATAL: DM:CAgentDownloadManager::DownloadUpdate: pDownloadJob->Init failed with 0x80246005.
2014-10-16 09:46:10:457 1280 18a8 DnldMgr ***********  DnldMgr: New download job [UpdateId = {C755B91C-2239-477D-BA6E-C931598B688B}.200]  ***********
2014-10-16 09:46:10:457 1280 18a8 DnldMgr FATAL: DM:CAgentDownloadManager::DownloadUpdate: pDownloadJob->Init failed with 0x80246005.
2014-10-16 09:46:10:457 1280 18a8 DnldMgr ***********  DnldMgr: New download job [UpdateId = {93C43016-CDCE-4F43-90E7-4B4B451ADA20}.203]  ***********
2014-10-16 09:46:10:473 1280 18a8 DnldMgr FATAL: DM:CAgentDownloadManager::DownloadUpdate: pDownloadJob->Init failed with 0x80246005.
2014-10-16 09:46:10:473 1280 18a8 DnldMgr ***********  DnldMgr: New download job [UpdateId = {0C3A813B-55FC-4B89-982C-CABEFF392A55}.201]  ***********
2014-10-16 09:46:10:473 1280 18a8 DnldMgr FATAL: DM:CAgentDownloadManager::DownloadUpdate: pDownloadJob->Init failed with 0x80246005.
2014-10-16 09:46:10:473 1280 18a8 DnldMgr ***********  DnldMgr: New download job [UpdateId = {C6006801-B5A1-48F6-8492-A2F16AE68FE1}.200]  ***********
2014-10-16 09:46:10:473 1280 18a8 DnldMgr FATAL: DM:CAgentDownloadManager::DownloadUpdate: pDownloadJob->Init failed with 0x80246005.
2014-10-16 09:46:10:473 1280 18a8 DnldMgr ***********  DnldMgr: New download job [UpdateId = {F89DC60F-2315-4931-92C3-9C0B8992290B}.200]  ***********
2014-10-16 09:46:10:473 1280 18a8 DnldMgr FATAL: DM:CAgentDownloadManager::DownloadUpdate: pDownloadJob->Init failed with 0x80246005.
2014-10-16 09:46:10:473 1280 18a8 DnldMgr ***********  DnldMgr: New download job [UpdateId = {95EED129-15C8-4934-8787-7BA09BEE91E4}.200]  ***********
2014-10-16 09:46:10:473 1280 18a8 DnldMgr FATAL: DM:CAgentDownloadManager::DownloadUpdate: pDownloadJob->Init failed with 0x80246005.
2014-10-16 09:46:10:473 1280 18a8 DnldMgr ***********  DnldMgr: New download job [UpdateId = {5C2068EA-3050-4F0D-869D-14AA42AB649D}.201]  ***********
2014-10-16 09:46:10:473 1280 18a8 DnldMgr FATAL: DM:CAgentDownloadManager::DownloadUpdate: pDownloadJob->Init failed with 0x80246005.
2014-10-16 09:46:10:473 1280 18a8 DnldMgr ***********  DnldMgr: New download job [UpdateId = {B488BBD6-3D17-4AAB-8E40-97D11D493750}.201]  ***********
2014-10-16 09:46:10:473 1280 18a8 DnldMgr FATAL: DM:CAgentDownloadManager::DownloadUpdate: pDownloadJob->Init failed with 0x80246005.
2014-10-16 09:46:10:473 1280 18a8 DnldMgr ***********  DnldMgr: New download job [UpdateId = {CC903009-1478-481A-AB3B-B8062A3EAC5F}.201]  ***********
2014-10-16 09:46:10:473 1280 18a8 DnldMgr FATAL: DM:CAgentDownloadManager::DownloadUpdate: pDownloadJob->Init failed with 0x80246005.
2014-10-16 09:46:10:473 1280 18a8 DnldMgr ***********  DnldMgr: New download job [UpdateId = {55D9E4FE-E4EC-44F3-81BE-A7C2EB9B07B2}.202]  ***********
2014-10-16 09:46:10:488 1280 18a8 DnldMgr FATAL: DM:CAgentDownloadManager::DownloadUpdate: pDownloadJob->Init failed with 0x80246005.
2014-10-16 09:46:10:488 1280 18a8 DnldMgr ***********  DnldMgr: New download job [UpdateId = {E795836E-047C-48A3-8F32-B7D52EB998E9}.201]  ***********
2014-10-16 09:46:10:488 1280 18a8 DnldMgr FATAL: DM:CAgentDownloadManager::DownloadUpdate: pDownloadJob->Init failed with 0x80246005.
2014-10-16 09:46:10:488 1280 18a8 DnldMgr ***********  DnldMgr: New download job [UpdateId = {838D207C-6A1C-4544-9E14-28BB457EEB9B}.200]  ***********
2014-10-16 09:46:10:488 1280 18a8 DnldMgr FATAL: DM:CAgentDownloadManager::DownloadUpdate: pDownloadJob->Init failed with 0x80246005.
2014-10-16 09:46:10:488 1280 18ac AU AU checked download status and it changed: Downloading is paused
2014-10-16 09:46:15:215 1280 18a8 Report CWERReporter finishing event handling. (00000000)
2014-10-16 09:46:17:508 1280 6e4 AU Network connection established, AU can do detection now
2014-10-16 09:46:17:508 1280 6e4 AU #############

You will notice all the Failed updates. That was the only reason I posted the code and may be a factor in your BSOD problem.

 

[IPCNightmare]

Hi essenbe,

ok so the main reason for the shut down is the response time windows can't handle. I have changed the settings for the graphic card and now I will only use the dedicated card.
You said that the nvidia graphic driver is out of date, so I used the "My Dell" tool to check for upates and drivers, but I do not get any update information. Should I make an update from the nvidia website or shouldn't I because of the vendor manipulation on the switching par.

Thomas

 

[essenbe]

If you are still getting BSODs it won't hurt to try Nvidia for a driver update, if you are sure you have disabled the on board graphics in BIOS. http://www.sevenforums.com/graphic-cards/602-latest-nvidia-forceware-video-drivers-windows-7-a.html . also, I see a lot of Apple stuff installed. They can also cause problems, but a lot of people run it fine. It just always caused me problems. You also have Dameon tools installed. That is a known BSOD causer, please remove it.

Daemon Tools, Alcohol 120% and Power Archiver Pro uses SCSI Pass Through Direct (SPTD), which is a well known cause of BSOD's.

1. Uninstall Daemon Tools.
2. Download the SPTD standalone installer and follow these steps:
- Double click the executable to open it
- Click the button shown below



If the button it is grayed out, as shown in the image, there is no more SPTD installation on your system, and you can just close the window.

After that, Please let us know if it improves things any.

 

[essenbe]

If you would, please hold down the Windows key (the one with the flag on it) and press R, you will get a run box. in the run box please type in msconfig and press OK. click the startup tab and please post a screenshot of that.

You have a lot of programs installed that all eat up resource and are running an X86 Operating system which can only address about 3.5 GB of ram. If you have a lot of programs running at the same time, you can run out of resources very quickly.