Solved Random BSOD's, mainly ntoskrnl.exe but also other errors.

[essenbe]

If you're having all those problems with your PSU, it could very well be the issue you've been having with the computer. I wish you would have said something about it sooner.

 

[Kreshnak]

I did mention the sounds earlier (page 3). But me being a novice about computers and their sounds didn't know what to make of it. But since it's probably not the RAM timings that you thought it might've been, I merely assume it's the PSU. The sound files are quite bad to be honest, they're recorded using a phone and the volume is pretty low too.

However when I start the PC the first time when I've cut the power it does a really loud and annoying sound. (Attachment: Computer sound startup) I have to press the power button for about 5 sec for it to turn off again, and when I start it again it doesn't make the sound anymore. Every now and then when I start it it makes another sound though, and doesn't always start. (Attachment: Computer Sound)

Anyways, I'm updating via windows update every odd hour with about 10 new updates in each batch. Only time will tell if I find anything there before I get to buy a new PSU tomorrow.

 

[essenbe]

I wish you lluck and keep in touch. We would like to know how things go. How are the BSODs?

 

[Kreshnak]

So I've replaced my PSU with the new HX one from Corsair. Haven't gone this long without a bsod since like February. Seems to be working, but I'll give it a few more days before I mark the thread as solved.

 

[Kreshnak]

So I've had two bsod's since yesterday. It seemed to be working alright until yesterday evening when i got the first one. Then I got another one this morning, however it does seem to be less frequent.

 

[centaur78]

Could you uninstall MSE for the time being

If it BSOD's again, could you also enable Driver verifier

 

[Kreshnak]

I'm away from home for a couple of days, but I'll try it when I come home.

 

[Kreshnak]

Uninstalled MSE but still got BSOD's. So I enabled driver verifier, got a bsod and couldn't even get past the start up screen. So I had to do a system restore.

EDIT:
Attached a new SF with some .dmp files aswell. Last one didn't have any because I made it right after a system restore.

 

[Kreshnak]

I'm thinking that it might be the processor. Can a faulty processor cause these kinds of bsod's? If that's the case, I'm just going to buy a new one. What do you think about this one: AMD FX 4-Core Black Edition FX-4300 (FD4300WMHKBOX) Details

 

[gregrocker]

Have you stress tested the processor with CPU - Stress Test with Prime95 - Windows 7 Forums

However the behavior after Driver Verifier normally means it is a driver. Are you using the drivers provided by WIn7 after a Clean Reinstall, have you installed all Important and Optional Updates after enabling Automatically deliver drivers via Windows Update (Step 3)?

Report back on these while you wait for an analyst to read the BSOD's to gather more clues. I will ask for one now. Sorry for the delay.

 

[x BlueRobot]

[COLOR=Red]BugCheck FC[/COLOR], {[COLOR=SeaGreen]fffff88005190410[/COLOR], 80000001998da963, fffff880027ec700, 2}

Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_GLOBAL::EndPreparation+1a3 )

Usual causes:  Device driver

2: kd>[COLOR=SeaGreen] lmvm atikmdag[/COLOR]
start             end                 module name
fffff880`0566d000 fffff880`061e0000   atikmdag T (no symbols)           
    Loaded symbol image file: atikmdag.sys
    Image path: \SystemRoot\system32\DRIVERS\atikmdag.sys
    Image name: atikmdag.sys
    Timestamp:        [COLOR=Red]Fri Mar 29 02:27:04 2013[/COLOR] (5154FBF8)
    CheckSum:         00B25604
    ImageSize:        00B73000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Your AMD/ATI graphics card driver seems to be a possible cause, please update to the latest WHQL from here - AMD Graphics Drivers & Software

WHQL
Release Date: April 24th 2013
Version: 13.4
In Device Manager: 12.104

 

[x BlueRobot]

From a Stop 0xA:

2: kd> [COLOR="SeaGreen"]lmvm nvstor[/COLOR]
start             end                 module name
fffff880`010b3000 fffff880`010de000   nvstor   T (no symbols)           
    Loaded symbol image file: nvstor.sys
    Image path: \SystemRoot\system32\drivers\nvstor.sys
    Image name: nvstor.sys
    Timestamp:        [COLOR="Red"]Fri Mar 19 20:45:11 2010[/COLOR] (4BA3E257)
    CheckSum:         000291A5
    ImageSize:        0002B000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Your nVidia Storage driver seems to be causing problems, it's most likely to be part of the chipset, check your motherboard's support page for a chipset update or check for updates from here - Drivers - Download NVIDIA Drivers

 

[Kreshnak]

I'm doing the stress test right now.

Yes I've installed all important and optional updates via windows update.

I've attached a screen shot of my device manager where it says the driver version of my graphics card. To me it seems that it is the latest version already.

 

[YoYo155]

A few I am seeing are:

ASACPI.sys   Mon Mar 28 05:30:36 [COLOR=Red][U][B]2005[/B][/U][/COLOR]
atikmpag.sys [COLOR=DarkOrchid][U][B]Fri Mar 29 04:09:45 2013[/B][/U][/COLOR]

• Catalyst Control Center 13.4

x BlueRobot, you're too fast!

http://www.sevenforums.com/members/x-bluerobot.html

 

[YoYo155]

I'm doing the stress test right now.

Yes I've installed all important and optional updates via windows update.

I've attached a screen shot of my device manager where it says the driver version of my graphics card. To me it seems that it is the latest version already.

CCC 13.4 was proven to be buggy in the past.

Uninstall the driver using AMD Catalyst Un-install Utility.
Then follow through with a pass of Driver Sweeper.

Important!

• When installing, do not install Catalyst Control Center !
• Choose to install the Display Driver only.

Download and install revision number 13.1

 

[Kreshnak]

I'm on it, as soon as I've left my stress test on for two hours. It's been on for half an hour now and haven't had an error yet.

 

[essenbe]

When you are running Prime95, be sure to keep a close check on your CPU temps. prime will make them go up extremely high. If you get close to a critical temp, shut the test down. prime is designed to test the CPU among other things. A bad CPU is probably the least likely problem you could have. They do go bad, but rarely. I tend to agree with Greg Rocker. If you run pretty stable in Safe mode, it sounds more like a driver.

When you updated BIOS, did you go back into bios and set it to optimized defaults, reset the ram to manufacturer's specs, and set the sata controller? As I recall, the last time you did that it helped your stability.

 

[Kreshnak]

How high is a critical temp? The CPU is at 74°C atm.

I don't remember if I did that, can check as soon as the stress test is done though.

 

[essenbe]

If you can download and install Core Temp it will tell you your TJ Max, (the temp you are reading now) for your CPU. TJ Max is the maximum temp of the cores.

 

[Kreshnak]

The stress test went for 2h+ error free. Downloading the 13.1 AMD Driver. Installed the new nVidia drivers.

As far as I could see the Bios was set to optimized defaults. Everything was set on "auto" concerning memory.