Hi NeoJediX,
BSOD Analysis:
------------------------------------------------------------------
Code:
[COLOR="Red"]BugCheck 7F[/COLOR], {[COLOR="Blue"]0[/COLOR], 0, 0, 0}
Probably caused by : monitor.sys ( monitor!BrightnessTargetToPercentage+32 )
Code:
Usual causes: Memory corruption, Hardware (memory in particular), Overclocking failure, Installing a faulty or mismatched hardware (especially memory) or a failure after installing it, 3rd party firewall, Device drivers, SCSI/network/BIOS updates needed, Improperly seated cards, Incompatible storage devices, Overclocking, Virus scanner, Backup tool, Bad motherboard, Missing Service Pack
The bugcheck indicates that your Intel CPU, generated a trap and the kernel wasn't able to catch this trap.
The error which occurred is here:
Code:
TRAP_FRAME: 86e3b590 -- ([COLOR="SeaGreen"].trap 0xffffffff86e3b590[/COLOR])
ErrCode = 00000000
[COLOR="red"]eax=00000000[/COLOR] ebx=7b241dc0 [COLOR="Red"]ecx=00000000[/COLOR] edx=00000000 esi=84dbe400 edi=84dbe544
eip=a1d0464a esp=86e3b604 ebp=86e3b604 iopl=0 nv up ei pl zr na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010246
monitor!BrightnessTargetToPercentage+0x32:
a1d0464a f7f1 [COLOR="Blue"]div[/COLOR] [COLOR="Red"]eax,ecx[/COLOR]
As we can see, the instruction issued was to divide the
eax and
ecx registers, the registers contain the value 0, and this is illegal operation, you not able to divide a value by 0.
Code:
LOCK_ADDRESS: 81769f60 -- ([COLOR="SeaGreen"]!locks 81769f60[/COLOR])
Resource @ nt!PiEngineLock (0x81769f60) Available
WARNING: SystemResourcesList->Flink chain invalid. Resource may be corrupted, or already deleted.
WARNING: SystemResourcesList->Blink chain invalid. Resource may be corrupted, or already deleted.
I'm going to guess that there may be some form of memory corruption, from what I'm guessing, the linked list for the system resources is now invalid, since the Flink and Blink don't point to correct node or the that node doesn't exist anymore. I've just read that
PiEngineLock is a PnP and Power State lock. I believe a lock is used by a thread to control the access to the resource by other threads.
Code:
0: kd> [COLOR="SeaGreen"]vertarget[/COLOR]
[COLOR="red"]Windows 7 Kernel Version 7600 MP[/COLOR] (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16385.x86fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0x81650000 PsLoadedModuleList = 0x81798810
Debug session time: Wed Jun 26 09:44:14.645 2013 (UTC + 1:00)
System Uptime: 0 days 0:00:36.441
--------------------------------------------------------------------
Steps to Do:
Install Service Pack 1:
Service Pack 1 has provided many security and stability updates for Windows 7, which would be highly beneficial for your system.
Update:
Code:
1: kd> [COLOR="SeaGreen"]lmvm igdkmd32[/COLOR]
start end module name
89804000 89d0c000 igdkmd32 T (no symbols)
Loaded symbol image file: igdkmd32.sys
Image path: \SystemRoot\system32\DRIVERS\igdkmd32.sys
Image name: igdkmd32.sys
Timestamp: [COLOR="Red"]Mon Oct 25 05:10:01 2010 [/COLOR](4CC50319)
CheckSum: 004989CE
ImageSize: 00508000
Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4
Your Intel graphics driver seems to be a possible cause, and is possibly outdated, please first check your model support page for updates, or check for updates from here -
Intel® Driver Update Utility
Run
Driver Verifier to scan for any corrupted drivers which may be causing problems, this program works by running various stress tests on drivers, in order to produce a BSOD which will locate the driver; run for
least 24 hours:
*Note*:The monitor.sys driver will reappear since it's a Windows driver.
