Code:
Loading Dump File [D:\Kingston\BSODDmpFiles\AJZ\040312-10545-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.17727.amd64fre.win7sp1_gdr.111118-2330
Machine Name:
Kernel base = 0xfffff800`0324a000 PsLoadedModuleList = 0xfffff800`0348e650
Debug session time: Tue Apr 3 16:12:52.666 2012 (UTC - 6:00)
System Uptime: 0 days 2:27:39.509
Loading Kernel Symbols
...............................................................
................................................................
............................................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1E, {0, 0, 0, 0}
Probably caused by : ntkrnlmp.exe ( nt!KiKernelCalloutExceptionHandler+e )
Followup: MachineOwner
---------
0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
KMODE_EXCEPTION_NOT_HANDLED (1e)
This is a very common bugcheck. Usually the exception address pinpoints
the driver/function that caused the problem. Always note this address
as well as the link date of the driver/image that contains this address.
Arguments:
Arg1: 0000000000000000, The exception code that was not handled
Arg2: 0000000000000000, The address that the exception occurred at
Arg3: 0000000000000000, Parameter 0 of the exception
Arg4: 0000000000000000, Parameter 1 of the exception
Debugging Details:
------------------
EXCEPTION_CODE: (Win32) 0 (0) - The operation completed successfully.
FAULTING_IP:
+6634393064363435
00000000`00000000 ?? ???
EXCEPTION_PARAMETER1: 0000000000000000
EXCEPTION_PARAMETER2: 0000000000000000
ERROR_CODE: (NTSTATUS) 0 - STATUS_WAIT_0
BUGCHECK_STR: 0x1E_0
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
PROCESS_NAME: System
CURRENT_IRQL: 2
EXCEPTION_RECORD: fffff80000b9c268 -- (.exr 0xfffff80000b9c268)
ExceptionAddress: fffff800032d188a (nt!KiProcessExpiredTimerList+0x000000000000004a)
ExceptionCode: c000001d (Illegal instruction)
ExceptionFlags: 00000000
NumberParameters: 0
TRAP_FRAME: fffff80000b9c310 -- (.trap 0xfffff80000b9c310)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000002 rbx=0000000000000000 rcx=fffffa80127eb650
rdx=fffffa8010b40e60 rsi=0000000000000000 rdi=0000000000000000
rip=fffff800032d188a rsp=fffff80000b9c4a0 rbp=000000000008aa69
r8=fffffa800d13db50 r9=000000000000006a r10=fffff8000343be80
r11=fffffa800d13daf0 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei ng nz na pe nc
nt!KiProcessExpiredTimerList+0x4a:
fffff800`032d188a f00fba2b07 lock bts dword ptr [rbx],7 ds:0088:00000000`00000000=????????
Resetting default scope
LAST_CONTROL_TRANSFER: from fffff800032be6fe to fffff800032c6d10
STACK_TEXT:
fffff800`00b9b348 fffff800`032be6fe : 00000000`00000000 00000000`00000000 fffff800`00b9bac0 fffff800`032f1da0 : nt!KeBugCheck
fffff800`00b9b350 fffff800`032f1a6d : fffff800`034cf71c fffff800`0340c078 fffff800`0324a000 fffff800`00b9c268 : nt!KiKernelCalloutExceptionHandler+0xe
fffff800`00b9b380 fffff800`032f0845 : fffff800`0340ffac fffff800`00b9b3f8 fffff800`00b9c268 fffff800`0324a000 : nt!RtlpExecuteHandlerForException+0xd
fffff800`00b9b3b0 fffff800`033017c1 : fffff800`00b9c268 fffff800`00b9bac0 fffff800`00000000 fffff800`00b9c4e0 : nt!RtlDispatchException+0x415
fffff800`00b9ba90 fffff800`032c63c2 : fffff800`00b9c268 fffffa80`1121cc20 fffff800`00b9c310 00000000`00000003 : nt!KiDispatchException+0x135
fffff800`00b9c130 fffff800`032c451f : fffff800`00b9c310 fffffa80`10c94902 fffffa80`42554800 fffffa80`00000000 : nt!KiExceptionDispatch+0xc2
fffff800`00b9c310 fffff800`032d188a : fffffa80`0d13db30 fffffa80`1121cc68 fffffa80`1121cc68 00000000`00000000 : nt!KiInvalidOpcodeFault+0x11f
fffff800`00b9c4a0 fffff800`032d17ee : 00000014`a0ade3ac fffff800`00b9cb18 00000000`0008aa69 fffff800`0343efa8 : nt!KiProcessExpiredTimerList+0x4a
fffff800`00b9caf0 fffff800`032d15d7 : 00000006`a5f795c2 00000006`0008aa69 00000006`a5f7953f 00000000`00000069 : nt!KiTimerExpiration+0x1be
fffff800`00b9cb90 fffff800`032bea6a : fffff800`0343be80 fffff800`03449cc0 00000000`00000000 fffff880`00000000 : nt!KiRetireDpcList+0x277
fffff800`00b9cc40 00000000`00000000 : fffff800`00b9d000 fffff800`00b97000 fffff800`00b9cc00 00000000`00000000 : nt!KiIdleLoop+0x5a
STACK_COMMAND: kb
FOLLOWUP_IP:
nt!KiKernelCalloutExceptionHandler+e
fffff800`032be6fe 90 nop
SYMBOL_STACK_INDEX: 1
SYMBOL_NAME: nt!KiKernelCalloutExceptionHandler+e
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 4ec79dd2
FAILURE_BUCKET_ID: X64_0x1E_0_nt!KiKernelCalloutExceptionHandler+e
BUCKET_ID: X64_0x1E_0_nt!KiKernelCalloutExceptionHandler+e
Followup: MachineOwner
---------
It is difficult to analyze one .dmp file and find patterns, especially when the .dmp file is inconclusive as yours is. Possible causes are Memory problems... Viruses... Corrupted hard disk file system... Corrupted System Files... Lack of Windows updates... Drivers...
Start with the following tests to see if we can narrow down the cause more:- If you are overclocking any hardware, please stop.
- Run SFC /SCANNOW Command - System File Checker up to three times to fix all errors with a restart in between each. Post back if it continues to show errors after a fourth run or if the first run comes back with no integrity violations.
- Run the boot version of Memtest86+ paying close attention to Parts 2 and 3 of the tutorial. Also, in case Memtest86+ misses anything and comes up with no errors, run the extended version of the Windows Memory Diagnostics Tool for at least five passes. These you may want to run overnight since they take a long time to complete (run them an hour before bed each of the next two nights and check before going to sleep that they are still running).
If you swap any memory components, follow these steps for ESD safety:
- Shut down and turn off your computer.
- Unplug all power supplies to the computer (AC Power then battery for laptops, AC power for desktops)
- Hold down the power button for 30 seconds to close the circuit and ensure all power drains from components.
- Make sure you are grounded by using proper grounding techniques, i.e. work on an anti-static workbench, anti-static desk, or an anti-static pad. Hold something metallic while touching it to the anti-static surface, or use an anti-static wristband to attach to the anti-static material while working.
Once these steps have been followed, it is safe to remove and replace components within your computer.
- An underlying driver may be incompatible\conflicting with your system. Run Driver Verifier to find any issues. To run Driver Verifier, do the following:
a.
Backup your system and user files
b.
Create a system restore point
c. If you do not have a Windows 7 DVD,
Create a system repair disc
d. In Windows 7:
- Click the Start Menu
- Type verifier in Search programs and files (do not hit enter)
- Right click verifier and click Run as administrator
- Put a tick in Create custom settings (for code developers) and click next
- Put a tick in Select individual settings from a full list and click next
- Set up the individual settings as in the image and click next
Attachment 205837 - Put a tick in Select driver names from a list
- Put a tick next to all non-Microsoft drivers.
- Click Finish.
- Restart your computer.
If Windows cannot start in normal mode with driver verifier running, start in safe mode. If it cannot start in safe mode or normal mode, restore the system restore point using
System Restore OPTION TWO.
Thanks to zigzag3143 for contributing to the Verifier steps.
If you are unable to start Windows with all drivers being verified or if the blue screen crashes fail to create .dmp files, run them in groups of 5 or 10 until you find a group that causes blue screen crashes and stores the blue screen .dmp files.
The idea with Verifier is to cause the system to crash, so do the things you normally do that cause crashes. After you have a few crashes, upload the crash reports for us to take a look and try to find patterns.
Also, please follow the https://www.sevenforums.com/crashes-d...tructions.html to provide us with more information regarding your crashes so we can give more specific troubleshooting steps.