Hello,
I've had quite a lot of blue screens since I installed windows 7. (About 8) It isn't that I force my computer or something, when xp was installed I never got a single blue screen..
Since the blue screen disappears too fast, I can't read what is written =/. I can see this :
irql_not_less_or_equal
I'm wondering how I could fix it? I browsed the forums a bit and found out I have to include my dumpfile, so I attached it.
I don't understand the instructions on how to read/debug the files, so if someone could help me with it?
I know it is probably a lot of work, but those blue screens annoy me...
Thanks!
Hi and welcome
If you have the rest of ths dumps we could use them. The Usual causes: Device driver, hardware, System service, compatibility, Remote control programs, memory, BIOS
Since the probable cause was ntkrnlmp.exe I would run a system file check
type cmd in search>right click and run as admin>>sfc /scannow
If you are overclocking stop.
ken J+
Code:
Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Users\K\Desktop\011610-18969-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*d:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`02e19000 PsLoadedModuleList = 0xfffff800`03056e50
Debug session time: Sat Jan 16 12:08:55.463 2010 (GMT-5)
System Uptime: 0 days 5:20:28.149
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
---------
1: 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:
+57d5952f02b9df64
00000000`00000000 ?? ???
EXCEPTION_PARAMETER1: 0000000000000000
EXCEPTION_PARAMETER2: 0000000000000000
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0x1E
PROCESS_NAME: svchost.exe
CURRENT_IRQL: 0
EXCEPTION_RECORD: fffff88007bc3568 -- (.exr 0xfffff88007bc3568)
ExceptionAddress: fffff88000c2a7eb (ataport!IdePortTranslateSrbToCrb+0x000000000000028f)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000001
Parameter[1]: 0000000020fffff8
Attempt to write to address 0000000020fffff8
TRAP_FRAME: fffff88007bc3610 -- (.trap 0xfffff88007bc3610)
Unable to read trap frame at fffff880`07bc3610
LAST_CONTROL_TRANSFER: from fffff80002e82c2e to fffff80002e8aed0
STACK_TEXT:
fffff880`07bc2648 fffff800`02e82c2e : fffff880`07bc0018 fffff880`01260494 00000000`00000000 fffff800`02ee161b : nt!KeBugCheck
fffff880`07bc2650 fffff800`02eb0bed : fffff800`03095d94 fffff800`02fd8b38 fffff800`02e19000 fffff880`07bc3568 : nt!KiKernelCalloutExceptionHandler+0xe
fffff880`07bc2680 fffff800`02eb8250 : fffff800`02fd8b30 fffff880`07bc26f8 fffff880`07bc3568 fffff800`02e19000 : nt!RtlpExecuteHandlerForException+0xd
fffff880`07bc26b0 fffff800`02ec51b5 : fffff880`07bc3568 fffff880`07bc2dc0 fffff880`00000000 fffffa80`01a40a70 : nt!RtlDispatchException+0x410
fffff880`07bc2d90 fffff800`02e8a542 : fffff880`07bc3568 00000000`00000000 fffff880`07bc3610 fffffa80`026cb7d0 : nt!KiDispatchException+0x135
fffff880`07bc3430 fffff800`02e890ba : 00000000`00000001 00000000`00000000 00000000`00004000 fffff880`00e0112c : nt!KiExceptionDispatch+0xc2
fffff880`07bc3610 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x23a
STACK_COMMAND: kb
FOLLOWUP_IP:
nt!KiKernelCalloutExceptionHandler+e
fffff800`02e82c2e 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: 4a5bc600
FAILURE_BUCKET_ID: X64_0x1E_nt!KiKernelCalloutExceptionHandler+e
BUCKET_ID: X64_0x1E_nt!KiKernelCalloutExceptionHandler+e
Followup: MachineOwner
---------
old drivers
Code:
ASACPI.sys fffff880`04898000 fffff880`048a0000 0x00008000 0x42476c4c 3/27/2005 9:30:36 PM
secdrv.SYS fffff880`04763000 fffff880`0476e000 0x0000b000 0x4508052e 9/13/2006 8:18:38 AM
PxHlpa64.sys fffff880`01088000 fffff880`01093d00 0x0000bd00 0x47d88a39 3/12/2008 8:58:17 PM
Quote