Kernel error 41

Anonymous
2013-09-25T22:06:12+00:00

Hi, for about 9 months now I'm experiencing kernel 41 errors. I got them about once or twice a month, but this month they happened already 6 times. I have a VAIO notebok VPCF23C5E with a 500 GB SSD drive with Win7 Pro SP1 German. I constantly use my notebook between 10-12 hours a day and work a lot with Photoshop, InDesign and Visual Studio. When the system crashes I'm doing nothing special, just clicking somewhere. The crashes never appeared on high loads, like copying a terabyte hard drive or heavy work in Photoshop. Normally I'm just writing an email or clicking in a program. Once the system just turned off without a blue screen. The bugcheck codes vary:

0, 0x0000001A, 0x00000050, 0x000000D1,0x0000010D, 0x0000000A, 0x0000001E

I have no clue where to start searching. I run the sony hardware tests and they reported no error.

All Windows and Sony updates are installed. The only non-Sony driver I have installed is the NVIDIA graphics driver. I know I updated it before, but can't recall when. I think I tried it as a solution for the crashes. I updated the driver again about a week ago after the crashes became more, but the crashes still happen.

If I can't find a solution I have to get the computer to Sony repair to check the hardware soroughly. I might be HW, but it could also be a driver issue. I just have tons of timely work to do and really can't be without the computer for days. So if anybody has an idea or even better a process how to pinpoint the source of the crashes I would be very thankful.

Cheers Marcus

Windows for home | Previous Windows versions | Windows update

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments No comments

60 answers

