Solved Event ID 41, Kernel-Power error...

Cr00zng

New Member
Member
Messages
196
I've been getting periodic errors, event ID 41 that states:

The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.

Well, I didn't loose power, the system stopped responding, but didn't crash with a BSOD...

The frequency of this error seems random, that hangs the system and then reboots without warning:

eventID41.jpg

The event ID 41 is always proceeded by two event ID 6, information level about the "FilterManager":

kernel43.jpg

There seems to be no rime and reason as to why this event is taking place. I could be just browsing the web with FF/IE, working on some MS Office documents, business programs, etc., and boom, down she goes...

The KB2028504 article points to hardware failure, overheating, overclocking, etc., but... The system runs with default clock settings, neither the CPU, nor the memory overclocked. This system also runs Windows 7 SP1 Professional 64-bits, dual-boot, that has no issues with random reboots, or any other problems for that matter.

Is there a way to disable loading the "FilterManager" for testing purposes?
 

My Computer

System One

  • OS
    Win 8.1
    Computer type
    PC/Desktop
    System Manufacturer/Model
    Dell Latitude
    CPU
    Intel i5-3350P (3.1 GHz)
    Motherboard
    Gigabyte
    Memory
    16 GBs
    Graphics Card(s)
    AMD Radeon HD7850
    Sound Card
    Built-in to MB
    Monitor(s) Displays
    2 x 24" Dell
    Screen Resolution
    3,840 x1,200
    Hard Drives
    128 GBs, OCZ Vertex, SATA III SSD
    256 GBs Intel SATA III SSD
    3 x Seagate 1 TBs HDD
    PSU
    Antec 750W
    Case
    Antec P185
    Internet Speed
    50 Gb/s
    Browser
    IE11, Firefox22.0
    Antivirus
    Vipre
    Other Info
    Works, most of the times unless Microsoft patches decide otherwise...
What drivers are loaded by the FilterManager before the crash? Are they the same for every crash? Event id 6 may be more useful for troubleshooting than event id 41 that just states that the system crashed and was automatically restarted. www.eventid.net suggests updating all the drivers, firmware, BIOS, etc., resetting the BIOS settings (jut in case), run hardware diagnostics, though if it works fine in Windows 7 is most probably a driver compatibility issue.
 

My Computer

System One

  • OS
    Windows 7 64-bit
    Computer type
    PC/Desktop
    System Manufacturer/Model
    HP H8-1040
    CPU
    Intel Core i7 2600 @ 3.40GHz
    Motherboard
    Pegatron 2AB5
    Memory
    10 GB
    Graphics Card(s)
    NVIDIA GeForce GTX 550 Ti
    Keyboard
    Logitech G105
    Internet Speed
    200 Mbs
Yes, Windows 7 runs just fine, this issue is only with W8.1.

Hardware being the root cause of the problem while probable, it's unlikely. Not to mention that hardware issues more likely would show up more frequently...

There are no drivers AFAICS, the hard lock happens on an already running system that has been up for a longer period of time. Based on the even viewer, all activities intermediately preceding the hard lock are related to the drives and NTFS checks of the drives:

kernelp43_2.jpg

Maybe MS code, or the Intel driver have some bugs that occasionally causes hard lock...
 

My Computer

System One

  • OS
    Win 8.1
    Computer type
    PC/Desktop
    System Manufacturer/Model
    Dell Latitude
    CPU
    Intel i5-3350P (3.1 GHz)
    Motherboard
    Gigabyte
    Memory
    16 GBs
    Graphics Card(s)
    AMD Radeon HD7850
    Sound Card
    Built-in to MB
    Monitor(s) Displays
    2 x 24" Dell
    Screen Resolution
    3,840 x1,200
    Hard Drives
    128 GBs, OCZ Vertex, SATA III SSD
    256 GBs Intel SATA III SSD
    3 x Seagate 1 TBs HDD
    PSU
    Antec 750W
    Case
    Antec P185
    Internet Speed
    50 Gb/s
    Browser
    IE11, Firefox22.0
    Antivirus
    Vipre
    Other Info
    Works, most of the times unless Microsoft patches decide otherwise...
I used to have this problem for months about 2-3 times a day, but suddenly a few weeks ago it stopped.
I have disabled all logging except system, performed some minor tweaks and I clean journal file each day.

Not sure, if any of it is related, but you might give it a try: fsutil usn deletejournal /d /n c:

P.S.: Some of the loggings are related to Kernel-Power, so who knows.
 

Attachments

  • capture_05132015_213927.jpg
    capture_05132015_213927.jpg
    114.3 KB · Views: 86
  • capture_05132015_213952.jpg
    capture_05132015_213952.jpg
    116.6 KB · Views: 82

My Computer

System One

  • OS
    Win 8.1.1 Pro x64
    Computer type
    Laptop
    System Manufacturer/Model
    Lenovo E525
    CPU
    AMD A4-3300M @ 2,0GHz
    Memory
    6GB DDR3 1333MHz
    Graphics Card(s)
    AMD Radeon HD 6480G 512MB shared
    Sound Card
    Creative Sound Blaster X-Fi Surround 5.1
    Screen Resolution
    1366x768
    Hard Drives
    WD 465GB
    Cooling
    Fusion Tweaker
    Keyboard
    Logitech K360
    Mouse
    Logitech M705
    Internet Speed
    50/50 MBps
    Browser
    Yandex
    Antivirus
    No AV & No Firewall
    Other Info
    Headphones: Sennheiser RS170
Thanks TairikuOkami...

It's been five days that my system didn't have the kernel power error. The relatively large Windows update may have something to do with and as such, I leave it alone for the time being. If it returns, I'll try your suggested solution...
 

My Computer

System One

  • OS
    Win 8.1
    Computer type
    PC/Desktop
    System Manufacturer/Model
    Dell Latitude
    CPU
    Intel i5-3350P (3.1 GHz)
    Motherboard
    Gigabyte
    Memory
    16 GBs
    Graphics Card(s)
    AMD Radeon HD7850
    Sound Card
    Built-in to MB
    Monitor(s) Displays
    2 x 24" Dell
    Screen Resolution
    3,840 x1,200
    Hard Drives
    128 GBs, OCZ Vertex, SATA III SSD
    256 GBs Intel SATA III SSD
    3 x Seagate 1 TBs HDD
    PSU
    Antec 750W
    Case
    Antec P185
    Internet Speed
    50 Gb/s
    Browser
    IE11, Firefox22.0
    Antivirus
    Vipre
    Other Info
    Works, most of the times unless Microsoft patches decide otherwise...
Back
Top