Jump to content


 


Register a free account to unlock additional features at BleepingComputer.com
Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.


Click here to Register a free account now! or read our Welcome Guide to learn how to use this site.

Photo

Dell XPS 9100 freezes/crashes with kernel error 41


  • Please log in to reply
24 replies to this topic

#1 sander66

sander66

  • Members
  • 77 posts
  • OFFLINE
  •  
  • Local time:04:58 PM

Posted 29 August 2014 - 07:40 PM

My Dell XPS 9100 started to crash/freeze randomly maybe every 3 days or so. There is no dmp file.

The event viewer logs a kernel power error 41.

 

I did run HW tests like memory tests that indicate no issue.

 

I am running Win7.1 with the latest SW.

 

Not sure how to diagnose the problem further as I have no errors or dmp's.

 



BC AdBot (Login to Remove)

 


m

#2 sflatechguy

sflatechguy

  • BC Advisor
  • 2,161 posts
  • OFFLINE
  •  
  • Gender:Male
  • Local time:04:58 PM

Posted 29 August 2014 - 09:34 PM

A kernel power 41 error simply means the computer shut down unexpectedly. Unfortunately, it's a blue screen code that doesn't provide any real info on what happened.

 

It may be your system isn't configure to create minidump files when it blue screens. To check this, go to Control Panel>System and Security, click System and then click Advanced Settings. When the new window opens, select the Advanced tab, Startup and Recovery, and click the Settings button. In the Starup and Recovery window, locate the Write debugging information section and make sure it is set to small memory dump if it isn't already. Then click OK to apply the change.


Edited by sflatechguy, 29 August 2014 - 09:34 PM.


#3 sander66

sander66
  • Topic Starter

  • Members
  • 77 posts
  • OFFLINE
  •  
  • Local time:04:58 PM

Posted 29 August 2014 - 10:39 PM

there was no blue screen. I checked, the PC is configured for generating dumps.



#4 sflatechguy

sflatechguy

  • BC Advisor
  • 2,161 posts
  • OFFLINE
  •  
  • Gender:Male
  • Local time:04:58 PM

Posted 29 August 2014 - 10:42 PM

More on kernel error 41. Scenario 3 sounds like your issue: http://support.microsoft.com/kb/2028504



#5 sander66

sander66
  • Topic Starter

  • Members
  • 77 posts
  • OFFLINE
  •  
  • Local time:04:58 PM

Posted 30 August 2014 - 07:49 AM

Yes, I changed to not restart. However, in many cases my PC just freezes, doesn't reboot on its own.



#6 sander66

sander66
  • Topic Starter

  • Members
  • 77 posts
  • OFFLINE
  •  
  • Local time:04:58 PM

Posted 30 August 2014 - 08:08 AM

Just about 4 minutes after making above change my PC crashed. This time, for the first time with a bluescreen. I was able to get this with "WhoCrashed"

 

 

On Sat 8/30/2014 12:53:02 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\083014-87313-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0x1A (0x41790, 0xFFFFFA8001C3D1C0, 0xFFFF, 0x0)
Error: MEMORY_MANAGEMENT
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 a severe memory management error occurred.
This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Sat 8/30/2014 12:53:02 PM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x1A (0x41790, 0xFFFFFA8001C3D1C0, 0xFFFF, 0x0)
Error: MEMORY_MANAGEMENT
Bug check description: This indicates that a severe memory management error occurred.
This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
 



#7 sflatechguy

sflatechguy

  • BC Advisor
  • 2,161 posts
  • OFFLINE
  •  
  • Gender:Male
  • Local time:04:58 PM

Posted 30 August 2014 - 10:57 AM

Based on the above bugcheck report, citing 0x41790 in the first parameter, there may be problems with your system memory. More details on that here: http://msdn.microsoft.com/en-us/library/windows/hardware/ff557391%28v=vs.85%29.aspx

 

Try running the Windows Memory Diagnostic Tool, http://windows.microsoft.com/en-us/windows7/diagnosing-memory-problems-on-your-computer, or download memtest86+, burn it to a CD, and run it from that, http://www.memtest.org/.

 

Just to be thorough, I'd like to see the rest of the minidump. You can either download and install Debugging Tools for Windows and run the report through that, or upload the minidump file here http://www.osronline.com/page.cfm?name=analyze . You may have to relocated the minidump to another folder or your desktop in order to upload it. In either case, copy and past the report generated in your next post.



#8 sander66

sander66
  • Topic Starter

  • Members
  • 77 posts
  • OFFLINE
  •  
  • Local time:04:58 PM

Posted 30 August 2014 - 11:13 AM

I did already run the Windows memory test. Found no issues.

 

Here is the OSROnline analysis:

Crash Dump Analysis provided by OSR Open Systems Resources, Inc. (http://www.osr.com)
Online Crash Dump Analysis Service
See http://www.osronline.com for more information
Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.18409.amd64fre.win7sp1_gdr.140303-2144
Machine Name:
Kernel base = 0xfffff800`0321f000 PsLoadedModuleList = 0xfffff800`03462890
Debug session time: Sat Aug 30 08:53:02.688 2014 (UTC - 4:00)
System Uptime: 0 days 14:51:04.702
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

MEMORY_MANAGEMENT (1a)
    # Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 0000000000041790, The subtype of the bugcheck.
Arg2: fffffa8001c3d1c0
Arg3: 000000000000ffff
Arg4: 0000000000000000

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

TRIAGER: Could not open triage file : e:\dump_analysis\program\triage\modclass.ini, error 2

BUGCHECK_STR:  0x1a_41790

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  CODE_CORRUPTION

PROCESS_NAME:  taskhost.exe

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from fffff80003305d50 to fffff80003294bc0

STACK_TEXT: 
fffff880`0d4b1958 fffff800`03305d50 : 00000000`0000001a 00000000`00041790 fffffa80`01c3d1c0 00000000`0000ffff : nt!KeBugCheckEx
fffff880`0d4b1960 fffff800`032813df : fffffa80`00000000 00000000`2cafffff 00000000`00000000 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x35084
fffff880`0d4b1b20 fffff800`03293e53 : ffffffff`ffffffff 00000000`0bcaf888 00000000`0bcaf880 00000000`00008000 : nt!NtFreeVirtualMemory+0x61f
fffff880`0d4b1c20 00000000`775b149a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`0bcaf848 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x775b149a


STACK_COMMAND:  kb

MODULE_NAME: memory_corruption

IMAGE_NAME:  memory_corruption

FOLLOWUP_NAME:  memory_corruption

DEBUG_FLR_IMAGE_TIMESTAMP:  0

MEMORY_CORRUPTOR:  ONE_BIT

FAILURE_BUCKET_ID:  X64_MEMORY_CORRUPTION_ONE_BIT

BUCKET_ID:  X64_MEMORY_CORRUPTION_ONE_BIT

Followup: memory_corruption



#9 sflatechguy

sflatechguy

  • BC Advisor
  • 2,161 posts
  • OFFLINE
  •  
  • Gender:Male
  • Local time:04:58 PM

Posted 30 August 2014 - 11:24 AM

Based on the fact that the bugcheck cited taskhost.exe, open up a command prompt with elevated privileges by typing cmd in the search bar, right clicking on the command window icon select Run as administrator. Then type in sfc /scannow.

 

If system file checker states it found errors it can't fix, open up the command prompt again and type in findstr /c:"[SR] Cannot repair member file" %windir%\logs\cbs\cbs.log > %userprofile%\Desktop\sfcdetails.txt . This will save the error messages to a file on the desktop. Copy and paste them in yur next post.



#10 sander66

sander66
  • Topic Starter

  • Members
  • 77 posts
  • OFFLINE
  •  
  • Local time:04:58 PM

Posted 30 August 2014 - 01:03 PM

SFC did not find an error.

 

C:\>sfc /scannow

Beginning system scan.  This process will take some time.

Beginning verification phase of system scan.
Verification 100% complete.

Windows Resource Protection did not find any integrity violations.

C:\>



#11 sflatechguy

sflatechguy

  • BC Advisor
  • 2,161 posts
  • OFFLINE
  •  
  • Gender:Male
  • Local time:04:58 PM

Posted 30 August 2014 - 01:18 PM

Taskhost.exe usually fails due to problems with dll files or drivers. SFC has ruled out system file issues.

Does the computer crash or freeze when you are using a specific application or program, or is it random?

If it occurs when you are using a particular program, uninstall and reinstall it.

If it is random, have you made any changes, like new hardware or drivers? Try uninstalling and reinstalling the drivers. It could also be external hardware, something you added at some point like a graphics card, sound card, external hard drive, etc. If you have anything like that, uninstall and reinstall those drivers.

#12 sander66

sander66
  • Topic Starter

  • Members
  • 77 posts
  • OFFLINE
  •  
  • Local time:04:58 PM

Posted 30 August 2014 - 01:39 PM

I believe that most of the time it happens in IE. I have IE v11.

 

Did not add anything for a while. The only remote suspect in this category would be a AMD driver for the 5670 clone that is in my PC. A while back I tried to install the latest AMD drivers which did not work. The card only works with the Dell driver (latest avail from 2010).



#13 sflatechguy

sflatechguy

  • BC Advisor
  • 2,161 posts
  • OFFLINE
  •  
  • Gender:Male
  • Local time:04:58 PM

Posted 30 August 2014 - 01:53 PM

Try using a different browser and see if the issue happens again.

Dells can be very fussy about drivers. Try disabling and re-enabling that in Device Manager. That will unload and reload the driver. See if that helps. If there is a yellow warning icon, then the Dell driver may be causing the issue.

#14 sander66

sander66
  • Topic Starter

  • Members
  • 77 posts
  • OFFLINE
  •  
  • Local time:04:58 PM

Posted 30 August 2014 - 01:58 PM

I think I will take the opportunity the card that allows me to use standard drivers.



#15 sflatechguy

sflatechguy

  • BC Advisor
  • 2,161 posts
  • OFFLINE
  •  
  • Gender:Male
  • Local time:04:58 PM

Posted 30 August 2014 - 02:06 PM

You mentioned it's an AMD clone. Who made it? Do they have drivers available at their website?




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users