locked
Event ID - 41 Task Category (63) Source - Kernel Power Win7 64bit RRS feed

  • General discussion

  • Hey guys I keep getting the BSOD. 28 times in the last week and is bugging me. Just wondering if you can help me fix this. Would be very much appreciated.


    Thursday, March 28, 2013 9:40 PM

All replies

  • This might sound simple but try plugging your usb devices into different ports.
    Thursday, March 28, 2013 11:26 PM
  • I don't think its that its a software or hardware error. Lots of them relate to memory management,
    Friday, March 29, 2013 12:04 AM


  • We do need the actual DMP file as it contains the only record of the sequence of events leading up to the crash, what drivers were loaded, and what was responsible.
    You may be able to get the DMP files without crashing by booting into safe mode (F8) with networking.
    If you are overclocking stop.  (chances are if you dont know if you are, you are not)a
    To enable us to assist you with your computer's BSOD symptoms, upload the contents of your "\Windows\Minidump" folder.  We need at least 2 DMP FILES to diagnose and confirm


    The procedure:

    * Copy the contents of \Windows\Minidump to another (temporary) location somewhere on your machine.
    * Zip up the copy.
    * Attach the ZIP archive to your post using the "paperclip" (file attachments) button. (if available on  your site, MS doesnt have this)
     *Please upload them to a file sharing service like Skydrive or"Rapidshare" and put a link to them in your reply.
    Link for how to  upload below.
    http://www.wikihow.com/Use-SkyDrive

    To ensure minidumps are enabled:

    * Go to Start, in the Search Box type: sysdm.cpl, press Enter.
    * Under the Advanced tab, click on the Startup and Recovery Settings... button.
    * Ensure that Automatically restart is unchecked.
    * Under the Write Debugging Information header select Small memory dump (256 kB) in the dropdown box (the 256kb varies).
    * Ensure that the Small Dump Directory is listed as %systemroot%\Minidump.
    * OK your way out.
    * Reboot if changes have been made.

    Please also run MSinfo32 and upload the output as well.
    To run MSinfo32 please go to start>run>MSinfo32
    Go to "file" "save" and upload the saved file with the DMPS
    (Instructions for XP, Vista, Win 7, Win 8)
    System specs are often useful so include whatever you know

    Friday, March 29, 2013 5:54 AM
  • Here are the errors.

    http://imgur.com/bJ0wkSt

    • Edited by Bammer316 Friday, March 29, 2013 1:39 PM
    Friday, March 29, 2013 1:38 PM
  • Bammer

    As it says in red on the instructions we need the ACTUAL dmp files not a snip of them.  We cant sort or explore a snip


    Wanikiya & Dyami -Team-ZigZag. www.ZigZag3143.com email Admin@zigzag3143.com

    Friday, March 29, 2013 1:54 PM
  • Oh sorry, here it is. http://www.mediafire.com/?kd8a183a5zf3h5f
    Saturday, March 30, 2013 12:31 PM
  • Bammer

    Ouch 50 crashes in 3 months.!!

     These crashes were caused by memory corruption (probably a driver).  Please run these two tests to verify your memory and find which driver is causing the problem.  

    *Dont forget to upload any further DMP files (especially those when verifier is running)

    *If you are overclocking anything reset to default before running these tests.
    In other words STOP!!!   If you dont know what this means you probably arent


    1-Memtest.
    *Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder or another ISO burning program. http://www.memtest.org 
    *Boot from the CD, and leave it running for at least 5 or 6 passes.
    *Just remember, any time Memtest reports errors, it can be either bad RAM or a bad motherboard slot.
    *Test the sticks individually, and if you find a good one, test it in all slots.

    Any errors are indicative of a memory problem.
    If a known good stick fails in a motherboard slot it is probably the slot.


    2-Driver verifier

    Using Driver Verifier is an iffy proposition. Most times it'll crash and it'll tell you what the driver is.

    *But sometimes it'll crash and won't tell you the driver.
    *Other times it'll crash before you can log in to Windows. If you can't get to Safe Mode, then you'll have to resort to offline editing of the registry to disable Driver Verifier.
    *I'd suggest that you first backup your data and then make sure you've got access to another computer so you can contact us if problems arise.
    *Then make a System Restore point (so you can restore the system using the Vista/Win7 Startup Repair feature).

    *In Windows 7 you can make a Startup Repair disk by going to Start....All Programs...Maintenance...Create a System Repair Disc - with Windows Vista you'll have to use your installation disk or the "Repair your computer" option at the top of the Safe Mode menu .

    Here is the procedure:

    - Go to Start and type in "verifier" (without the quotes) and press Enter
    - Select "Create custom settings (for code developers)" and click "Next"
    - Select "Select individual settings from a full list" and click "Next"
    - Select everything EXCEPT FOR "Low Resource Simulation" and click "Next"
    - Select "Select driver names from a list" and click "Next"
    *Then select all drivers NOT provided by Microsoft and click "Next"
    - Select "Finish" on the next page.
    *Reboot the system and wait for it to crash to the Blue Screen.
    *Continue to use your system normally, and if you know what causes the crash, do that repeatedly. The objective here is to get the system to crash because Driver Verifier is stressing the drivers out. If it doesn't crash for you, then let it run for at least 36 hours of continuous operation.
    *If you can't get into Windows because it crashes too soon, try it in Safe Mode.
    *If you can't get into Safe Mode, try using System Restore from your installation DVD to set the system back to the previous restore point that you created.

    *Further Reading
    http://support.microsoft.com/kb/244617


    Wanikiya & Dyami -Team-ZigZag. www.ZigZag3143.com email Admin@zigzag3143.com

    Saturday, March 30, 2013 3:00 PM