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,176
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.
kemical
Essential Member
- Joined
- Aug 28, 2007
- Messages
- 36,176
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/
kemical
Essential Member
- Joined
- Aug 28, 2007
- Messages
- 36,176
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.
Similar threads
- Replies
- 3
- Views
- 1K
- Replies
- 1
- Views
- 555
- Replies
- 2
- Views
- 3K
- Solved
Windows 7
Window Driver Framework Violation BSOD
- Replies
- 1
- Views
- 4K
- Replies
- 1
- Views
- 1K