Fairly random BSOD, event 41, kernel-power (newly built PC)

Page 1 of 2 12 LastLast

  1. Posts : 7
    Windows 10 Professional
       #1

    Fairly random BSOD, event 41, kernel-power (newly built PC)


    So I've just built a PC and within a day it has had BSOD a couple of times. The event viewer says event 41, kernel-power, category 63

    When I did build my computer the RAM was an issue, and was fixed after moving it to a different slot. It's DDR4 in a LGA1151 board, and it's the Crucial Ballistix 1x8GB, and I'm guessing it's something to do with that

    But I'll include the debug file anyway to verify this.

    Cheers

    Attachment 34962
      My Computer


  2. Posts : 14,901
    Windows 10 Pro
       #2

    Hi Sarcastic Goats,

    Welcome to the 10forums.

    While I'm taking a look at the information
    Please fill in your system specs
    Please go to this site and download the tool. The tool will give you detailed information about your system specs, please fill in your system specs more completely.
    How to fill in your system specs:

      My Computers


  3. Posts : 14,901
    Windows 10 Pro
       #3

    The cause of the crashes is your network card, the driver is old and needs updating
    Check for driver updates here

    Code:
    3: kd> lmvm athurxstart             end                 module name
    fffff801`bb400000 fffff801`bb5de000   athurx   T (no symbols)           
        Loaded symbol image file: athurx.sys
        Image path: \SystemRoot\System32\drivers\athurx.sys
        Image name: athurx.sys
        Timestamp:        Wed Apr 20 12:07:45 2011 (4DAEB071)
        CheckSum:         001E1C78
        ImageSize:        001DE000
        Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
      My Computers


  4. Posts : 7
    Windows 10 Professional
    Thread Starter
       #4

    axe0 said:
    The cause of the crashes is your network card, the driver is old and needs updating
    Check for driver updates here

    Code:
    3: kd> lmvm athurxstart             end                 module name
    fffff801`bb400000 fffff801`bb5de000   athurx   T (no symbols)           
        Loaded symbol image file: athurx.sys
        Image path: \SystemRoot\System32\drivers\athurx.sys
        Image name: athurx.sys
        Timestamp:        Wed Apr 20 12:07:45 2011 (4DAEB071)
        CheckSum:         001E1C78
        ImageSize:        001DE000
        Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
    Is this the LAN or the wireless receiver? It's a TP Link WN722N

    Edit: So I'm guessing it's the wireless receiver, apparently it is:
    Chipset: Atheros AR9002U

    WI1 chip1: Atheros AR9271


    There's a driver for the AR9271 and for the AR9002WB, so which one do I use?
      My Computer


  5. Posts : 14,901
    Windows 10 Pro
       #5

    Sorry, I thought I had added the device.
    Check in your device manager, maybe there is the information you need.
      My Computers


  6. Posts : 7
    Windows 10 Professional
    Thread Starter
       #6

    axe0 said:
    Sorry, I thought I had added the device.
    Check in your device manager, maybe there is the information you need.
    Alright I'll check, thanks
      My Computer


  7. Posts : 14,901
    Windows 10 Pro
       #7

    Keep us posted :)
      My Computers


  8. Posts : 7
    Windows 10 Professional
    Thread Starter
       #8

    axe0 said:
    Keep us posted :)
    It uses AR2971 which isn't available for Windows 10, I'll just use the homeplug (although, again made by TP-link are known for dropping out)
      My Computer


  9. Posts : 14,901
    Windows 10 Pro
       #9

    No driver for windows 10, but it is still good to update the driver.
    I cannot say for sure, but my guess would be that updating the driver (even though there is no windows 10 driver available) may solve the crash.
      My Computers


  10. Posts : 7
    Windows 10 Professional
    Thread Starter
       #10

    axe0 said:
    No driver for windows 10, but it is still good to update the driver.
    I cannot say for sure, but my guess would be that updating the driver (even though there is no windows 10 driver available) may solve the crash.
    Will this be different to the TP-link one, because right now it's running the latest driver off the TP-Link website
      My Computer


 

  Related Discussions
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 09:20.
Find Us




Windows 10 Forums