BSOD 8 hours after reinstalling Windows 7 64 bits

[ArgentineBoy]

So, I finally got my hands on a Ultimate 64 bits OS (as my father mistakenly bought a 32 bits H.Premium OS).

Basically, yesterday, I reinstalled it. I installed all the motherboard drivers which came with the gygabite CD, and then downloaded the ATI drivers. Installed STALKER, played it for half an hour and then I turned it off (thinking everything was alright).

Then, today, 8 hours later, I turn it on and I find after a while it had enter repairing mode because it couldn't initiate Windows. "WTF", I thought, as yesterday it didn't crash or BSOD. So it has obviously something to do with cold boot.

It "repaired" the PC and when it restarted, I found out that AVG no longer worked and the ATI drivers seemed to have been...nullified (?). Had to reinstall them again. One more restart and it works fine (I'll just have to download MSI instead of AVG...).

Ok, before we get into hardware stuff, I'll remind you that I've done several Memtest and OCCT tests with this machine (Of course, after it started working fine after several BSODS in every single cold boot). Temperature is alright, never going further than 50 degrees C. There is no OC. RAM is at 1.50v as specified by GSKILL, CPU is at 2.6ghz and the ATI HD 5850 XXX has been Underclocked, as it came from factory with 755/1125 when normal ones come with 725/1000. Hard drive is perfect. Checked it with the WD tools and no error came up. All PASS.

Im attaching the dump to let you see what might have caused this. I mean, come on, one day, just after doing a clean reinstall? BSODs? Like that?

Thanks for help.

PD: The previous Windows install DID BSOD after every single cold boot, but after a couple of BSOD's, it started working fine, though, sometimes it seemed files "vanished" or were no longer "there".

 

[Arc]

Hello ArgentineBoy.

► We need more info, as per Blue Screen of Death (BSOD) Posting Instructions.

► Install Service Pack 1

Windows 7 Kernel Version [COLOR=Red]7600 [/COLOR]MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
[COLOR=Red]Built by: 7600[/COLOR].16385.amd64fre.win7_rtm.090713-1255

► It is your Display Driver.

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 50, {fffffa803074f828, 0, fffff88004938d90, 2}

Unable to load image \SystemRoot\system32\DRIVERS\atikmdag.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for atikmdag.sys
*** ERROR: Module load completed but symbols could not be loaded for atikmdag.sys

Could not read faulting driver name
[COLOR=Red]Probably caused by : atikmdag.sys[/COLOR] ( atikmdag+67d90 )

Followup: MachineOwner
---------

Uninstall it using Driver Fusion and then download and install the latest one.

► Check DirectX
Diagnosing basic problems with DirectX

► Update Realtek High Definition Audio Function Driver from Realtek

 kd> lmvm RTKVHD64
start             end                 module name
fffff880`06abb000 fffff880`06cd8300   RTKVHD64 T (no symbols)           
    Loaded symbol image file: RTKVHD64.sys
    Image path: \SystemRoot\system32\drivers\RTKVHD64.sys
    [COLOR=Red]Image name: RTKVHD64.sys
    Timestamp:        Tue Dec 08 15:50:05 2009 [/COLOR](4B1E2855)
    CheckSum:         0021EFFE
    ImageSize:        0021D300
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

► Update Atheros network adapter driver from ATHEROS drivers for Microsoft Windows (Atheros?????)

kd> lmvm athrx
start             end                 module name
fffff880`04256000 fffff880`043ae000   athrx    T (no symbols)           
    Loaded symbol image file: athrx.sys
    Image path: \SystemRoot\system32\DRIVERS\athrx.sys
    [COLOR=Red]Image name: athrx.sys
    Timestamp:        Tue Jun 09 23:36:49 2009[/COLOR] (4A2EA4B9)
    CheckSum:         0015FE99
    ImageSize:        00158000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

► Uninstall AVG, use Microsoft Security Essentials - Free Antivirus for Windows.

Let us know the results.

 

[ArgentineBoy]

So, 06:44 PM, it has been +- 10 hours since I last touched the PC. This time was even weirder as I didn't BSOD when I logged on and used for it for a couple of minutes, it BSOD right off from the bat after the "Windows is initating" screen. Had to go through it for 5 times in order to write this.

Uninstall it using Driver Fusion and then download and install the latest one.

Impossible, these ARE the latest one.

Uninstall AVG

Can't find the AVG uninstaller

EDIT: What puzzles me the most, is, that if the problem is faulty hardware, how come it doesn't keep BSOD'ing instead of stopping the BSOD's and working fine?

 

[Arc]

So, 06:44 PM, it has been +- 10 hours since I last touched the PC. This time was even weirder as I didn't BSOD when I logged on and used for it for a couple of minutes, it BSOD right off from the bat after the "Windows is initating" screen. Had to go through it for 5 times in order to write this.

Uninstall it using Driver Fusion and then download and install the latest one.

Impossible, these ARE the latest one.

Uninstall AVG

Can't find the AVG uninstaller

EDIT: What puzzles me the most, is, that if the problem is faulty hardware, how come it doesn't keep BSOD'ing instead of stopping the BSOD's and working fine?

Readily refused.
I usually dont ask for any help when I know that I will refuse it.

 

[ArgentineBoy]

Why you think I readily refused? I did all your steps except (right now downloading Service Pack 1) more info. I haven't refused any help, I just told two things: That my drivers are the latest one for HD 5850 and that I can't find the AVG Uninstaller.

EDIT: Here's the info.

 

[Arc]

You need to uninstall and reinstall your display driver. Otherwise you will not be able to stop display related crashes that you are having. I have the ability to check whether those are latest or not. I used the "latest" just to make it clear that I am not suggesting to shift to an "older" version.

To uninstall AVG, Go to Control panel > Programs and features.

Well, Here's your latest driver, in action.

....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 50, {fffffa803074f828, 0, fffff88004938d90, 2}

Unable to load image \SystemRoot\system32\DRIVERS\atikmdag.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for atikmdag.sys
*** ERROR: Module load completed but symbols could not be loaded for atikmdag.sys

Could not read faulting driver name
[COLOR=Red]Probably caused by : atikmdag.sys[/COLOR] ( atikmdag+67d90 )

Followup: MachineOwner
---------

For your satisfaction, you have installed that ATI display driver on Saturday, 28th July.

kd> lmvm atikmdag
start             end                 module name
fffff880`048d1000 fffff880`052f2000   atikmdag T (no symbols)           
    Loaded symbol image file: atikmdag.sys
    Image path: \SystemRoot\system32\DRIVERS\atikmdag.sys
   [COLOR=Red] Image name: atikmdag.sys
    Timestamp:        Sat Jul 28 07:18:09 2012[/COLOR] (501344D9)
    CheckSum:         009DA146
    ImageSize:        00A21000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

I can say only one thing ... I dont know any other way to change the situation to favorable, other than uninstalling /reinstalling the problem driver as the first try. If it is impossible, there the solution is equally impossible, as far as I can say you.

 

[ArgentineBoy]

28th July? That's kinda....wrong. I mean...I did the fresh reinstall this monday, 1st October.

 

[Arc]

28th July? That's kinda....wrong. I mean...I did the fresh reinstall this monday, 1st October.

That is the driver's date. You can check it easily.

And sorry I cannot spend my time on an impossible project.

 

[ArgentineBoy]

Ok, I've removed all the old drivers, downloaded the latest ones again and installed them.

Have you checked the info in the RAR?

 

[ArgentineBoy]

Wow, well, 6 hours later, I turned it on and I haven't had a BSOD....yet. Im gonna see how it plays this time. What's more, Programs haven't crashed, which is a signal of everything working OK (100% of the time something would crash and then it would BSOD a couple of minutes later)
I'll now have to solve the sound issue (I hope it's the only issue left with this machine).

 

[Arc]

Close your BSOD thread, and start a new one in Music, Pictures & Video - Windows 7 Forums

 

[ArgentineBoy]

No, wait, they're back. This time I (I turned it on this morning, went to school for 8 hours, came back) got circa 4 BSODS. In one moment, after the loading screen, it just restarted, no blue screen at all.

I took a quick glimpse and saw something like AFD.sys. Im uploading the dump.

I've yet to download SP1 but I don't have the time. Maybe Friday I'll leave it downloading.

PD: I've already got a sound thread and waiting for a reply.

PD2: What could make a OS go nuts after a -+ 8 hour rest? Can it be something related to hard drives, spin up time and such (though, as said before, tests show everything is OK)? Heat? I insist it's extremely weird. It all goes FUBAR after the first boot in 8 hours, a couple of BSODS and restarts here and there, programs crash in the meanwhile....and then...suddenly, everything works 100% fine (well, except sound) after a restart?

 

[Arc]

Your crash dumps are not showing any finite probable cause. In such a situation, it is better to enable Driver Verifier to monitor the drivers.

Driver Verifier - Enable and Disable

Run Driver Verifier for 24 hours or the occurrence of the next crash, whichever is earlier.

Let us know the results, with the subsequent crash dumps, if any.