New
#31
The latest crash points to audiodg.exe which is a known issue. See Fix: Audiodg.exe High CPU Usage to resolve it.
The prior crash does indeed point to the graphics card or its drivers as a likely culprit.
The latest crash points to audiodg.exe which is a known issue. See Fix: Audiodg.exe High CPU Usage to resolve it.
The prior crash does indeed point to the graphics card or its drivers as a likely culprit.
Hi Writhziden
Thanks also for your help so far..
Updates since the last dump:
Been in touch with the seller of the laptop, and they've asked me to try reverting to the original hardware configuration (to rule out my SSD basically), so I'm back to a 500GB HDD & Optical Drive.
The crashes are very very easy to reproduce (infact i can force a BSOD by starting the game F1 2011, and running the benchmark test, before the game completes a lap of monaco (about a 1:20 ?) the machine bluescreens)
I've just done some digging through device manager (I dont know what possessed me) - baring in mind nothing was 'stickered' as having an issue (yellow ! etc.) .. Digging through the System devices, i picked up the properties of the SMBus (thinking that the BSODs are pointing to Chipset / Graphics things..) and it appears even after installing the chipset drivers etc, the SMBus driver was very outdated (Windows default??) - And i've installed a new SMBus driver (which appears latest)
I've attached the old dumps anyway, but im hoping that updating this will remove the paging/irq issues which seem to be the main reasoning of the BSODs.
Regards
Annnnnnnnnd I was hoping that would fix the problem...
And it hasnt
So any more guidance would be more appreciated :P
First dump in this one added was playing F1 2011 - pointed to Graphics driver so performed a clean install, played the same game and in less than 3 minutes I got a BSOD. (this is the second dump)
Regards
Last edited by Matt2k; 28 May 2012 at 16:04. Reason: added dumps.. duh
Crashes primarily indicate your graphics card or DirectX.
Have you done a factory restore to make sure it is not a corrupted Windows registry (or do you even have that option with your laptop vendor?)?
Thanks for the reply,
Laptop came without OS, as I have an MSDN subscription via university.
Tried Windows 7 x64 Pro and an updated SP1 ISO (via USB stick install) to rule out the media too.
Have done... 8? or so formats in the last 2 weeks to remove any messes made by drivers / third party software inbetween.
When first received the laptop, the GPU was bad (caused BSODs at random.. familiar story ) So I'm thinking that either the GPU is also dud, or when the GPU went it has damaged the chipset / other part of the motherboard...
I'm waiting to hear back from the seller to see if im able to swap it (should do) but i really cannot think of anything else software based that could be the issue....
Regards
Agreed; your steps are sound and the logic is likely dead on. :) Let us know what the seller says.
After reading between the lines of what the seller put
I found the service manual online for the laptop (about as rare as rocking horse poop, it seems) and dismantled the unit completely.
Just about to stress the laptop for a few hours to ensure the problem has resolved, but although the laptop passed memtest (and several other, memory diagnostics for hours) it appears there may be a dodgy pair within the unit.
I've removed and fingers crossed I have no more problems... RMA'ing the RAM will be much cheaper than shipping the laptop across the world
Many thanks for the help and guidance (and finding several drivers I hadnt found, even through the manufacturers websites..)
I'll post back in a few days or so and hopefully everything will be fine.
You're welcome. Look forward to hearing back. Very nice work, by the way!! Best of luck!
Hey
Just thought id report back.
Laptop has been running smooth as silk for 2 weeks, RMA'ing the RAM removed (even though it passed every test thrown at it, with just those two sticks in together the laptop has a massive wobbly, without them in at all its been rock steady.)
Go figure, obviously the issue is something the memtester-progs either arent set to detect or didnt/arent able to detect.
On the plus side, the WLAN has stopped causing any grief too, So all the work done buy you chaps in this thread has been MUCH appreciated. I can stop stressing and enjoy using this machine now
Kind Regards
Matt
Great to hear. When you are confident it is solved, you may mark the tread solved.
As to the memory testing, Finicky RAM is good further reading.