crash, freeze, lock up

Hi all
First off my specs are as follows:
.Windows 7 64 bit
.HD6950 2GB
.6GB Ram
.Creative sound blaster card
.AMD Phenom II x4 955 processor @ 3.20 GHz

About a month back now i stupidly let my brother try to over clock my processor via the bios, when i noticed an increase in cpu temperature, went up to around 60 - 70 c i immediatly told him to put it back to default, which he did, but the temp was still higher then it was normally... anyway i started getting BSOD (blue screen of death) randomly, also a strange crash too wen the screen would become very thin horrizontal lines of colour and the sound would become very distort (if i had any sound on at the time of crash) so i went out bought a new heat sink which brought the temp down to around a steady 30c, and at the time of installation i cleaned my comp out thourghly... everything was one fine, no problems until the other night (about 4 weeks down the line...) started again, BSOD, crash etc... so i formated my pc last night, soon as i got everything up and running again, i installed portal 2 to give it a whirl, i got 4 BSOD's and 2 crashes trying the game out, then i removed 2 of my 3 sticks of ram (hoping one of them could have failed) and i played the game for about 2 hours no problem, came off it and the computer just froze, no distorted sound, bsod... just a regular freeze, rebooted comp, bsod etc... so guys, im at my witts end here, i dunno what it could be, unless the processor is knackered now... anyway to test it?

 

I doubt anything is wrong with your cpu - the computer wouldn't work at all if the cpu were fried.
Based on what's happening, I would test the memory with memtest 86+ as a first step.

You can find memtest 86+ here:
http://majorgeeks.com/Memtest86_d4226.html

You have to burn the .ISO to a cd, then boot from the cd to run it.

 

Recent experiences have led me to believe that the most likely culprit is always a Creative Labs product, where one is installed.

>.<

 

I prefer to troubleshoot and view all the evidence before apportioning any blame

@ silverbullet: If you can copy some of the minidumps to your Desktop, zip and attach them, I'll try to debug them and check for old and/or known bad drivers.

 

Here ya go, hope this is what you need anyway?

YeeHa, ive been using the creative sound card for... pfft 3 / 4 years now? so i doubt its that....

Abekl i will run mem test maybe tonight or tomorrow...

 

So far, it's looking like it is soundcard driver-related!

Probably caused by : portcls.sys ( portcls!CPortPinWavePci:eviceIoControl+3eb )

CPortPinWavePci = this looks like it's the Creative sound card.

I'm guessing a recent Windows/Microsoft Update has broken the compatibilty with the currently loaded Creative drivers, I'd check if Creative have any newer drivers available.



EDIT: your second analysis points to the ATI video driver; again, check with AMD/ATI for the latest driver. For fewer chances of bugs further on down the line, uninstall the CCC (Catalyst Control Center) and install the drivers only package.

 

since ive only just formatted (still not done anything appart from put drivers on....) ive got the latest version of my ati drivers, as for the creative card, im using the same drivers as ive had for.... well as long as ive had windows 7 now, i had difficulty finding them as its an old sound card now, maybe your right? i remeber there been a few updates before i started having problems... but fyi ive been running with 1 stick of ram (2gb) all night now and so far no crash...so i will put the other 2 sticks back in n run a mem test too

 

ran a memory test, was running for around 5 hours, got 2 errors...

removed creative sound drivers, and using motherbord one now... still got the crash after i thought everything was fine... so heres today's error report, and i think its something else this time... dxgmms1.sys?

 

The dxgmms1.sys points to it being graphics related.

EDIT:

This needs further investigating, Memtest86+ overnight or at least 7 runs on each stick. Is the BIOS setup correctly for the RAM you have installed?

 

any error indicates a memory problem. I think you have two problems, memory and perhaps graphic.
Fix the memory first so you know any errors then will be graphics related.

 

right i think i may have solved it... looks to be an issue with ATI 11.3 drivers... quite a few forums related to it when i googled it, same with 11.2 drivers aswell, so ive reverted back to 11.1 (january release) and so far so good... not holding my breath though, but thanks guys, if i dont get any problems i will come back just to confirm, that way anyone else having the problem will know too

 

well so far so good... put my creative drivers on, and ive been on my computer all day with no crash, so it looks to be a driver problem with the 11.3 ati drivers....

 

