Solved New Build and got a BSOD after doing windows update

[NDJeff]

I just built a new computer from scratch and installed Windows 7 Pro x64. Install was no problem but when I did a Windows Update I got the BSOD. It has also happened two more times. I have not installed anything else on this computer except for:

- LAN Drivers
- Audio Drivers
- Trend Micro Titanium Internet Security 2012

If anyone could help me sort this out I'd greatly appreciate it. I've done a few builds before with XP and had no problems.

 

[NDJeff]

As an update here, all the hardware that I'm running is brand new except for my graphics card which is about 7 years old. It's an ASUS EN6200 Nvidia card. Could this be something that is causing the crashes?

 

[usasma]

I've seen several issues recently with Trend Micro - all on fairly new installations. Try this:

Anti-Virus Removal:
Please do the following:
- download a free antivirus for testing purposes: Free AntiVirus
- uninstall the antivirus software from your system (you can reinstall it, if so desired, when we're done troubleshooting)
- remove any remnants of the antivirus software using one of these free tools: Antivirus Uninstallers
- IMMEDIATELY install and update the free antivirus
- check to see if this fixes the BSOD's
NOTE: NEVER run more than 1 anti-virus, firewall, Internet Security/Security Center application at the same time.

Drivers for your USB 3.0 controller aren't installed. You can get them from the motherboard manufacturer's download website.

Only 55 updates after SP1 - most systems have 70 or more after SP1. Please check with Windows Update and get any available updates

We've seen BSOD issues with SSD's as the technology tries to mature. Here's what I've compiled so far:

There's not a whole bunch available to test SSD's. The "easiest" test is to remove the SSD, install a platter-based hard drive, install Windows and test for stability that way.

Here's some suggestions:
- Update the SSD's firmware to the latest available version (VERY IMPORTANT!!!)
- Slow the memory (RAM) down to the next slower speed (I've only seen one person who claimed that this worked for them).
- Use any manufacturer's utilities that you may have. If you don't have any, then try this free one (I haven't used it myself): Crystal Dew World
- Update chipset and storage controller drivers to the latest available from the manufacturer of the device (not the manufacturer of the motherboard). Be sure to update ALL controllers on the motherboard!
....NOTE: Recently (Nov 2011) we had BSOD issues with the Marvell 91xx controller and an SSD. You may have to switch controllers also.-
Replace the SSD with a platter based hard drive and see if that stops the BSOD's. If it does, then it's likely that there's a problem with the SSD OR an incompatibility with your system.
It's my opinion that SSD's aren't reliable enough (with current hardware) to be used on a system that needs to work reliably. Until I see reliability I will not recommend, nor will I use, SSD's for critical applications.
06 Dec 2011 - This post tends to confirm issues with certain SSD chipsets and certain controllers - [SOLVED] cant find the cause of BSOD F4 - Tech Support Forum

nVidia video drivers date from 2009, please update them immediately: Graphics Driver - GeForce 285.62 Driver - GeForce

Driver Verifier enabled memory dump blamed a core Windows component. Since this is unlikely, we have to suspect a hardware issue (which includes compatibility issues, low-level driver problems, and maybe even malware).
I don't know which 3rd party drivers you tested, so I can't comment on that possibility.

IMO I'd try removing the Trend Micro stuff first. If that doesn't stop the BSOD's, then I'd run Driver Verifer according to these directions: Driver Verifier Settings

BSOD BUGCHECK SUMMARY

[font=lucida console]
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\012412-7971-01.dmp]
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Tue Jan 24 10:02:30.229 2012 (UTC - 5:00)
System Uptime: 0 days 0:13:39.836
Probably caused by : ntkrnlmp.exe ( nt!KiKernelCalloutExceptionHandler+e )
BUGCHECK_STR:  0x1E_0
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x1E_0_nt!KiKernelCalloutExceptionHandler+e
Bugcheck code 0000001E
Arguments 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000
BiosVersion = 0901
BiosReleaseDate = 11/24/2011
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\012412-8221-01.dmp]
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Tue Jan 24 09:47:51.288 2012 (UTC - 5:00)
System Uptime: 0 days 0:14:50.521
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+4874 )
DRIVER_VERIFIER_DETECTED_VIOLATION (c4)
BUGCHECK_STR:  0xc4_91
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  TrustedInstall
FAILURE_BUCKET_ID:  X64_0xc4_91_nt!_??_::FNODOBFM::_string_+4874
Bugcheck code 000000C4
Arguments 00000000`00000091 00000000`00000000 fffffa80`07b53b60 00000000`00000000
BiosVersion = 0901
BiosReleaseDate = 11/24/2011
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\012412-5865-01.dmp]
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Tue Jan 24 09:13:33.060 2012 (UTC - 5:00)
System Uptime: 0 days 0:01:50.667
Probably caused by : ntkrnlmp.exe ( nt!KiKernelCalloutExceptionHandler+e )
BUGCHECK_STR:  0x1E_0
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x1E_0_nt!KiKernelCalloutExceptionHandler+e
Bugcheck code 0000001E
Arguments 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000
BiosVersion = 0901
BiosReleaseDate = 11/24/2011
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
  
  [/font]

 

[NDJeff]

Thank you very much for your help usasma! I tried a couple different things.

