Windows7 Blue Screening/crashes

[Antichrist]

Ok I can't figure this out, and I've been having problems for a few weeks now, so I'll ask here.

 

I built this PC 2 years ago.

 

Specs:

 

Motherboard: Asus M5A97

CPU: AMD FX 6100 @ 3.3 (Not overclocking)

RAM: Corsair Vengeance 16GB (4x4GB)

HDD: Seagate Barracuda 1TB 7200 RPM 32MB cache SATA

Video: EVGA GTS450 (1GB) (Nvidia)

Sound: Onboard Realtek 5.1 digital audio

PSU: 730 Raidmax

OS: Windows 7 64 bit

AV: Microsoft Windows Defender (No other AV programs in use)

 

Everything worked perfectly on the PC. No crashes. No blue screens. No problems or complaints.

I recently got a virus (Thanks Tumblr) Which was the newest Moneypak virus, and did not allow me to boot into safe mode for removal, as when I did, each time it would just restart the PC into normal mode. So I decided to format, and reinstall Windows 7 again, and start fresh.

 

This is when all my problems started. No hardware changes. Still using the same software as well. When I play Steam games, I get a screen freeze that goes black, and the PC seems to "lock" with a repeating buzzzzzzzzzzz sound through my speakers. Afterwards, the PC reboots.

 

I could also multitask easily with dual monitors, while running ET. Now, I get BSOD if I do too much. Yet sometimes, I can do a ton, and have no issues.

 

I have also received a number of errors:

Video error: nvlddmkm

- EventData

      \Device\Video5       !051d(2558)       0000000002003000000000000E00AAC0000000000000000000000000000000000000000000000000

 

Bugcheck:

EventData

    param1 0x0000001a (0x0000000000041790, 0xfffffa8003b22780, 0x000000000000ffff, 0x0000000000000000)     param2 C:\Windows\MEMORY.DMP     param3 120213-27768-01

 

Kernal-Power:

BugcheckCode 26     BugcheckParameter1 0x41790     BugcheckParameter2 0xfffffa8003b22780     BugcheckParameter3 0xffff     BugcheckParameter4 0x0

 

Service Control Manager:

EventData

    param1 1     param2 Restart the service     param3 Windows Modules Installer     param4 %%1056

 

Distributed COM: 

EventData

    param1 {995C996E-D918-4A8C-A302-45719A6F4EA7}

 

And I ran a memory test last night and received this: The Windows Memory Diagnostic tested the computer's memory and detected hardware errors. To identify and repair these problems, contact the computer manufacturer

UserData

    - Results

      LaunchType Manual       CompletionType Fail       MemorySize 16330       TestType 10       TestDuration 3443       TestCount 12       NumPagesTested 4171155       NumPagesUnTested 1863       NumBadPages 8       T1NumBadPages 4       T2NumBadPages 4       T3NumBadPages 5       T4NumBadPages 8       T5NumBadPages 7       T6NumBadPages 6       T7NumBadPages 4       T8NumBadPages 5       T9NumBadPages 7       T10NumBadPages 8       T11NumBadPages 6       T12NumBadPages 6       T13NumBadPages 0       T14NumBadPages 0       T15NumBadPages 0       T16NumBadPages 0

 

I've NEVER had a problem until I got the virus, and formatted and did a new install. Is it possible these errors, including the memory error are all driver/installation related?

[RedBaird]

Did you install all the mobo & system drivers and then update the hardware drivers, as you would when building a system?

 

My last build required a specific order of mobo, system and hardware driver-installations.  The mobo manual warned to not do them out of order.

 

I would check the BIOS, just to be thorough. 

 

=============

 

"The malware prevalently targets Windows computers, although it was recently found to be affecting machines running Mac OS X as well."

[Ann!b@l]

I'm not an expert but for having experienced some BSOD and having solved them with a lot of hours of search on internet, I can try to advise you some softwares to identify and/or fix the issue, but without waranty of succes..

 

-WhoCrashed (the free edition)

-DDU (I use this one for a clean uninstall of my graphic drivers)

 

 

So mostly, my BSOD were caused by a bad setting in my BIOS or a driver.. About your BIOS, I would suggest you to start by setting it on his default values and check if you still get these BSOD.

 

Now from the windows errors report, the first one seems to be your graphic card (nvlddmkm=nvidia). So if your issue comes only from this dll, I got the same one there's few weeks and it's easy to fix.

 

First soltuion, try to uninstall/reinstall your nvidia driver with DDU.

 

