Consistent occurances within a minute now

I was having some BSOD issues, and figured it was time to start updating drivers. I updated my GPU, but it did not stop.

I then flashed over the newest BIOS for my Mobos, and no BSODS occurred but I did get random hard resets. When these occurred, upon restarting and logging back in, within the first few minutes, if not the first thirty seconds, my desktop would restart again. There was no BSOD flashing, so I unchecked the option to auto-restart, which brought back the physical blue screens. In the past 24 hours (24-08-2013), I've had 7 or so stops. Attached is my filedump and CPU-Z results.

Months ago, I was having frequent BSOD also, but changing my command rate from 2T to 1T immediately dissolved all of them, until recently.

From the little I can tell, I see x3b stops, but I'm not sure how to correct the ntoskrnl.exe driver errors. Runs in safemode with network, no problem**.

All help is appreciated

**Edit: Just BSOD in safemode, with no error code. Shut it down for now..

Welcome to Seven Forums:).


Your bugcheck show a number of possible suspects including RAM:

Code:

SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: fffff80002effc0e, Address of the instruction which caused the bugcheck
Arg3: fffff8800646cb60, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.

Code:

fffff880`0646c6d8  fffff880`042d9750 Rt64win7+0x1a750
fffff880`0646c7f8  fffff880`042c1c74 Rt64win7+0x2c74
fffff880`0646c830  fffff880`042c18a0 Rt64win7+0x28a0
fffff880`0646c848  fffff880`042c1940 Rt64win7+0x2940

By using the lmvm command we get more information about the file:

Code:

lmvm Rt64win7
start             end                 module name
fffff880`042bf000 fffff880`04334000   Rt64win7 T (no symbols)           
    Loaded symbol image file: Rt64win7.sys
    Image path: \SystemRoot\system32\DRIVERS\Rt64win7.sys
    Image name: Rt64win7.sys
    Timestamp:        Thu Apr 21 21:15:33 2011 (4DB07445)

We can now see that the driver is very old!

• Driver Reference Table - Rt64win7.sys

Download the latest from your OEM - Realtek Lan driver


-=======================================================-

Code:

SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: fffff80002ebe6e4, Address of the instruction which caused the bugcheck
Arg3: fffff880094ee6f0, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.

Code:

fffff880`094ee238  fffff880`0489a9e3 atikmdag+0x349e3
fffff880`094ee3b8  fffff880`0488b040 atikmdag+0x25040
fffff880`094ee818  fffff880`0489a9e3 atikmdag+0x349e3
fffff880`094ee868  fffff880`0489a9e3 atikmdag+0x349e3
fffff880`094ee9b8  fffff880`048735d4 atikmdag+0xd5d4
fffff880`094ee9c8  fffff880`04915428 atikmdag+0xaf428
fffff880`094ee9f8  fffff880`04913729 atikmdag+0xad729
fffff880`094eea28  fffff880`04916c9c atikmdag+0xb0c9c
fffff880`094eea48  fffff880`049133f7 atikmdag+0xad3f7
fffff880`094eea58  fffff880`0492562a atikmdag+0xbf62a
fffff880`094eea78  fffff880`049261f1 atikmdag+0xc01f1
fffff880`094eed18  fffff880`01237d0c VirtuWDDM+0x1d0c

Code:

lmvm VirtuWDDM
start             end                 module name
fffff880`01236000 fffff880`0124b000   VirtuWDDM T (no symbols)           
    Loaded symbol image file: VirtuWDDM.sys
    Image path: \SystemRoot\system32\DRIVERS\VirtuWDDM.sys
    Image name: VirtuWDDM.sys
    Timestamp:        Thu Jul 07 15:40:25 2011 (4E15A939)

Update or remove entirely - VIRTU LucidInterop

• Driver Reference Table - VirtuWDDM.sys

Code:

lmvm atikmdag
start             end                 module name
fffff880`04866000 fffff880`053d9000   atikmdag T (no symbols)           
    Loaded symbol image file: atikmdag.sys
    Image path: \SystemRoot\system32\DRIVERS\atikmdag.sys
    Image name: atikmdag.sys
    Timestamp:        Fri Mar 29 05:27:04 2013 (5154FBF8)

