Freeze - sound lock

E

-Ever-

Limp Gawd
Joined
Sep 27, 2002
Messages
218
Hi guys,

I'm getting a strange freeze with Diablo 3. It's completely random, as in not just when a lot of on-screen action is taking place.

Video: http://youtu.be/hjGjbP_D5D4

Happens randomly in game. Screen freezes, sound locks / loops. My mouse still works, and I can continue talking to my friends in Ventrillo (IE, it's not an entire computer freeze). It sometimes resets on its own after five to twenty seconds. Another important note is that using the Start Menu key to minimize, alt-tabbing, or ctrl-alt-delete tends to kick it out of the cycle, in that it will be fixed when I maximize. Of course I'm dead when I return >:]

Have tried:
Have tried:
Reinstalled D3
Tried different gfx drivers
Updated mobo drivers
Updated mobo bios
Updated SSD firmware
Returned CPU to stock clock
Turned sound quality down to 16bit
Disabling all hardware devices for Sound in Device Manager
Turning sound off in D3
Ran Heaven. Default score ~1,500 60fps. Temperatures were reasonable.
Ran MemTest86+ found out one of my two new sticks were bad. Thought I solved the problem, tried running with just one 4g stick, still getting the lockup. Not sure if this could still cause the issue as I'm only running one of the two sticks..


New build, fresh Win7 and D3.

i5 3750 (ivy bridge)
ATI 7850 gfx
z77 motherboard
8gig 1600
M4 SSD (OS, D3, etc)
 
Last edited:
find the amd sound driver in device manager and disable/uninstall it. Its really fucking irritating.
should be under sound/video/game controllers > amd high def audio device
I reboot for kicks afterwards, to be sure.
 
Intereasting. AMD, as in the graphics company? It includes sound drivers?

Also, in the case it works, why do I need to turn it back on? Will my sound work during D3?

Thank you.
 
I don't play any other games, so I can't test that way unfortunately.

Updated OP under "have tried."

Disabling sound altogether didn't work. Neither did reinstalling D3.
 
dude, used CATALYST 12.1! Ever since i update to 12.4, 12.5, 12.6 or 12.7 ! SC2, DIABLO 3, BF 3 all will crash! But, i find a way to overcome the crash, that is to play a video on the background while running your games! But it won't work after you close your video for 30 sec.

My HD 7970 is having the same symptom as yours! BLACK SCREEN CRASH WITH AUDIO SUTTTERING! AMD SUCKS WITH DRIVER SUPPORT!
 
Updated OP with a YouTube clip of the lock.

Heaven results:

Default pass: 60fps, 1,500 score, 30-120 min/max

With vSync: 40fps, 1,000 score, 20-60 min/max

Temperatures:

CPU: Ranging from 23c-53c across all the cores

GFX: 34c-59c
 
Last edited:
Please check your "Event Viewer"... What you are looking for is listed as Event Type = Error, Event ID = 9, Source = iaStor... If see this happening along with the LockUps I have a fix... It seems that SSD drives being used with Z77 Chipsets have an issue with going into low power mode (LPM)... LPM can be disable for the needed Sata channels via Regedit... Below is a link to solution along with further info... I had this same issue with 2 OCZ Vertex SSD's in Raid... Since the fix I've had Zero Lockups in 3 days... The computer in question is used 10-12 hours a day...

http://forum.crucial.com/t5/Solid-S...eze-ups-in-Windows-7-solved-for-me/td-p/38766

I hope this is helpful and solves your issue...
 
Ye freezing is mostly SSD/unstable overclock issues, but since it happens on stock, its prooly Iastor drivers/SSD issue, good point there, i had the same issues, and fixed it with the registry fix from that thread as well.
 
Excellent, sounds promising. Thank you. I'll try this tonight and edit the post with findings.
 
This same EXACT thing happens to me. It doesn't happen in any other games.

It does it in D3 regardless of settings, whether they are on the highest settings or the lowest (even at 1024x768 or whatever). Playing at the highest settings doesn't cause it to happen more often and playing at the lowest doesn't make it happen less often.

...but because it doesn't happen in any other games I play I'm not going to pull my hair out over it.
 
SSD LowPowerMode idea didn't work. I didn't have Error 9 in Event Viewer. I did the registry trick anyways and I'm still locking up.

Thinking about installing D3 on my HDD and seeing what happens.
 
Try uninstalling the AMD driver and let Microsoft find the update automatically in Device Manager and see if it works correctly, just what I'll try to do, not really a solution...

If it's still frozen, card must be defective....
 
have you tried reinstalling windows? you should try a complete fresh reinstall of everything.
 
Ugh, I had the same thing and it took forever for me to track it down to my PCIe WIFI card. Installing Atheros drivers instead of the Win7 default fixed it.

Unfortunately when you Google the problem you'll see a lot of people having it for different reasons. A common solution was to buy a sound card and disable onboard audio.

Good luck tracking it down.
 
Using onboard audio.

How would one deduce that it's a "bad" motherboard? And not something obvious, like RAM isn't working in one of the DIMMs.
 
-Ever- said:
Using onboard audio.

How would one deduce that it's a "bad" motherboard? And not something obvious, like RAM isn't working in one of the DIMMs.
Click to expand...

If you had spare ram then you should be able to blatantly determine whether it's something obvious or not, but you never really stated that except you had 2 bad sticks.
 
halodude23 said:
If you had spare ram then you should be able to blatantly determine whether it's something obvious or not, but you never really stated that except you had 2 bad sticks.
Click to expand...

OP says one stick is bad. Thus I was able to deduce that the motherboard memory slots aren't bad because the good memory stick works in any of the main slots.

So, how can a motherboard be "bad" besides this? And if so, how do you deduce it enough to justify an RMA?
 
Last edited:
I would have guessed it was the RAM being bad but you said the "clean" stick is running solo now and still working. You should try running that RAM in someone else's working system to see if that's the issue.. if that ram runs fine and nothing is wrong, then it would end up being the mobo.
 
Still happening after disabling the drives sleep modes.

Considering installing D3 on my HDD (instead of my SSD) and trying that.
 
Switched the install from my SSD to my HDD and am yet to see the issue again. Thoughts?
 
New memory installed today, but the issue looks to be SSD / Crucial M4 related as I'm yet to see it since switching the install locations.
 
-Ever- said:
New memory installed today, but the issue looks to be SSD / Crucial M4 related as I'm yet to see it since switching the install locations.
Click to expand...

You said you try with HDD and nothing changed? how come its the SSD now?
 
You must log in or register to reply here.
Back
Top