:strip_exif()/u/42785/Squirt.gif?f=community)
(Allereerst hoop ik dat ik gegronde reden heb om hier te posten, want ikzelf heb geen enkel idee meer!)
Ik heb sinds een tijdje last van blauwe schermpjes, maar ze zijn steeds anders! Eerst heb ik ze niet opgeschreven, maar later wel en ik ben de volgende tegengekomen:
KMODE_EXCEPTION_NOT_HANDLED in ati3daug.dll (video driver dus)
En nu de volgende 2 en deze heb ik gedebugged:
nummer 1:
Microsoft (R) Windows Debugger Version 6.3.0011.2
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\WINNT\Minidump\Mini051704-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: C:\WINNT\Symbols
Executable search path is: C:\WINNT
*** WARNING: symbols timestamp is wrong 0x4047db83 0x3ee6c002 for ntoskrnl.exe
Windows 2000 Kernel Version 2195 (Service Pack 4) UP Free x86 compatible
Kernel base = 0x80400000 PsLoadedModuleList = 0x8046e8f0
Debug session time: Mon May 17 14:03:35 2004
System Uptime: not available
*** WARNING: symbols timestamp is wrong 0x4047db83 0x3ee6c002 for ntoskrnl.exe
Loading Kernel Symbols
........................................................................................................
Loading unloaded module list
.................
Loading User Symbols
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck A, {2c, 2, 0, 804423ea}
Probably caused by : memory_corruption ( nt!MiWaitForInPageComplete+233 )
Followup: MachineOwner
---------
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: 0000002c, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000000, value 0 = read operation, 1 = write operation
Arg4: 804423ea, address which referenced memory
Debugging Details:
------------------
READ_ADDRESS: unable to read from 80482fac
unable to read from 80482a08
unable to read from 804828e0
unable to read from 80474e00
unable to read from 804828f8
unable to read from 80482a04
unable to read from 80474e04
unable to read from 80482ac4
unable to read from 80482f80
0000002c
CURRENT_IRQL: 2
FAULTING_IP:
nt!MiWaitForInPageComplete+233
804423ea 8b402c mov eax,[eax+0x2c]
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: DRIVER_FAULT
BUGCHECK_STR: 0xA
LAST_CONTROL_TRANSFER: from 804423ea to 804690f3
STACK_TEXT:
aed24c3c 804423ea aed24d00 804c045e aed24d64 nt!KiTrap13+0xe8
aed24cc4 804419f9 02f016e0 c000bc04 aed24cfc nt!MiWaitForInPageComplete+0x233
aed24d00 8044b442 00000000 02f016e0 c000bc04 nt!MiResolvePageFileFault+0x5a
aed24d4c 80468f3a 00000000 02f016e0 00000001 nt!NtMapUserPhysicalPagesScatter+0x76
aed24d4c 0040d120 00000000 02f016e0 00000001 nt!KiTrap11+0x7f
WARNING: Frame IP not in any known module. Following frames may be wrong.
0012dc00 00000000 00000000 00000000 00000000 0x40d120
FOLLOWUP_IP:
nt!MiWaitForInPageComplete+233
804423ea 8b402c mov eax,[eax+0x2c]
SYMBOL_STACK_INDEX: 1
FOLLOWUP_NAME: MachineOwner
SYMBOL_NAME: nt!MiWaitForInPageComplete+233
MODULE_NAME: nt
DEBUG_FLR_IMAGE_TIMESTAMP: 4047db83
STACK_COMMAND: kb
IMAGE_NAME: memory_corruption
BUCKET_ID: 0xA_nt!MiWaitForInPageComplete+233
Followup: MachineOwner
---------
En nummer 2:
Microsoft (R) Windows Debugger Version 6.3.0011.2
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\WINNT\Minidump\Mini051804-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: C:\WINNT\Symbols
Executable search path is: C:\WINNT
*** WARNING: symbols timestamp is wrong 0x4047db83 0x3ee6c002 for ntoskrnl.exe
Windows 2000 Kernel Version 2195 (Service Pack 4) UP Free x86 compatible
Kernel base = 0x80400000 PsLoadedModuleList = 0x8046e8f0
Debug session time: Tue May 18 23:46:26 2004
System Uptime: not available
*** WARNING: symbols timestamp is wrong 0x4047db83 0x3ee6c002 for ntoskrnl.exe
Loading Kernel Symbols
.......................................................................................................
Loading unloaded module list
..........
Loading User Symbols
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck C2, {7, b8a, e2289600, e2289608}
*** WARNING: symbols timestamp is wrong 0x4047dcd6 0x3eb1ea3c for win32k.sys
unable to read from 80482a04
unable to read from 80482a08
unable to get MmPageSize - probably bad symbols
Probably caused by : win32k.sys ( win32k!GreSetRectRgn+56 )
Followup: MachineOwner
---------
kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
BAD_POOL_CALLER (c2)
The current thread is making a bad pool request. Typically this is at a bad IRQL level or double freeing the same allocation, etc.
Arguments:
Arg1: 00000007, Attempt to free pool which was already freed
Arg2: 00000b8a, (reserved)
Arg3: e2289600, Memory contents of the pool block
Arg4: e2289608, Address of the block of pool being deallocated
Debugging Details:
------------------
unable to read from 80482a04
unable to read from 80482a08
unable to get MmPageSize - probably bad symbols
BUGCHECK_STR: 0xc2_7
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: DRIVER_FAULT
LAST_CONTROL_TRANSFER: from 8046b8a2 to 8046baa2
STACK_TEXT:
af33253c 8046b8a2 e2289608 00000000 a00063c9 nt!MiAllocatePoolPages+0x29c
af33255c a00842e2 e2289608 00000000 af332630 nt!MiAllocatePoolPages+0xb7
af332584 a000d00e 00000000 af3325a0 00000000 win32k!GreSetRectRgn+0x56
af3325b4 a000d8e8 e2816008 00910910 af332630 win32k!InternalInvalidate2+0x18b
af332600 a00063a1 00000000 a00068b0 e29c6008 win32k!xxxSendEraseBkgnd+0x4b
af33263c a0006614 e296f008 af332704 a000af25 win32k!ulGetMatchingIndexFromColorref+0x35
af33265c a00685b4 1c010206 00000001 00f4fd74 win32k!RGNMEMOBJ::RGNMEMOBJ+0x10
af332714 a0002e27 00000000 a01b0380 00000000 win32k!vExpandAndCopyText+0x4d
af3327b8 a006dab8 01040038 a0002e27 00000000 win32k!GreReleaseSemaphore+0x11
af3327c0 a0002e27 00000000 a01b0380 00000000 win32k!xxxGetInitMenuParam+0x2b
af3327f0 a0007219 85a25c68 af3327e0 af332bb8 win32k!GreReleaseSemaphore+0x11
af33281c a0014a71 a0317c68 e212a308 00000002 win32k!_PostMessage+0xc7
e2c89448 00000000 00000000 00000000 00000000 win32k!vSpUpdateSpriteVisRgn+0x2c2
FOLLOWUP_IP:
win32k!GreSetRectRgn+56
a00842e2 8b06 mov eax,[esi]
SYMBOL_STACK_INDEX: 2
FOLLOWUP_NAME: MachineOwner
SYMBOL_NAME: win32k!GreSetRectRgn+56
MODULE_NAME: win32k
IMAGE_NAME: win32k.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4047dcd6
STACK_COMMAND: kb
BUCKET_ID: 0xc2_7_win32k!GreSetRectRgn+56
Followup: MachineOwner
---------
Volgens M$ kb kunnen ze alle drie met drivers of hardware te maken hebben. Nu heb ik in mijn systeem mijn Abit NF7-S bord al vervangen en ook mijn hardeschijf (was IDE nu SATA en de oude gaf met seatools een SMART error).
Geheugen (1Gb Kingston valueram (2x 512 voor dual channel)) heb ik getest met de nieuwste memtest (die nu net in de updates staat vermeld) en deze geeft na 3 passes aan dat er geen enkele fout is.
Ook heb ik win2k al een aantal keren moeten herinstalleren, omdat in het hele systeem geen enkel programma meer fatsoenlijk wil draaien na een dergelijke error. Dus deze 2 BSOD's zijn voorgekomen na een VERSE win2k installatie waarbij ik alle windows updates heb toegepast en de nieuwste drivers gebruik voor geluidskaart, videokaart en Nforce 2 drivers.
Verder heb ik na de IRQL BSOD gekeken of er een IRQ conflict bestond tussen hardware onderdelen. Het bleek dat mijn audiokaart een IRQ moest delen met mijn videokaart en dit heb ik gelijk verholpen door de audiokaart een slot op te schuiven.
Nog even mijn systeem:
2600+ Barton (draaiend op normale snelheid 11.5x166)
Abit NF7-S mainboard (is dus al een keertje vervangen, lost het probleem niet op)
1gb Kingston valueram (2x 512 voor dual channel)(getest met memtest => geen fouten)
Soundblaster Live! 5.1 soundcard
160gb Seagate 7200.7 SATA en een 60gb seagate 5400rpm IDE
Ehm ... help?
Ik heb sinds een tijdje last van blauwe schermpjes, maar ze zijn steeds anders! Eerst heb ik ze niet opgeschreven, maar later wel en ik ben de volgende tegengekomen:
KMODE_EXCEPTION_NOT_HANDLED in ati3daug.dll (video driver dus)
En nu de volgende 2 en deze heb ik gedebugged:
nummer 1:
Microsoft (R) Windows Debugger Version 6.3.0011.2
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\WINNT\Minidump\Mini051704-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: C:\WINNT\Symbols
Executable search path is: C:\WINNT
*** WARNING: symbols timestamp is wrong 0x4047db83 0x3ee6c002 for ntoskrnl.exe
Windows 2000 Kernel Version 2195 (Service Pack 4) UP Free x86 compatible
Kernel base = 0x80400000 PsLoadedModuleList = 0x8046e8f0
Debug session time: Mon May 17 14:03:35 2004
System Uptime: not available
*** WARNING: symbols timestamp is wrong 0x4047db83 0x3ee6c002 for ntoskrnl.exe
Loading Kernel Symbols
........................................................................................................
Loading unloaded module list
.................
Loading User Symbols
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck A, {2c, 2, 0, 804423ea}
Probably caused by : memory_corruption ( nt!MiWaitForInPageComplete+233 )
Followup: MachineOwner
---------
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: 0000002c, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000000, value 0 = read operation, 1 = write operation
Arg4: 804423ea, address which referenced memory
Debugging Details:
------------------
READ_ADDRESS: unable to read from 80482fac
unable to read from 80482a08
unable to read from 804828e0
unable to read from 80474e00
unable to read from 804828f8
unable to read from 80482a04
unable to read from 80474e04
unable to read from 80482ac4
unable to read from 80482f80
0000002c
CURRENT_IRQL: 2
FAULTING_IP:
nt!MiWaitForInPageComplete+233
804423ea 8b402c mov eax,[eax+0x2c]
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: DRIVER_FAULT
BUGCHECK_STR: 0xA
LAST_CONTROL_TRANSFER: from 804423ea to 804690f3
STACK_TEXT:
aed24c3c 804423ea aed24d00 804c045e aed24d64 nt!KiTrap13+0xe8
aed24cc4 804419f9 02f016e0 c000bc04 aed24cfc nt!MiWaitForInPageComplete+0x233
aed24d00 8044b442 00000000 02f016e0 c000bc04 nt!MiResolvePageFileFault+0x5a
aed24d4c 80468f3a 00000000 02f016e0 00000001 nt!NtMapUserPhysicalPagesScatter+0x76
aed24d4c 0040d120 00000000 02f016e0 00000001 nt!KiTrap11+0x7f
WARNING: Frame IP not in any known module. Following frames may be wrong.
0012dc00 00000000 00000000 00000000 00000000 0x40d120
FOLLOWUP_IP:
nt!MiWaitForInPageComplete+233
804423ea 8b402c mov eax,[eax+0x2c]
SYMBOL_STACK_INDEX: 1
FOLLOWUP_NAME: MachineOwner
SYMBOL_NAME: nt!MiWaitForInPageComplete+233
MODULE_NAME: nt
DEBUG_FLR_IMAGE_TIMESTAMP: 4047db83
STACK_COMMAND: kb
IMAGE_NAME: memory_corruption
BUCKET_ID: 0xA_nt!MiWaitForInPageComplete+233
Followup: MachineOwner
---------
En nummer 2:
Microsoft (R) Windows Debugger Version 6.3.0011.2
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\WINNT\Minidump\Mini051804-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: C:\WINNT\Symbols
Executable search path is: C:\WINNT
*** WARNING: symbols timestamp is wrong 0x4047db83 0x3ee6c002 for ntoskrnl.exe
Windows 2000 Kernel Version 2195 (Service Pack 4) UP Free x86 compatible
Kernel base = 0x80400000 PsLoadedModuleList = 0x8046e8f0
Debug session time: Tue May 18 23:46:26 2004
System Uptime: not available
*** WARNING: symbols timestamp is wrong 0x4047db83 0x3ee6c002 for ntoskrnl.exe
Loading Kernel Symbols
.......................................................................................................
Loading unloaded module list
..........
Loading User Symbols
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck C2, {7, b8a, e2289600, e2289608}
*** WARNING: symbols timestamp is wrong 0x4047dcd6 0x3eb1ea3c for win32k.sys
unable to read from 80482a04
unable to read from 80482a08
unable to get MmPageSize - probably bad symbols
Probably caused by : win32k.sys ( win32k!GreSetRectRgn+56 )
Followup: MachineOwner
---------
kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
BAD_POOL_CALLER (c2)
The current thread is making a bad pool request. Typically this is at a bad IRQL level or double freeing the same allocation, etc.
Arguments:
Arg1: 00000007, Attempt to free pool which was already freed
Arg2: 00000b8a, (reserved)
Arg3: e2289600, Memory contents of the pool block
Arg4: e2289608, Address of the block of pool being deallocated
Debugging Details:
------------------
unable to read from 80482a04
unable to read from 80482a08
unable to get MmPageSize - probably bad symbols
BUGCHECK_STR: 0xc2_7
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: DRIVER_FAULT
LAST_CONTROL_TRANSFER: from 8046b8a2 to 8046baa2
STACK_TEXT:
af33253c 8046b8a2 e2289608 00000000 a00063c9 nt!MiAllocatePoolPages+0x29c
af33255c a00842e2 e2289608 00000000 af332630 nt!MiAllocatePoolPages+0xb7
af332584 a000d00e 00000000 af3325a0 00000000 win32k!GreSetRectRgn+0x56
af3325b4 a000d8e8 e2816008 00910910 af332630 win32k!InternalInvalidate2+0x18b
af332600 a00063a1 00000000 a00068b0 e29c6008 win32k!xxxSendEraseBkgnd+0x4b
af33263c a0006614 e296f008 af332704 a000af25 win32k!ulGetMatchingIndexFromColorref+0x35
af33265c a00685b4 1c010206 00000001 00f4fd74 win32k!RGNMEMOBJ::RGNMEMOBJ+0x10
af332714 a0002e27 00000000 a01b0380 00000000 win32k!vExpandAndCopyText+0x4d
af3327b8 a006dab8 01040038 a0002e27 00000000 win32k!GreReleaseSemaphore+0x11
af3327c0 a0002e27 00000000 a01b0380 00000000 win32k!xxxGetInitMenuParam+0x2b
af3327f0 a0007219 85a25c68 af3327e0 af332bb8 win32k!GreReleaseSemaphore+0x11
af33281c a0014a71 a0317c68 e212a308 00000002 win32k!_PostMessage+0xc7
e2c89448 00000000 00000000 00000000 00000000 win32k!vSpUpdateSpriteVisRgn+0x2c2
FOLLOWUP_IP:
win32k!GreSetRectRgn+56
a00842e2 8b06 mov eax,[esi]
SYMBOL_STACK_INDEX: 2
FOLLOWUP_NAME: MachineOwner
SYMBOL_NAME: win32k!GreSetRectRgn+56
MODULE_NAME: win32k
IMAGE_NAME: win32k.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4047dcd6
STACK_COMMAND: kb
BUCKET_ID: 0xc2_7_win32k!GreSetRectRgn+56
Followup: MachineOwner
---------
Volgens M$ kb kunnen ze alle drie met drivers of hardware te maken hebben. Nu heb ik in mijn systeem mijn Abit NF7-S bord al vervangen en ook mijn hardeschijf (was IDE nu SATA en de oude gaf met seatools een SMART error).
Geheugen (1Gb Kingston valueram (2x 512 voor dual channel)) heb ik getest met de nieuwste memtest (die nu net in de updates staat vermeld) en deze geeft na 3 passes aan dat er geen enkele fout is.
Ook heb ik win2k al een aantal keren moeten herinstalleren, omdat in het hele systeem geen enkel programma meer fatsoenlijk wil draaien na een dergelijke error. Dus deze 2 BSOD's zijn voorgekomen na een VERSE win2k installatie waarbij ik alle windows updates heb toegepast en de nieuwste drivers gebruik voor geluidskaart, videokaart en Nforce 2 drivers.
Verder heb ik na de IRQL BSOD gekeken of er een IRQ conflict bestond tussen hardware onderdelen. Het bleek dat mijn audiokaart een IRQ moest delen met mijn videokaart en dit heb ik gelijk verholpen door de audiokaart een slot op te schuiven.
Nog even mijn systeem:
2600+ Barton (draaiend op normale snelheid 11.5x166)
Abit NF7-S mainboard (is dus al een keertje vervangen, lost het probleem niet op)
1gb Kingston valueram (2x 512 voor dual channel)(getest met memtest => geen fouten)
Soundblaster Live! 5.1 soundcard
160gb Seagate 7200.7 SATA en een 60gb seagate 5400rpm IDE
Ehm ... help?
"And folks, if you don't like a little pain once in a while, poker is probably not your game. 'Cause as you can see, you're gonna get it!" (Mike Sexton)
:strip_icc():strip_exif()/u/60100/crop5f04722cd929a_cropped.jpeg?f=community)