Second solution:

-search in C:\NIVIDIA\DisplayDrivers\[Version of the driver you installed]\International\Display\ for the same dll stored during the install but under the name "nvlddmkm.sy_". The place where is located the file can a bit differ from a computer to an other one but most of the time looks like this

 

-copy and place it at the root of C:\ (C:\nvlddmkm.sy_)

 

-go into C:\Windows\System32\Drivers. Once there, look for the broken file named nvlddmkm.sys and rename it to nvlddmkm.sys.old

 

-open the prompt command (key Windows+R)

 

-type \cd in order to work at the root of your disk.

 

-still in there, expand the .sy_ file in typing expand.exe nvlddmkm.sy_ nvlddmkm.sys

 

-go take this file in C:\nvlddmkm.sys and substitute it (copy/past) at the old one in C:\Windows\System32\drivers\

 

-restart your pc and you're done.

Edited December 3, 2013 by Ann!b@l

[UAdave]

I would try memtest on your RAM (it takes awhile so overnight might work best) as well but it sounds like the RAM is bad if it's failing hardware tests. We can analyze your blue screen logs as well if you want to upload/zip the contents of C:\Windows\Minidump to see what is causing those.

[Vanaraud]

The error seems like a nvidia driver related.

I´m wondering if you installed chipset and other drivers for your mobo and in right order. Also Windows format after a virus attack, not very sure about it. Personally I would wipe it out with "zero fill\low level format" from your manufacturer and also clean MBR. At your own risk ofcourse. My bet is on HD vendors specialised programs but maybe there are some other programs accepted by majority. Haven´t had to do it by myself for a long time now.

[Antichrist]

Did you install all the mobo & system drivers and then update the hardware drivers, as you would when building a system?

 

My last build required a specific order of mobo, system and hardware driver-installations.  The mobo manual warned to not do them out of order.

 

I would check the BIOS, just to be thorough. 

 

=============

 

"The malware prevalently targets Windows computers, although it was recently found to be affecting machines running Mac OS X as well."

 

I'm not 100% sure, but I do believe the order was :Windows CD installation, Then motherboard CD, Then Video card CD, Then ran Windows update.

 

BIOS settings are all default, as I have no overclocking, no voltages changes etc...

 

I'm not an expert but for having experienced some BSOD and having solved them with a lot of hours of search on internet, I can try to advise you some softwares to identify and/or fix the issue, but without waranty of succes..

 

-WhoCrashed (the free edition)

-DDU (I use this one for a clean uninstall of my graphic drivers)

 

 

So mostly, my BSOD were caused by a bad setting in my BIOS or a driver.. About your BIOS, I would suggest you to start by setting it on his default values and check if you still get these BSOD.

 

Now from the windows errors report, the first one seems to be your graphic card (nvlddmkm=nvidia). So if your issue comes only from this dll, I got the same one there's few weeks and it's easy to fix.

 

First soltuion, try to uninstall/reinstall your nvidia driver with DDU.

 

Second solution:

-search in C:\NIVIDIA\DisplayDrivers\[Version of the driver you installed]\International\Display\ for the same dll stored during the install but under the name "nvlddmkm.sy_". The place where is located the file can a bit differ from a computer to an other one but most of the time looks like this

 

-copy and place it at the root of C:\ (C:\nvlddmkm.sy_)

 

-go into C:\Windows\System32\Drivers. Once there, look for the broken file named nvlddmkm.sys and rename it to nvlddmkm.sys.old

 

-open the prompt command (key Windows+R)

 

-type \cd in order to work at the root of your disk.

 

-still in there, expand the .sy_ file in typing expand.exe nvlddmkm.sy_ nvlddmkm.sys

 

-go take this file in C:\nvlddmkm.sys and substitute it (copy/past) at the old one in C:\Windows\System32\drivers\

 

-restart your pc and you're done.

I have used DDU now, and removed the drivers, and reinstalled the latest Beta drivers (331.93). The last time, I was using the latest drivers (331.82), but not the beta drivers.

I'll try this out and see it I have the same problem. Next step, If I have problems, I will run DDU again (Thanks for that link also, quite helpful!) And then install the OLD drivers that came on the installation CD. After that I will try the second solution.

It should take me 1-2 days to know if these Beta drivers are working or not.

I would try memtest on your RAM (it takes awhile so overnight might work best) as well but it sounds like the RAM is bad if it's failing hardware tests. We can analyze your blue screen logs as well if you want to upload/zip the contents of C:\Windows\Minidump to see what is causing those.

