Server 2008 file Server Blue Screen Under Load

[RobbinHood]

hello there i keep currently getting blue screens when i copy 400+gig from drive to drive or over network i have tried reinstalling windows all the hdds are good no problems and i have run memtest and memeory passed

system specs
dual core
16gig ddr3 ram
2x rocketraid 2680
16 wd green 2tbs

please help meee

 

[drescherjm]

i have run memtest and memeory passed

Have you done that overnight? 1 or 2 passes will only tell you if you have very bad ram. It likely will not catch subtle memory problems like bit filps when the ram heats up.

Also if your are overclocking your CPU or not running your ram at the BIOS auto setting I would try resetting the bios to optimized defaults and retesting,

 

[mwroobel]

What is the error and stop code you are receiving?

 

[RobbinHood]

072412-49686-01.rar

hey there thanks for the reply

yes i have left the memtest over night and did 6 passes
unit is not overclocked left everything at factory settings
also tried reset bios to setup defaults still bluescreen

error code is

ntoskrnl.exe ntoskrnl.exe+ef6a2

i have attached the dump file if it helps

http://www.snetworks.com.au/072412-49686-01.rar

 

[mwroobel]

072412-49686-01.rar

hey there thanks for the reply

yes i have left the memtest over night and did 6 passes
unit is not overclocked left everything at factory settings
also tried reset bios to setup defaults still bluescreen

error code is

ntoskrnl.exe ntoskrnl.exe+ef6a2

i have attached the dump file if it helps

http://www.snetworks.com.au/072412-49686-01.rar

Well, it is explorer.exe that is actually causing the bluescreen. My first suggestion would be to update all of your storage drivers to the latest, and make sure you are installing signed drivers.

*******************************************************************************
* *
* 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: ffffffffffffffff, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000001, 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: fffff800016c3c22, address which referenced memory

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


WRITE_ADDRESS: ffffffffffffffff

CURRENT_IRQL: 2

FAULTING_IP:
nt!KxWaitForLockOwnerShip+12
fffff800`016c3c22 48890a mov qword ptr [rdx],rcx

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: DRIVER_FAULT_SERVER_MINIDUMP

BUGCHECK_STR: 0xA

PROCESS_NAME: explorer.exe

TRAP_FRAME: fffff880079ad910 -- (.trap 0xfffff880079ad910)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=00000000062fcc00 rbx=0000000000000000 rcx=fffff880079adb68
rdx=ffffffffffffffff rsi=0000000000000000 rdi=0000000000000000
rip=fffff800016c3c22 rsp=fffff880079adaa0 rbp=fffff880079adb40
r8=fffff800017fbe80 r9=0000000000000000 r10=fffff800018bb840
r11=0000058000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei ng nz na pe nc
nt!KxWaitForLockOwnerShip+0x12:
fffff800`016c3c22 48890a mov qword ptr [rdx],rcx ds:dbd0:ffffffff`ffffffff=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER: from fffff80001682469 to fffff80001682f00

STACK_TEXT:
fffff880`079ad7c8 fffff800`01682469 : 00000000`0000000a ffffffff`ffffffff 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
fffff880`079ad7d0 fffff800`016810e0 : 00000000`00000000 fffffa80`06810f60 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69
fffff880`079ad910 fffff800`016c3c22 : 00000000`00000000 fffffa80`0ca0d060 00000000`0000007f 00000000`00000001 : nt!KiPageFault+0x260
fffff880`079adaa0 fffff800`0169baf4 : fffffa80`06810f60 fffff900`c1af9018 00000000`00000000 fffff880`079ae000 : nt!KxWaitForLockOwnerShip+0x12
fffff880`079adad0 fffff800`01678c54 : 00000000`00000000 ffffffff`ffffffff 00000000`00000000 fffff960`000b97f8 : nt!MiInsertPageInFreeOrZeroedList+0x4e4
fffff880`079adbd0 fffff800`01678585 : 00000000`00000000 00000000`00000005 00000000`00000000 00000000`00000000 : nt!MiDeleteSystemPagableVm+0x254
fffff880`079add30 fffff800`017b234f : fffff900`c1c37010 fffff880`079ae080 00000000`00000001 fffff880`062fc000 : nt!MiFreePagedPoolPages+0x129
fffff880`079ade80 fffff800`017b687c : 00000000`00000000 fffff880`079ae050 fffff880`079adfc0 00000000`00000001 : nt!MiFreePoolPages+0x343
fffff880`079adf90 fffff960`00124ad8 : fffff900`c1af9228 00000000`00000000 00000000`35316847 00000000`00000001 : nt!ExFreePoolWithTag+0x7cc
fffff880`079ae040 fffff960`001252b2 : fffff900`c00be000 fffff900`c1af9000 00000000`00000000 fffff900`c1af9228 : win32k!FreeObject+0x58
fffff880`079ae070 fffff960`0012544c : 00000000`00000000 fffff880`00000000 fffff900`c1af9000 fffff900`00000000 : win32k!SURFACE::bDeleteSurface+0x58a
fffff880`079ae1c0 fffff960`000e661d : 00000000`0f0502a9 fffff900`c1af9000 00000000`0f0502a9 00000000`00000000 : win32k!bDeleteSurface+0x34
fffff880`079ae1f0 fffff800`01682153 : fffffa80`0cc66b60 fffff880`079ae2a0 00000000`0185000f fffff900`c00be000 : win32k!NtGdiDeleteObjectApp+0xd5
fffff880`079ae220 000007fe`ff52118a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`0980eb98 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7fe`ff52118a


STACK_COMMAND: kb

FOLLOWUP_IP:
win32k!FreeObject+58
fffff960`00124ad8 488b5c2430 mov rbx,qword ptr [rsp+30h]

SYMBOL_STACK_INDEX: 9

SYMBOL_NAME: win32k!FreeObject+58

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: win32k

IMAGE_NAME: win32k.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bc5e0

FAILURE_BUCKET_ID: X64_0xA_win32k!FreeObject+58

BUCKET_ID: X64_0xA_win32k!FreeObject+58

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

 

[RobbinHood]

cheers mate i just updated all my mainboard drivers installed latest rocketraid drivers and am copying 700gig atm will see how that goes overnight see if it bluescreens again

 

[haileris]

I definitely had this kind of issue on a Hyper-V box but can't exactly remember how I resolved it (or even if I did to be fair). Make sure you are upto date with patches and as mentioned earlier make sure you have latest storport / scsciport drivers.

Hotfix
Something like http://support.microsoft.com/kb/980135, http://support.microsoft.com/kb/976674 or http://support.microsoft.com/kb/2553708 might also be relevant. None of them appear to exactly match your issue though.