qn 1: Can frequent BSODs and a Memory stick with errors cause file corruption?

qn 2: for a SSD, is win7-64 disk mgmt->check now required/enuf?

 

Le Story:

Hi, I started having BSODs recently last week and many C2Ds on both FSX and XP10. In FSX, It usually happened around UK region and troubleshooting I found out I could turn off all Uk2000 free addons and was able to make a successful flight from EGNT-EGKK in the default A321. Tried replay immediately and had a C2D. Tried FSX repair option, then delete fsx.cfg, everything, and it would start and error out at some place. Finally now FSX just flat out refuses to start. XP10 starts, but XP10 installer just won't run so can't upgrade to beta. :nea:

 

Doing a memtest in between I found out one of the memory modules had errors, lots, so I removed it and I am only using 1 stick, 4GB (Corsair Vengeance). I don't have any anti-virus, just use microsoft security essentials, I am wondering if it could be a virus, but I have not used AV in 4 yrs and I have never had so many problems.

 

Computer config: 2x120 SSD (OS on SanDisk, FSX/XP10 on Corsair)

Mem: 1x4GB Corsair Vengeance 1600mhz (but Bios only shows 1333mhz)

Proc: i7-2700k 3.5Ghz, HT enabled, Auto OC

Mobo: Asus P8Z77-vPRO

Power: 950Watts Silencer Mk11

Tower: Cooler Master 920 with additional fans