I ran the windows memory test overnight, and the results I saw in Event Viewer are posted as the last item in my first post. I have not yet ran the memtest program that is not affiliated with Microsoft. For the minidump files, I am currently using JZip, but it doesn't offer me an option to extract the DMP files. When opened in notepad, there is only gibberish. Will I need a new zip program or am I doing something wrong?

 

The error seems like a nvidia driver related.

I´m wondering if you installed chipset and other drivers for your mobo and in right order. Also Windows format after a virus attack, not very sure about it. Personally I would wipe it out with "zero fill\low level format" from your manufacturer and also clean MBR. At your own risk ofcourse. My bet is on HD vendors specialised programs but maybe there are some other programs accepted by majority. Haven´t had to do it by myself for a long time now.

I  was thinking that, but wasn't 100% sure. I wasn't able to find a clear solution with Google searching. I found several results, but nothing definite for a fix. The behavior I'm experiencing now is completely different from what the virus I had does, so I don't believe the two are related. But I do agree that there seems to be a definite  NVidia problem. With normal PC use, I don't recall having any problems, but when I played a game, that is when I would see the freezing.

 

It might also be worth noting that when I look in device manager, I do not see any conflicts or problems noted with the yellow exclamation point. When I right click display adapter and look at properties, it tells me that it is functioning properly.

[Ol Smoke]

I have seen this before and these guys are on the right track.  When building a new PC you must run the MB drivers first for the chipsets.  Always use the one off of the included CD that came with MB.

All the drivers on the CD have been tested with the MB, so use them first and see how the system runs.  Then update the chipset first if you need to.

 

Here is a simple test for memory problems.  Do like UADave said.  Run a memory test.  IF you get any errors at all, print out the sheet or take a screenshot of it or just write it all down.

THen swap positions of the memory chips on the MB, and run it again.  IF the errors happen again, check where they are listed as being in the memory position.  If the numbers change,

then you have a memory chip problem.  If the numbers don't change, you have a problem with MB.

 

There is also a program on the internet that will test the video card memory.  Just do a search for it.  I found it on Tom's Hardware Page.

[Antichrist]

Ok well as of right now, I completed the steps I stated in my last post on Dec 3, and have done nothing else. I have received no new errors, no crashes and no freezes. Event Viewer only shows me two issues, one when my cable modem disconnected, and another which I'm pretty sure is unrelated: The PST Service service is marked as an interactive service.  However, the system is configured to not allow interactive services.  This service may not function properly.

 

But bottom line, so far so good. No blue screens, no crashes. No freezing. Next I just gotta try a steam game

[jaie]

Post removed

Edited December 6, 2013 by jaie

[JoeDirt]

When dealing with issues like these as someone who has extensive knowledge of troubleshooting, even though my job is more administrative now these are the steps I would expect anyone that is doing its own troubleshooting to do.

#1 Update BIOS to the latest version.

#2 Update all the system drivers/windows updates to the latest version. For drivers obviously confirm the date in device manager because I don't want to tell you how many times people unzip a driver and think its installed.

#3 When having video related issues within games make sure your audio drivers are up to date.

#4 If your computer is BSOD'ing when you are running CPU/GPU intensive program/game make sure you run an application that tracks temperatures.

#5 Track voltage, big voltage drops = inadequate/bad power supply.

#6 When asking for help post all the relevant data which include OS (with service pack info), driver version etc. If your system creates a minidump during crash, attach it.

#7 I know I am missing something else but I didn't have my morning coffee yet.

[Antichrist]

#1 BIOS Update: Updating now.

 

And as for #2 on the list, I have all required windows updates installed. The most recent check for updates was yesterday at 9:34pm.

 

Optional updates not installed:

Bing Bar 7.3 (KB2673774)

Bing Desktop v1.3.1

NVIDIA Corporation - Graphics adapter WDDM1.1/1.2/1.3 (This was previously installed, and subsequently removed when I ran the Display Driver Uninstaller program as Ann!b@l suggested)

 

#3 Audio drivers: WIll update after completion of BIOS update.

 

This will cover #4 and #5 in the list:

Readings are all taken at rest, with forums open in Firefox, XFire running, and my Asus TurboV EVO program running.

 

Vcore: .888 V - 1.333V

+3.3V: 3.264V

+5V:  5.035V

+12V: 11.994V

+VDDA: 2.484V

CPU: 40C

