Tech Support banner

Status
Not open for further replies.
1 - 20 of 50 Posts

·
Registered
Joined
·
36 Posts
Discussion Starter · #1 · (Edited)
Hey!

I've recently installed my very own rig. I've updated everything (Windows, drivers etc.)

Since a few days ago my computer has started to randomly give me these nasty BSODs. This usually occurs in middle of games.

I first suspected there was something with RealTek drivers, as my system crashed after a while when I was either listening to music or using Skype, TeamSpeak or such. But I've reinstalled and updated it's drivers so I'm not so sure anymore.

OS - Windows 8 x64 OEM English (Retail DVD)
-(I had Ubuntu installed for a day and wiped that thing away the moment my optical drive arrived)
-I built the system and installed the OS about two weeks ago (20.7) and haven't reinstalled the OS.

CPU - Intel Core i5-3570K 3.4GHz Socket 1155 Box
Video Card - Asus GeForce GTX 660ti DC2-series
Motherboard - ASRock Z77 Pro4 ATX
Power Supply - XFX 650W

I tried running the driver verifier but it resulted in a BSOD after restarting. I tried finding the minidump but can't for the life of me find it. I followed the post on making sure I've enabled it though. Found them and uploaded.

Also I've run tests for error on my RAM with memtest86+ which resulted in 0 errors and same with the HDD with HD Tune pro.
 

Attachments

·
TSF Team, Emeritus
Joined
·
4,349 Posts
Re: New system - Random BSOD

Hi,

First off, in regards to the perfmon:

Symptom:
Device cannot start.

Cause: A device has a configuration problem that prevents it from starting properly.

Details: The device, Microsoft ISATAP Adapter, cannot start properly. It may not have the correct driver installed or may be experiencing a hardware failure. The Plug and Play ID for this device is 13.

Resolution:
1. Verify the correct driver is installed.
2. Try updating the drivers using Windows Update.
3. Check with the manufacturer for an updated driver.
4. Attempt to uninstall and then reinstall the device using Device Manager.

-------------------------

Symptom:
Device cannot start.

Cause: A device has a configuration problem that prevents it from starting properly.

Details: The device, Microsoft Teredo Tunneling Adapter, cannot start properly. It may not have the correct driver installed or may be experiencing a hardware failure. The Plug and Play ID for this device is 14.

Resolution:
1. Verify the correct driver is installed.
2. Try updating the drivers using Windows Update.
3. Check with the manufacturer for an updated driver.
4. Attempt to uninstall and then reinstall the device using Device Manager.

-------------

Onto the dumps, we have many DPC_WATCHDOG_VIOLATION (133) bugchecks.

This bugcheck can have two ultimate causes, really:

1. Whether a single DPC exceeded a timeout

OR

2. Whether the system cumulatively spent an extended period of time at IRQL DISPATCH_LEVEL or above.whether the system cumulatively spent an extended period of time at IRQL DISPATCH_LEVEL or above.

In your case, it's #2. If we take a look at the call stack:

