Another BSOD thread ... sorry:p

[ApolloCXVII]

Hey guy. I've been searching through a few of the other threads in here, trying to work out my bsod but I'm struggling to find anyone with something like mine.
I'm new to this minidump stuff and have read the sticky about it at the top of the thread.

http://www.sevenforums.com/attachment.php?attachmentid=30329&stc=1&d=1254644078

They seem to occur quite randomly and haven't been able to draw any common indicators for when they occur.
Any help would be greatly appreciated!

 

[ApolloCXVII]

anyone got anything for me?!

 

[thefabe]

Please fill in all your sytem specs in your user cp. This way some of the more qualified Gurus on this site will have more information avalible to them to do a more through analisys of your dump file. Thanks and welcome to sevenforums

 

[Antman]

Like this...

 

[ApolloCXVII]

Please fill in all your sytem specs in your user cp. This way some of the more qualified Gurus on this site will have more information avalible to them to do a more through analisys of your dump file. Thanks and welcome to sevenforums

Done! Thanks for replying mate.
This looks like the best forum for everything, 'Windows 7', on the net!

PS: your system is SWEEET!

 

[zigzag3143]

Please fill in all your sytem specs in your user cp. This way some of the more qualified Gurus on this site will have more information avalible to them to do a more through analisys of your dump file. Thanks and welcome to sevenforums

Done! Thanks for replying mate.
This looks like the best forum for everything, 'Windows 7', on the net!

PS: your system is SWEEET!

Apollo

If you go to c:\windows\minidump , zip the dump file (*.dmp) and upload it to us, we can analyze it for you

let us know if you need help with any of this

ken

 

[ApolloCXVII]

Heres the minidump.

 

[zigzag3143]

Heres the minidump.

Apollo

you were running opera at the time of the crash, right?

dump is inconclusive but opera caused it. I cant offer any advise except to run a system file check (sfc /scannow)

Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\K\Desktop\100409-26707-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*d:\symbols*Symbol information
Executable search path is:
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`02a53000 PsLoadedModuleList = 0xfffff800`02c90e50
Debug session time: Sun Oct 4 02:36:54.223 2009 (GMT-4)
System Uptime: 0 days 0:05:32.580
Loading Kernel Symbols
...............................................................
................................................................
.....................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 101, {31, 0, fffff88002dd3180, 3}

Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )

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

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

CLOCK_WATCHDOG_TIMEOUT (101)
An expected clock interrupt was not received on a secondary processor in an
MP system within the allocated interval. This indicates that the specified
processor is hung and not processing interrupts.
Arguments:
Arg1: 0000000000000031, Clock interrupt time out interval in nominal clock ticks.
Arg2: 0000000000000000, 0.
Arg3: fffff88002dd3180, The PRCB address of the hung processor.
Arg4: 0000000000000003, 0.

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


BUGCHECK_STR: CLOCK_WATCHDOG_TIMEOUT_4_PROC

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

PROCESS_NAME: opera.exe

 

[ApolloCXVII]

Yeah I'm fairly sure its not Opera causing it because i have had the same bsod with PROCESS NAME: system.

CLOCK_WATCHDOG_TIMEOUT (101)
An expected clock interrupt was not received on a secondary processor in an
MP system within the allocated interval. This indicates that the specified
processor is hung and not processing interrupts.
Arguments:
Arg1: 0000000000000031, Clock interrupt time out interval in nominal clock ticks.
Arg2: 0000000000000000, 0.
Arg3: fffff88002dd3180, The PRCB address of the hung processor.
Arg4: 0000000000000003, 0.

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


BUGCHECK_STR: CLOCK_WATCHDOG_TIMEOUT_4_PROC

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

PROCESS_NAME: System

CURRENT_IRQL: d

How do i run the system file check? i tried opening the program and its just flashed up and closed really quickly...

 

[H2SO4]

Yeah I'm fairly sure its not Opera causing it because i have had the same bsod with PROCESS NAME: system.

CLOCK_WATCHDOG_TIMEOUT (101)

The "process name" is irrelevant, odd as that may seem.

In fact, apps are not capable of causing this type of crash, and very few driver problems are thus endowed. This is very hardware-ish.

If it's an AMD processor, I'd suggest a thorough examination of the many detailed posts on the AMD forum regarding this complex issue. If the box is under warranty, you may wish to leave the troubleshooting to the place where you bought it.

 

[ApolloCXVII]

run a system file check (sfc /scannow)

