Code:
-
Loading Dump File [C:\Users\Mike\Downloads\BSODDmpFiles\whomeno\Windows_NT6_BSOD_jcgriff2\112211-14203-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 7601 (Service Pack 1) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17514.x86fre.win7sp1_rtm.101119-1850
Machine Name:
Kernel base = 0x82816000 PsLoadedModuleList = 0x82960850
Debug session time: Tue Nov 22 17:40:24.511 2011 (UTC - 7:00)
System Uptime: 0 days 0:29:36.589
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}
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+50ed0d )
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
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
PROCESS_NAME: System
CURRENT_IRQL: 2
LAST_CONTROL_TRANSFER: from 8e51fd0d to 8285504b
STACK_TEXT:
8293e6a0 8e51fd0d badb0d00 00000000 85de4a10 nt!KiTrap00+0x8b
WARNING: Stack unwind information not available. Following frames may be wrong.
8293e710 85db5064 848bb000 863d5000 00000000 nvlddmkm+0x50ed0d
8293e814 8e456cdd 863d5000 848bb000 85db5064 0x85db5064
8293e96c 8e527710 85db5750 85db5064 85db56e8 nvlddmkm+0x445cdd
8293e9a0 8e52ab6b 863d5000 848bb000 85dbf364 nvlddmkm+0x516710
8293e9dc 8e52aef3 8293ea20 8293ea34 863d5000 nvlddmkm+0x519b6b
8293ea58 8e52b133 863d5000 848bb000 00000000 nvlddmkm+0x519ef3
8293ea8c 8e3f80bc 00000002 00000001 00000000 nvlddmkm+0x51a133
8293eb74 8e313fe9 04000000 848c60f8 00000000 nvlddmkm+0x3e70bc
8293eb90 8e186c90 00000000 848c60f8 8e99f2f8 nvlddmkm+0x302fe9
8293ec34 8e0bc5e3 86034000 848c60f8 86034000 nvlddmkm+0x175c90
8293ec58 8e0356f5 82943600 86034078 8294b404 nvlddmkm+0xab5e3
8293ec6c 8e035369 8e0356c3 8293ecd4 8288e1b5 nvlddmkm+0x246f5
8293ec78 8288e1b5 86034078 86034000 00000000 nvlddmkm+0x24369
8293ecd4 8288e018 82941d20 8294b380 00000000 nt!KiExecuteAllDpcs+0xf9
8293ed20 8288de38 00000000 0000000e 00000000 nt!KiRetireDpcList+0xd5
8293ed24 00000000 0000000e 00000000 00000000 nt!KiIdleLoop+0x38
STACK_COMMAND: kb
FOLLOWUP_IP:
nvlddmkm+50ed0d
8e51fd0d ?? ???
SYMBOL_STACK_INDEX: 1
SYMBOL_NAME: nvlddmkm+50ed0d
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nvlddmkm
IMAGE_NAME: nvlddmkm.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4e992973
FAILURE_BUCKET_ID: 0x7f_0_nvlddmkm+50ed0d
BUCKET_ID: 0x7f_0_nvlddmkm+50ed0d
Followup: MachineOwner
---------
-
Loading Dump File [C:\Users\Mike\Downloads\BSODDmpFiles\whomeno\Windows_NT6_BSOD_jcgriff2\112211-14484-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 7601 (Service Pack 1) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17514.x86fre.win7sp1_rtm.101119-1850
Machine Name:
Kernel base = 0x82842000 PsLoadedModuleList = 0x8298c850
Debug session time: Tue Nov 22 17:44:51.940 2011 (UTC - 7:00)
System Uptime: 0 days 0:03:32.018
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}
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+50ed0d )
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
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
PROCESS_NAME: svchost.exe
CURRENT_IRQL: 2
LAST_CONTROL_TRANSFER: from 8f110d0d to 8288104b
STACK_TEXT:
8078a970 8f110d0d badb0d00 00000000 85e10418 nt!KiTrap00+0x8b
WARNING: Stack unwind information not available. Following frames may be wrong.
8078a9e0 85dd5064 848bb000 85dd1000 00000000 nvlddmkm+0x50ed0d
8078aae4 8f047cdd 85dd1000 848bb000 85dd5064 0x85dd5064
8078ac3c 8f118710 85dd5750 85dd5064 85dd56e8 nvlddmkm+0x445cdd
8078ac70 8f11bb6b 85dd1000 848bb000 85df1364 nvlddmkm+0x516710
8078acac 8f11bef3 8078acf0 8078ad04 85dd1000 nvlddmkm+0x519b6b
8078ad28 8f11c133 85dd1000 848bb000 00000000 nvlddmkm+0x519ef3
8078ad5c 8efe90bc 00000002 00000001 00000000 nvlddmkm+0x51a133
8078ae44 8ef04fe9 04000000 848c60f8 00000000 nvlddmkm+0x3e70bc
8078ae60 8ed77c90 00000000 848c60f8 8f5902f8 nvlddmkm+0x302fe9
8078af04 8ecad5e3 85fe0000 848c60f8 85fe0000 nvlddmkm+0x175c90
8078af28 8ec266f5 8296f600 85fe0078 849d9dcc nvlddmkm+0xab5e3
8078af3c 8ec26369 8ec266c3 8078afa4 828ba1b5 nvlddmkm+0x246f5
8078af48 828ba1b5 85fe0078 85fe0000 00000000 nvlddmkm+0x24369
8078afa4 828ba018 8296dd20 849d9d48 00000000 nt!KiExecuteAllDpcs+0xf9
8078aff4 828b97dc 9d5a1ce4 00000000 00000000 nt!KiRetireDpcList+0xd5
8078aff8 9d5a1ce4 00000000 00000000 00000000 nt!KiDispatchInterrupt+0x2c
828b97dc 00000000 0000001a 00d6850f bb830000 0x9d5a1ce4
STACK_COMMAND: kb
FOLLOWUP_IP:
nvlddmkm+50ed0d
8f110d0d ?? ???
SYMBOL_STACK_INDEX: 1
SYMBOL_NAME: nvlddmkm+50ed0d
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nvlddmkm
IMAGE_NAME: nvlddmkm.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4e992973
FAILURE_BUCKET_ID: 0x7f_0_nvlddmkm+50ed0d
BUCKET_ID: 0x7f_0_nvlddmkm+50ed0d
Followup: MachineOwner
---------
Those were the only two I could load so far. I will try on my other computer. In the meantime, these drivers need to be updated:
Code:
ASACPI 9648d000 9648e420 Thu Aug 12 20:52:52 2004 (411c2d04) 00004aa7 ASACPI.sys
vncmirror 96571000 96578000 Fri Mar 14 11:42:46 2008 (47dab916) 00007111 vncmirror.sys
Rtnicxp 964dd000 964ec000 Fri May 30 09:12:11 2008 (4840194b) 00018af7 Rtnicxp.sys
ADIHdAud 966b5000 96716000 Fri Jan 16 07:59:37 2009 (4970a0d9) 0006ae0e ADIHdAud.sys
vsmraid 88aa4000 88ac9000 Fri Jan 30 18:13:29 2009 (4983a5b9) 00029423 vsmraid.sys
dump_vsmraid 9677f000 967a4000 Fri Jan 30 18:13:29 2009 (4983a5b9) 00029423 dump_vsmraid.sys
Of the above, ASACPI.SYS is a known BSOD problem on Windows 7. Update the driver by:
1. Going to the Asus motherboard support site
When you reach the website:
2. Scroll down the page and click Utilities
3. Hold Ctrl and press f (ctrl+f) to enter the browser's find feature
4. Search for "ATK0110 driver for WindowsXP/Vista/Win7 32&64-bit" (without quotes)
5. Download and install the driver.
6. After installation is complete, verify that it installed correctly.
a. Click Start Menu
b. Click My Computer
c. Go to C:\WIndows\System32\drivers\
d. Verify that the ASACPI.SYS file is dated 2009 or newer (2010,etc.)
Thanks to JMH and zigzag3143 for the above information.
Let us know if the above steps fix your issue. Otherwise, we have other steps to try.