me again =/ 2 days with no problems, then it starts again... only seems to be happening when i am on a game now...

todays crash was probably caused by atikmdag.sys but the last 2 were probably caused by ntkrnlmp.exe (cpu or memory related?)

anyway the reverse of ati drivers seems to have helped, just im getting these 2 problems now =/

 

now ive just got probably caused by xusb21.sys
thats like 5 different problems now, wtf is going on?

 

and another one, probably caused by win32k.sys

 

Many random BSOD's are usually indicative of memory or other hardware failure; if the hardware is shot, no amount of software fiddling will fix it. Revisit posts #2, #10 and #11.

 

right okay, well im testing a new card as we speak, ive "borrowed" my mates HD4870 to try so i can eliminate graphic card problems hopefully, i will leave memtest running tonight, just out of curiosity, wen the mem test finishes, were will it save the log? or do i have to write all the codes and errors down?

 

got bsod with different card (which im releaved about as ive only just bought that 6950) got another error , probably caused by cdd.dll

 

Do you think it might be time to test your memory with MemTest86+ now?

If so, read the instructions here at carrona.org, I think you'll find all you need there. Report back when you have tested the memory over 7 passes or overnight without errors and we'll move on to checking the next piece of hardware.

 

im going to run the test over night cos i can still use my computer now without playing a game, its only 17:25 here in the uk, but when the memtest is eventually done, how do i get the results so i can post them here?

 

The results should be onscreen.

 

10 hours 50 mins, 13 passes, no errors =/

 

Ok, that should rule out memory errors.

Can you attach the last 3 minidumps please? Copy them to your Desktop, zip and attach the resulting zip file, I'll try to check them over for clues as to what's happening here.

 

here you go, last 3 crashes from yesterday

sorry i only use winrar, and that wouldnt upload...

Like ive been saying, they seem to be completly random, ive googled what each probable cause is... but i just find the whole thing.... just weird, i mean why can it be fine one day, even weeks without a problem then start again? i mean ive just been on a game this morning for over an hour, no crash yet.... whereas yesterday, within the first 5 - 10 mins if that

 

I need the complete dumps, not a readout from WinDbg.

 

sorry... how do i do that? is it back on the info for windbg

add the command !analyze -v to the dump? is that it

 

C:\Windows\Minidump\ copy the last 3 *.dmp files to your Desktop then zip and attach them.

 

here you go, hope thats right, ive not use winzip for a good 6 years
whilst typing this i got bsod again, so ive also added tht dmp file too

 

Are you still on the original graphics card or on the replacement/test card you tried out?

Can you give me the make/model of the motherboard and power supply please?

 

im back on my newest card, my HD6950 on older drivers, i still got bsod with replacment card.

Motherboard is Asus M4A785TD-V EVO 785G Socket AM3
Power supply is a Thermaltake TR2 - 500watt true powersupply

 

just had a thought, n this is gonna sound really stupid but... worth asking you.... when i stupidly let my brother overclock my cpu, i told him to reset what ever he changed in the bios to default, if he reset everything to default in the bios which im sure he did, he may have enabled the onboard sound + graphic chip (the motherboard can make use of the ati hybrid system with the onboard graphic chip which i dont use as i have my own graphic card) ive always disabled the on board sound as i use a sound card, if this is enabled again, could it be either the on board sound chip and or graphic chip causing these random crashes?

 

I've read that the hybrid graphics doesn't actually work on this chipset family anyway.

What I'm seeing in the older 2 dumps is errors with DirectX while gaming. Can you update DirectX with the installer here, it'll improve compatibility with non fully DX10/11 games.

 

well ive disabled the onboard sound because tht was enabled, and that could have been conflicting with the creative drivers?... and disabled the internal graphic option.... so far so good. Ive already tried that dx update, but ive just done it again as youve suggested, says i already have the latest version.

As a completly unreleated question, ive just noticed something on the startup screen (after i restart computer) where it should say my ram type + quantity it now just says ddr3 1333 ungaged ... my ram can support up to 1600. how do i change that? and what does it mean by ungaged? just so you know anyway my memory is Kingston 4GB (2x2GB) DDR3 1600MHz/PC3-12800 , i have 3 sticks of 2GB

 

Why change the RAM settings if the memory has passed testing but you still have BSOD's?