MB: 32C

CPU Fan 1735 RPM

 

CPU Frequency

 

Core 0 1404

Core 1 1404

Core 2 1404

Core 3 1404

Core 4 1404

Core 5 1404

 

Running ET, speccing a player. 15 people playing. I let the game run about 10 minutes before taking temperature readings. CPU frequencies varied so I gave the lowest I saw and highest on each core over a 1 minute period for each core. Only Vcore and +12V varied so I gave the highest and lowest reading during a 1 minute period.

 

Vcore 1.244-1.368V

+3.3V: 3.264V

+5V: 5.035V

+12V: 11.891-11.943V

+VDDA: 2.484V

CPU: 55C-56C

MB: 33C

CPU Fan: 2045 RPM

 

CPU Frequency

 

Core 0 3314-3612

Core 1 3259-3612

Core 2 3310-3648

Core 3 3348-3612

Core 4 3310-3612

Core 5 3258-3612

 

#6:

Windows 7 Professional 64 bit. Service Pack 1. I was using NVidia driver version 331.82 at the time. (At the suggestion Ann!b@l gave, I have since completely removed the old driver, and upgraded to 331.93 Beta and have had no problems as of yet, but need to test a more graphic intense game than ET, which is next after my post, just in case it crashes.)

 

Event Viewer, last date I had crashes was 02 December. Windows Logs: System: Filter current log to show Critical, Error, and Warning only:

 

7:01pm was Kernel-Power (Critical)

7:02pm was EventLog (Unexpected shutdown- Error)

7:02pm was Bug Check (Error)

7:32pm was Bug Check (Error) 

7:45pm was nvlddmkm (Error)

 

Minidump from 02 December 7:02pm and 7:32pm (No minidump for 7:45pm)

120213-27206-01.zip

 

[JoeDirt]

The attached minidumps indicate an issue with RAM. Can you check the timings and voltage on the ram stick itself and what you have in BIOS is identical.

[Antichrist]

#1 BIOS is now Flashed and up to date.

 

# 3 Downloading Audio driver update now, and I'm also downloading chipset, USB 3.0, and SATA drivers to make sure they're all updated as well.

 

This is my RAM:

http://www.newegg.com/Product/Product.aspx?gclid=CO7PwPCTnLsCFUJlMgodc0sA8w&Item=N82E16820145345&nm_mc=KNC-GoogleAdwords&cm_mmc=KNC-GoogleAdwords-_-pla-_-Desktop+Memory-_-N82E16820145345&ef_id=UnJ24gAAAVBcjTZo:20131206174740:s

 

Listed Specs:

• DDR3 1600 (PC3 12800)
• Timing 9-9-9-24
• Cas Latency 9
• Voltage 1.5V

Now going to BIOS to check settings.

 

Ok BIOS time. It has a fancy set up utility that I'm not really used to using yet. It has auto detect for numerous settings, and memory was one of them.

 

DRAM CAS# Lat                   CHa  9 CHb 9

DRAM RAS# to CAS# Delay CHa 9 CHb 9

DRAM RAS# PRE Time         CHa 9 CHb 9

DRAM RAS# ACT Time         CHa 24 CHb 24

 

DRAM READ to PRE Time CHa 5 CHb 5

DRAM RAS# to RAS# Delay CHa 5 CHb 5

DRAM WRITE to READ Delay CHa 5 CHb 5

DRAM CAS# write Latency CHa 7 CHb 7

DRAM WRITE Recovery Time CHa 10 CHb 10

DRAM Ref Cycle time 160ms

DRAM Row Cycle Time CHa 34 CHb 34

DRAM READ To WRITE Delay CHa 7 CHb 7

DRAM WRITE To READ Delay (DD) CHa 1 CHb 1

 

I was also able to view all 4 channels seperately, and every number is identical in every column. 9 9 9 24 for every stick of RAM (4 total sticks, 4GB each)

[Antichrist]

Ok I went over everything one more time, and even formatted and reinstalled Windows to make sure I installed all the system drivers first before windows updates, and I still get blue screens.

 

I ran memtest86 today, and It seems to be showing a ton of errors, so I'm RMA'ing my RAM off to Corsair.

 

Thanks for the help everyone, and Joe you were right on about the memory error. I was hoping it was just a driver issue, but that wasn't the case unfortunately.

[redy.]

if you have two memory bars, take one out and let the system run with just one. If it runs more stable the one you took out is the one with the issues. If not try it with the other one.