Thanks for everyone's help.
Drivers were the first troubleshooting we went at.
I was able to debug the memory dump and got:
BugCheck A, {1c, 2, 1, 80132238}
Probably caused by : ntkrnlmp ( nt!MiDecrementCloneBlockReference+de )
Followup: MachineOwner
--------
and:
efe2fbdc 80132238 nt!KiTrap0E+0x284 (FPO: [0,0] TrapFrame @ efe2fbdc)
efe2fc68 80131285 nt!MiDecrementCloneBlockReference+0xde (FPO: [Non-Fpo])
efe2fcb4 80130f85 nt!MiDeletePte+0x29d (FPO: [Non-Fpo])
efe2fd74 801268db nt!MiDeleteVirtualAddresses+0x249 (FPO: [Non-Fpo])
efe2fe28 8019b6a0 nt!MmCleanProcessAddressSpace+0x21b (FPO: [Non-Fpo])
efe2fea4 8019b198 nt!PspExitThread+0x486
efe2feb0 8011b97d nt!P***itSpecialApc+0x1a (FPO: [5,0,1])
efe2feec 80141ba2 nt!KiDeliverApc+0x181 (FPO: [Non-Fpo])
efe2feec 4d00d2aa nt!KiExceptionExit+0x3a (FPO: [0,0] TrapFrame @ efe2ff04)
00d4dbb4 00000000 0x4d00d2aa
Now if only I knew what MiDecrementCloneBlockReference module was?
But I'm happy that the memory address from the blue screen and the stack call match.
I'm a little outta my element here, no real IT department and I run the intel. system (as a databases admin) on this box with little to no support (small company)