Raiden72 Posted May 26, 2007 Posted May 26, 2007 (edited) I installed the upgrade. Everytime it starts up after the green loading bar, it gives me the blue screen of death. Here is what's from the memory.dmp. Shouldn't be too hard to find an explanation please help!BugCheck 7E, {c0000005, 81836f72, 82468a68, 82468764}*** ERROR: Module load completed but symbols could not be loaded for mssmbios.sys ????***** Kernel symbols are WRONG. Please fix symbols to do analysis.**************************************************************************** ****** ****** Your debugger is not using the correct symbols ****** ****** In order for this command to work properly, your symbol path ****** must point to .pdb files that have full type information. ****** ****** Certain .pdb files (such as the public OS symbols) do not ****** contain the required information. Contact the group that ****** provided you with these symbols if you need this command to ****** work. ****** ****** Type referenced: nt!_KPRCB ****** ******************************************************************************************************************************************************** ****** ****** Your debugger is not using the correct symbols ****** ****** In order for this command to work properly, your symbol path ****** must point to .pdb files that have full type information. ****** ****** Certain .pdb files (such as the public OS symbols) do not ****** contain the required information. Contact the group that ****** provided you with these symbols if you need this command to ****** work. ****** ****** Type referenced: nt!KPRCB ****** ******************************************************************************************************************************************************** ****** ****** Your debugger is not using the correct symbols ****** ****** In order for this command to work properly, your symbol path ****** must point to .pdb files that have full type information. ****** ****** Certain .pdb files (such as the public OS symbols) do not ****** contain the required information. Contact the group that ****** provided you with these symbols if you need this command to ****** work. ****** ****** Type referenced: nt!_KPRCB ****** ******************************************************************************************************************************************************** ****** ****** Your debugger is not using the correct symbols ****** ****** In order for this command to work properly, your symbol path ****** must point to .pdb files that have full type information. ****** ****** Certain .pdb files (such as the public OS symbols) do not ****** contain the required information. Contact the group that ****** provided you with these symbols if you need this command to ****** work. ****** ****** Type referenced: nt!KPRCB ****** ******************************************************************************************************************************************************** ****** ****** Your debugger is not using the correct symbols ****** ****** In order for this command to work properly, your symbol path ****** must point to .pdb files that have full type information. ****** ****** Certain .pdb files (such as the public OS symbols) do not ****** contain the required information. Contact the group that ****** provided you with these symbols if you need this command to ****** work. ****** ****** Type referenced: nt!_KPRCB ****** ******************************************************************************************************************************************************** ****** ****** Your debugger is not using the correct symbols ****** ****** In order for this command to work properly, your symbol path ****** must point to .pdb files that have full type information. ****** ****** Certain .pdb files (such as the public OS symbols) do not ****** contain the required information. Contact the group that ****** provided you with these symbols if you need this command to ****** work. ****** ****** Type referenced: nt!_KPRCB ****** ****************************************************************************Probably caused by : ntkrnlmp.exe??????? ( nt!KeSynchronizeExecution+12 )Followup: MachineOwner---------MODULE_NAME: ntFAULTING_MODULE: 81800000 ntDEBUG_FLR_IMAGE_TIMESTAMP: 4549ad6cEXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at "0x%08lx" referenced memory at "0x%08lx". The memory could not be "%s".FAULTING_IP: nt!KeSynchronizeExecution+1281836f72 f00fba2b00 lock bts dword ptr [ebx],0EXCEPTION_RECORD: 82468a68 -- (.exr 0xffffffff82468a68)ExceptionAddress: 81836f72 (nt!KeSynchronizeExecution+0x00000012) ExceptionCode: c0000005 (Access violation) ExceptionFlags: 00000000NumberParameters: 2 Parameter[0]: 00000001 Parameter[1]: 0000001cAttempt to write to address 0000001cCONTEXT: 82468764 -- (.cxr 0xffffffff82468764)eax=85ba4000 ebx=0000001c ecx=8041d300 edx=84c07000 esi=85ba4000 edi=84c1d028eip=81836f72 esp=82468b30 ebp=82468b74 iopl=0 nv up ei pl zr na pe nccs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00210246nt!KeSynchronizeExecution+0x12:81836f72 f00fba2b00 lock bts dword ptr [ebx],0 ds:0023:0000001c=????????Resetting default scopeDEFAULT_BUCKET_ID: WRONG_SYMBOLSBUGCHECK_STR: 0x7ELAST_CONTROL_TRANSFER: from 82468b9c to 81836f72STACK_TEXT: WARNING: Stack unwind information not available. Following frames may be wrong.82468b74 82468b9c 8189a8b8 85ba271c 85ba2600 nt!KeSynchronizeExecution+0x1200000000 00000000 00000000 00000000 00000000 0x82468b9cFOLLOWUP_IP: nt!KeSynchronizeExecution+1281836f72 f00fba2b00 lock bts dword ptr [ebx],0SYMBOL_STACK_INDEX: 0SYMBOL_NAME: nt!KeSynchronizeExecution+12FOLLOWUP_NAME: MachineOwnerIMAGE_NAME: ntkrnlmp.exeSTACK_COMMAND: .cxr 0xffffffff82468764 ; kbBUCKET_ID: WRONG_SYMBOLSFollowup: MachineOwner---------wtf? Edited May 26, 2007 by Raiden72
Shark007 Posted May 26, 2007 Posted May 26, 2007 Are you overclocking? If so, set it to defaults.Is your computer more than 8 months old and you live in an older building?your fans/heatsinks (esp. on the CPU) may be clogged and in need a cleaning.When cleaning with compressed air, do not allow the air to spin the fans.It will turn them to fast and damage the bearings/bushings.shark
cluberti Posted May 26, 2007 Posted May 26, 2007 Would it be possible for you to post the .dmp here, or put it somewhere we can all get to it?
Raiden72 Posted May 26, 2007 Author Posted May 26, 2007 That dmp file was 43mb. I was upgrading from windows XP home OEM edition to Vista home premium. Here's another piece of what happened: When i tried to put it in safe mode it started loading a bunch of the drivers and stuff and the last one it loaded was crcdisk.sys and then it restarted the computer. IDK how a dmp file could help so much
cluberti Posted May 28, 2007 Posted May 28, 2007 That dmp file was 43mb. I was upgrading from windows XP home OEM edition to Vista home premium. Here's another piece of what happened: When i tried to put it in safe mode it started loading a bunch of the drivers and stuff and the last one it loaded was crcdisk.sys and then it restarted the computer. IDK how a dmp file could help so muchBecause it tells us what happened, that's how. If you can zip it and place it somewhere we can get to it, that might help (no guarantees, but it might).
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now