Windows 8 and 8.1 Forums


Kernal Power Error ID 41 Windows 8.1

  1. #1


    Posts : 3
    windows 8.1

    Kernal Power Error ID 41 Windows 8.1


    Hello

    I built a new pc recently and it has been giving me some trouble. At first when i installed the windows 7 ultimate and that when the problem began. I ran in to BSOD. I thought it might be due to the windows and installed windows 8.1. The problem seemed to have been fixed but just now, i had a windows 8.1 message saying"pc ran into ....... collecting error info"

    Please help! this was my first computer i ever built and never expected to be this many problems

      My System SpecsSystem Spec

  2. #2


    India
    Posts : 2,097
    Windows 8.1 Industry Pro B-)


    Hi Grishnak197 ^_^,

    In order to analyse the situation for you, I would need the dump files in order to help you out. Kindly follow the instructions over here -
    Blue Screen of Death (BSOD) Posting Instructions

    Kernel Power Error ID 41 is generally related to Power Issues. I would suggest you to check the system for loose connections and make sure that the system is not getting overheated.

    Let me know how it goes ^_^
      My System SpecsSystem Spec

  3. #3


    Posts : 3
    windows 8.1


    Here is the zip

    See what u can do about!

    Attachment 54239Attachment 54239

    Thanks
      My System SpecsSystem Spec

  4. #4


    India
    Posts : 2,097
    Windows 8.1 Industry Pro B-)


    Hi Grishnak197 ^_^,

    I have analysed your dump files and below has been provided an analysis of the same for informative purposes :-
    Code:
    **************************Sat Nov 22 03:18:15.086 2014 (UTC + 5:30)**************************
    Loading Dump File [C:\SysnativeBSODApps\112214-4843-01.dmp]
     
    Windows 8 Kernel Version 9600 MP (4 procs) Free x64
     
    Built by: 9600.17031.amd64fre.winblue_gdr.140221-1952
     
    System Uptime: 0 days 0:25:01.726
     
    Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+2aebd )
     
    BugCheck 1A, {41201, fffff68000044100, 80000000e0cc086f, ffffe00092990240}
    BugCheck Info: MEMORY_MANAGEMENT (1a)
     
    Arguments: 
    Arg1: 0000000000041201, The subtype of the bugcheck.
    Arg2: fffff68000044100
    Arg3: 80000000e0cc086f
    Arg4: ffffe00092990240
    BUGCHECK_STR:  0x1a_41201
     
    PROCESS_NAME:  explorer.exe
     
    FAILURE_BUCKET_ID:  0x1a_41201_nt!_??_::FNODOBFM::_string_
     
    CPUID:        "Intel(R) Core(TM) i5-4690K CPU @ 3.50GHz"
     
    MaxSpeed:     3500
     
    CurrentSpeed: 3500
     
      BIOS Version                  V1.4
     
      BIOS Release Date             07/18/2014
     
      Manufacturer                  MSI
     
      Product Name                  MS-7866
     
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Fri Nov 21 22:04:50.281 2014 (UTC + 5:30)**************************
    Loading Dump File [C:\SysnativeBSODApps\112214-15906-01.dmp]
     
    Windows 8 Kernel Version 9600 MP (4 procs) Free x64
     
    Built by: 9600.17031.amd64fre.winblue_gdr.140221-1952
     
    System Uptime: 0 days 2:05:20.922
     
    *** WARNING: Unable to verify timestamp for e22w8x64.sys
     
    *** ERROR: Module load completed but symbols could not be loaded for e22w8x64.sys
     
    *** WARNING: Unable to verify checksum for win32k.sys
     
    Probably caused by : e22w8x64.sys ( e22w8x64+87e5 )
     
    BugCheck 1E, {ffffffffc0000005, fffff800fcfdb7e5, 0, ffffffffffffffff}
    BugCheck Info: KMODE_EXCEPTION_NOT_HANDLED (1e)
     
    Arguments: 
    Arg1: ffffffffc0000005, The exception code that was not handled
    Arg2: fffff800fcfdb7e5, The address that the exception occurred at
    Arg3: 0000000000000000, Parameter 0 of the exception
    Arg4: ffffffffffffffff, Parameter 1 of the exception
    BUGCHECK_STR:  0x1E_c0000005_R
     
    PROCESS_NAME:  System
     
    FAILURE_BUCKET_ID:  0x1E_c0000005_R_e22w8x64+87e5
     
    CPUID:        "Intel(R) Core(TM) i5-4690K CPU @ 3.50GHz"
     
    MaxSpeed:     3500
     
    CurrentSpeed: 3500
     
      BIOS Version                  V1.4
     
      BIOS Release Date             07/18/2014
     
      Manufacturer                  MSI
     
      Product Name                  MS-7866
     
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Fri Nov 21 19:59:06.670 2014 (UTC + 5:30)**************************
    Loading Dump File [C:\SysnativeBSODApps\112214-5000-01.dmp]
     
    Windows 8 Kernel Version 9600 MP (4 procs) Free x64
     
    Built by: 9600.17031.amd64fre.winblue_gdr.140221-1952
     
    System Uptime: 0 days 1:03:43.215
     
    Probably caused by : ntkrnlmp.exe ( nt!KiSystemServiceExit+24b )
     
    BugCheck 1, {7ffba1e7ac1a, 0, 800000, ffffd0018132bb80}
    BugCheck Info: APC_INDEX_MISMATCH (1)
     
    Arguments: 
    Arg1: 00007ffba1e7ac1a, Address of system call function or worker routine
    Arg2: 0000000000000000, Thread->ApcStateIndex
    Arg3: 0000000000800000, (Thread->SpecialApcDisable << 16) | Thread->KernelApcDisable
    Arg4: ffffd0018132bb80, Call type (0 - system call, 1 - worker routine)
    BUGCHECK_STR:  0x1
     
    DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
     
    PROCESS_NAME:  MsMpEng.exe
     
    FAILURE_BUCKET_ID:  0x1_SysCallNum_8_nt!KiSystemServiceExit
     
    CPUID:        "Intel(R) Core(TM) i5-4690K CPU @ 3.50GHz"
     
    MaxSpeed:     3500
     
    CurrentSpeed: 3500
     
      BIOS Version                  V1.4
     
      BIOS Release Date             07/18/2014
     
      Manufacturer                  MSI
     
      Product Name                  MS-7866
     
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Fri Nov 21 09:49:15.489 2014 (UTC + 5:30)**************************
    Loading Dump File [C:\SysnativeBSODApps\112114-4093-01.dmp]
     
    Windows 8 Kernel Version 9600 MP (4 procs) Free x64
     
    Built by: 9600.17031.amd64fre.winblue_gdr.140221-1952
     
    System Uptime: 0 days 0:48:04.130
     
    Probably caused by : win32k.sys ( win32k!DirectComposition::CDwmChannel::ReferenceHandleAndLock+93 )
     
    BugCheck A, {0, 2, 1, fffff803cd30a3f3}
    BugCheck Info: IRQL_NOT_LESS_OR_EQUAL (a)
     
    Arguments: 
    Arg1: 0000000000000000, memory referenced
    Arg2: 0000000000000002, IRQL
    Arg3: 0000000000000001, bitfield :
     bit 0 : value 0 = read operation, 1 = write operation
     bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
    Arg4: fffff803cd30a3f3, address which referenced memory
    BUGCHECK_STR:  AV
     
    DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
     
    PROCESS_NAME:  dwm.exe
     
    FAILURE_BUCKET_ID:  AV_win32k!DirectComposition::CDwmChannel::ReferenceHandleAndLock
     
    CPUID:        "Intel(R) Core(TM) i5-4690K CPU @ 3.50GHz"
     
    MaxSpeed:     3500
     
    CurrentSpeed: 3500
     
      BIOS Version                  V1.4
     
      BIOS Release Date             07/18/2014
     
      Manufacturer                  MSI
     
      Product Name                  MS-7866
     
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Fri Nov 21 02:31:12.617 2014 (UTC + 5:30)**************************
    Loading Dump File [C:\SysnativeBSODApps\112114-1921-01.dmp]
     
    Windows 8 Kernel Version 9600 MP (4 procs) Free x64
     
    Built by: 9600.17031.amd64fre.winblue_gdr.140221-1952
     
    System Uptime: 0 days 2:14:11.255
     
    Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )
     
    BugCheck 109, {a3a01f5961b89538, 0, 6af107f8b647a301, 101}
    BugCheck Info: CRITICAL_STRUCTURE_CORRUPTION (109)
     
    Arguments: 
    Arg1: a3a01f5961b89538, Reserved
    Arg2: 0000000000000000, Reserved
    Arg3: 6af107f8b647a301, Failure type dependent information
    Arg4: 0000000000000101, Type of corrupted region, can be
     0 : A generic data region
     1 : Modification of a function or .pdata
     2 : A processor IDT
     3 : A processor GDT
     4 : Type 1 process list corruption
     5 : Type 2 process list corruption
     6 : Debug routine modification
     7 : Critical MSR modification
    BUGCHECK_STR:  0x109
     
    DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
     
    PROCESS_NAME:  csrss.exe
     
    FAILURE_BUCKET_ID:  BAD_STACK
     
    CPUID:        "Intel(R) Core(TM) i5-4690K CPU @ 3.50GHz"
     
    MaxSpeed:     3500
     
    CurrentSpeed: 3500
     
      BIOS Version                  V1.4
     
      BIOS Release Date             07/18/2014
     
      Manufacturer                  MSI
     
      Product Name                  MS-7866
     
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Fri Nov 21 00:16:38.031 2014 (UTC + 5:30)**************************
    Loading Dump File [C:\SysnativeBSODApps\112114-1906-01.dmp]
     
    Windows 8 Kernel Version 9600 MP (4 procs) Free x64
     
    Built by: 9600.17031.amd64fre.winblue_gdr.140221-1952
     
    System Uptime: 0 days 4:10:18.670
     
    Probably caused by : ntkrnlmp.exe ( nt!KiSystemServiceExit+24b )
     
    BugCheck 1, {7ffa7022b16a, 0, ffff, ffffd001becfbb80}
    BugCheck Info: APC_INDEX_MISMATCH (1)
     
    Arguments: 
    Arg1: 00007ffa7022b16a, Address of system call function or worker routine
    Arg2: 0000000000000000, Thread->ApcStateIndex
    Arg3: 000000000000ffff, (Thread->SpecialApcDisable << 16) | Thread->KernelApcDisable
    Arg4: ffffd001becfbb80, Call type (0 - system call, 1 - worker routine)
    BUGCHECK_STR:  0x1
     
    DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
     
    PROCESS_NAME:  MsMpEng.exe
     
    FAILURE_BUCKET_ID:  0x1_SysCallNum_5d_nt!KiSystemServiceExit
     
    CPUID:        "Intel(R) Core(TM) i5-4690K CPU @ 3.50GHz"
     
    MaxSpeed:     3500
     
    CurrentSpeed: 3500
     
      BIOS Version                  V1.4
     
      BIOS Release Date             07/18/2014
     
      Manufacturer                  MSI
     
      Product Name                  MS-7866
     
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Thu Nov 20 20:05:55.777 2014 (UTC + 5:30)**************************
    Loading Dump File [C:\SysnativeBSODApps\112114-1828-01.dmp]
     
    Windows 8 Kernel Version 9600 MP (4 procs) Free x64
     
    Built by: 9600.17031.amd64fre.winblue_gdr.140221-1952
     
    System Uptime: 0 days 3:31:03.416
     
    Probably caused by : ntkrnlmp.exe ( nt!KiFastFailDispatch+d0 )
     
    BugCheck 139, {3, ffffd000d29bd3b0, ffffd000d29bd308, 0}
    BugCheck Info: KERNEL_SECURITY_CHECK_FAILURE (139)
     
    Arguments: 
    Arg1: 0000000000000003, A LIST_ENTRY has been corrupted (i.e. double remove).
    Arg2: ffffd000d29bd3b0, Address of the trap frame for the exception that caused the bugcheck
    Arg3: ffffd000d29bd308, Address of the exception record for the exception that caused the bugcheck
    Arg4: 0000000000000000, Reserved
    BUGCHECK_STR:  0x139
     
    DEFAULT_BUCKET_ID:  LIST_ENTRY_CORRUPT
     
    PROCESS_NAME:  svchost.exe
     
    FAILURE_BUCKET_ID:  0x139_3_nt!KiFastFailDispatch
     
    CPUID:        "Intel(R) Core(TM) i5-4690K CPU @ 3.50GHz"
     
    MaxSpeed:     3500
     
    CurrentSpeed: 3500
     
      BIOS Version                  V1.4
     
      BIOS Release Date             07/18/2014
     
      Manufacturer                  MSI
     
      Product Name                  MS-7866
     
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Thu Nov 20 16:34:27.942 2014 (UTC + 5:30)**************************
    Loading Dump File [C:\SysnativeBSODApps\112014-1984-01.dmp]
     
    Windows 8 Kernel Version 9600 MP (4 procs) Free x64
     
    Built by: 9600.17031.amd64fre.winblue_gdr.140221-1952
     
    System Uptime: 0 days 4:49:00.581
     
    Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+20d9a )
     
    BugCheck 50, {ffffd001a90431af, 0, ffffd001a8844f4b, 2}
    BugCheck Info: PAGE_FAULT_IN_NONPAGED_AREA (50)
     
    Arguments: 
    Arg1: ffffd001a90431af, memory referenced.
    Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
    Arg3: ffffd001a8844f4b, If non-zero, the instruction address which referenced the bad memory
     address.
    Arg4: 0000000000000002, (reserved)
    BUGCHECK_STR:  AV
     
    DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
     
    PROCESS_NAME:  System
     
    FAILURE_BUCKET_ID:  AV_nt!_??_::FNODOBFM::_string_
     
    CPUID:        "Intel(R) Core(TM) i5-4690K CPU @ 3.50GHz"
     
    MaxSpeed:     3500
     
    CurrentSpeed: 3500
     
      BIOS Version                  V1.4
     
      BIOS Release Date             07/18/2014
     
      Manufacturer                  MSI
     
      Product Name                  MS-7866
     
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    Below is a list of 3rd party drivers present on your system :-
    Code:
    **************************Sat Nov 22 03:18:15.086 2014 (UTC + 5:30)**************************
    tmp540B.tmp                 Sat Jul 26 18:59:37 2008 (488B26C1)
    MBfilt64.sys                Fri Jul 31 09:10:32 2009 (4A7267B0)
    intelppm.sys                Thu Aug 22 14:16:35 2013 (5215CFEB)
    ikbevent.sys                Fri Jan 10 23:22:53 2014 (52D03375)
    imsevent.sys                Fri Jan 10 23:22:53 2014 (52D03375)
    ISCTD.sys                   Thu Jan 23 01:07:35 2014 (52E01DFF)
    asstor64.sys                Mon Jan 27 15:00:34 2014 (52E6273A)
    AMDACPKSL.SYS               Wed Mar 12 05:19:44 2014 (531FA118)
    AtihdWB6.sys                Wed Mar 12 05:20:02 2014 (531FA12A)
    e22w8x64.sys                Wed Mar 26 21:28:37 2014 (5332F92D)
    INETMON.sys                 Thu Apr  3 22:20:43 2014 (533D9163)
    dump_iaStorA.sys            Sat May  3 04:36:56 2014 (53642510)
    iaStorA.sys                 Sat May  3 04:36:56 2014 (53642510)
    RTKVHD64.sys                Tue Jul 15 16:23:15 2014 (53C5081B)
    bwcW8x64.sys                Fri Sep 12 01:13:49 2014 (5411FB75)
    atikmpag.sys                Tue Sep 16 03:29:06 2014 (5417612A)
    atikmdag.sys                Tue Sep 16 03:51:08 2014 (54176654)
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Fri Nov 21 22:04:50.281 2014 (UTC + 5:30)**************************
    tmp33B2.tmp                 Sat Jul 26 18:59:37 2008 (488B26C1)
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Fri Nov 21 19:59:06.670 2014 (UTC + 5:30)**************************
    tmp3076.tmp                 Sat Jul 26 18:59:37 2008 (488B26C1)
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Fri Nov 21 09:49:15.489 2014 (UTC + 5:30)**************************
    ISCTD64.sys                 Wed Nov 28 01:22:34 2012 (50B51A02)
    atikmpag.sys                Fri Apr 18 06:37:07 2014 (53507ABB)
    atikmdag.sys                Fri Apr 18 07:43:16 2014 (53508A3C)
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Fri Nov 21 02:31:12.617 2014 (UTC + 5:30)**************************
    dump_storahci.sys           Thu Aug 22 17:10:39 2013 (5215F8B7)
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Fri Nov 21 00:16:38.031 2014 (UTC + 5:30)**************************
    mrxsmb30.sys                Thu Aug 22 17:05:42 2013 (5215F78E)
    tmp540B.tmp - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed.
    http://www.carrona.org/drivers/driver.php?id=MBfilt64.sys
    http://www.carrona.org/drivers/driver.php?id=intelppm.sys
    http://www.carrona.org/drivers/driver.php?id=ikbevent.sys
    http://www.carrona.org/drivers/driver.php?id=imsevent.sys
    http://www.carrona.org/drivers/driver.php?id=ISCTD.sys
    http://www.carrona.org/drivers/driver.php?id=asstor64.sys
    http://www.carrona.org/drivers/driver.php?id=AMDACPKSL.SYS
    http://www.carrona.org/drivers/driver.php?id=AtihdWB6.sys
    http://www.carrona.org/drivers/driver.php?id=e22w8x64.sys
    http://www.carrona.org/drivers/driver.php?id=INETMON.sys
    http://www.carrona.org/drivers/driver.php?id=dump_iaStorA.sys
    http://www.carrona.org/drivers/driver.php?id=iaStorA.sys
    http://www.carrona.org/drivers/driver.php?id=RTKVHD64.sys
    http://www.carrona.org/drivers/driver.php?id=bwcW8x64.sys
    http://www.carrona.org/drivers/driver.php?id=atikmpag.sys
    http://www.carrona.org/drivers/driver.php?id=atikmdag.sys
    tmp33B2.tmp - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed.
    tmp3076.tmp - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed.
    http://www.carrona.org/drivers/driver.php?id=ISCTD64.sys
    http://www.carrona.org/drivers/driver.php?id=atikmpag.sys
    http://www.carrona.org/drivers/driver.php?id=atikmdag.sys
    http://www.carrona.org/drivers/driver.php?id=dump_storahci.sys
    mrxsmb30.sys - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed.

    There are lots of drivers in the Dump files having the TMP extension. This kind of behaviour is shown by the WinRing Service. I checked your Event Logs and found that the service is being installed remotely. Kindly do a system wide search for "WinRing0x64.sys" and see the location where it is found. If you are not able to find that driver, kindly do a system wide search for the term "WinRing" and report back with the findings.

    Also, in the first dump file, the Killer Network Manger is blamed. This has caused problems in the past. I would suggest you to follow the below quote (Follow Note 2 first. If it does not work, follow note 1) -
    (Thanks Usasma!)At times the Killer Network Manager may cause BSOD problems:

    NOTE1:Link thanks to blueelvis (15Oct2014): https://forum-en.msi.com/index.php?topic=178064.0 This is a method for removing all the network software and only installing the driver. Perfect for those issues that can't be resolved any other way!

    NOTE2: See this link first: BSOD while playing on msi gt70 dragon edition 2 (thanks to kaelaan) It appears that the Killer Service problem was solved with the latest release of the Qualcomm versions of the drivers (so try updating to a version dated from later in 2014).
    The Qualcomm Atheros Killer Service/KillerNetManager is known to cause BSOD's. Please follow the workaround instructions here:

    First, open the Run dialog (Win + R keys) and type in "services.msc" (without the quotes) and press Enter
    Scroll down and locate the "Qualcomm Atheros Killer Service" and right click on it. Select "Stop"
    Right click on it again and this time select "Properties"
    In the dropdown box for "Startup type", select "Disabled", then click on the "OK" button at the bottom of the window

    Next, open Task Manager (right click on TaskBar and select "Task Manager")
    Click on the "More details" dropdown (if present)
    Click on the "Startup" tab
    Scroll down and locate the "KillerNetManager" entry, right click on it and select "Disable"
    There may also be an Install Shield (with the Killer gaming K next to it), if so Right click on it and select "Disable"
    Finally, restart the system in order for the changes to take affect.


    At times the Killer Network Manager will continue to load. If so, it's usually listed in the MSINFO32...Software Environment...Startup Programs section. If it is, please try this:

    It may be that the instructions aren't stopping everything.
    In some cases, there's a program running out of the Program Files/Program Files (x86) directory.
    "c:\program files\qualcomm atheros\killer network manager\killer~1.exe" (NOTE: killer~1.exe is most likely killernetmanager.exe)
    In other cases, there's a program running out of c:\windows\installer\{Long string of letters, numbers, and dashes}\networkmanager.exe_130c27d738f34c89bddf21bcfd74b56d.exe (the long string of letters and numbers may change)

    Here's some things to try
    1) Please see if there are any entries in the Startup tab of Task Manager that are related to Qualcomm/Atheros/Killer Network Manager (and NOT the card itself) and disable them (please let us know what you find) Be careful as the wrong selection can disable the network card.
    2) Check in "msconfig" for any entries that aren't in the Startup tab of Task Manager. Let us know if you find any Qualcomm/Atheros/Killer entries there (we'll disable them differently if they are there).
    3) Locate the "c:\program files\qualcomm atheros\killer network manager\killer~1.exe" and rename the .exe to .BAD (the killer~1 is actually a filename that starts with killer and ends with .exe) There will be an error in event viewer, but it'll stop the bugger from loading.
    4) Locate the "c:\windows\installer\{Long string of letters, numbers, and dashes}\networkmanager.exe_130c27d738f34c89bddf21bcfd74b56d.exe" entry and rename the last .exe to .BAD (the long string of letters and numbers may change)

    Just FYI - here are the MSI workaround instructions: MSI USA - Online Technical Support FAQ







    Also, the bug check code is random. I would suggest you to run the Hardware Diagnostics over here -
    Hardware Diagnostics

    Let me know how it goes ^_^
      My System SpecsSystem Spec

  5. #5


    Posts : 3
    windows 8.1


    Hey man
    It the killer network manager! after i did as u instructed, it hasnt stopped in the past 12 hrs.

    Thanks so much man!
    U have done something that was impossible to solve most of the technicians here in Australia

    Hats Off!
      My System SpecsSystem Spec

