📎 AI Summary:
The forum thread discusses a user experiencing recurring Blue Screen of Death (BSOD) errors, specifically related to "DPC Watchdog Violation," while playing League of Legends on a Windows laptop. The initial issue was linked to the Intel graphics driver (igdkmd64.sys), and solutions involved updating or reinstalling the driver, as well as running system scans (sfc /scannow) and memtest to identify potential corruption. Over time, the user’s system showed file corruption affecting drivers, prompting suggestions for a clean Windows reinstall to resolve the underlying issues. Overall, the conversation is focused on troubleshooting and resolving driver-related BSODs with a cautious, problem-solving tone.

wakamu

New Member
Joined
Dec 17, 2013
Messages
4
Thread Author #1
Hi, whenever I play League of Legends now, I get BSOD that claim DPC Watchdog Violation.

I had a previous igdkmd64.sys driver irql not less or equal error that was seemingly fixed by removing Norton a week ago. Since then, I had no bsod's playing LoL until today.
 

Attachments

Solution
Code:
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 133, {0, 501, 500, 0}

*** WARNING: Unable to verify timestamp for igdkmd64.sys
*** ERROR: Module load completed but symbols could not be loaded for igdkmd64.sys
Probably caused by : igdkmd64.sys ( igdkmd64+63379 )

Followup: MachineOwner

Hi,
same again Intel display...

kemical

Essential Member
Joined
Aug 28, 2007
Messages
36,160
Code:
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 133, {0, 501, 500, 0}

*** WARNING: Unable to verify timestamp for igdkmd64.sys
*** ERROR: Module load completed but symbols could not be loaded for igdkmd64.sys
Probably caused by : igdkmd64.sys ( igdkmd64+63379 )

Followup: MachineOwner

Please update your Intel graphics driver:
http://support.toshiba.com/support/modelHome?freeText=1200007392
Laptop drivers are supplied by the manufacturer so please make sure I have the correct model in the link above.
 

wakamu

New Member
Joined
Dec 17, 2013
Messages
4
Thread Author #3
Thank you~

So far, there have been no BSOD's. I'll post back if any still happen.
 

kemical

Essential Member
Joined
Aug 28, 2007
Messages
36,160
Code:
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 133, {0, 501, 500, 0}

*** WARNING: Unable to verify timestamp for igdkmd64.sys
*** ERROR: Module load completed but symbols could not be loaded for igdkmd64.sys
Probably caused by : igdkmd64.sys ( igdkmd64+63379 )

Followup: MachineOwner

Hi,
same again Intel display driver. Try using this application to remove the old driver and then re-install:
Link Removed

You can obtain new copies from the link above. Just check the os to see if any files have become corrupted. Right click in the bottom left hand corner of the screen and click on admin command prompt. Type:
sfc /scannow
Press enter and await results.

Try running memtest86:
http://www.memtest.org/
 

Solution

wakamu

New Member
Joined
Dec 17, 2013
Messages
4
Thread Author #6
Yes, it said stuff had been corrupted. (uploaded cbs log below)

I'll run the memtest over night while sleeping.
 

Attachments

kemical

Essential Member
Joined
Aug 28, 2007
Messages
36,160
Code:
2014-02-17 03:59:07, Info                  CSI    000004b5 [SR] Cannot repair member file [l:36{18}]"Amd64\CNBJ2530.DPB" of prncacla.inf, Version = 6.3.9600.16384, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type = [l:24{12}]"driverUpdate", TypeName neutral, PublicKey neutral in the store, hash mismatch
2014-02-17 03:59:13, Info                  CSI    000004b6 Hashes for file member \SystemRoot\WinSxS\amd64_prncacla.inf_31bf3856ad364e35_6.3.9600.16384_none_9590ba64d5b91f79\Amd64\CNBJ2530.DPB do not match actual file [l:36{18}]"Amd64\CNBJ2530.DPB" :
  Found: {l:32 b:e6aeGcWF/T38nCcBHUsKpxH8n/ntmcWin0e7A1/84K0=} Expected: {l:32 b:n520k714Uu3utHa5JGQ6HQYbZphKhlMWq5pEmfnCDuw=}
2014-02-17 03:59:13, Info                  CSI    000004b7 [SR] Cannot repair member file [l:36{18}]"Amd64\CNBJ2530.DPB" of prncacla.inf, Version = 6.3.9600.16384, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type = [l:24{12}]"driverUpdate", TypeName neutral, PublicKey neutral in the store, hash mismatch

Looks like from the above that files relating to the processor have become corrupt. You can always try a 'Refresh' but personally I would do a clean install booting off the windows 8 install disk.