Code:
0: kd> kv
Child-SP          RetAddr           : Args to Child                                                           : Call Site
fffff803`9bfdc0f8 fffff803`9a7dafa3 : 00000000`00000133 00000000`00000001 00000000`00001e00 00000000`00000000 : nt!KeBugCheckEx
fffff803`9bfdc100 fffff803`9a69f774 : 00000000`00000000 00000000`000025a6 fffff803`9bfdc280 fffff780`00000320 : nt! ?? ::FNODOBFM::`string'+0x14600
fffff803`9bfdc180 fffff803`9ad6feca : fffffa80`06d058d0 00000002`00000000 fffffa80`06cac490 fffffa80`06cdf000 : nt!KeUpdateTime+0x2ec
fffff803`9bfdc360 fffff803`9a65401e : 00000000`59c2e10a 00000000`036f0000 fffff803`9ad99580 fffffa80`06cac000 : hal!HalpTimerClockInterrupt+0x86
fffff803`9bfdc390 fffff880`060595e0 : 00000002`00000000 fffffa80`06d058d0 fffff803`9bfdc570 fffff880`0605a3ab : nt!KiInterruptDispatchLBControl+0x1ce (TrapFrame @ fffff803`9bfdc390)
fffff803`9bfdc520 00000002`00000000 : fffffa80`06d058d0 fffff803`9bfdc570 fffff880`0605a3ab fffff803`9bfdc570 : [U][B][COLOR=Red]nvlddmkm[/COLOR][/B][/U]+0x3635e0
fffff803`9bfdc528 fffffa80`06d058d0 : fffff803`9bfdc570 fffff880`0605a3ab fffff803`9bfdc570 00000000`036f0000 : 0x00000002`00000000
fffff803`9bfdc530 fffff803`9bfdc570 : fffff880`0605a3ab fffff803`9bfdc570 00000000`036f0000 fffffa80`06cac000 : 0xfffffa80`06d058d0
fffff803`9bfdc538 fffff880`0605a3ab : fffff803`9bfdc570 00000000`036f0000 fffffa80`06cac000 fffffa80`06cdf000 : 0xfffff803`9bfdc570
fffff803`9bfdc540 fffff803`9bfdc570 : 00000000`036f0000 fffffa80`06cac000 fffffa80`06cdf000 fffffa80`06d058d0 : [COLOR=Red][U][B]nvlddmkm[/B][/U][/COLOR]+0x3643ab
fffff803`9bfdc548 00000000`036f0000 : fffffa80`06cac000 fffffa80`06cdf000 fffffa80`06d058d0 00000000`00000001 : 0xfffff803`9bfdc570
fffff803`9bfdc550 fffffa80`06cac000 : fffffa80`06cdf000 fffffa80`06d058d0 00000000`00000001 fffff803`9bfdc5d0 : 0x36f0000
fffff803`9bfdc558 fffffa80`06cdf000 : fffffa80`06d058d0 00000000`00000001 fffff803`9bfdc5d0 fffff880`066fa4a6 : 0xfffffa80`06cac000
fffff803`9bfdc560 fffffa80`06d058d0 : 00000000`00000001 fffff803`9bfdc5d0 fffff880`066fa4a6 00000000`00000000 : 0xfffffa80`06cdf000
fffff803`9bfdc568 00000000`00000001 : fffff803`9bfdc5d0 fffff880`066fa4a6 00000000`00000000 00000000`036f0000 : 0xfffffa80`06d058d0
fffff803`9bfdc570 fffff803`9bfdc5d0 : fffff880`066fa4a6 00000000`00000000 00000000`036f0000 00000000`00000000 : 0x1
fffff803`9bfdc578 fffff880`066fa4a6 : 00000000`00000000 00000000`036f0000 00000000`00000000 fffffa80`06cdf000 : 0xfffff803`9bfdc5d0
fffff803`9bfdc580 00000000`00000000 : 00000000`036f0000 00000000`00000000 fffffa80`06cdf000 fffff803`036f0000 : [COLOR=Red][U][B]nvlddmkm[/B][/U][/COLOR]+0xa044a6
We see mentions of nvlddmkm which is nvlddmkm.sys (nVidia video driver).

Ensure you have the latest video card drivers. If you are already on the latest video card drivers, uninstall and install a version or a few versions behind the latest to ensure it's not a latest driver only issue. If you have already experimented with the latest video card driver and many previous versions, please give the beta driver for your card a try.

I cannot seem to locate your verifier enabled dump among these. Can you do me a favor? Delete all of your current minidumps, enable Driver Verifier again, and upload that dump ASAP? A very fresh verifier enabled dump would be great.

Regards,

Patrick
 

·
Registered
Joined
·
36 Posts
Discussion Starter · #3 ·
Re: New system - Random BSOD

Thank you for that very quick reply!

Firstly about the Microsoft ISATAP Adapter. I have no idea what it is, I tried looking for updates for it or even disable them totally. There's actually two of those and "Teredo Tunneling Pseudo-Interface" with a yellow mark on them. No idea why they're there.

Then regarding the nVidia driver. I had the most latest driver and then updated to the latest beta driver just to see if this would fix anything. That didn't help though. :(

I tried doing the Driver Verifier method again but as I have to do a System Restore, it just brings the old dumps back without a new one. :/
 

·
Registered
Joined
·
36 Posts
Discussion Starter · #4 ·
Re: New system - Random BSOD

