Freezing or BSOD while copying folders

  • Thread starter Thread starter azinkin
  • Start date Start date
A

azinkin

Hi,

I've just freshly installed Windows XP SP2 (this is about the third time...)
on my brand new system (all bought a week ago) and I have a problem: Often
when copying folders, Windows just freezes and I can't do anything with it,
so I have to restart. Sometimes I hear a beep just before this happens. If
it's not the freezing, I get a BSOD 1000000A (debug analysis attached at
bottom of message). Sometimes, along with the freezing, short thin vertical
stripes appear on the upper side of the screen. What the hell is happening,
Windows ?!

I've been struggling with this problem for almost a week... I work in the
video editing industry, and I feel this problem very hard. Please help me
out, if you can.

My system is made of the following:
ASUS P5Q-E motherboard (latest BIOS version)
Intel Core2Quad Q9550 processor
Corsair 2GB DDR2 Twin2X dual-channel 1066Mhz 5-5-5-15 EPP
Seagate SATA-II 500GB 32MB cache 7200rpm ST3500320NS (set as IDE Enhanced in
BIOS)
Gigabyte nVidia Geforce 8600GT 256MB

My system drivers installed:
Intel P45 Chipset, latest driver from the ASUS site
GPU driver, latest version from the Gygabite site
Marvell Yukon Ethernet Controller - latest version from the ASUS site

I have not installed any programs, only a few, essential, ones.

Things I've done to try to solve the problem:
Reinstalled Windows
Ran CHKDSK
Tested the RAM sticks separately and both (twice), with memtest86+, for 10
passes or more, no problems found
Tested the HDD (2 times) with Seatools (Seagate's Diagnostics program) no
problems found
Changed the SATA port, changed SATA cables
Scanned for viruses
I updated to Service Pack 3 and installed allother updates.

So.. I am certain that this is not a Hardware issue.

I've analyzed the minidumps created by the 1000000A error and an interesting
fact is that, every time, the last three Arguments, the
LAST_CONTROL_TRANSFER, the FAILURE_BUCKET_ID, the STACK_TEXT and other things
are the same! I'll paste here a few relevant codes from the analysis. I hope
some of you understand these codes better than me... If you want more
information, please ask.

BugCheck 1000000A, {a39423e8, 2, 1, 80522438}
DEFAULT_BUCKET_ID: DRIVER_FAULT
PROCESS_NAME: explorer.exe
STACK_TEXT:
b5bb49c0 80522c1e 00000000 e32ad388 81886000 nt!MiRemovePageFromList+0x6e
b5bb49d8 8051bbfb 00000000 ca270000 00001000 nt!MiRemoveAnyPage+0xc8
b5bb4ae0 804e39e9 ca270000 025564a0 00000000 nt!MmCopyToCachedPage+0x229
b5bb4b70 804e17de 8a0d88e8 025564a0 b5bb4ba4 nt!CcMapAndCopy+0x1af
b5bb4bf4 ba674846 89f7dc18 00070000 00010000 nt!CcFastCopyWrite+0x230
b5bb4c5c ba6e0a27 89f7dc18 b5bb4cd4 00010000 Ntfs!NtfsCopyWriteA+0x23d
b5bb4c90 8057d1fd 89f7dc18 b5bb4cd4 00010000 sr!SrFastIoWrite+0x77
b5bb4d38 8054161c 00000adc 00000000 00000000 nt!NtWriteFile+0x30b
b5bb4d38 7c90e4f4 00000adc 00000000 00000000 nt!KiFastCallEntry+0xfc
IMAGE_NAME: memory_corruption
FAILURE_BUCKET_ID: 0xA_W_nt!MiRemovePageFromList+6e
 
(set as IDE Enhanced in BIOS)
Why this setting?

The complete mini dump report might help.

--



Gerry
~~~~
FCA
Stourport, England
Enquire, plan and execute
~~~~~~~~~~~~~~~~~~~
 
azinkin said:
Hi,

I've just freshly installed Windows XP SP2 (this is about the third time...)
on my brand new system (all bought a week ago) and I have a problem: Often
when copying folders, Windows just freezes and I can't do anything with it,
so I have to restart. Sometimes I hear a beep just before this happens. If
it's not the freezing, I get a BSOD 1000000A (debug analysis attached at
bottom of message). Sometimes, along with the freezing, short thin vertical
stripes appear on the upper side of the screen. What the hell is happening,
Windows ?!

