November 26, 201213 yr Hello, i always get a Bluescreen with my new PC. Its very bad. What i do: Bios reset, CPU fan, PC fan, ne drivers, new graphic card...but nothing of that help. Betriebssystem: Windows 7 64 bit -Seagate ST2000DM001 2TB -ASUS P8H67-M EVO R.3.0 -Kingston HypermaX DIMM 8 GB DDR3-1333 Ke -Intel Core i7 2600 -GTX 560ti-Enermax PRO082+II 525W I have some Aerosoft addons... Can you help me?
November 26, 201213 yr Try using a benchmark program to see if it is FSX or a general problem. See here for benchmark programs that can be used to test the stability and speed of your PC: http://simmerhead.files.wordpress.com/2012/02/bench04.jpg Simmerhead - Making the virtual skies unsafe since 1987!
November 26, 201213 yr Try this freeware program which reads the file to give you some clues where the trouble lies: http://download.cnet.com/BlueScreenView/3000-2094_4-10965136.html Noel Noel System: 9900X3D Noctua NH-D15 G2, MSI Pro 650-P WiFi, G.SKILL 64GB (2 x 32GB) 288-Pin PC RAM DDR5 6000, WD NVMe 2Tb x 1, Sabrent NVMe 2Tb x 1, RTX 4090 FE, Corsair RM1000W PSU, Win11 Home, LG Ultra Curved Gsync Ultimate 3440x1440, Phanteks Enthoo Pro Case, TCA Boeing Edition Yoke & TQ, Cessna Trim Wheel, RTSS Framerate Limiter w/ Front Edge Sync. Aircraft used in MSFS 2024: Fenix A320, Aerosoft CRJ, FBW, WT 787X, I-Fly 737 MAX 8, Citation Longitude.
November 26, 201213 yr Bluescreens are usually hardware related, but run some Prime95, aida and Intel Burn Tests to check overall stability. 101 stop seems to point to cpu and it usually occurs when overclocked with too little Vcore. If you are running stock, check that your cooler is attached firmly and that all the capacitors and mosfets look healthy on the MB. If you are running unstable overclocks, up the voltages or lower the oc accordingly and test the stability with Prime95 by running it 8 hours minimum, preferably a day.
November 26, 201213 yr Download and install debugging tools for windows ... Set your windebug to point to ms symbols .. Load the memory.dmp file in the debugger and analyze the crash dump ...
November 28, 201213 yr This is the best link for troubleshooting this BSOD -a clock interrupt was not received on a secondary processor: http://www.sevenforums.com/crash-lockup-debug-how/63501-stop-0x101-clock_watchdog_timeout-troubleshtg.html. I also found that one person fixed this problem by updating his BIOS. I'm moving this up to the CTD forum. Thanks! Best regards, Jim This is an automatic message. This topic has been moved from "MS FSX Forum" to "Crash To Desktop (CTD) Forum". This move has been done for a number of possible reasons. The most likely reason is that the post was off topic. The topic could also have contained images or a video that were not appropriate to the original forum it was posted in. The images might not have been "illustrative" or "explanatory" in nature. The topic could have been moved because we deemed it to be more appropriately placed elsewhere. Please ensure that your posts are "on topic" and contain illustrative images or videos as appropriate. Do not post videos or images just for entertainment purposes anywhere but in the screen shot or video forums. Members who continue to post off topic posts can be denied entry to specific forums in order to reduce and remove the practice. Your cooperation is appreciated. Jim Young | AVSIM Online! - Simming's Premier Resource! Member, AVSIM Board of Directors - Serving AVSIM since 2001 Submit News to AVSIMImportant other links: Basic FSX Configuration Guide | AVSIM CTD Guide | AVSIM Prepar3D Guide | Help with AVSIM Site | Signature Rules | Screen Shot Rule | AVSIM Terms of Service (ToS) I7 8086K 5.0GHz | GTX 1080 TI OC Edition | Dell 34" and 24" Monitors | ASUS Maximus X Hero MB Z370 | Samsung M.2 NVMe 500GB and 1TB | Samsung SSD 500GB x2 | Toshiba HDD 1TB | WDC HDD 1TB | Corsair H115i Pro | 16GB DDR4 3600C17 | Windows 10
Create an account or sign in to comment