I tried again and got them.
I have to restart the computer twice before I get the chance to do a system restore and as both dmp files size are different, I'll just upload both.
 

Attachments

·
TSF Team, Emeritus
Joined
·
4,349 Posts
Re: New system - Random BSOD

Ah, no, let me explain.

Only do the system restore if you cannot boot into safe mode to disable driver verifier to boot back into normal Windows. If you use system restore right after enabling verifier, it just erases the dump that was just generated.

So, enable verifier, let it crash, go into safe mode and disable verifier, boot into normal Windows, attach latest verifier dump only.

Regards,

Patrick
 

·
Registered
Joined
·
36 Posts
Discussion Starter · #6 ·
Re: New system - Random BSOD

Ah sorry about that. I could almost feel you facepalming infront of your monitor. :banghead:

I managed to do it right this time.
 

Attachments

·
TSF Team, Emeritus
Joined
·
4,349 Posts
Re: New system - Random BSOD

It's no issue! I've had many people get confused over that before, among other things in that canned speech for Verifier. I think I will rewrite it soon to save any further future confusion.

Anyway, onto the dump!

It is indeed a DRIVER_VERIFIER_DETECTED_VIOLATION (c4) bugcheck and it is successfully flagging a driver which happens to be IOMap64.sys which is the
ASUS Kernel Mode Driver / Asus Smart Doctor/iTracker 2 driver.


On the call stack:

Code:
2: kd> kv
Child-SP          RetAddr           : Args to Child                                                           : Call Site
fffff880`1e4616e8 fffff801`2f4c919c : 00000000`000000c4 00000000`00000083 00000000`00000000 00000000`01000000 : nt!KeBugCheckEx
fffff880`1e4616f0 fffff801`2f4c050d : fffff880`00000012 fffff880`1de00000 00000000`00000000 fffff801`2f2ab9d8 : nt!VerifierBugCheckIfAppropriate+0x3c
fffff880`1e461730 fffff801`2f4dc673 : 00000000`00000000 00000000`01000000 fffffa80`0d7c7cb0 fffffa80`0d0666f8 : nt!MmCheckMapIoSpace+0xa9
fffff880`1e461770 fffff880`1cbf6525 : 00000000`00000000 fffffa80`0d0666c0 00000000`f60009fb 00000000`00001000 : nt!VerifierMmMapIoSpace+0x43
fffff880`1e4617b0 00000000`00000000 : fffffa80`0d0666c0 00000000`f60009fb 00000000`00001000 fffff880`1e4617f0 : [COLOR=Red][U][B]IOMap64+0x3525[/B][/U][/COLOR]
So here's my theory...

In the earlier non-verifier enabled minidumps, they were *133 bugchecks faulting nVidia's video driver. Asus Smart Doctor AFAIK is a program that is used to adjust and monitor voltages for your video card.

Judging from running a lmvm on the driver:

Timestamp: Thu Feb 04 20:55:34 2010 (4B6B7A96)
I presume you simply installed this software because it was included software with the disc that came with the motherboard or video card?

I am going to temporarily recommend removing Smart Doctor for troubleshooting purposes as I believe it's conflicting. It's not necessary software for the functionality of your video card.

Regards,

Patrick
 

·
Registered
Joined
·
36 Posts
Discussion Starter · #8 ·
Re: New system - Random BSOD

Yes, I installed it from the cards disk. It's a handy tool for monitoring the temperatures and adjusting the fans.

Alright I'll try and uninstall that software.
 

·
TSF Team, Emeritus
Joined
·
4,349 Posts
Re: New system - Random BSOD

Great!

If it ends up being the issue which we will find out soon, we can try and grab you the latest version and see if that solves it. If not, and you still have the issue on the latest version, there are other programs that are handy in regards to fan speeds, etc.

Regards,

Patrick
 

·
Registered
Joined
·
36 Posts
Discussion Starter · #10 ·
Re: New system - Random BSOD

I uninstalled it, did the verifier thingmajig again, only this time it didn't actually BSOD on me which I suppose is a good thing but also sad.
As I could adjust all sorts of things with that software, OCing and voltage tweaking and other fancy stuff.
 

