New
#21
This was caused by the generic monitor.sys that Windows loads for your monitor, and it appears to be related to the brightness calculation causing a divide by zero fault. Unfortunately, I do not see any obvious reason for this to occur. Try uninstalling your monitor driver in safe mode. To do so, you will need to setup your computer to shut down manually:Code:Loading Dump File [C:\Users\Mike\Downloads\BSODDmpFiles\mraimondi\Windows_NT6_BSOD_jcgriff2\123011-59217-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: SRV*c:\users\mike\documents\symbols*http://msdl.microsoft.com/download/symbols Executable search path is: Windows 7 Kernel Version 7600 MP (2 procs) Free x86 compatible Product: WinNt, suite: TerminalServer SingleUserTS Personal Built by: 7600.16905.x86fre.win7_gdr.111025-1503 Machine Name: Kernel base = 0x81a43000 PsLoadedModuleList = 0x81b8b810 Debug session time: Fri Dec 30 13:30:51.409 2011 (UTC - 7:00) System Uptime: 0 days 0:00:47.221 Loading Kernel Symbols ............................................................... .............................................. Loading User Symbols Loading unloaded module list . ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 7F, {0, 0, 0, 0} Probably caused by : monitor.sys ( monitor!BrightnessTargetToPercentage+32 ) Followup: MachineOwner --------- 0: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* UNEXPECTED_KERNEL_MODE_TRAP (7f) This means a trap occurred in kernel mode, and it's a trap of a kind that the kernel isn't allowed to have/catch (bound trap) or that is always instant death (double fault). The first number in the bugcheck params is the number of the trap (8 = double fault, etc) Consult an Intel x86 family manual to learn more about what these traps are. Here is a *portion* of those codes: If kv shows a taskGate use .tss on the part before the colon, then kv. Else if kv shows a trapframe use .trap on that value Else .trap on the appropriate frame will show where the trap was taken (on x86, this will be the ebp that goes with the procedure KiTrap) Endif kb will then show the corrected stack. Arguments: Arg1: 00000000, EXCEPTION_DIVIDED_BY_ZERO Arg2: 00000000 Arg3: 00000000 Arg4: 00000000 Debugging Details: ------------------ BUGCHECK_STR: 0x7f_0 TRAP_FRAME: 87453590 -- (.trap 0xffffffff87453590) ErrCode = 00000000 eax=00002710 ebx=00000000 ecx=00000000 edx=00000000 esi=907dea88 edi=6f821738 eip=8bfbf64a esp=87453604 ebp=87453604 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: 8bfbf64a f7f1 div eax,ecx Resetting default scope CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT PROCESS_NAME: System CURRENT_IRQL: 0 LOCK_ADDRESS: 81ba8f60 -- (!locks 81ba8f60) Resource @ nt!PiEngineLock (0x81ba8f60) 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. 1 total locks PNP_TRIAGE: Lock address : 0x81ba8f60 Thread Count : 0 Thread address: 0x00000000 Thread wait : 0x0 LAST_CONTROL_TRANSFER: from 8bfbf64a to 81a872eb STACK_TEXT: 87453590 8bfbf64a badb0d00 00000000 00002004 nt!KiTrap00+0x8b 87453604 8bfbf95a 6f821738 6f821764 8bfbd248 monitor!BrightnessTargetToPercentage+0x32 87453620 8bfc0343 6f821764 860634c8 8ce29ec8 monitor!BrightnessInit+0x98 8745373c 860352c3 731d6180 87453778 860634c8 monitor!EvtDriverDeviceAdd+0x3c3 87453758 86035755 731d6180 87453778 8da6b910 Wdf01000!FxDriverDeviceAdd::Invoke+0x28 87453964 86035821 91ff04b0 8745398c 81a57767 Wdf01000!FxDriver::AddDevice+0xc1 87453970 81a57767 8da6b910 91ff04b0 8fbfb3e8 Wdf01000!FxDriver::AddDevice+0x1b 8745398c 81bf27cf 91ff04b0 86035806 00000004 nt!PpvUtilCallAddDevice+0x19 874539d4 81beb306 8da6b910 86035806 00000002 nt!PnpCallAddDevice+0xb9 87453aa8 81bea892 8fbfb3e8 87453cd0 8d80b538 nt!PipCallDriverAddDevice+0x565 87453ca4 81be4636 83191208 8d80b538 87453cd0 nt!PipProcessDevNodeTree+0x15d 87453cd8 81a56f7f 81ba6e80 831ca798 81b7d5bc nt!PiProcessReenumeration+0x74 87453d00 81ab106b 00000000 00000000 831ca798 nt!PnpDeviceActionWorker+0x224 87453d50 81c51a55 00000001 9eee4584 00000000 nt!ExpWorkerThread+0x10d 87453d90 81b03219 81ab0f5e 00000001 00000000 nt!PspSystemThreadStartup+0x9e 00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x19 STACK_COMMAND: kb FOLLOWUP_IP: monitor!BrightnessTargetToPercentage+32 8bfbf64a f7f1 div eax,ecx SYMBOL_STACK_INDEX: 1 SYMBOL_NAME: monitor!BrightnessTargetToPercentage+32 FOLLOWUP_NAME: MachineOwner MODULE_NAME: monitor IMAGE_NAME: monitor.sys DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bc286 FAILURE_BUCKET_ID: 0x7f_0_monitor!BrightnessTargetToPercentage+32 BUCKET_ID: 0x7f_0_monitor!BrightnessTargetToPercentage+32 Followup: MachineOwner ---------
1. Click Start Menu
2. Click All Programs
3. Click Accessories
4. Click command prompt
5. Type in shutdown /r /t 300 (five minutes should be enough time to uninstall the monitor driver before the computer restarts) and hit enter
To uninstall the monitor:
1. Click Start Menu
2. Right click My Computer/Computer
3. Click Manage
4. Click Device Manager from the list on the left
5. Click and expand Monitors
6. Right click your monitor
7. Click Uninstall
8. Click OK.
You may lose your monitor at this point, but it will restart on its own within five minutes, Windows will load, and the driver will be reloaded (hopefully correctly this time). Post back your results. :)
No monitor is listed there!
Ah, you're right. In safe mode, it does not show up... Let me look into how to get around that issue.
Alright, I found the solution:
Run an elevated command prompt:
1. Click Start Menu
2. Click All Programs
3. Click Accessories
4. Right click Command Prompt
5. Click Run as administrator
6. Type into command prompt “set devmgr_show_nonpresent_devices=1″ without quotes
7. Hit enter.
8. Type “devmgmt.msc” without quotes
9. Click View (at the top)
10. Check Show hidden devices
Now you can click to expand the Monitors and uninstall
Ok, I can still try this, but while I was in device manager, I uninstalled the display adapter. There were two listed. Windows restarted in normal mode, but the display is a generic driver with low resolution. Should I try to find a display driver and install it?
Also, some of the windows updates rolled back since they failed proper installation.
Installed the correct driver, restarted, crashed. Attached the BSOD files again.
So it runs with a generic driver, crashes with the intel driver.
But, when I first reformatted, it ran with the intel driver at normal resolution. Strange, huh?
Yeah, you definitely have a strange problem here. Have you tried uninstalling the monitor.sys in safe mode?
Im in devmngr, with "everything" shown now, but still no monitor?! Interestingly, "Security Processor Loader Driver" has a ! on it. Probably not related, though, huh? Just uninstalled graphics driver again. I'll try finding the driver buried in the restore partition, and see how it works.