peculiar crashing error

Soldato
Joined
24 Feb 2004
Posts
14,399
Location
St.Andrews
Hey,

Got problems with my PC crashing in a most odd manner. When waiting for things to happen in games and what not I tend to drum on my desk which when hit hard enough causes a solid lock up with the sound stuck/looping.

Obvious answer is don't hit the desk but why is it happening? Tower is on the floor but against the desk leg so perhaps vibrations being passed to the case and the SSD?

Any pointers of where to start looking would be great!
 
Well the obvious thing to do is boot up and get to a point when the problem is likely to occur, then disconnect all peripherals and see if you can get the problem to replicate.

If you can I'd suggest checking all connections are solid inside the case. If they are, move the case or stop hitting your desk
 
Hmmm started happening in Borderlands 2 now without any desk hitting! Crash log in Event Viewer mentions something about a USB/Card Reader driver failing to load.

Wondering if there's something more sinister at work? Maybe worth running memtest?
 
list you pc parts,lockups with sound looping like that are usually gpu setting or pc memory setting/voltage related
 
HOOOGE Delay because GAMES :D

Also stopped because of this crashing issue! Rather annoying but never mind....

System spec is:

4670K (I think, Devils Canyon anyway)
16GB (2x8) TeamGroup Memory
Gigybyte Z97 Gaming 3 Motherboard
Crucial M500 SSD, 240GB
1 x 4TB WD Green (iirc...honestly can't remember, might be seagate!?)

Only thing I can see in the crash logs is a reference to WUDFPf.sys and a driver failing to load?

The driver \Driver\WUDFRd failed to load for the device WpdBusEnumRoot\UMB\2&37c186b&0&STORAGE#VOLUME#_??_USBSTOR#DISK&VEN_GENERIC&PROD_FLASH_HS-CF&REV_4.44#070802000073&0#.

The driver file is present in Windows/System/Drivers - this is the only entry of note, the rest just say improper shutdown etc - nothing out of the ordinary when it locks solid.

Any ideas? Considering just throwing it out the window already :p
 
Hmmm on second inspection of the event viewer that error is AFTER the reboot, no obvious indication of what's causing this now I look more closely at it :(
 
Just locked up again (in BL2 :D ) but this time dumped me to a BSOD!

The one thing I did manage to spot from the BSOD before it restarted was something called ATIKMDAG.sys so I'm leaning towards the graphics drivers perhaps?
 
Back
Top Bottom