|
|
![]() |
| Thread Tools | Search this Thread |
#1
| |||
| |||
Windows 8 - BSOD ERROR 0x00000124(ntoskrnl.exe+52a489) My newly installed windows 8 has started coming with BSOD ERROR 0x00000124(ntoskrnl.exe+52a489). I am not able to track out the exact cause of this issue. By now I have tried running a thorough scan in my system using Bit defender and have ran Scannow command as well. The BSOD occurs randomly but it has started coming up more frequently. I don?t have much experience with windows 8. I have been using it since a couple of months only. I never came across any BSOD when I was running windows 7, please suggest me an effective solution to deal with this error as soon as possible. |
#2
| |||
| |||
Re: Windows 8 - BSOD ERROR 0x00000124(ntoskrnl.exe+52a489) First try out below things and let me know if any one of them make any difference in your case:
|
#3
| |||
| |||
Re: Windows 8 - BSOD ERROR 0x00000124(ntoskrnl.exe+52a489) Before I suggest you anything, answer me the following questions, so that I can have better idea of your case: Have you made clean installation of windows 8 pro? How frequently the BSOD occurs? Have you made any hardware or software changes recently? How many ram sticks are installed in your system?? |
#4
| |||
| |||
Re: Windows 8 - BSOD ERROR 0x00000124(ntoskrnl.exe+52a489) My system is up to date with all recommended windows update installed. I have installed latest driver for all my hardware?s. I have run ccleaner in my system and it has cleared up some registry entries. I have installed latest bios for my Motherboard but I am still out of luck. Yes I have made clean installation of windows 8 pro. The BSOD occurs after every half an hour and I have to restart my system to get rid of the BSOD. I haven?t made any hardware changes in my system but I have installed some games and applications like rain meter, chrome browser etc which I used to use in windows 7 without any issues. I have single 4 GB ram stick installed in my system. Do I need to check anything else??? |
#5
| |||
| |||
Re: Windows 8 - BSOD ERROR 0x00000124(ntoskrnl.exe+52a489) If the BSOD is occurring so frequently then I guess there might be something wrong with your RAM. In that case you can try running memtest with memtest86+ overnight and check out if it comes clean. If you have any query regarding the memtest then you can feel free to ask, best of luck. |
#6
| |||
| |||
Re: Windows 8 - BSOD ERROR 0x00000124(ntoskrnl.exe+52a489) There are possibilities that some newly installed application might be causing this BSOD. However, I am not so sure about it but I would try uninstalling recently installed application one by one to find out the culprit one. If you want then you can perform a system restore as well. You can restore your system to a point when you were not having any such issues. Before performing system restore go through the affected program list so that you can make note of the applications and program that will be lost after the process. |
#7
| |||
| |||
Re: Windows 8 - BSOD ERROR 0x00000124(ntoskrnl.exe+52a489) Thanks for your suggestion guys there was something wrong with my RAM, it was not able to pass the memtest. I have installed a ram form one of my old systems and everything is working fine. God knows what went wrong with my new 4GB ram after installing windows 8. It worked fine for almost 8 months with windows 7. Anyways I am happy for getting rid of the BOSD, thanks for your help once again. |
![]() |
|
Thread Tools | Search this Thread |
|
![]() | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
Getting error 0x00000124 on Windows Server 2008 | NAKKIRAN | Operating Systems | 3 | 02-11-2010 04:13 AM |
BSOD - ntoskrnl.exe +70600 listed as cause - HELP! | Vigi | Operating Systems | 6 | 20-08-2010 06:41 AM |
Overclock BSOD 0x00000124 ERROR | Bnnyboy | Overclocking & Computer Modification | 7 | 16-08-2010 10:19 AM |
BSOD 0x00000124 for Windows 7 64 bit | gakar06 | Motherboard Processor & RAM | 1 | 16-08-2010 10:15 AM |
BSOD 'BAD_POOL_HEADER' ntoskrnl.exe | Ujagar | Operating Systems | 5 | 23-03-2010 11:25 AM |