Sort by: Most helpful
  1. Anonymous
    2013-09-26T19:37:44+00:00

    Thanks for the update Marcus, and my pleasure. I look forward to your reply.

    Regards,

    Patrick

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2013-09-26T19:31:12+00:00

    Hi Patrick,

    thank you very much for your time and your amazing and clear descriptions. This is extremely helpful.

    I followed your instructions. The system did not BSOD during start-up. It is still running, just quiet slow with CPU usage around 25%.

    As soon as I have more information I will let you know.

    Cheers Marcus

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2013-09-26T18:35:21+00:00

    Hi Marcus,

    Thanks for the dump! Also, for future reference, Kernel error 41 just implies that the system shut down unexpectedly.

    The attached DMP file is of the WDF_VIOLATION (10d) bugcheck.

    This indicates that Kernel-Mode Driver Framework (KMDF) detected that Windows found an error in a framework-based driver.

    BugCheck 10D, {6, 3, 57fef1fcfd8, fffffa8008d3aaf0}

    The 1st parameter of the bugcheck is 6 which indicates that a fatal error was made in handling a WDF request. In this case, parameter 2 further specifies the type of fatal error that has been made, as defined by the enumeration WDF_REQUEST_FATAL_ERROR.

    The 2nd parameter of the bugcheck is 3 which indicates that a driver attempted to send a framework request that has already been sent to an I/O target.

    To find out what driver is causing this, let's go ahead and enable Driver Verifier:

    Driver Verifier:

    What is Driver Verifier?

    Driver Verifier is included in Windows 8, 7, Windows Server 2008 R2, Windows Vista, Windows Server 2008, Windows 2000, Windows XP, and Windows Server 2003 to promote stability and reliability; you can use this tool to troubleshoot driver issues. Windows kernel-mode components can cause system corruption or system failures as a result of an improperly written driver, such as an earlier version of a Windows Driver Model (WDM) driver.

    Essentially, if there's a 3rd party driver believed to be at issue, enabling Driver Verifier will help flush out the rogue driver if it detects a violation.

    Before enabling Driver Verifier, it is recommended to create a System Restore Point:

    Vista - START | type rstrui - create a restore point

    Windows 7 - START | type create | select "Create a Restore Point"

    Windows 8 - http://www.eightforums.com/tutorials/4690-restore-point-create-windows-8-a.html

    How to enable Driver Verifier:

    Start > type "verifier" without the quotes > Select the following options -

    1. Select - "Create custom settings (for code developers)"
    2. Select - "Select individual settings from a full list"
    3. Check the following boxes -
    • Special Pool
    • Pool Tracking
    • Force IRQL Checking
    • Deadlock Detection
    • Security Checks (Windows 7 & 8)
    • DDI compliance checking (Windows 8)
    • Miscellaneous Checks
    1. Select  - "Select driver names from a list"
    2. Click on the "Provider" tab. This will sort all of the drivers by the provider.
    3. Check EVERY box that is [B]NOT[/B] provided by Microsoft / Microsoft Corporation.
    4. Click on Finish.
    5. Restart.

    Important information regarding Driver Verifier:

    • If Driver Verifier finds a violation, the system will BSOD.
    • After enabling Driver Verifier and restarting the system, depending on the culprit, if for example the driver is on start-up, you may not be able to get back into normal Windows because Driver Verifier will flag it, and as stated above, that will cause / force a BSOD.

    If this happens, do not panic, do the following:

    • Boot into Safe Mode by repeatedly tapping the F8 key during boot-up.
    • Once in Safe Mode - Start > type "system restore" without the quotes.
    • Choose the restore point you created earlier.

    If you did not set up a restore point, do not worry, you can still disable Driver Verifier to get back into normal Windows:

    • Start > Search > type "cmd" without the quotes.
    • To turn off Driver Verifier, type in cmd "verifier /reset" without the quotes.

    ・    Restart and boot into normal Windows.

    How long should I keep Driver Verifier enabled for?

    It varies, many experts and analysts have different recommendations. Personally, I recommend keeping it enabled for at least 24 hours. If you don't BSOD by then, disable Driver Verifier.

    My system BSOD'd, where can I find the crash dumps?

    They will be located in %systemroot%\Minidump

    Any other questions can most likely be answered by this article:

    http://support.microsoft.com/kb/244617

    Regards,

    Patrick

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2013-09-26T09:46:35+00:00

    Hi Patrick,

    thanks a lot for your help.

    Here is the link to the minidump-file: http://www.worldofswing.com/download/ms/072913-9609-01.zip

    There was only one mini dump file in the folder. In the system fauilure settings the setting to overwrite existing files was selected. I unselected it now. I also clean the drive once in a while to free disc space.  I surley have deleted mini dump files with it in the past. I will collect them now. I normally sent crash information to Microsoft when requested.

    Error Reporting Service was set to Manual. I set it to Automatic.

    Let me know if the dump file is helpful or if I can do anything else.

    Regards Marcus

    Was this answer helpful?

    0 comments No comments
  5. Anonymous
    2013-09-25T22:15:36+00:00

    Hi,

    In order to assist you, we will need the DMP files to analyze what exactly occurred at the time of the crash, etc.

    If you don't know where DMP files are located, here's how to get to them:

     1.    Navigate to the %systemroot%\Minidump folder.

     2.    Copy any and all DMP files in the Minidump folder to your Desktop and then zip up these files.

     3.    Upload the zip containing the DMP files to Skydrive or a hosting site of your choice and paste in your reply.

    If you are going to use Skydrive but don't know how to upload to it, please visit the following:

    http://www.wikihow.com/Use-SkyDrive

    Please note that any "cleaner" programs such as TuneUp Utilities, CCleaner, etc, by default will delete DMP files upon use.

    If your computer is not generating DMP files, please do the following:

    1. Start > type %systemroot% which should show the Windows folder, click on it. Once inside that folder, ensure there is a Minidump folder created. If not, CTRL-SHIFT-N to make a New Folder and name it Minidump.
    2. Windows key + Pause key. This should bring up System. Click Advanced System Settings on the left > Advanced > Performance > Settings > Advanced > Ensure there's a check-mark for 'Automatically manage paging file size for all drives'.
    3. Windows key + Pause key. This should bring up System. Click Advanced System Settings on the left > Advanced > Startup and Recovery > Settings > System Failure > ensure there is a check mark next to 'Write an event to the system log'.

    Ensure Small Memory Dump is selected and ensure the path is %systemroot%\Minidump.

    1. Double check that the WERS is ENABLED:

    Start > Search > type services.msc > Under the name tab, find Windows Error Reporting Service > If the status of the service is not Started then right click it and select Start. Also ensure that under Startup Type it is set to Automatic rather than Manual. You can do this by right clicking it, selecting properties, and under General selecting startup type to 'Automatic', and then click Apply.

    If you cannot get into normal mode to do any of this, please do this via Safe Mode.

    Regards,

    Patrick

    Was this answer helpful?

    0 comments No comments