- Sep 15, 2013
- 174
- 0
- 10,680
I've kept track of the BSOD error messages I recieved (I may have missed some)
SYSTEM_THREAD_EXCEPTION_NOT_HANDLED (ACPI.sys)
BAD_POOL_HEADER
ATTEMPTED EXECUTE OF NO EXECUTE MEMORY
KMODE EXEPTION NOT HANDLED
MEMORY MANAGEMENT
Okay so the autorepair went on for over an hour to no avail, I got my boot disk out and even that autorepair failed.
Eventually I tried opening W8 in safe mode using CMD on the disk but when I used the bcdedit /set {default} safeboot network - I would get the message "The boot configuration store could not be opened. The requested system device cannot be found."
Eventually I tried another solution, which was to use sfc /scannow - which didn't do much.
I then tried bootrec /fixboot (from this thread's suggestion http://www.tomshardware.co.uk/answers/id-1704392/stupid-prepairing-automaic-repair-loop.html) and the repair managed to create a log file and I managed to log on.
Now I need your help in finding the problem - I know you will say it's probably memory but I really doubt it - I've never had a problem with RAM, I changed where the RAM was placed in the mobo and it still functioned in the BIOS and is working fine now. I suspect this may be a driver issue - how can I pinpoint what's causing this?
I'm a huge temperature freak, none of my parts overheated at the time of the crash, though I was playing a graphic intensive game.
Thank you.
SYSTEM_THREAD_EXCEPTION_NOT_HANDLED (ACPI.sys)
BAD_POOL_HEADER
ATTEMPTED EXECUTE OF NO EXECUTE MEMORY
KMODE EXEPTION NOT HANDLED
MEMORY MANAGEMENT
Okay so the autorepair went on for over an hour to no avail, I got my boot disk out and even that autorepair failed.
Eventually I tried opening W8 in safe mode using CMD on the disk but when I used the bcdedit /set {default} safeboot network - I would get the message "The boot configuration store could not be opened. The requested system device cannot be found."
Eventually I tried another solution, which was to use sfc /scannow - which didn't do much.
I then tried bootrec /fixboot (from this thread's suggestion http://www.tomshardware.co.uk/answers/id-1704392/stupid-prepairing-automaic-repair-loop.html) and the repair managed to create a log file and I managed to log on.
Now I need your help in finding the problem - I know you will say it's probably memory but I really doubt it - I've never had a problem with RAM, I changed where the RAM was placed in the mobo and it still functioned in the BIOS and is working fine now. I suspect this may be a driver issue - how can I pinpoint what's causing this?
I'm a huge temperature freak, none of my parts overheated at the time of the crash, though I was playing a graphic intensive game.
Thank you.
Facebook
Twitter
Instagram