damicomdd
asked on
Upgrade from windows 2000 to windows 2003 caused server to constantly reboot
After upgrading our dell 2650 from windows 2000 to windows 2003 the server continues to reboot just after the windows 2003 splash screen. the memory dump has the following which I cannot find anything on:
BugCheck E1, {8041342e, 2, 85e6a168, 85e6a168}
Probably caused by : ntkrnlmp.exe ( nt!CcWorkerThread+0 )
Followup: MachineOwner
!analyze -v results:
WORKER_THREAD_RETURNED_AT_ BAD_IRQL (e1)
Arguments:
Arg1: 8041342e, address of worker routine (do ln on this to find guilty driver)
Arg2: 00000002, IRQL returned at (should have been 0, but isn't).
Arg3: 85e6a168, workitem parameter
Arg4: 85e6a168, workitem address
Debugging Details:
------------------
FAULTING_IP:
nt!CcWorkerThread+0
8041342e 55 push ebp
DEFAULT_BUCKET_ID: INTEL_CPU_MICROCODE_ZERO
BUGCHECK_STR: 0xE1
LAST_CONTROL_TRANSFER: from 804578ca to 80417b8c
STACK_TEXT:
f2043da8 804578ca 85e6a168 00000000 00000000 nt!ExpWorkerThread+0xf4
f2043ddc 8046c966 80417a98 00000000 00000000 nt!PspSystemThreadStartup+ 0x54
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16
STACK_COMMAND: .bugcheck ; kb
FOLLOWUP_IP:
nt!CcWorkerThread+0
8041342e 55 push ebp
FAULTING_SOURCE_CODE:
FOLLOWUP_NAME: MachineOwner
SYMBOL_NAME: nt!CcWorkerThread+0
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 4344ec59
FAILURE_BUCKET_ID: 0xE1_nt!CcWorkerThread+0
BUCKET_ID: 0xE1_nt!CcWorkerThread+0
Followup: MachineOwner
---------
2: kd> ln 8041342e
(8041342e) nt!CcWorkerThread | (804135d2) nt!ExFreeToPPNPagedLookasi deList
Exact matches:
nt!CcWorkerThread = <no type information>
BugCheck E1, {8041342e, 2, 85e6a168, 85e6a168}
Probably caused by : ntkrnlmp.exe ( nt!CcWorkerThread+0 )
Followup: MachineOwner
!analyze -v results:
WORKER_THREAD_RETURNED_AT_
Arguments:
Arg1: 8041342e, address of worker routine (do ln on this to find guilty driver)
Arg2: 00000002, IRQL returned at (should have been 0, but isn't).
Arg3: 85e6a168, workitem parameter
Arg4: 85e6a168, workitem address
Debugging Details:
------------------
FAULTING_IP:
nt!CcWorkerThread+0
8041342e 55 push ebp
DEFAULT_BUCKET_ID: INTEL_CPU_MICROCODE_ZERO
BUGCHECK_STR: 0xE1
LAST_CONTROL_TRANSFER: from 804578ca to 80417b8c
STACK_TEXT:
f2043da8 804578ca 85e6a168 00000000 00000000 nt!ExpWorkerThread+0xf4
f2043ddc 8046c966 80417a98 00000000 00000000 nt!PspSystemThreadStartup+
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16
STACK_COMMAND: .bugcheck ; kb
FOLLOWUP_IP:
nt!CcWorkerThread+0
8041342e 55 push ebp
FAULTING_SOURCE_CODE:
FOLLOWUP_NAME: MachineOwner
SYMBOL_NAME: nt!CcWorkerThread+0
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
DEBUG_FLR_IMAGE_TIMESTAMP:
FAILURE_BUCKET_ID: 0xE1_nt!CcWorkerThread+0
BUCKET_ID: 0xE1_nt!CcWorkerThread+0
Followup: MachineOwner
---------
2: kd> ln 8041342e
(8041342e) nt!CcWorkerThread | (804135d2) nt!ExFreeToPPNPagedLookasi
Exact matches:
nt!CcWorkerThread = <no type information>
ASKER
This was ans upgrade and I do believe it was the raid drivers that were the problem. The upgrade is finished now, how can i get back to a point to add the drivers?
You should be able to install from device manager by selecting the controllers properties and then selecting update driver
ASKER
The server reboots before it even gets to the logon screen so i cannot use the device manager
try starting in safe mode by pressing F8 on starting the Server up...
ASKER
Tried safe mode but after it goes through the driver list it reboots
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Has the Processor speed changed?
Could also be faulty RAM do you have one you can swap. (or take each one out one at a time?)