Need help interpreting Crash dump analysis

I have a win2k3 R2 SP2 server that randomly BSODs.  The only hardware I have tried replacing is the RAM chips though that doesn't seem to have made a difference.  I recently ran a crash dump analysis with Microsofts tool.  I have never used it before and am not very familiar with how to read it but my impression is it's a driver issue.  Any additional input would be appreciated, thanks.  Let me know if I need to submit something further to help.
Loading unloaded module list
0: kd> !analyze -v
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
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 kernel debugger is available get stack backtrace.
Arg1: 00000000, memory referenced
Arg2: d0000002, IRQL
Arg3: 00000008, value 0 = read operation, 1 = write operation
Arg4: 00000000, address which referenced memory
Debugging Details:
GetContextState failed, 0x80070026
Unable to read selector for PCR for processor 1
*** WARNING: Unable to verify timestamp for cdrom.sys
*** ERROR: Module load completed but symbols could not be loaded for cdrom.sys
GetContextState failed, 0x80070026
Unable to read selector for PCR for processor 1
READ_ADDRESS:  00000000 
00000000 ??              ???
TRAP_FRAME:  8089a538 -- (.trap 0xffffffff8089a538)
ErrCode = 00000010
eax=89ecd000 ebx=00000000 ecx=ffdffa48 edx=ffdffa40 esi=8a544240 edi=ffdffa40
eip=00000000 esp=8089a5ac ebp=8089a600 iopl=0     vif nv up ei pl zr na pe nc
cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00090246
00000000 ??              ???
Resetting default scope
LAST_CONTROL_TRANSFER:  from 00000000 to 8088c963
00000000 ??              ???
8089a538 00000000 badb0d00 ffdffa40 8a5188bc nt!KiTrap0E+0x2a7
WARNING: Frame IP not in any known module. Following frames may be wrong.
8089a5a8 808320f0 8a544240 00000000 b9c9e160 0x0
8089a600 8088de1f 00000000 0000000e 00000000 nt!KiRetireDpcList+0xca
8089a604 00000000 0000000e 00000000 00000000 nt!KiIdleLoop+0x37
8088c963 833da0628a8000  cmp     dword ptr [nt!KiFreezeFlag (808a62a0)],0
SYMBOL_NAME:  nt!KiTrap0E+2a7
FOLLOWUP_NAME:  MachineOwner
IMAGE_NAME:  ntkrpamp.exe
BUCKET_ID:  0xD1_CODE_AV_NULL_IP_nt!KiTrap0E+2a7
Followup: MachineOwner

Open in new window

Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

QlemoBatchelor, Developer and EE Topic AdvisorCommented:
Not very useful, that crash dump. The BSOD is caused by a driver, but as the information is almost completely invalid either the unknown driver corrupts memory (unlikely) or it is a memory failure. As you have exchanged RAM already, I'm stuck. Are you overclocking RAM?

If can get a hand on the next dump, compare it with this one. Should it show a completely different exception as D1, and/or changing module info, this confirms the suspicion. You should run a burn-in memory testing tool like MemTest86+ ( to make sure RAM and memory bus are ok.
CyberDocSupportAuthor Commented:
No overclocking on the memory.....I'll try something like memtest and keep an eye out for the next dump as well.
CyberDocSupportAuthor Commented:
Ran Memtest for 12+ hours with no errors reported.
Newly released Acronis True Image 2019

In announcing the release of the 15th Anniversary Edition of Acronis True Image 2019, the company revealed that its artificial intelligence-based anti-ransomware technology – stopped more than 200,000 ransomware attacks on 150,000 customers last year.

QlemoBatchelor, Developer and EE Topic AdvisorCommented:
So we have to wait for the next crash, I reckon ...
CyberDocSupportAuthor Commented:
Seems that way.  The way things are going that won't be very long..........
CyberDocSupportAuthor Commented:
Turns out it was a motherboard problem.  Replacing it seems to have fixed the issue

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
System Utilities

From novice to tech pro — start learning today.