I've been struggling with this problem for almost a week... I work in the
video editing industry, and I feel this problem very hard. Please help me
out, if you can.

My system is made of the following:
ASUS P5Q-E motherboard (latest BIOS version)
Intel Core2Quad Q9550 processor
Corsair 2GB DDR2 Twin2X dual-channel 1066Mhz 5-5-5-15 EPP
Seagate SATA-II 500GB 32MB cache 7200rpm ST3500320NS (set as IDE Enhanced in
BIOS)
Gigabyte nVidia Geforce 8600GT 256MB

My system drivers installed:
Intel P45 Chipset, latest driver from the ASUS site
GPU driver, latest version from the Gygabite site
Marvell Yukon Ethernet Controller - latest version from the ASUS site

I have not installed any programs, only a few, essential, ones.

Things I've done to try to solve the problem:
Reinstalled Windows
Ran CHKDSK
Tested the RAM sticks separately and both (twice), with memtest86+, for 10
passes or more, no problems found
Tested the HDD (2 times) with Seatools (Seagate's Diagnostics program) no
problems found
Changed the SATA port, changed SATA cables
Scanned for viruses
I updated to Service Pack 3 and installed allother updates.

So.. I am certain that this is not a Hardware issue.

I've analyzed the minidumps created by the 1000000A error and an interesting
fact is that, every time, the last three Arguments, the
LAST_CONTROL_TRANSFER, the FAILURE_BUCKET_ID, the STACK_TEXT and other things
are the same! I'll paste here a few relevant codes from the analysis. I hope
some of you understand these codes better than me... If you want more
information, please ask.

BugCheck 1000000A, {a39423e8, 2, 1, 80522438}
DEFAULT_BUCKET_ID: DRIVER_FAULT
PROCESS_NAME: explorer.exe
STACK_TEXT:
b5bb49c0 80522c1e 00000000 e32ad388 81886000 nt!MiRemovePageFromList+0x6e
b5bb49d8 8051bbfb 00000000 ca270000 00001000 nt!MiRemoveAnyPage+0xc8
b5bb4ae0 804e39e9 ca270000 025564a0 00000000 nt!MmCopyToCachedPage+0x229
b5bb4b70 804e17de 8a0d88e8 025564a0 b5bb4ba4 nt!CcMapAndCopy+0x1af
b5bb4bf4 ba674846 89f7dc18 00070000 00010000 nt!CcFastCopyWrite+0x230
b5bb4c5c ba6e0a27 89f7dc18 b5bb4cd4 00010000 Ntfs!NtfsCopyWriteA+0x23d
b5bb4c90 8057d1fd 89f7dc18 b5bb4cd4 00010000 sr!SrFastIoWrite+0x77
b5bb4d38 8054161c 00000adc 00000000 00000000 nt!NtWriteFile+0x30b
b5bb4d38 7c90e4f4 00000adc 00000000 00000000 nt!KiFastCallEntry+0xfc
IMAGE_NAME: memory_corruption
FAILURE_BUCKET_ID: 0xA_W_nt!MiRemovePageFromList+6e
Click to expand...



Troubleshooting a Stop 0x0000000A Error in Windows XP:
http://support.microsoft.com/default.aspx?scid=kb;en-us;q314063

This error always refer to a bad Driver/Hardware installed and also been
related to memory:
Poor contacts, bad chips, wrong speed and mismatched Type. Try to Start with
One 1G or one stick of RAM and see if that will help.
http://en.wikipedia.org/wiki/Serial_Presence_Detect

How to perform a clean boot in Windows XP
http://support.microsoft.com/?id=310353

If the above didn't help then You may have a bad RAM try to test your RAM by
running Memory test by
downloading this tool and unzip it and make a floppy or CD/DVD and run it on
Reboot.
http://oca.microsoft.com/en/windiag.asp.
You may need to reposition/reset the RAM sticks in their slots.
HTH,
nass
 
Yeah, I installed Windows 3 times already, each time trying different BIOS
settings, different drivers... This problem is really stressfull... I work in
video editing, and I cannot work on this computer because doing that with
this problem I risk to lose the work.

About the information you gave me, I've installed the latest drivers from my
motherboard's site... I've also tested hardware, see "Things I've done to try
to solve the problem:" in my post.

Thanks for the reply
 
Hello Gerry,

"IDE Enhanced" is the default setting on my BIOS. I had it on "IDE
compatible" and on "AHCI" too, but it didn't change anything.

I'll now paste the minidump analysis of the 2 1000000A errors I had. You can
notice that they have many things in common.



Microsoft (R) Windows Debugger Version 6.9.0003.113 X86
Copyright (c) Microsoft Corporation. All rights reserved.

Loading Dump File [C:\WINDOWS\Minidump\Mini100108-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is:
SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: c:\windows\System32; c:\windows\system\System32;
http://www.alexander.com/SymServe.
Windows XP Kernel Version 2600 (Service Pack 3) MP (4 procs) Free x86
compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 2600.xpsp.080413-2111
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055d720
Debug session time: Wed Oct 1 17:47:21.609 2008 (GMT+3)
System Uptime: 0 days 0:12:47.210
Loading Kernel Symbols
.........................................................................................................
Loading User Symbols
Loading unloaded module list
.................
*******************************************************************************
*
*
* Bugcheck Analysis
*
*
*
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000000A, {a39423e8, 2, 1, 80522438}

Probably caused by : memory_corruption ( nt!MiRemovePageFromList+6e )

Followup: MachineOwner
---------

3: 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: a39423e8, 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: 80522438, address which referenced memory

Debugging Details:
------------------


WRITE_ADDRESS: a39423e8

CURRENT_IRQL: 2

FAULTING_IP:
nt!MiRemovePageFromList+6e
80522438 834c1008ff or dword ptr [eax+edx+8],0FFFFFFFFh

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: DRIVER_FAULT

BUGCHECK_STR: 0xA

PROCESS_NAME: explorer.exe

LAST_CONTROL_TRANSFER: from 80522c1e to 80522438

STACK_TEXT:
bab279c0 80522c1e 00000000 e314d600 c7886000 nt!MiRemovePageFromList+0x6e
bab279d8 8051bbfb 00000000 ca980000 00001000 nt!MiRemoveAnyPage+0xc8
bab27ae0 804e39e9 ca980000 0266a800 00000000 nt!MmCopyToCachedPage+0x229
bab27b70 804e17de 8a51a110 0266a800 bab27ba4 nt!CcMapAndCopy+0x1af
bab27bf4 ba674846 89b999f0 048c0000 00010000 nt!CcFastCopyWrite+0x230
bab27c5c ba6e0a27 89b999f0 bab27cd4 00010000 Ntfs!NtfsCopyWriteA+0x23d
bab27c90 8057d1fd 89b999f0 bab27cd4 00010000 sr!SrFastIoWrite+0x77
bab27d38 8054161c 000007a0 00000000 00000000 nt!NtWriteFile+0x30b
bab27d38 7c90e4f4 000007a0 00000000 00000000 nt!KiFastCallEntry+0xfc
WARNING: Frame IP not in any known module. Following frames may be wrong.
02bae0e8 00000000 00000000 00000000 00000000 0x7c90e4f4


STACK_COMMAND: kb

FOLLOWUP_IP:
nt!MiRemovePageFromList+6e
80522438 834c1008ff or dword ptr [eax+edx+8],0FFFFFFFFh

SYMBOL_STACK_INDEX: 0

SYMBOL_NAME: nt!MiRemovePageFromList+6e

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP: 4802516a

IMAGE_NAME: memory_corruption

FAILURE_BUCKET_ID: 0xA_W_nt!MiRemovePageFromList+6e

BUCKET_ID: 0xA_W_nt!MiRemovePageFromList+6e

Followup: MachineOwner
---------

3: kd> lmvm nt
start end module name
804d7000 806e4000 nt (pdb symbols)
c:\symbols\ntkrpamp.pdb\7D6290E03E32455BB0E035E38816124F1\ntkrpamp.pdb
Loaded symbol image file: ntkrpamp.exe
Mapped memory image file: c:\windows\System32\ntkrnlpa.exe
Image path: ntkrpamp.exe
Image name: ntkrpamp.exe
Timestamp: Sun Apr 13 21:31:06 2008 (4802516A)
CheckSum: 001F442E
ImageSize: 0020D000
File version: 5.1.2600.5512
Product version: 5.1.2600.5512
File flags: 0 (Mask 3F)
File OS: 40004 NT Win32
File type: 1.0 App
File date: 00000000.00000000
Translations: 0409.04b0
CompanyName: Microsoft Corporation
ProductName: Microsoft® Windows® Operating System
InternalName: ntkrpamp.exe
OriginalFilename: ntkrpamp.exe
ProductVersion: 5.1.2600.5512
FileVersion: 5.1.2600.5512 (xpsp.080413-2111)
FileDescription: NT Kernel & System
LegalCopyright: © Microsoft Corporation. All rights reserved.





Microsoft (R) Windows Debugger Version 6.9.0003.113 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\WINDOWS\Minidump\Mini100208-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is:
SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: c:\windows\System32; c:\windows\system\System32;
http://www.alexander.com/SymServe.
Windows XP Kernel Version 2600 (Service Pack 3) MP (4 procs) Free x86
compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 2600.xpsp.080413-2111
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055d720
Debug session time: Thu Oct 2 15:22:02.218 2008 (GMT+3)
System Uptime: 0 days 0:22:19.205
Loading Kernel Symbols
..........................................................................................................
Loading User Symbols
Loading unloaded module list
...................
*******************************************************************************
*
*
* Bugcheck Analysis
*
*
*
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000000A, {9ee620e8, 2, 1, 80522438}

Probably caused by : memory_corruption ( nt!MiRemovePageFromList+6e )

Followup: MachineOwner
---------

3: 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: 9ee620e8, 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: 80522438, address which referenced memory

Debugging Details:
------------------


WRITE_ADDRESS: 9ee620e8

CURRENT_IRQL: 2

FAULTING_IP:
nt!MiRemovePageFromList+6e
80522438 834c1008ff or dword ptr [eax+edx+8],0FFFFFFFFh

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: DRIVER_FAULT

BUGCHECK_STR: 0xA

PROCESS_NAME: explorer.exe

LAST_CONTROL_TRANSFER: from 80522c1e to 80522438

STACK_TEXT:
b5bb49c0 80522c1e 00000000 e32ad388 81886000 nt!MiRemovePageFromList+0x6e
b5bb49d8 8051bbfb 00000000 ca270000 00001000 nt!MiRemoveAnyPage+0xc8
b5bb4ae0 804e39e9 ca270000 025564a0 00000000 nt!MmCopyToCachedPage+0x229
b5bb4b70 804e17de 8a0d88e8 025564a0 b5bb4ba4 nt!CcMapAndCopy+0x1af
b5bb4bf4 ba674846 89f7dc18 00070000 00010000 nt!CcFastCopyWrite+0x230
b5bb4c5c ba6e0a27 89f7dc18 b5bb4cd4 00010000 Ntfs!NtfsCopyWriteA+0x23d
b5bb4c90 8057d1fd 89f7dc18 b5bb4cd4 00010000 sr!SrFastIoWrite+0x77
b5bb4d38 8054161c 00000adc 00000000 00000000 nt!NtWriteFile+0x30b
b5bb4d38 7c90e4f4 00000adc 00000000 00000000 nt!KiFastCallEntry+0xfc
WARNING: Frame IP not in any known module. Following frames may be wrong.
027be0e8 00000000 00000000 00000000 00000000 0x7c90e4f4


STACK_COMMAND: kb

FOLLOWUP_IP:
nt!MiRemovePageFromList+6e
80522438 834c1008ff or dword ptr [eax+edx+8],0FFFFFFFFh

SYMBOL_STACK_INDEX: 0

SYMBOL_NAME: nt!MiRemovePageFromList+6e

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP: 4802516a

IMAGE_NAME: memory_corruption

FAILURE_BUCKET_ID: 0xA_W_nt!MiRemovePageFromList+6e

BUCKET_ID: 0xA_W_nt!MiRemovePageFromList+6e

Followup: MachineOwner
 
Hello nass,

I've already tested with each of the RAM sticks installed and the problem
was still there. Also I've tested the RAM individually and together with
memtest86+ for over 10 passes and it didn't find any problems.

About clean boot, I must say that I have almost no programs installed (only
sutff like WinRAR, Acrobat Reader...) and the drivers are also minimal (only
chipset, gpu, sound and network...) I have the latest versions of the drivers.

I've also tested the HDD with the manufacturer's Diagnostic Tool, Seatools.
It found no problems. And I've done more things to rule out a hardware cause
(changed cables, ports, BIOS...)

All these made me come to the conclusion that it is a Windows problem...
 
Your computer has a way to 'reset' itself. By that I mean a way to erase
the hard disk and reinstall the software that was on the computer when
it arrived at your doorstep. This is done either with so-called recovery
CDs or a recovery partition. The OEM can show you how to do this. (The
procedure can vary from model to model.)

If you reset your computer to the way it was when it left the factory,
does it work properly? If it does not: You have a warranty issue with
the vendor. If it does: Something you did to the computer after you
first turned it on is causing your problem.
---
Leonard Grey
Errare humanum est

"A Day in the Life of a Web 2.0 Hacker" - PC Magazine
http://www.pcmag.com/article2/0,2817,2330952,00.asp
 
I know about the Recovery Console, but never used it. I figured that by
completely reinstalling Windows would fix everything related to it...

The problem is that this is not a branded PC, since I bought all the
components separately. They were indeed assembled at the service of the shop
where I got them from, but they did not install Windows for me. I had to do
that. And since the first time I did that, while not changing anything in
BIOS or something, I had this problem. Its strange indeed. I've thought of
hardware causes too, but after running tests many times on the HDD, RAM and
CPU, and finding no problems... I turned to Windows for anwsers.
 
I didn't say anything about using the Recovery Console.

With no OEM to turn to, no way of resetting to factory settings and no
manufacturer technical support, your only remaining recourse is to show
your computer to a professional technician.
---
Leonard Grey
Errare humanum est

"A Day in the Life of a Web 2.0 Hacker" - PC Magazine
http://www.pcmag.com/article2/0,2817,2330952,00.asp
 
You receive a "Stop 0x0000000A" error message in Windows XP
http://support.microsoft.com/kb/314063#top

These all seem very similar to your problem.
http://snipurl.com/414qv [www_google_com]

Are you getting any other Stop Error codes?


--



Hope this helps.

Gerry
~~~~
FCA
Stourport, England
Enquire, plan and execute
~~~~~~~~~~~~~~~~~~~
Hello Gerry,

"IDE Enhanced" is the default setting on my BIOS. I had it on "IDE
compatible" and on "AHCI" too, but it didn't change anything.

I'll now paste the minidump analysis of the 2 1000000A errors I had.
You can notice that they have many things in common.



Microsoft (R) Windows Debugger Version 6.9.0003.113 X86
Copyright (c) Microsoft Corporation. All rights reserved.

Loading Dump File [C:\WINDOWS\Minidump\Mini100108-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is:
SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: c:\windows\System32;
c:\windows\system\System32; http://www.alexander.com/SymServe.
Windows XP Kernel Version 2600 (Service Pack 3) MP (4 procs) Free x86
compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 2600.xpsp.080413-2111
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055d720
Debug session time: Wed Oct 1 17:47:21.609 2008 (GMT+3)
System Uptime: 0 days 0:12:47.210
Loading Kernel Symbols
.......................................................................................................
Loading User Symbols
Loading unloaded module list
................
*******************************************************************************
*
*
* Bugcheck Analysis
*
*
*
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000000A, {a39423e8, 2, 1, 80522438}

Probably caused by : memory_corruption ( nt!MiRemovePageFromList+6e )

Followup: MachineOwner
---------

3: 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: a39423e8, 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: 80522438, address which referenced memory

Debugging Details:
------------------


WRITE_ADDRESS: a39423e8

CURRENT_IRQL: 2

FAULTING_IP:
nt!MiRemovePageFromList+6e
80522438 834c1008ff or dword ptr [eax+edx+8],0FFFFFFFFh

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: DRIVER_FAULT

BUGCHECK_STR: 0xA

PROCESS_NAME: explorer.exe

LAST_CONTROL_TRANSFER: from 80522c1e to 80522438

STACK_TEXT:
bab279c0 80522c1e 00000000 e314d600 c7886000
nt!MiRemovePageFromList+0x6e bab279d8 8051bbfb 00000000 ca980000
00001000 nt!MiRemoveAnyPage+0xc8
bab27ae0 804e39e9 ca980000 0266a800 00000000
nt!MmCopyToCachedPage+0x229 bab27b70 804e17de 8a51a110 0266a800
bab27ba4 nt!CcMapAndCopy+0x1af
bab27bf4 ba674846 89b999f0 048c0000 00010000 nt!CcFastCopyWrite+0x230
bab27c5c ba6e0a27 89b999f0 bab27cd4 00010000 Ntfs!NtfsCopyWriteA+0x23d
bab27c90 8057d1fd 89b999f0 bab27cd4 00010000 sr!SrFastIoWrite+0x77
bab27d38 8054161c 000007a0 00000000 00000000 nt!NtWriteFile+0x30b
bab27d38 7c90e4f4 000007a0 00000000 00000000 nt!KiFastCallEntry+0xfc
WARNING: Frame IP not in any known module. Following frames may be
wrong. 02bae0e8 00000000 00000000 00000000 00000000 0x7c90e4f4


STACK_COMMAND: kb

FOLLOWUP_IP:
nt!MiRemovePageFromList+6e
80522438 834c1008ff or dword ptr [eax+edx+8],0FFFFFFFFh

SYMBOL_STACK_INDEX: 0

SYMBOL_NAME: nt!MiRemovePageFromList+6e

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP: 4802516a

IMAGE_NAME: memory_corruption

FAILURE_BUCKET_ID: 0xA_W_nt!MiRemovePageFromList+6e

BUCKET_ID: 0xA_W_nt!MiRemovePageFromList+6e

Followup: MachineOwner
---------

3: kd> lmvm nt
start end module name
804d7000 806e4000 nt (pdb symbols)
c:\symbols\ntkrpamp.pdb\7D6290E03E32455BB0E035E38816124F1\ntkrpamp.pdb
Loaded symbol image file: ntkrpamp.exe
Mapped memory image file: c:\windows\System32\ntkrnlpa.exe
Image path: ntkrpamp.exe
Image name: ntkrpamp.exe
Timestamp: Sun Apr 13 21:31:06 2008 (4802516A)
CheckSum: 001F442E
ImageSize: 0020D000
File version: 5.1.2600.5512
Product version: 5.1.2600.5512
File flags: 0 (Mask 3F)
File OS: 40004 NT Win32
File type: 1.0 App
File date: 00000000.00000000
Translations: 0409.04b0
CompanyName: Microsoft Corporation
ProductName: Microsoft® Windows® Operating System
InternalName: ntkrpamp.exe
OriginalFilename: ntkrpamp.exe
ProductVersion: 5.1.2600.5512
FileVersion: 5.1.2600.5512 (xpsp.080413-2111)
FileDescription: NT Kernel & System
LegalCopyright: © Microsoft Corporation. All rights reserved.





Microsoft (R) Windows Debugger Version 6.9.0003.113 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\WINDOWS\Minidump\Mini100208-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is:
SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: c:\windows\System32;
c:\windows\system\System32; http://www.alexander.com/SymServe.
Windows XP Kernel Version 2600 (Service Pack 3) MP (4 procs) Free x86
compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 2600.xpsp.080413-2111
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055d720
Debug session time: Thu Oct 2 15:22:02.218 2008 (GMT+3)
System Uptime: 0 days 0:22:19.205
Loading Kernel Symbols
........................................................................................................
Loading User Symbols
Loading unloaded module list
..................
*******************************************************************************
*
*
* Bugcheck Analysis
*
*
*
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000000A, {9ee620e8, 2, 1, 80522438}

Probably caused by : memory_corruption ( nt!MiRemovePageFromList+6e )

Followup: MachineOwner
---------

3: 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: 9ee620e8, 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: 80522438, address which referenced memory

Debugging Details:
------------------


WRITE_ADDRESS: 9ee620e8

CURRENT_IRQL: 2

FAULTING_IP:
nt!MiRemovePageFromList+6e
80522438 834c1008ff or dword ptr [eax+edx+8],0FFFFFFFFh

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: DRIVER_FAULT

BUGCHECK_STR: 0xA

PROCESS_NAME: explorer.exe

LAST_CONTROL_TRANSFER: from 80522c1e to 80522438

STACK_TEXT:
b5bb49c0 80522c1e 00000000 e32ad388 81886000
nt!MiRemovePageFromList+0x6e b5bb49d8 8051bbfb 00000000 ca270000
00001000 nt!MiRemoveAnyPage+0xc8
b5bb4ae0 804e39e9 ca270000 025564a0 00000000
nt!MmCopyToCachedPage+0x229 b5bb4b70 804e17de 8a0d88e8 025564a0
b5bb4ba4 nt!CcMapAndCopy+0x1af
b5bb4bf4 ba674846 89f7dc18 00070000 00010000 nt!CcFastCopyWrite+0x230
b5bb4c5c ba6e0a27 89f7dc18 b5bb4cd4 00010000 Ntfs!NtfsCopyWriteA+0x23d
b5bb4c90 8057d1fd 89f7dc18 b5bb4cd4 00010000 sr!SrFastIoWrite+0x77
b5bb4d38 8054161c 00000adc 00000000 00000000 nt!NtWriteFile+0x30b
b5bb4d38 7c90e4f4 00000adc 00000000 00000000 nt!KiFastCallEntry+0xfc
WARNING: Frame IP not in any known module. Following frames may be
wrong. 027be0e8 00000000 00000000 00000000 00000000 0x7c90e4f4


STACK_COMMAND: kb

FOLLOWUP_IP:
nt!MiRemovePageFromList+6e
80522438 834c1008ff or dword ptr [eax+edx+8],0FFFFFFFFh

SYMBOL_STACK_INDEX: 0

SYMBOL_NAME: nt!MiRemovePageFromList+6e

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP: 4802516a

IMAGE_NAME: memory_corruption

FAILURE_BUCKET_ID: 0xA_W_nt!MiRemovePageFromList+6e

BUCKET_ID: 0xA_W_nt!MiRemovePageFromList+6e

Followup: MachineOwner
---------



Gerry said:
(set as IDE Enhanced in BIOS)
Why this setting?

The complete mini dump report might help.

--



Gerry
~~~~
FCA
Stourport, England
Enquire, plan and execute
~~~~~~~~~~~~~~~~~~~
Click to expand...
Click to expand...
 
Why single out computers?

--
Regards.

Gerry
~~~~
FCA
Stourport, England
Enquire, plan and execute
~~~~~~~~~~~~~~~~~~~
 
The cause was an incompatibility between the Intel Q9550 and the BIOS (v901
or later). I solved it by setting CPU Margin Enhancement to "Performance
Mode" instead of "Optimised Mode" (default setting).

Thanks to all the people that wanted to help.
 
azinkin said:
The cause was an incompatibility between the Intel Q9550 and the BIOS (v901
or later). I solved it by setting CPU Margin Enhancement to "Performance
Mode" instead of "Optimised Mode" (default setting).

Thanks to all the people that wanted to help.
Click to expand...

Thanks for your feedback and sharing this info much appreciated.
Good luck.
nass
 
Back
Top