Ok, nu behöver jag experthjälp.
Har haft problem med att min dator startar om med jämna mellanrum och då ofta med blåskärm och meddelandet IRQL_NOT_LESS_OR_EQUAL. Denna dator står på dygnet runt och ofta startar den om mitt i natten vilket gör att jag då inte vet om det alltid blir blåskärm.
Datorn är relativt ny, har köpt delar själv och byggt ihop den. Har haft den i ca:6månader och den har fungerat kanon fram till ca:1månad sedan...
Jag har testat att köra Windbg och öppnat en av filerna som ligger i Minidump mappen. (vad är det för skillnad på dessa och Memory.dmp?)
Dock förstår jag ju inte mycket utav den information jag får fram och behöver därför lite expertis hjälp, eller en vägledning till var jag kan få hjälp med att åtgärda mitt problem.
Eftersom jag har flera filer i Minidump mappen bifogar jag här dom senaste två dump filerna och ser om det kan hjälpa.
Microsoft ® Windows Debugger Version 6.11.0001.404 X86
Copyright © Microsoft Corporation. All rights reserved.
Loading Dump File [C:\WINDOWS\Minidump\Mini031509-02.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*C:\WINDOWS\Symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows XP Kernel Version 2600 (Service Pack 3) MP (2 procs) Free x86 compatible
Product: WinNt
Built by: 2600.xpsp_sp3_gdr.080814-1236
Machine Name:
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055d720
Debug session time: Sun Mar 15 20:45:39.828 2009 (GMT+1)
System Uptime: 0 days 3:40:25.077
Loading Kernel Symbols
...............................................................
................................................................
...............
Loading User Symbols
Loading unloaded module list
.........
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck A, {91aaf008, 2, 1, 8052390d}
Probably caused by : memory_corruption ( nt!MiReleasePageFileSpace+55 )
Followup: MachineOwner
---------
0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
IRQL_NOT_LESS_OR_EQUAL (a)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high. This is usually
caused by drivers using improper addresses.
If a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: 91aaf008, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000001, bitfield :
bit 0 : value 0 = read operation, 1 = write operation
bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: 8052390d, address which referenced memory
Debugging Details:
------------------
WRITE_ADDRESS: 91aaf008
CURRENT_IRQL: 2
FAULTING_IP:
nt!MiReleasePageFileSpace+55
8052390d 213e and dword ptr [esi],edi
CUSTOMER_CRASH_COUNT: 2
DEFAULT_BUCKET_ID: DRIVER_FAULT
BUGCHECK_STR: 0xA
TRAP_FRAME: a580aac0 -- (.trap 0xffffffffa580aac0)
ErrCode = 00000002
eax=8a2b32f0 ebx=c000b020 ecx=00000000 edx=00000000 esi=91aaf008 edi=fffffffe
eip=8052390d esp=a580ab34 ebp=a580ab44 iopl=0 nv up ei pl zr na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010246
nt!MiReleasePageFileSpace+0x55:
8052390d 213e and dword ptr [esi],edi ds:0023:91aaf008=????????
Resetting default scope
LAST_CONTROL_TRANSFER: from 8052390d to 805446f0
STACK_TEXT:
a580aac0 8052390d badb0d00 00000000 bf805500 nt!KiTrap0E+0x238
a580ab44 80523e44 00000000 42000000 01604000 nt!MiReleasePageFileSpace+0x55
a580ab7c 80523fb8 c000b020 01604000 00000000 nt!MiDeletePte+0x4a2
a580ac44 8051a1dd e1a7db20 018b3fff 00000000 nt!MiDeleteVirtualAddresses+0x164
a580acf4 805b2d79 87ca1598 8a146fc8 a580ad64 nt!MiRemoveMappedView+0x237
a580ad38 805b2e68 8a2db858 87cb2e48 00000000 nt!MiUnmapViewOfSection+0x12b
a580ad54 8054162c ffffffff 87ca1598 00cef4a0 nt!NtUnmapViewOfSection+0x54
a580ad54 7c90e4f4 ffffffff 87ca1598 00cef4a0 nt!KiFastCallEntry+0xfc
WARNING: Frame IP not in any known module. Following frames may be wrong.
00cef4a0 00000000 00000000 00000000 00000000 0x7c90e4f4
STACK_COMMAND: kb
FOLLOWUP_IP:
nt!MiReleasePageFileSpace+55
8052390d 213e and dword ptr [esi],edi
SYMBOL_STACK_INDEX: 1
SYMBOL_NAME: nt!MiReleasePageFileSpace+55
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
DEBUG_FLR_IMAGE_TIMESTAMP: 48a3fbd9
IMAGE_NAME: memory_corruption
FAILURE_BUCKET_ID: 0xA_nt!MiReleasePageFileSpace+55
BUCKET_ID: 0xA_nt!MiReleasePageFileSpace+55
Followup: MachineOwner
---------
Microsoft ® Windows Debugger Version 6.11.0001.404 X86
Copyright © Microsoft Corporation. All rights reserved.
Loading Dump File [C:\WINDOWS\Minidump\Mini031509-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*C:\WINDOWS\Symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows XP Kernel Version 2600 (Service Pack 3) MP (2 procs) Free x86 compatible
Product: WinNt
Built by: 2600.xpsp_sp3_gdr.080814-1236
Machine Name:
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055d720
Debug session time: Sun Mar 15 16:46:08.223 2009 (GMT+1)
System Uptime: 0 days 14:45:01.972
Loading Kernel Symbols
...............................................................
................................................................
..............
Loading User Symbols
Loading unloaded module list
..........
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck A, {c7ddf4f0, 2, 0, 8051bb93}
Probably caused by : memory_corruption ( nt!MmCopyToCachedPage+1b1 )
Followup: MachineOwner
---------
0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
IRQL_NOT_LESS_OR_EQUAL (a)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high. This is usually
caused by drivers using improper addresses.
If a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: c7ddf4f0, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000000, bitfield :
bit 0 : value 0 = read operation, 1 = write operation
bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: 8051bb93, address which referenced memory
Debugging Details:
------------------
READ_ADDRESS: c7ddf4f0
CURRENT_IRQL: 2
FAULTING_IP:
nt!MmCopyToCachedPage+1b1
8051bb93 8b00 mov eax,dword ptr [eax]
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: DRIVER_FAULT
BUGCHECK_STR: 0xA
TRAP_FRAME: a4cda8cc -- (.trap 0xffffffffa4cda8cc)
ErrCode = 00000000
eax=c7ddf4f0 ebx=d5886000 ecx=00000000 edx=00000000 esi=e261c220 edi=03000000
eip=8051bb93 esp=a4cda940 ebp=a4cdaa40 iopl=0 nv up ei pl zr na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010246
nt!MmCopyToCachedPage+0x1b1:
8051bb93 8b00 mov eax,dword ptr [eax] ds:0023:c7ddf4f0=????????
Resetting default scope
LAST_CONTROL_TRANSFER: from 8051bb93 to 805446f0
STACK_TEXT:
a4cda8cc 8051bb93 badb0d00 00000000 a4cda8ec nt!KiTrap0E+0x238
a4cdaa40 804e39f9 c9f44000 0f6dd650 00000000 nt!MmCopyToCachedPage+0x1b1
a4cdaad0 804e17ee 89587008 0f6dd650 a4cdab04 nt!CcMapAndCopy+0x1af
a4cdab54 b9d5c846 87dd12a8 00d44000 00001000 nt!CcFastCopyWrite+0x230
a4cdabbc b9dc8a27 87dd12a8 87c11fa0 00001000 Ntfs!NtfsCopyWriteA+0x23d
a4cdabf0 b9dd6018 87dd12a8 87c11fa0 00001000 sr!SrFastIoWrite+0x77
a4cdac24 b9dd61e4 00000004 00000000 87c11f98 fltmgr!FltpPerformFastIoCall+0x230
a4cdac50 b9de1c38 00cdac70 00000001 00000000 fltmgr!FltpPassThroughFastIo+0x78
a4cdac90 8057d1fd 87dd12a8 a4cdacd4 00001000 fltmgr!FltpFastIoWrite+0x148
a4cdad38 8054162c 00000398 00000000 00000000 nt!NtWriteFile+0x30b
a4cdad38 7c90e4f4 00000398 00000000 00000000 nt!KiFastCallEntry+0xfc
WARNING: Frame IP not in any known module. Following frames may be wrong.
0012f050 00000000 00000000 00000000 00000000 0x7c90e4f4
STACK_COMMAND: kb
FOLLOWUP_IP:
nt!MmCopyToCachedPage+1b1
8051bb93 8b00 mov eax,dword ptr [eax]
SYMBOL_STACK_INDEX: 1
SYMBOL_NAME: nt!MmCopyToCachedPage+1b1
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
DEBUG_FLR_IMAGE_TIMESTAMP: 48a3fbd9
IMAGE_NAME: memory_corruption
FAILURE_BUCKET_ID: 0xA_nt!MmCopyToCachedPage+1b1
BUCKET_ID: 0xA_nt!MmCopyToCachedPage+1b1
Followup: MachineOwner
---------
0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
IRQL_NOT_LESS_OR_EQUAL (a)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high. This is usually
caused by drivers using improper addresses.
If a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: c7ddf4f0, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000000, bitfield :
bit 0 : value 0 = read operation, 1 = write operation
bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: 8051bb93, address which referenced memory
Debugging Details:
------------------
READ_ADDRESS: c7ddf4f0
CURRENT_IRQL: 2
FAULTING_IP:
nt!MmCopyToCachedPage+1b1
8051bb93 8b00 mov eax,dword ptr [eax]
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: DRIVER_FAULT
BUGCHECK_STR: 0xA
TRAP_FRAME: a4cda8cc -- (.trap 0xffffffffa4cda8cc)
ErrCode = 00000000
eax=c7ddf4f0 ebx=d5886000 ecx=00000000 edx=00000000 esi=e261c220 edi=03000000
eip=8051bb93 esp=a4cda940 ebp=a4cdaa40 iopl=0 nv up ei pl zr na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010246
nt!MmCopyToCachedPage+0x1b1:
8051bb93 8b00 mov eax,dword ptr [eax] ds:0023:c7ddf4f0=????????
Resetting default scope
LAST_CONTROL_TRANSFER: from 8051bb93 to 805446f0
STACK_TEXT:
a4cda8cc 8051bb93 badb0d00 00000000 a4cda8ec nt!KiTrap0E+0x238
a4cdaa40 804e39f9 c9f44000 0f6dd650 00000000 nt!MmCopyToCachedPage+0x1b1
a4cdaad0 804e17ee 89587008 0f6dd650 a4cdab04 nt!CcMapAndCopy+0x1af
a4cdab54 b9d5c846 87dd12a8 00d44000 00001000 nt!CcFastCopyWrite+0x230
a4cdabbc b9dc8a27 87dd12a8 87c11fa0 00001000 Ntfs!NtfsCopyWriteA+0x23d
a4cdabf0 b9dd6018 87dd12a8 87c11fa0 00001000 sr!SrFastIoWrite+0x77
a4cdac24 b9dd61e4 00000004 00000000 87c11f98 fltmgr!FltpPerformFastIoCall+0x230
a4cdac50 b9de1c38 00cdac70 00000001 00000000 fltmgr!FltpPassThroughFastIo+0x78
a4cdac90 8057d1fd 87dd12a8 a4cdacd4 00001000 fltmgr!FltpFastIoWrite+0x148
a4cdad38 8054162c 00000398 00000000 00000000 nt!NtWriteFile+0x30b
a4cdad38 7c90e4f4 00000398 00000000 00000000 nt!KiFastCallEntry+0xfc
WARNING: Frame IP not in any known module. Following frames may be wrong.
0012f050 00000000 00000000 00000000 00000000 0x7c90e4f4
STACK_COMMAND: kb
FOLLOWUP_IP:
nt!MmCopyToCachedPage+1b1
8051bb93 8b00 mov eax,dword ptr [eax]
SYMBOL_STACK_INDEX: 1
SYMBOL_NAME: nt!MmCopyToCachedPage+1b1
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
DEBUG_FLR_IMAGE_TIMESTAMP: 48a3fbd9
IMAGE_NAME: memory_corruption
FAILURE_BUCKET_ID: 0xA_nt!MmCopyToCachedPage+1b1
BUCKET_ID: 0xA_nt!MmCopyToCachedPage+1b1
Followup: MachineOwner
---------
Vet inte vad jag ska göra för att komma tillrätta med mitt problem, hoppas någon utav er därute kan hjälpa mig!