• I uninstalled Trend Micro and installed the free one from Microsoft but I still had a BSOD after that
• I updated the drivers for the video card and installed the ones for the USB
• I still had crashing issues so the last thing I did on your list was update the firmware for my SSD and so far I've been crash free.

Since then I've been able to download/install all the windows updates and a couple other programs I need. So fingers crossed but everything looks good so far! Thanks!

 

[NDJeff]

Alright, so here's the newest update:

• It looked like the firmware update for the SSD was doing the trick but then I had another crash last night.
• My next step was to put in a regular hard drive and install windows 7 there
• I installed Windows 7 on the regular hard drive and as I was scanning the computer with the free Microsoft anti-virus I got another BSOD
• This leads me to believe that it can't be the SSD since the same thing happened with a regular hard drive

Are there any suggestions on what my next step should be?

 

[usasma]

Zip up and upload the memory dumps so we can have a look at them.

 

[NDJeff]

Here's a quick question before I get the memory dumps again.

I ran a memtest and it came back with no errors, however it said my memory was running at 11-11-11-28 and the specifications that came with my memory said it should be 9-9-9-24. I went into bios and switched it to the manufacturers specs.

Do you think this is what was causing my BSOD's?

 

[usasma]

It's possible. Leave it the way it is for a couple of days and see if it blue screens.
Then put the timings back to the other level and try it for a few days.
That'll tell you if that's the cause or not.

 

[Dave76]

Welcome to Seven Forums.

We need to know what components you have.
Can you post your system specs.
Use this link to find your system specs.
Speccy Free System information Utility
Then click the 'My System Specs' dropbox in any of your posts.

Go to your motherboard website and download and install all the drivers for your board.
Which BIOS version do you have?

When you get a crash on a new build it's a good idea to take a close look at the hardware and it's settings in BIOS.

Can you download CPUZ and post a snip of the CPU, Mainboard, Memory, and SPD tabs.
For posting the information , enter 'Snipping tool' in the Start button > Search box, hit enter. Select the area you want to post and save to a convenient place. Then post the screen shot in your next post, use this tutorial to do it.
How to Post a Screenshot in Seven Forums

With this information we can make better suggestions to find the cause of the crashes.

 

[NDJeff]

Well, I changed to setting on the memory to 9-9-9-24 and I thought it made a difference until I got a couple crashes today. I put my system specs up here so everyone can look at them. I am going to attach the pics I got from CPU-Z here. Hopefully this can give you guys a clue as to what is going on here. Please let me know if you need any other information.

 

[Dave76]

There is a known issue with some AMD CPU Integrated Memory Controllers (IMC) that have BSoDs when running RAM above 1333MHz.

For testing purposes manually set your RAM frequency to 1333MHZ (may be 666MHZ in your BIOS), RAM timings to 9-9-9-24, leave the rest on auto, and the 'Command Rate' to 2T.
Save and Exit your BIOS.

Go to your BIOS and tell us what the CPU, RAM and the CPU integrated memory controller voltages are.
Look for DRAM and CPU VTT voltages.
In your next post tell us these voltages.

 

[NDJeff]

Alright, I changed those RAM setting in BIOS and have made a note of the voltages.

The CPU (VCORE) voltage is 1.392
RAM Voltage is 1.500

I could not find anything called CPU VTT Voltage anywhere. I did find one called CPU VDDA Voltage and that is 2.496. Some of the other voltages I see are:

NB Voltage = 1.100
SB Voltage = 1.100

Let me know if these are what you are looking for. If you need more info I can get that to you. Thanks!

 

[Dave76]

It's the CPU/NB voltage, the CPU integrated memory controller voltage.

With 8GB RAM the DRAM and CPU/NB voltage might need a small bump.

Most CPUs will need a CPU-NB Voltage boost of +0.10V, so if your default is 1.10V, set it to 1.20V.

 

[NDJeff]

Okay, what do you think I should change those voltages to? By CPU/NB voltage do you mean the item listed just as NB Voltage at 1.100V?

 

[Dave76]

It's not the NB voltage.

It's CPU/NB voltage, See page 3-7 and 3-12 of your ASUSTek M5A97 motherboard manual.

See my last post, for voltage setting for the CPU/NB voltage.

Change the CPU & NB Voltage from [Offset mode] to [Manual mode].
Then set the CPU/NB voltage to +0.10V of the current setting, so if your default is 1.10V, set it to 1.20V.

Post the full set of cash files if you get another one.
We need these to analyze the BSoDs.

 

[NDJeff]

Okay, so when I'm in BIOS and I change CPU & NB Voltage to "manual" mode then I get a line item for:

CPU/NB Manual Voltage = 1.125V

Per your previous post you mean I should bump this up to 1.225V?

Also, what is your suggestion for a change on the DRAM voltage?

Thanks very much for your help!

 

[Dave76]

Yes change the CPU/NB Manual Voltage to 1.225V.
Check for stability.
If you get another crash, post the dump files and other supporting files.

See if this runs stable, it should.
If not, then another CPU/NB voltage bump to 1.300v.
That RAM should run stable at DRAM 1.500v, we'll see after the CPU/NB bump to 1.225v.

 

[NDJeff]

Will do. Thanks Dave, I really appreciate your help on this.

 

[Dave76]

You're Welcome.

 

[NDJeff]

It's been a few days and so far so good with the changes that you suggested I make. The real test will be on Monday when I put a full day of work on it, but no crashes at all this week. Thanks!