Continuous BSOD Kernel-Power ID 41 BugCheckCode 209

Question

Hello everyone, I have just upgraded my hardware since I'm testing some features with directx 11 and rendering software. 

Unfortunately I'm getting continuous BSOD when I stress my pc with games or rendering.

I've searched online and it looks like the problem can be caused by a lot of different things.

I've attached the dump and honestly I'm not able to debug them. 

Would you please help me understand where is the problem?

Hardware:

PSU 750W

Asus Motherboard P5P43TD PRO

CPU Intel Q9550

Corsair 3x2GB 

Nvidia GeForce GTX 760

SSD Samsung EVO PRO

HD Western Digital Caviar Green

Windows 8.1 Pro

3 System Events:

Event Log Crash 1

Event Log Crash 2

Event Log Crash 3

3 Minidumps: Minidumps on Dropbox

Answer 1

BugCheck D1, {ffffcf81af98cf50, 2, 0, fffff801940ccc69}

Unable to load image \SystemRoot\system32\DRIVERS\L1E62x64.sys, Win32 error 0n2

*** WARNING: Unable to verify timestamp for L1E62x64.sys

*** ERROR: Module load completed but symbols could not be loaded for L1E62x64.sys

Probably caused by : L1E62x64.sys ( L1E62x64+6c69 )

FOLLOWUP_IP:

L1E62x64+6c69

fffff801`940ccc69 4d8b36          mov     r14,qword ptr [r14]

SYMBOL_NAME:  L1E62x64+6c69

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: L1E62x64

IMAGE_NAME:L1E62x64.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4e7ad518

FAILURE_BUCKET_ID:  X64_0xD1_VRF_L1E62x64+6c69

BUCKET_ID:X64_0xD1_VRF_L1E62x64+6c69

Followup: MachineOwner

Loaded symbol image file: L1E62x64.sys

    Image path: \SystemRoot\system32\DRIVERS\L1E62x64.sys

    Image name: L1E62x64.sys

    Timestamp:        Thu Sep 22 02:26:32 2011 (4E7AD518)

Driver Description: Atheros AR8121/AR8113/AR8114 PCI-E Ethernet Controller (NDIS6.20)

Please update the driver noted above, preferably from your system, motherboard or device manufacturer's support website.

You should also look into installing an older driver for nVidia display, if you continue to crash.

Answer 2

If you cant find it, don't worry about it. You are not supposed to check it anyway.

Answer 3

Okay I just went through the Driver Verifier process and now the system crashes at startup blaming "L1E62x64.sys". 

Should I use this guide to solve this? 

http://www.solvusoft.com/en/files/bsod-blue-screen-error/sys/windows/microsoft/windows-8-consumer-preview-iso-images/l1e62x64-sys/

Answer 4

I am trying to use Driver Verifier but I got a question.

In those instructions it says "Don't check these for Win 8" but I can't find the "Concurrency Stress Test".

I checked everything except "Randomized Low Resources Simulation", "DDI Compliance Checking" and "DDI Compliance Checking (additional)". 

What should I do?

Answer 5

SYMBOL_NAME:  tcpip!TcpTcbCarefulDatagram+ea9

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: tcpip

IMAGE_NAME:  tcpip.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  53eebd32

FAILURE_BUCKET_ID:  X64_0xD1_tcpip!TcpTcbCarefulDatagram+ea9

BUCKET_ID:  X64_0xD1_tcpip!TcpTcbCarefulDatagram+ea9

Followup: MachineOwner

---

Use !analyze -v to get detailed debugging information.

BugCheck D1, {ffffe0006dcebdf8, 2, 0, fffff801f95d64bb}

Probably caused by : partmgr.sys ( partmgr!PmIoCompletion+12b )

Followup: MachineOwner

BugCheck D1, {fffff801a1431a17, b, 0, fffff80155b10b3d}

Unable to load image \SystemRoot\system32\DRIVERS\nvlddmkm.sys, Win32 error 0n2

*** WARNING: Unable to verify timestamp for nvlddmkm.sys

*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys

Probably caused by : nvlddmkm.sys ( nvlddmkm+cfb3d )

Three crashes, three different causes. Run driver verifier (DV) per the instructions in the link below, to help pin down the real cause.

Note: Make sure to read and remember the steps to reset DV in the event of a crash, and post a link to the newly generated crash dump here.

Driver Verifier-- tracking down a mis-behaving driver. Created by ZigZag3143, Co.authored by by JMH3143

http://answers.microsoft.com/en-us/windows/wiki/windows_other-system/driver-verifier-tracking-down-a-mis-behaving/f5cb4faf-556b-4b6d-95b3-c48669e4c983