August 19, 201213 yr This is a known issue with overclocked CPUs and I have provided you with the solution already. Turn off your power saving features in the BIOS, especially C states and speedstep. If this for some reason doesn't solve your problem, give the actual stop code as requested and the cause can be determined.
August 22, 201213 yr Hello again! I am sorry for being silent for a few days but my plan was to watch my system for at least three days and see how things are going. I have followed Alain’s precious advice as well as followed TechguyMaxC’s remarks. I did change some stuff in BIOS. However let me say again I am not a tech guy. So I may have done something incorrectly. Also please take it into consideration when seeing and pointing out my errors, no matter how stupid. Things trivial for you may be very difficult for me. After doing all I understand I should have, which was on Sunday (August 19) evening, I was happy not to see any more BSOD’s on Mondays as well as Tuesday. Well… until this morning. The best thing is I got another BSOD being at the AVSIM forum and… trying to write this post thanking you for curing my problem. LOL! Since then I got another (just a moment ago). I haven’t installed anything since Sunday. So one more time I would like to kindly ask you to be easy-going with me, a tech ignorant, and help me again (I hope the last time). I probably set something wrong, but this is not to my bad will but the low level of understanding what I am actually doing. I don’t want to paste many screenshots from BIOS, not to tire your eyes and bandwith. So, I decided to write down some info from BIOS which I believe may be of use. So now my BIOS, after some tweaking I did, is showing the following data: M.I.T.: BIOS version …F6 BLCK …100 MHz (all the time slighly changing when seen in BIOS) CPU Frequency …4013 MHz (all the time slighly changing when seen in BIOS) Memory Frequency …1600 MHz (all the time slighly changing when seen in BIOS) Total Memory Size …8192 MB CPU Temp …40 C Vcore …1.320 V DRAM Voltage …1.524 V CPU Clock Ratio … [40x] <-- choice is any value between 16 and 59 Real-Time Ratio Changes in OS … [disabled] BLCK/DMI/PEG Clock Control … [disabled] X.M.P. … [disabled] System Mem Multiplier (SPD) … [16.00] <--- other choices are: AUTO, 8.00, 10.66, 13.33, 16.00, 18.66, 21.33 Performance Enhance … [standard] DRAM Timinig (SPD) … [expert] Profile DDR Voltage …1.5 v Channel A Timing …9-9-9-24 and Command Rate 1 [Auto] <-- other values left at [AUTO] Channel B Timing … 9-9-9-24 and Command Rate 1 [Auto] <-- other values left at [AUTO] Dynamic Vcore (DVID) … +0.000 v [AUTO] Graphics DVID …+0.000 v [AUTO] DRAM Voltage … 1.500 v <-- choice is many values to mark (not type in) between 1.360 v and 2.400 v HDD S.M.A.R.T Capability … [disabled] eXtreme HDD (XHD) … [disabled] DCH SATA Control Mode … [AHCI] <-- choice is also IDE and RAID (XHD) POWER MANAGEMENT: ACPI Suspend Type …[S1(POS)] <-- the other option is S3(POS) HPET mode …[64-bit mode] <-- the other option is 32-bit mode AC Back Function … [Sort-Off] CPU Smart Fan Mode …[AUTO] <-- the other options are Voltage and PWM If there is anything wrong here, plese be so kind to tell me what and how to change it. And if there is anything else in BIOS you would like to know, just tell me and I will immediately check and report it. ------------------------------------------------------------------------------------------------------------------------------------------------ Now the CPU-Z and what it is showing now: ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- In the end the BlueScreenViewer’s BSOD errors from the last few days: I also have the WinDebugger, but I can’t get more info than in BSV, partly because I can’t cope with the symbols ('your debugger is not using correct symbols'). Can I hope for a little bit more of your patience and assistance? Thank you very much in advance. Have a great day/night wherever you are!
August 22, 201213 yr I will let tech. and Dazz take over from here since I don't have your hardware (some stuff does not change), as teck. said turn off your power saving features in the BIOS, especially C states and speedstep, I can see on your last screen shot that it's not disable because your core voltage on the CPU-z show 1.044v., it should always show 1.320 as seen on your bios screen shots. As far as not been a tech. guy don't worry about it, we all started somewhere. Good luck. PS: look like your memory spec. are 2T so you may want to manually set your command rate at 2T in bios, after your system is rock solid you may try 1T (with some minor adjustments ..maybe).
August 22, 201213 yr Dear Alain, I will let tech. and Dazz take over from here Fine. Then let me thank you very much for your assistance so far. I hope I will be able to do you a favour one day too. I am looking forward to hearing from tech and Dazz. turn off your power saving features in the BIOS, especially C states and speedstep I admit that post was the first place where I have ever heard about 'C states'! :blush: I went over to BIOS nad searched anything connected with C1, C2, C3, etc. So I changed C3 into C1 and also disabled one or two power settings. Looks like I didn't do my homework well, so I will immediately return to BIOS and restudy all entries. As for the 'speedstep', I wasn't able to find anything. I will certainly retry in a moment. look like your memory spec. are 2T so you may want to manually set your command rate at 2T in bios I will do it it no time. Thank you!
August 22, 201213 yr You will probably find C states and speedstep under "Advance CPU Core Features" or something like that, press enter and you'll have all the changeable settings . :good:
August 22, 201213 yr Speedstep may also be called "EIST" which stands for Enhanced Intel Speedstep Technology. You really must disable C states in addition to this in order for things to function correctly. Also, what voltage is your RAM rated for? Could you also download the tool "bluescreenview" and post a screen shot of the latest BSOD please?
August 22, 201213 yr Hey, guys! You are really fast. Thank you so much. You will probably find C states and speedstep under "Advance CPU Core Features" or something like that, press enter and you'll have all the changeable settings OK, thanks, here is this part of my BIOS and the situation: Speedstep may also be called "EIST" Bingo, found it now and disabled! Thank you. <--- The photo above was taken BEFORE I dosabled it. :wink: Also, what voltage is your RAM rated for? Please see the screen shown here by Alain (from another of my posts). Could you also download the tool "bluescreenview" and post a screen shot of the latest BSOD please? I did in the previous post, so I guess you want to see the full dll list too. OK, so here it is (the last one, no space for several BSOD reports). Sorry for the size, but it must be readable for you (I cut it into pieces to show you): Go to C:/windows/minidump and upload it's contents I can't open the DMP format, and the WInDBG gives me the problem I explained in my previous post. But of course I will post it: Loading Dump File [C:\Windows\Minidump\082212-20092-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: *** Invalid *** **************************************************************************** * Symbol loading may be unreliable without a symbol search path. * * Use .symfix to have the debugger choose a symbol path. * * After setting your symbol path, use .reload to refresh symbol locations. * **************************************************************************** Executable search path is: ********************************************************************* * Symbols can not be loaded because symbol path is not initialized. * * * * The Symbol Path can be set by: * * using the _NT_SYMBOL_PATH environment variable. * * using the -y <symbol_path> argument when starting the debugger. * * using .sympath and .sympath+ * ********************************************************************* Unable to load image \SystemRoot\system32\ntoskrnl.exe, Win32 error 0n2 *** WARNING: Unable to verify timestamp for ntoskrnl.exe *** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Personal Built by: 7601.17835.amd64fre.win7sp1_gdr.120503-2030 Machine Name: Kernel base = 0xfffff800`02e4b000 PsLoadedModuleList = 0xfffff800`0308f670 Debug session time: Wed Aug 22 19:11:15.852 2012 (UTC + 2:00) System Uptime: 0 days 0:41:30.054 ********************************************************************* * Symbols can not be loaded because symbol path is not initialized. * * * * The Symbol Path can be set by: * * using the _NT_SYMBOL_PATH environment variable. * * using the -y <symbol_path> argument when starting the debugger. * * using .sympath and .sympath+ * ********************************************************************* Unable to load image \SystemRoot\system32\ntoskrnl.exe, Win32 error 0n2 *** WARNING: Unable to verify timestamp for ntoskrnl.exe *** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe Loading Kernel Symbols ............................................................... ................................................................ ............. Loading User Symbols Loading unloaded module list .... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 51, {1, fffff8a00b3de410, 86bc000, 465} ***** Kernel symbols are WRONG. Please fix symbols to do analysis. ************************************************************************* *** *** *** *** *** Your debugger is not using the correct symbols *** *** *** *** In order for this command to work properly, your symbol path *** *** must point to .pdb files that have full type information. *** *** *** *** Certain .pdb files (such as the public OS symbols) do not *** *** contain the required information. Contact the group that *** *** provided you with these symbols if you need this command to *** *** work. *** *** *** *** Type referenced: nt!_KPRCB *** *** *** ************************************************************************* Probably caused by : ntoskrnl.exe ( nt+7f1c0 ) Followup: MachineOwner ---------
August 22, 201213 yr You're missing the symbols, upload the files, the dmp's in a zip file to dropbox or something
August 22, 201213 yr upload the files, the dmp's in a zip file to dropbox or something Done, sir! :smile: http://filesave.me/file/21525/dump-zip.html
August 22, 201213 yr Done, sir! :smile: http://filesave.me/f...5/dump-zip.html Did you install your motherboard's chipset drivers?
August 22, 201213 yr Did you install your motherboard's chipset drivers? All right, so I think it was like that: After reinstalling Windows (done e.g. to try to get rid of BSOD's) I installed them from the original mobo CD. But since the BSOD's did not disappear, I found newer (latest) drivers in the Net and installed them. It made no difference though.
August 22, 201213 yr All right, so I think it was like that: After reinstalling Windows (done e.g. to try to get rid of BSOD's) I installed them from the original mobo CD. But since the BSOD's did not disappear, I found newer (latest) drivers in the Net and installed them. It made no difference though. Ok, the crashes are caused by registry corruption, memory corruption, driver faults... just about everything at the lowest level. Why don't you try the Win 7 forum link I posted? There are very knowledgeable people there, I'm afraid I can only suggest an elimination process: - run memory (memtest) checks one stick at a time - run the WD Data LifeGuard diagnostic tool on your hard drive to check for HDD errors - make sure you have your BIOS reset to defaults, update your BIOS and do a clear-cmos - try running the system in safe mode for a while, if doesn't crash it may be a bad driver, then you can use driver verifier to find the offending driver
August 22, 201213 yr Hey, Dazz! Thank you very much for your help. the crashes are caused by registry corruption, memory corruption, driver faults... just about everything at the lowest level So the news is very bad. :sorry: Why don't you try the Win 7 forum link I posted? There are very knowledgeable people there I am afraid I would have to start it all from the beginning and be asked about the same things. I am sure you guys are extremely knowledgeable, so there will be no miracles. run memory (memtest) checks one stick at a time I already did but I will then do it again. run the WD Data LifeGuard diagnostic tool on your hard drive to check for HDD errors Ok, thanks, will do. So far I have only used CHKDSK and HD Tune. make sure you have your BIOS reset to defaults, update your BIOS and do a clear-cmos Sure I will, though it will not be easy (especially the clear-cmos I have to read about to start with). try running the system in safe mode for a while Yep, though you can see the time interval between two BSOD's may even be three days, so taking into consideration that it is not only my simming, but also my working and web computer, well... you can use driver verifier to find the offending driver I already did and took care of two such files. It didn't change anything. And nothing else has been reported. Once again for all your help. Looks like this is just a cursed computer (see also my blurries/jaggies threads). Have a calm night!
Create an account or sign in to comment