Win7 BSOD -new machine being built

jelson

jelson

Member
Joined
Aug 30, 2013
Posts
9
Hi!


·OS - Windows 7
· x64
· Windows 7 64-bit
· full retail version
· Age of system - New (~ 200 hrs on the hardware)
· Age of OS installation - New, clean retail install

· AMD Phenom II 995 Black Edition (X4 955)
· MSI N550GTX-Ti Cyclone II OC 1GD5
· ASUS M5A99X EVO
· Corsair TX650 V2 - 80 PLUS BRONZE

· Custom built
· no model #


This is new machine that I'm in the process of getting ready to serve as my primary machine

Very little is currently installed yet. Last installations were Photoshop CS 5 and Lightroom 3


While running FreeFileSync 5.18 (portable) to copy data files from the old machine to the new one, I experienced 3 BSODs on the 16th


Notes:

  • copied and subsequently updated a lot of user files over ethernet: ~ 97 K files (65 GB)
  • 1st 3 BSOD occured while I had switched back to the XP machine; didn't discover the crash until I switched back to the Win7 machine (using a KVM switch)

I've experienced 7 BSOD so far. All but 3 occurred while FFS was running.



  • Installed the Windows Debugger and ran analysis and also Nirsoft's BlueScreen View.

After doing some reading, decided to

  1. run MemTest86: ran overnight & completed over 7 passes with no errors logged
  2. run Kaspersky Rescue Disc 10 from USB: nothing found
  3. update FreeFileSync to 5.20


After updating FFS, experienced the next to last BSOD (on the 25th) while on the desktop (FFS not running)


After discovering this forum and reading some of the posts,
  • ran Driver Verifier for over 24 hrs: no problems

Last night, I had been processing photos in Lightroom 3 (for over an hour) when something went wrong as I clicked on a menu in Lightroom and got a BSOD (Driver Verifier was running)



  • Ran the BSOD app along with Perfmon and have zipped up the files.

Note: I've included the debugger analysis text for the 3 BSOD on the 16th (CCleaner deleted those 1st 3 dumps; changed that setting since.)


I've also installed and ran SeaTools for Windows
  • All 3 drives passed the SMART, Short DST & Short Generic tests. (didn't run the Long Generic)
  • Also, have had Hard Drive Sentinel Pro running on the machine for awhile: no problems with any of the drives
  • Samsung Drive Magician also says the SSD is fine.

BTW, I do have images of the system drive I can restore if need be (last ones taken before and after installation & activation of Photoshop and Lightroom)

So, would appreciate any advice, trying to systematically build up the new machine to be as lean and rock solid as my XP machine has been.

And I do realize that my nVidia driver is a bit old (Oct 2012): it's the last driver customized by MSI for their Geforce cards. Probably should move up to at least 314.22

Thanks in advance
 

Attachments

Hi,

All of the attached DMP files are of the SYSTEM_SERVICE_EXCEPTION (3b) bugcheck.

An exception happened while executing a routine that transitions from non-privileged code to privileged code.

This bugcheck is generally related to a video driver issue.

And I do realize that my nVidia driver is a bit old (Oct 2012): it's the last driver customized by MSI for their Geforce cards. Probably should move up to at least 314.22
Click to expand...

Wouldn't be surprised if this was the issue.

Ensure you have the latest video card drivers. If you are already on the latest video card drivers, uninstall and install a version or a few versions behind the latest to ensure it's not a latest driver only issue. If you have already experimented with the latest video card driver and many previous versions, please give the beta driver for your card a try.

  • Samsung Drive Magician also says the SSD is fine.
Click to expand...

Is the firmware up to date?

Regards,

Patrick
 
Thanks Patrick!

This is good news. :smile9:
I'll install 314.22 today (read of their being some instability problems with the 320.xx drivers-- mainly complaints on nVidia and other GPU forums.)

Heh... and I thought it was a good idea to use the MSI customized video driver :banghead:

Thanks again.

Oh yeah, the SSD firmware is up to date.
 
Let me know how it goes :+)

Heh... and I thought it was a good idea to use the MSI customized video driver
Click to expand...

It wasn't a bad idea per se, but it's always good to have the latest drivers for your devices. If you ever have a problem, that's when you can roll back a version or so.

Regards,

Patrick
 
Patrick said:
Let me know how it goes :+)

Heh... and I thought it was a good idea to use the MSI customized video driver
Click to expand...

It wasn't a bad idea per se, but it's always good to have the latest drivers for your devices. If you ever have a problem, that's when you can roll back a version or so.
Click to expand...

Will do...

So far so good: uninstalled the old one (306.97) and manually deleted the leftover nVidia folders. Then installed 314.22 WHQL (just Display driver & PhysX).

Any suggestions other than running Driver Verifier to check the system's stability?

Want to ensure the system is rock solid before I proceed further with the system build.

Thanx
 
Nope, good work for now! Keep me updated. If you go a few days without BSOD'ing, disable verifier and you should be in the clear.

Regards,

Patrick
 
I had such high hopes....