Kernal Power Error ID 41 Windows 8.1
Related Threads
I was recently checking the event viewer for errors and I noticed since August 16 I am having a huge pile of errors 90% coming from Kernal-EventTracing, event ID 2. I have tried troubleshooting yesterday for hours but could not find a solution. Even with a clean boot (disabling all non-Microsoft...
Hi all, I have a newly built computer (custom build), which has been plaguing me for awhile now. Built it, and did not seem to have issues for a few days, but within the first week, started suffering from two main issues. The first to surface was that when I told it to shutdown, it would...
- This is a pretty much brand new laptop, that worked for 5 weeks no problem, but since changing country's and setting up my own wifi hotspot this seems to be happening. Below is the event log, and attached is the dm Log Collector file. It also seems to happen whilst watching netflix, but...
Hello everyone, I've recently built a new system using the X99 platform and have been experiencing a problem. Every once and a while, my PC will just randomly restart with no BSOD screen. I have ran Prime95 on Blend mode for 8 hours with no errors and haven't been able to replicate the...
Kernal-Power 41-63 Forced Reboots in BSOD Crashes and Debugging
Problem: Win 8 machine has forced reboots every 20 min while left unattended and a few time while attended. The problem first arose after trying to install a scanner driver for an older dell black laser printer/scanner/fax. Never got the scanner working, but now the PC keeps rebooting and...
Kernal 41 Error in BSOD Crashes and Debugging
Have looked everywhere and had tried various methods on how to solved this. Am having a very frustrating time with this. My Computer will suddenly freeze up and will not respond and will be forced to hold down the power button or cut the power. This happens 2-3 times a day and would be grateful...
Solved Windows 8 Kernel Power error in General Support
I installed clean Windows 8. I checked the event viewer to see if everything is OK. But it has 4 critical error and they were all Kernel Power Error. I noticed these Kernel Power Errors are caused by when I restart my PC. Example is when I installed Photoshop, I restarted and I checked the Event...
Eight Forums Android App Eight Forums IOS App Follow us on Facebook