Start playing your usual game - what game is it anyway? - we need to get another dump to upload.

 

i dont want to change it i just woundered why it was saying ungaged? ive not seen tht before, plus i know it runs at 1333 standard, i have to tell the bios to run it at 1600 but i know nothing about that...

usually play company of heroes, bad company 2, more recently portal 2 will keep playing n see if i get a crash lol btw can i just thnk you satrow, i know what its like to have someone who dosnt know what their talking about asking a million questions, and i really appriciate it =)

 

here you go, heres the latest one... =/ was just on a game again...

 

Everything still points towards graphics being the most likely problem, try going back to AMD and downloading a previous version of the graphics driver. Try to download a drivers only package, at this stage, we don't need the added complications of any additional software loading at boot.

Testing with Furmark might save you several hours of waiting for the next BSOD.

 

furmark got the temp up to 82c, before i stopped it (wasnt too sure whether it would stop) but my card typically runs between 35c - 60c (if playing a game) i have a pretty well ventalted computer. Im just gonna test a display driver only... did you want me to run that furmark longer? will it stop on its own accord?

 

this one has just happened with display driver only.... probable cause hardware?

 

Hmm, this one comes up with hardware as a cause and lots of tcpip calls in the stack trace, no hint of graphics:

Code:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck FC, {fffff88001743fd8, 8000000003d31121, fffff88002d8b240, 0}

[B]Probably caused by : hardware ( tcpip[/B]!Ipv4PnpEventProviderNotify+828 )

Followup: MachineOwner
---------

2: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

ATTEMPTED_EXECUTE_OF_NOEXECUTE_MEMORY (fc)
An attempt was made to execute non-executable memory.  The guilty driver
is on the stack trace (and is typically the current instruction pointer).
When possible, the guilty driver's name (Unicode string) is printed on
the bugcheck screen and saved in KiBugCheckDriver.
Arguments:
Arg1: fffff88001743fd8, Virtual address for the attempted execute.
Arg2: 8000000003d31121, PTE contents.
Arg3: fffff88002d8b240, (reserved)
Arg4: 0000000000000000, (reserved)

Debugging Details:
------------------


CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xFC

PROCESS_NAME:  System

CURRENT_IRQL:  2

TRAP_FRAME:  fffff88002d8b240 -- (.trap 0xfffff88002d8b240)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffff88001744050 rbx=0000000000000000 rcx=fffff88002d8b400
rdx=fffffa8008bef080 rsi=0000000000000000 rdi=0000000000000000
rip=fffff88001743fd8 rsp=fffff88002d8b3d8 rbp=0000000000015504
 r8=fffff88002d8b410  r9=fffffa800608e638 r10=0000000000000369
r11=fffff88002d8b438 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl zr na po nc
tcpip!Ipv4PnpEventProviderNotify+0x828:
fffff880`01743fd8 0100            add     dword ptr [rax],eax ds:e502:fffff880`01744050=00030735
Resetting default scope