About an hour and a half from restarting the system with verifier running, got another BSOD: "PAGE_FAULT_IN_NONPAGED_AREA (50)" :(

Argh!

Had left AIMP 3 (portable) playing music and switched back to the old machine via KVM switch. Came back a several hours later to find it had BSOD'd.

So, I decided to see if I could stress the system and see if I got more BSODs before I reported back.

Long and short of it: have been running verifier for the last 50 hours without problem.

I installed prime95 and HWMonitor.

<with verifier running> Ran prime95 for about 15 hrs: for about 9 hrs I was running it's "Blends torture test" while I had MSI Kombustor running it furry GPU torture test (similar to FurrMark)

Don't know of any way to push the system any harder: CPU temp went from 27 to 43 C, MB from 25 to 33 C and GPU from 25 to 55 C

Later last night, I processed about 150 photos through Photoshop and Lightroom, still no trouble.

Now, I'm wondering if I need to

  1. run MemTest86 for a day or two
  2. also check the voltages on the extra PCIE power cable with a digital multimeter. (already checked the 12v on a molex)

Have any suggestions Patrick?

Reran the BSOD app & zipped up the folder: View attachment BSOD_docs_2013-09-04.zip

Note: I moved the previous minidumps to a "Saved" subfolder, so they aren't in the attachment
 
P.S. after reading some of the other posts, could Asus AI Suite be a potential source of the problem?
(Haven't overclocked the system or the GPU)
 
Due to the *50, I am going to recommend a Memtest for NO LESS than ~8 passes (several hours). If it passes, move on to hard disk diagnostics to be sure.

P.S. after reading some of the other posts, could Asus AI Suite be a potential source of the problem?
Click to expand...

Yes, I'd recommend removing that bloatware for now.

Memtest:

Memtest86+:

Download Memtest86+ here:

Memtest86+ - Advanced Memory Diagnostic Tool

Which should I download?

You can either download the pre-compiled ISO that you would burn to a CD and then boot from the CD, or you can download the auto-installer for the USB key. What this will do is format your USB drive, make it a bootable device, and then install the necessary files. Both do the same job, it's just up to you which you choose, or which you have available (whether it's CD or USB).

How Memtest works:

Memtest86 writes a series of test patterns to most memory addresses, reads back the data written, and compares it for errors.

The default pass does 9 different tests, varying in access patterns and test data. A tenth test, bit fade, is selectable from the menu. It writes all memory with zeroes, then sleeps for 90 minutes before checking to see if bits have changed (perhaps because of refresh problems). This is repeated with all ones for a total time of 3 hours per pass.

Many chipsets can report RAM speeds and timings via SPD (Serial Presence Detect) or EPP (Enhanced Performance Profiles), and some even support changing the expected memory speed. If the expected memory speed is overclocked, Memtest86 can test that memory performance is error-free with these faster settings.

Some hardware is able to report the "PAT status" (PAT: enabled or PAT: disabled). This is a reference to Intel Performance acceleration technology; there may be BIOS settings which affect this aspect of memory timing.

This information, if available to the program, can be displayed via a menu option.

Any other questions, they can most likely be answered by reading this great guide here:

FAQ : please read before posting

-------------------------------------------------------------------------------------------------------------

Chkdsk:

Chkdsk:
There are various ways to run Chkdsk~

Method 1:

Start > Search bar > Type cmd (right click run as admin to execute Elevated CMD)

Elevated CMD should now be opened, type the following:

chkdsk x: /r

x implies your drive letter, so if your hard drive in question is letter c, it would be:

chkdsk c: /r

Restart system and let chkdsk run.

Method 2:


Open the "Computer" window
Right-click on the drive in question
Select the "Tools" tab
In the Error-checking area, click <Check Now>.

If you'd like to get a log file that contains the chkdsk results, do the following:

Press Windows Key + R and type powershell.exe in the run box

Paste the following command and press enter afterwards:

get-winevent -FilterHashTable @{logname="Application"; id="1001"}| ?{$_.providername –match "wininit"} | fl timecreated, message | out-file Desktop\CHKDSKResults.txt

This will output a .txt file on your Desktop containing the results of the chkdsk.

If chkdsk turns out okay, run Seatools -

SeaTools | Seagate

You can run it via Windows or DOS. Do note that the only difference is simply the environment you're running it in. In Windows, if you are having what you believe to be device driver related issues that may cause conflicts or false positive, it may be a wise decision to choose the most minimal testing environment (DOS).

Run all tests EXCEPT: Fix All, Long Generic, and anything Advanced.

Regards,

Patrick
 
Interim report

ran MemTest for about 36 hrs: over 17 passes, no errors

Ran ChkDsk:


  • Samung SSD (boot drive): no errors
  • WD Black 1TB:
    • (data partition): single index error, "free space marked as allocated..." type, fixed
    • (storage partition): no errors
  • Seagate Green 2TB : error message only at the end: "The second NTFS boot sector is unwriteable."

Right now, I'm copying everything off the Seagate using Teracopy with CRC test.

Then I'll run SeaTools for DOS "Long Test" on the Seagate.
 
The Seagate passed the Short Test in SeaTools for DOS

Ran the Long Test, but the program halted sometime later (was sleeping during the Long Test) because it's looking for a floppy drive :(

Could still see part of the GUI and no results for Long Test were showing


So, ran the Self-Test and the Short Generic tests in SeaTools for Windows: the Seagate PASSED both.

Going ahead with the Long Generic on the Seagate since it tests the surface sectors.
 
The Seagate drive PASSED the Long Generic Test in SeaTools. (took ~ 7 hrs)

Did a full surface Read Test of it in Hard Drive Sentinel as well: PASSED too (took 6 hrs)

So, shrank the volume a bit via Disk Management and then extended it back to full disk size (Interestingly, Disk Defrag service has to be enabled in order to shrink a volume)

Then did a ChkDsk on it: No errors

NOTE: Driver Verifier has been running this whole time (6 days) without a BSOD
 

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top