You're using version 13.4:

Code:

Driver Version: 12.104.0.0

Uninstall Catalyst Control Center using | AMD Catalyst Un-install Utility
Then follow through with a pass of Driver Sweeper.

Download version 13.1

   Note

Install the display driver only! | Do not install the Catalyst Control Center software.

Test the RAM following this tutorial:

• RAM - Test with Memtest86+

koolkat77 said:

   Tip

• Pay close attention to part 3 of the tutorial "If you have errors"
• Test the RAM with Memtest86+ for at least 7-10 passes. It may take up to 22 passes to find problems. Make sure to run it once after the system has been on for a few hours and is warm, and then also run it again when the system has been off for a few hours and is cold.

After the test post a picture of the results.

Just to add to YoYo's analysis, if I may:

There is possible issues regarding ataport.sys. Ataport.sys is prone to malware called a rootkit.
Please scan the system for possible virus infection with the following programs.

Anti-rootkit utility TDSSKiller
Windows Defender Offline
Cheers
Dave

I'm about to run the memtest. I've completed the suggestions (thank you, yoyo), and downloaded the latest realtek driver, uninstalled Virtu, uninstalled catalyst control center and redownloaded the driver without the control center bit checked, but throughout each I was getting BSODs. I'm uploading a second minidump, as two were ones I've not seen before.

If memtest comes up clean, I'll try what northernsoul55 suggested.

I will post screenshots of the runs regardless, though I do have a question. I'm running it now, while it has been running for about half an hour. Does that count as a "cold" run, or a "warm" run?

Multiple Edits: Pass #2.0, 118k errors. Should I begin testing sticks individually now, or let it finish the 7 minimum passes? How do I take a picture of the results? Would a camera phone pic work for you guys?

Edit 2: I read "If you had motherboard/temperature/setup issues then you'd be getting thousands of errors all over the place." Is this sounding like a mobos issue? Perhaps flashing over the new BIOS screwed something up.. the BSODs definitely weren't occurring this frequently beforehand.. Could I fix this by rolling back the BIOs flashes?

varilrn said:

I will post screenshots of the runs regardless, though I do have a question. I'm running it now, while it has been running for about half an hour. Does that count as a "cold" run, or a "warm" run?

It is considered a warm machine at that point.

varilrn said:

Multiple Edits: Pass #2.0, 118k errors. Should I begin testing sticks individually now, or let it finish the 7 minimum passes? How do I take a picture of the results? Would a camera phone pic work for you guys?

No need to run the whole 7 passes once errors are found.
Yes any readable picture will suffice.

varilrn said:

Edit 2: I read "If you had motherboard/temperature/setup issues then you'd be getting thousands of errors all over the place." Is this sounding like a mobos issue? Perhaps flashing over the new BIOS screwed something up.. the BSODs definitely weren't occurring this frequently beforehand.. Could I fix this by rolling back the BIOs flashes?

It is possible that the new BIOS has different default settings than the older.
But it's normally not the cause of so many errors, you are apparently feel comfortable enough
to FLASH the BIOS so you could try the older version although I don't believe it to be the cause.

   Warning

Flashing the BIOS is a risky business and should not be performed unless positive to be the cause.
Flashing the BIOS is at your own risk, you may end up bricking the motherboard.

varilrn said:

So, I haven't tested both RAM sticks completely, just popped in the single B stick, into the same slot that I tried stick A.

Stick A ran 13 passes with 0 errors, but stick B, in the same slot, is immediately getting errors.

Should I just try to run the desktop with only the one stick of good RAM and see if I get any BSOD? In the meantime, I'll continue running stick B.

This might help you determine what and which of the two is bad, the stick, the slot or both.

Arc said:

No code has to be inserted here. It is a RAM, a bad RAM.

But if you have got a result like that:
No code has to be inserted here. It is a motherboard issue. The particular slot is bad.

Yes in the meantime after you're done testing remove the bad stick from the system.

My pleasure :) .
Thank you for reporting back, glad to hear you're up and running again.