MISALIGNED_IP: 
tcpip!Ipv4PnpEventProviderNotify+828
fffff880`01743fd8 0100            add     dword ptr [rax],eax

LAST_CONTROL_TRANSFER:  from fffff80002d424b1 to fffff80002cc3740

STACK_TEXT:  
fffff880`02d8b0d8 fffff800`02d424b1 : 00000000`000000fc fffff880`01743fd8 80000000`03d31121 fffff880`02d8b240 : nt!KeBugCheckEx
fffff880`02d8b0e0 fffff800`02cc182e : fffffa80`00220003 fffffa80`098c2a10 fffffa80`08277900 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x40a25
fffff880`02d8b240 fffff880`01743fd8 : fffff880`01648833 fffffa80`05ff1f90 fffff880`0164f953 fffffa80`05ffba70 : nt!KiPageFault+0x16e
fffff880`02d8b3d8 fffff880`01648833 : fffffa80`05ff1f90 fffff880`0164f953 fffffa80`05ffba70 00000000`00015504 : tcpip!Ipv4PnpEventProviderNotify+0x828
fffff880`02d8b3e0 fffff880`01640780 : fffffa80`098c2a10 00000000`00000004 00000000`00000002 00000000`00015504 : tcpip!InetDereferenceLocalAddressAf+0x33
fffff880`02d8b440 fffff880`01632770 : 00000000`00000000 00000000`00000004 fffffa80`05ff36a0 fffffa80`05ff36a0 : tcpip!TcpCleanupTimeWaitTcb+0x20
fffff880`02d8b470 fffff880`0167ee44 : fffffa80`098c2a00 00000000`00015504 fffffa80`098c2a10 00000000`00000004 : tcpip!TcpDereferenceTimeWaitTcb+0x20
fffff880`02d8b4a0 fffff880`01672d18 : 00000000`00015504 00000000`00000004 00000000`00000690 00000000`000004b0 : tcpip!TcpProcessExpiredTimeWaitTcbTimers+0x104
fffff880`02d8b4f0 fffff800`02ccf29e : fffff880`02d8b600 fffffa80`0000b5b8 00000000`00000001 00000000`00000000 : tcpip!TcpPeriodicTimeoutHandler+0x31a
fffff880`02d8b570 fffff800`02ccedd6 : fffffa80`059bac68 fffffa80`059bac68 00000000`00000000 00000000`00000000 : nt!KiProcessTimerDpcTable+0x66
fffff880`02d8b5e0 fffff800`02ccf4be : 00000002`081ad57d fffff880`02d8bc58 00000000`0000da7e fffff880`02d66548 : nt!KiProcessExpiredTimerList+0xc6
fffff880`02d8bc30 fffff800`02ccecb7 : 00000000`a3542fc2 00000000`0000da7e 00000000`a3542f8f 00000000`0000007e : nt!KiTimerExpiration+0x1be
fffff880`02d8bcd0 fffff800`02ccbeea : fffff880`02d63180 fffff880`02d6dfc0 00000000`00000000 fffff800`02de3db0 : nt!KiRetireDpcList+0x277
fffff880`02d8bd80 00000000`00000000 : fffff880`02d8c000 fffff880`02d86000 fffff880`02d8bd40 00000000`00000000 : nt!KiIdleLoop+0x5a


STACK_COMMAND:  kb

FOLLOWUP_IP: 
tcpip!Ipv4PnpEventProviderNotify+828
fffff880`01743fd8 0100            add     dword ptr [rax],eax

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  tcpip!Ipv4PnpEventProviderNotify+828

FOLLOWUP_NAME:  MachineOwner

IMAGE_NAME:  hardware

DEBUG_FLR_IMAGE_TIMESTAMP:  0

MODULE_NAME: hardware

FAILURE_BUCKET_ID:  X64_IP_MISALIGNED

BUCKET_ID:  X64_IP_MISALIGNED

Followup: MachineOwner
--

Which game are you usually playing when the BSODs occur?

Install the Win7 and WinServer 2008 R2 Driver from here via Device Manager for your RealTek network adapter from here, you'll need to extract the files to a folder first, I guess, then point DevMan to the folder. Run the Furmark test again once it's installed.

See if you can track down and install a more recent driver for your Creative sound card too.

 

The hardware .dmp happened when I was just browsing a website... Like I said if I play a game it's either bad company 2 or company of heroes... But i get some freezes too were I just have to restart computer

 

My guess is that the in-game freezes might be happening because the data expected is corrupt (because of some TCP/IP errors). Go ahead and update those network drivers and run some more hard tests.

 

Device manager said the drivers were already up to date for that...

There are no recent drivers for the sound card as it is old now and support for it has been dropped but ive been using windows 7 for a good year now without any problems up until all this started happening. But i will keep looking....

In regards to in-game freezes, ive not had freezes when playing games, it has always been bsod, the freezes occur when im on my desktop or browsing internet... But i also do get some bsod when on desktop too, its all just too random =/

 

The driver I pointed to is over 2 years newer than the one I see installed on your system. Current Rt64win7.sys is 2/26/2009, latest is 3/21/2011. Try the self-installing version instead.

 

right ive installed that now... just wait for another bsod?

 

Yes please, game or stress test it again; watch streaming movies at the same time .

 

lol i'll go on bad company for a bit, see how long it lasts

 

was on game for 4 hours last night, no problem, go on it for 15 mins today and when i came off it, comp froze, with distorted sound, no bsod... this is what i hate so much about it because i cant seem to say what is causing it, or do a specific task to cause it -_-

 

Reads like another TDR.