Cooler: Corsair H80 (temps don't seem to be the problem so far, everything below 55degC at all times)

Video: nVidia 560ti DS (double-shot, right)

Software in use: FSX/Accel, REX, UT UK/USA, GEX USA, ASE networked, Asft EGLL (all this in the test area). I was able to make safe full flights yesterday over CONUS two times in the QW BAe, but now I can't open FSX, period.

 

Anyways, I decided to reinstall Win7 and FSX (oh how I dread that, just did it two months ago), but my second qn is, would I have to check the SSD for errors? I was concerned if that was causing the problems. Windows Device Management Check Now option reported absolutely no errors. I also started a lot of spikes in the video, really messed up scenery for a few seconds, random textures, but everything would return to normal, that was 12 hrs before the whole thing said bye bye... :Rolling Eyes:

 

I am in the process of taking backups, just software, but before I take the plunge and reinstall Win7, (this time getting the a/v just to be sure) and FSX and eventually XP10, is there a way to check and make sure these errors don't show up again in a week after install? I checked the other memory module already thru memtest and it came clean.

 

Also, if there are any suggested steps to try recovery, I will try it before I throw in the towel and restart from scratch. I do have time next week to try all this.

 

Irony is, I just read about Usepools=0 and got the best 30fps I have seen on my system, steady with NGX/FSDT JFK with sliders mostly to the right, *sigh* oh well!!

 

Any and all help/recommendations is most appreciated.

 

Best..,

Charan

Have you tried running with default bios settings? I see you've got auto OC on... not exactly sure what it's setting everything to. Can you download CPU-z and let us know what your vcore (core voltage) and core speed is? BSOD's usually come from overclocking issues, but also memory issues. Do you recall the error codes in the BSOD?

 

Also, have you run a stability testing program, like Intel Burn Test, Prime 95? IBT can be really rough on CPU's but a standard test would work fine.

 

Also I'd try disabling HT in BIOS.

Hey Ryan,

 

I was under the impression the BSODs were caused by the faulty memory, which is not in the system anymore. The CPU settings have been on auto while I was having the crashes themselves, and they still are, CPU-Z shows 0.976 at capture, but it went up 1.216, on an idle system. (image below)

 

My problem now is I can't launch FSX or repair it, even that won't work anymore, to see if I can get it to run a bit before it crashes again. Something looks corrupt, just can't tell which one though. XP10 launches but the installer/updater won't launch, so I am not sure if it will crash later or may continue without errors. I am just concerned about running the SSD into the ground. That's why I was curious if there were some chkdsk kind of tools for SSD, which I couldn't find.

 

I want to see if I can atleast save the Win7-64bit install, instead of reinstalling both Win7 and FSX.

 

 

The vcore is fine on idle... You said it went to 1.2v when you were flying? I run about 1.35v for 4.4GHz under full load. Did you build this yourself? I'd recommend settings BIOS defaults and seeing if that does anything. I think there might be two separate issues... disk corruption is a possibility in this case, but the crashes could be OCing related.

 

I know it's a PITA but I'd reinstall Windows, then with stock BIOS settings run some stability tests like IBT and make sure everything is stable at default settings. At this point I wouldn't even attempt to reinstall FSX or XP.

 

Out of curiosity are you running SSD RAID0?

No RAIDs, just two isolated SSDs, one for OS and one for FSX/XP10. I realized the windows installation is messed up, either corrupted or whatever happened, as renaming a folder fixed something. So the problem extends, so backing up stuff to reinstall windows.

 

I tried reinstalling XPX, and patched to Beta 9, two good flights. Copied scenery files from backup, and XPX died instantly, this was from the other drive on the same system. So guaranteed, either the messed up RAM or drive corrupted the files.

 

As soon as I finish backup, I will wipe the drive clean and reinstall Windows, try running XP as it doesn't need a reinstall and see what I get. I still haven't found a tool to diagnose SSDs, the one on windows says it's fine, so I am going to have to go with it.

 

The 1.2 Voltage spike was at idle, I couldn't start FSX...being single monitor setup, most of the time I don't run CPU-z, might have to run it this time.

 

I did build the system, meant to borrow other pieces of H/W and ended up being brand new all except monitor/key/mouse of course Video card which I had only got 2 week b4 system build. What sucks is some GoFlight modules hang even though connected to onboard USB 2.0 ports via hubs, that is something I need to figure out.

 

I have had the BIOS at default, which of course comes with HT enabled. I will go step by step this time and see what I get. Will keep IBT at the top of my list, cheers Ryan.

Sorry to hear of the issues... BSOD's are never fun to figure out... Post back here when Windows is reinstalled...

Here's the result of the IBT post Win7 Reinstall, and nick's tweaks minus FSX tweaks:

 

 

System looks a bit stable. Ran a full A/V scan from boot came back alright.

 

Of course I can't launch FSX as I am yet to figure out how to get it running without having to reinstall.

See signature to troubleshoot BSODs related to overclocking.

System looks a bit stable. Ran a full A/V scan from boot came back alright.

 

Back when I first built my system I turned memory frequency on the BIOS to auto. Bad move! I ran Intel Burn Test, Prime 95, Windows 7 memory diagnostics program, and ASUS's diagnostic program and all programs said I had passed every test and there was nothing wrong with my memory settings. Then, about a month or two later, after no BSOD's, no FSX crashes, no problems whatsoever, I start getting crashes. I did a lot of research and found that ASUS had issues with their motherboards in managing memory and it's best to do it manually. So, like Ryan stated above I got ahold of CPU-Z and looked under the SPD tab for the proper frequency, timings, and voltages for my memory. Since I wanted the highest frequency (1600Mhz), I looked to the far right column and it showed XMP-1600. So in order to get the highest frequency I had to change the BIOS profile from Manual to X.M.P, set the Frequency to 1600, then went to the timing page and set those figures as represented in the CPU-Z. The CPU-Z also stated the Dram Voltage should be 1.650 volts. That fixed everything and I have never had a crash since changing those settings. You live and learn...

 

Best regards,

Jim

Hi Jim,

 

thanks for that info...I have been looking at the bios and being confused on why a DDR3-1600Mhz chip will show max speed of 1333Mhz on auto. Only one good 4GB stick in the comp now, the other one is done in. the XMP-1600 profile only shows 1.50v, so I should be good with it. I will see how it goes.

 

I have completely already reinstalled Windows and FSX now, so far so good with the good remaining RAM.