Ok so i ran a system file check and it said that it found some errors but didnt tell me exactly what they were! what would be the next step now?

If it's an AMD processor, I'd suggest a thorough examination of the many detailed posts on the AMD forum regarding this complex issue.

Checked the AMD forums. Found a few threads with 'similar' problems but know one seems to know whats going on.
BIOS update seemed to come up a bit in the forums but how can i update my bios on my M3A? The Asus's bios update tool doesn't have windows 7 as option when i go through the product select system on the ASUS website, and when i tried the Vista version it said it was not compatible with my operating sytem.

Thanks for the help so far guys!

 

[septprince]

run a system file check (sfc /scannow)

Ok so i ran a system file check and it said that it found some errors but didnt tell me exactly what they were! what would be the next step now?

If it's an AMD processor, I'd suggest a thorough examination of the many detailed posts on the AMD forum regarding this complex issue.

Checked the AMD forums. Found a few threads with 'similar' problems but know one seems to know whats going on.
BIOS update seemed to come up a bit in the forums but how can i update my bios on my M3A? The Asus's bios update tool doesn't have windows 7 as option when i go through the product select system on the ASUS website, and when i tried the Vista version it said it was not compatible with my operating sytem.

Thanks for the help so far guys!

Install it by changing its compatibility mode to vista. It should work.

 

[ApolloCXVII]

BIOS has been updated. Seems to have fixed it (fingers crossed). But I'd like to be sure can you guys recommend a stress test of my CPU or system as a whole that will confirm that my system is no longer getting these blue screens?

Thanks.

 

[ApolloCXVII]

Ok so updating the BIOS didnt help. my system just blue screened with the same error twice in a row. Has anyone got any ideas what i could try now!!?

 

[H2SO4]

Ok so updating the BIOS didnt help. my system just blue screened with the same error twice in a row. Has anyone got any ideas what i could try now!!?

The error means that the processor cores are having trouble getting each other's attention. There was a range of AMD processors which were particularly susceptible to this issue, and some of them needed microcode updates and such to fix the underlying cause. I don't know whether your processor falls into that category, which is why I suggested you read the AMD forums carefully. From memory, search for "optimizer", "phenom", and "TLB" (translation lookaside buffer).

Otherwise, it could be anything from a literally broken processor to a BIOS power management plan that allows at least some of the cores to "go to sleep" to the point where they are inaccessible in a timely manner. A commonly attempted workaround is to disable all processor and PCI express power management in the hope that the individual cores will always stay awake, thus masking the issue. Obviously, that has very negative effects on laptop battery life and power consumption in general. Run these from an elevated CMD prompt and follow the bouncing ball from there:

powercfg /?
powercfg -l
powercfg -query

The ones you want to modify are the "Link State Power Management" and the "Minimum processor state" for your chosen power plan. Change the settings so everything is in "high performance" mode all the time.

 

[ApolloCXVII]

Thanks so much for your help H2SO4. Finally seemed to have worked this problem out. The problem is basically how you explained from what i can tell.

AMD released a 'tlb' fix which was in turn distributed by the mother board brands bios updates.

I've applied the fix and everything seems to be going fine, however after researching the patch it seems that it often has a much larger drop in processing power then the 10 % conceded by AMD's media release. many games don't perform very well under the fix, such as World in Conflict which is almost unplayable dropping a whopping 40%.

Admins this problem has been solved. I suggest anyone upgrading with from xp to windows 7, running a phenom 9500 or 9600, should google the tlb fix if they run into a similar BSOD.


Thanks for everyones help. - ApolloCXVII

PS now "upgrading" to a AMD Phenom II X3 720 I've read good things about these tri cores, should be fun.

 

[H2SO4]

Thanks so much for your help H2SO4. Finally seemed to have worked this problem out. The problem is basically how you explained from what i can tell.

AMD released a 'tlb' fix which was in turn distributed by the mother board brands bios updates.

I've applied the fix and everything seems to be going fine, however after researching the patch it seems that it often has a much larger drop in processing power then the 10 % conceded by AMD's media release. many games don't perform very well under the fix, such as World in Conflict which is almost unplayable dropping a whopping 40%.

Admins this problem has been solved. I suggest anyone upgrading with from xp to windows 7, running a phenom 9500 or 9600, should google the tlb fix if they run into a similar BSOD.


Thanks for everyones help. - ApolloCXVII

PS now "upgrading" to a AMD Phenom II X3 720 I've read good things about these tri cores, should be fun.

I'm glad to hear you got it sorted. Have rep for being methodical and patient