C
Crocket-P
First let's go in the order of what happened:
* I pull out the old (Intel/LGA) CPU and in the process fatfinger the socket, bending three pins
* Using a small needle I bent the three pins back into place and put the new CPU in
* The computer turns on but the monitor and USB peripherals (mouse, keyboard, etc.) do not respond, internet tells me I need to update the BIOS
* Put old CPU in and computer turns on, begin to update BIOS
* BIOS update freezes and internet tells me my only option is to turn Computer off and hope it turns back on again, which I do
* Computer turns back on and BIOS reads as updated
* New CPU still does not work so I write it off and plan to return it
* Return old CPU and close up case, computer runs fine afterwards
* Two days later I am playing a game (Smite) and get the first BSoD I have ever had in my life
* I reboot and load the game again, after which I get another BSoD
I have now installed microsoft's debug tools but I can't make heads or tails of the dump file, other than it lists the process as Smite.exe (as in this process caused it or it was running during the event?) and the probable cause as "ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+29aa9 )"
Memory Dump: MEMORY.DMP
Continue reading...
* I pull out the old (Intel/LGA) CPU and in the process fatfinger the socket, bending three pins
* Using a small needle I bent the three pins back into place and put the new CPU in
* The computer turns on but the monitor and USB peripherals (mouse, keyboard, etc.) do not respond, internet tells me I need to update the BIOS
* Put old CPU in and computer turns on, begin to update BIOS
* BIOS update freezes and internet tells me my only option is to turn Computer off and hope it turns back on again, which I do
* Computer turns back on and BIOS reads as updated
* New CPU still does not work so I write it off and plan to return it
* Return old CPU and close up case, computer runs fine afterwards
* Two days later I am playing a game (Smite) and get the first BSoD I have ever had in my life
* I reboot and load the game again, after which I get another BSoD
I have now installed microsoft's debug tools but I can't make heads or tails of the dump file, other than it lists the process as Smite.exe (as in this process caused it or it was running during the event?) and the probable cause as "ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+29aa9 )"
Memory Dump: MEMORY.DMP
Continue reading...