June 30, 201015 yr Hi,In my almighty wisdom I decided to try to overclock my system (again).I have a i5-661 with a ASUS Maximus III formula moboBasically the only thing I did was increasing the buspeed from 133 to 153 (multiplier stayed 25) and increased the RAM Voltage to 1.64.(I have 2 x 2GB Corsair PC3-10600 / 1600 RAM which should accept 1.65V)Everything else was left on AUTO settings.This resulted in a core speed of 3.850 Ghz (coming from 3.33 Ghz)I ran OCCT for an hour without any problem, CPU temp was stable a 53CNext I started FS2004, and boom: BSOD - Bad Pool Caller.Oki, no panic, end mission and just reset BIOS back to (automated) default. Started FS2004 again under my normal settings: bang, again BSOD.Also with other apps, I get the BSODMaybe I did blew up my memory. I ran 2 passes of Memtest86, without any problems.Houston....... do we have a problem?Anyone a suggestion how to proceed?Egbert Location: Vleuten, The Netherlands, 17.3dme SPL 108.40 | Simulator: FS2024 System: AMD 7800X3D - Gigabyte X670 - RTX 4090 - 64GB DDR5 - 2 x 2TB SSD - 32" 1440p Display - Windows 11 Pro
June 30, 201015 yr Hi,In my almighty wisdom I decided to try to overclock my system (again).I have a i5-661 with a ASUS Maximus III formula moboBasically the only thing I did was increasing the buspeed from 133 to 153 (multiplier stayed 25) and increased the RAM Voltage to 1.64.(I have 2 x 2GB Corsair PC3-10600 / 1600 RAM which should accept 1.65V)Everything else was left on AUTO settings.This resulted in a core speed of 3.850 Ghz (coming from 3.33 Ghz)I ran OCCT for an hour without any problem, CPU temp was stable a 53CNext I started FS2004, and boom: BSOD - Bad Pool Caller.Oki, no panic, end mission and just reset BIOS back to (automated) default. Started FS2004 again under my normal settings: bang, again BSOD.Also with other apps, I get the BSODMaybe I did blew up my memory. I ran 2 passes of Memtest86, without any problems.Houston....... do we have a problem?Anyone a suggestion how to proceed?EgbertAccording to info at the following link, this memory leak can be caused by corrupt software or a bad driver, such as a video card driver: http://aumha.org/a/stop.htm. I would uninstalled/reinstall the video card driver first and, if the BSOD continues, do the same to the sound card. I remember getting this error several years ago and remember pulling my DVD drive out and the crashes stopped. I replaced the DVD drive.Best regards,Jim
June 30, 201015 yr You can download BlueScreenView http://www.softpedia.com/get/System/Back-U...creenView.shtmlThis will tell you if the crash was caused by a program, a driver or hardware. Look at the information, do a little Google search and you will probably know what is causing it and how to fix it.
July 1, 201015 yr You can download BlueScreenView http://www.softpedia.com/get/System/Back-U...creenView.shtmlThis will tell you if the crash was caused by a program, a driver or hardware. Look at the information, do a little Google search and you will probably know what is causing it and how to fix it.Good advice! I saved that software link as a Favorite. Never know when you might get one of those nasty BSOD's!Jim
July 1, 201015 yr Author Hi all,Thanks for your replies!I'll download and run BlueScreenView and hopefully I can determine what exactly is the cause.On the positive side: When running XP under safe-mode, I can start up FS2004, so most likely it is indeed a driver issue.Keep you posted.Egbert Location: Vleuten, The Netherlands, 17.3dme SPL 108.40 | Simulator: FS2024 System: AMD 7800X3D - Gigabyte X670 - RTX 4090 - 64GB DDR5 - 2 x 2TB SSD - 32" 1440p Display - Windows 11 Pro
Create an account or sign in to comment