·
TSF Team, Emeritus
Joined
·
4,349 Posts
Re: New system - Random BSOD

I'd play around with the system for a bit and see how its behavior is. If you don't BSOD, it looks like we found the issue.

An alternative program that's actually better (in my opinion) is MSI Afterburner. I'd check it out if you haven't already.

When you feel or are confident enough that your problem is solved, please navigate to 'Thread Tools' at the top of the thread and select 'Mark this thread as solved'.

Regards,

Patrick
 

·
Registered
Joined
·
36 Posts
Discussion Starter · #12 ·
Re: New system - Random BSOD

Hate to say it, but seems like the problem is still there.

This time around it just froze for a very long time so I just restarted without waiting for the actual "BSOD with a sad face". :/
 

·
TSF Team, Emeritus
Joined
·
4,349 Posts
Re: New system - Random BSOD

Hi,

Are you overclocking your card, is any component in the system overclocked and not at stock settings?

Have you had any crashes since the time of that post to attach the DMP from?

Regards,

Patrick
 

·
Registered
Joined
·
36 Posts
Discussion Starter · #14 ·
Re: New system - Random BSOD

Truly sorry for the delayed reply.

I haven't overclocked anything. I've let them stay as they've always been.

I reinstalled my Windows 8 and for a while it all seemed good. No random crashes or BSoD.

Alas, once again I've ran into this same problem. Computer freezes in middle of a game, sound drops, no response from mouse or keyboard. It'll stay like this for a whopping 20minutes before it automaticly restarts and saves a dump.

I've checked the temperatures and they all seem fine so I can't really blame it on overheating either.

Here's the the minidump it saved.
 

Attachments

·
TSF Team, Emeritus
Joined
·
4,349 Posts
Re: New system - Random BSOD

Hi,

You mentioned you reinstalled Windows 8, but the DMP attached is Windows 7?

Also I've run tests for error on my RAM with memtest86+
For how long? If it was anything less than ~8 passes (many hours), run it again for at least 8 passes.

Regards,

Patrick
 

·
Registered
Joined
·
36 Posts
Discussion Starter · #16 ·
Re: New system - Random BSOD

Why would it be Windows 7? That confuses the hell out of me. I only own Windows 8, and I've only reinstalled Windows 8. :/


I ran the memtest86+ overnight. Atleast a good 12 hours, can't remember how many passes it was though.

Thanks for the quick reply!
 

·
TSF Team, Emeritus
Joined
·
4,349 Posts
Re: New system - Random BSOD

Windows 7 Kernel Version 9200 MP (4 procs) Free x64
It appears to be a bug the more I look now, as 9200 MP is not a Windows 7 version, but AFAIK is the Windows 8 RTM. Windows 7 versions for the release would be 7600 (non-SP1), and 7601 for when SP1 is installed.

Anyway!!! Now that we've ironed that out, I'd run Memtest one more time to be sure for at least ~8 passes. If Memtest comers up okay, let's move onto hard disk diagnostics:

start>search bar>type cmd right click and select run as admin

Elevated CMD should now be opened, type the following:

chkdsk x: /r

x implies your drive letter, so if your hard drive in question is letter c, it would be:

chkdsk c: /r

Restart system and let chkdsk run.
If chkdsk turns out okay, run Seatools - SeaTools | Seagate

Run everything minus Fix All and Long Generic.

Regards,

Patrick
 

·
Registered
Joined
·
36 Posts
Discussion Starter · #18 ·
Re: New system - Random BSOD

My gf actually took a note on the memtest, according to her it did 13passes.

Also I'm currently running the chkdsk. It's been stuck 27% for well over 30 minutes. Is it bugged or just simply not updating the progress in real time?
 

·
Registered
Joined
·
36 Posts
Discussion Starter · #19 ·
Re: New system - Random BSOD

Alright, turns out I was just an impatient kid who keeps asking "Are we there yet?"

So I ran all the tests with the SeaTool and Western Digitals own tool and found 0 errors.

Also I did more digging and found many people with very similar symptoms like mine ending up blaming the Realtek onboard audio. But I've updated it to the latest driver (or atleast I think I have). The site is very, well, not-user-friendly.
 
1 - 20 of 50 Posts
Status
Not open for further replies.
Top