Jump to content


 


Register a free account to unlock additional features at BleepingComputer.com
Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.


Click here to Register a free account now! or read our Welcome Guide to learn how to use this site.

Photo

Unexplainable Bsod


  • Please log in to reply
7 replies to this topic

#1 fallout

fallout

  • Members
  • 6 posts
  • OFFLINE
  •  
  • Local time:01:39 AM

Posted 08 June 2007 - 02:58 PM

Hello guys this is my first post, i cant seem to find help for this anywhere im running windows vista x64 and whenever i run a cpu intensive app such as winavi converter or adobe premiere it runs for a while then i eventually get this strange bsod saying:

A clock interupt was not received on a secondary processor within the allocated time interval

Im running a amd 4400 and i have absolutely no idea what i've done wrong everything is installed as it should be

Thanks for looking :S

BC AdBot (Login to Remove)

 


#2 usasma

usasma

    Still visually handicapped (avatar is memory developed by my Dad


  • BSOD Kernel Dump Expert
  • 25,090 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Southeastern CT, USA
  • Local time:02:39 AM

Posted 09 June 2007 - 06:29 AM

Linky: http://msdn2.microsoft.com/En-US/library/aa469194.aspx

In short, it says that your processor isn't responding. I seem to recall some special "driver" type software for the AMD processors (I'm an Intel kinda guy! :huh: that could possibly help you. Also, you may try uninstalling and reinstalling the winavi and/or adobe programs to see if that helps. Make sure that you're using 64 bit apps when testing - it might also have something to do with the translation from 64 bit to 32 bit processing if you're running 32 bit apps on a 64 bit system.
My browser caused a flood of traffic, sio my IP address was banned. Hope to fix it soon. Will get back to posting as soon as Im able.

- John  (my website: http://www.carrona.org/ )**If you need a more detailed explanation, please ask for it. I have the Knack. **  If I haven't replied in 48 hours, please send me a message. My eye problems have recently increased and I'm having difficult reading posts. (23 Nov 2017)FYI - I am completely blind in the right eye and ~30% blind in the left eye.<p>If the eye problems get worse suddenly, I may not be able to respond.If that's the case and help is needed, please PM a staff member for assistance.

#3 fallout

fallout
  • Topic Starter

  • Members
  • 6 posts
  • OFFLINE
  •  
  • Local time:01:39 AM

Posted 09 June 2007 - 09:29 AM

Thanks for the reply i'll look into the software i've just finished a clean instal of vista 32-bit so that should be able to narrow the problem down a little bit i'll test it out and get back to you :huh:

cheers
fallout

#4 fallout

fallout
  • Topic Starter

  • Members
  • 6 posts
  • OFFLINE
  •  
  • Local time:01:39 AM

Posted 09 June 2007 - 12:24 PM

Thanks foor the help although i've tried using windows 32 bit now and im still getting the problem, also i've installed any amd software i could find and none of it seems to work, any further help would be greatly appreciated as im going crazy.

Could this be a problem with my processor itself?

cheers
fallout

#5 fallout

fallout
  • Topic Starter

  • Members
  • 6 posts
  • OFFLINE
  •  
  • Local time:01:39 AM

Posted 09 June 2007 - 12:49 PM

Ok after analysing the dump file

--------------------------------------------------------------------------------------------------------------------------------------------
Microsoft ® Windows Debugger Version 6.7.0005.0
Copyright © Microsoft Corporation. All rights reserved.

Extracted C:\Users\Terry\AppData\Local\Temp\000009480_Mini060907-02.dmp from
C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Report0a30d7c2\Report.cab

Loading Dump File [C:\Users\Terry\AppData\Local\Temp\000009480_Mini060907-02.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows Vista Kernel Version 6000 MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 6000.16386.x86fre.vista_rtm.061101-2205
Kernel base = 0x81800000 PsLoadedModuleList = 0x81911db0
Debug session time: Sat Jun 9 17:30:02.255 2007 (GMT+1)
System Uptime: 0 days 0:33:27.062
Loading Kernel Symbols
..................................................................................................................................................................
Loading User Symbols
Loading unloaded module list
......
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 101, {60, 0, 8247e120, 1}

Probably caused by : ntkrpamp.exe ( nt!KeFlushTb+11a )

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: 00000060, Clock interrupt time out interval in nominal clock ticks.
Arg2: 00000000, 0.
Arg3: 8247e120, The PRCB address of the hung processor.
Arg4: 00000001, 0.

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


ORIGINAL_CAB_PATH: C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Report0a30d7c2\Report.cab

CUSTOMER_CRASH_COUNT: 2

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

BUGCHECK_STR: 0x101

PROCESS_NAME: WinAVI.exe

CURRENT_IRQL: 1c

LAST_CONTROL_TRANSFER: from 81828448 to 818d85c9

STACK_TEXT:
885df9c0 81828448 00000101 00000060 00000000 nt!KeBugCheckEx+0x1e
885df9f4 8189056d 84dc401b 000000d1 885dfa88 nt!KeUpdateRunTime+0xd4
885df9f4 818af0b1 84dc401b 000000d1 885dfa88 nt!KeUpdateSystemTime+0xed
885dfa88 81829604 00000001 00000000 06f5e000 nt!KeFlushTb+0x11a
885dfaa4 818b6b19 818f3788 00000001 00000000 nt!KeFlushMultipleRangeTb+0x91
885dfc34 818b6483 84a6ab50 00000001 885dfc78 nt!MiAgeWorkingSet+0x3b5
885dfc90 818b0294 00000002 885dfcb0 00000001 nt!MiProcessWorkingSets+0x1c2
885dfcd8 818afe88 00000000 844acc38 00000000 nt!MmWorkingSetManager+0x3a3
885dfd7c 81a254a8 00000000 885d4680 00000000 nt!KeBalanceSetManager+0x12a
885dfdc0 8189145e 818afd5e 00000000 00000000 nt!PspSystemThreadStartup+0x9d
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16


STACK_COMMAND: kb

FOLLOWUP_IP:
nt!KeFlushTb+11a
818af0b1 f390 pause

SYMBOL_STACK_INDEX: 3

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

IMAGE_NAME: ntkrpamp.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 4549ae00

SYMBOL_NAME: nt!KeFlushTb+11a

FAILURE_BUCKET_ID: 0x101_nt!KeFlushTb+11a

BUCKET_ID: 0x101_nt!KeFlushTb+11a

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



DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

Does that mean there will be no way to fix this other than wait for microsoft, also does it mean that my hardware is ok :huh:

#6 usasma

usasma

    Still visually handicapped (avatar is memory developed by my Dad


  • BSOD Kernel Dump Expert
  • 25,090 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Southeastern CT, USA
  • Local time:02:39 AM

Posted 09 June 2007 - 01:29 PM

I would suspect it's either the WinAVI program either being corrupted or not compatible with Vista.
After that I'd start looking for Vista compatible drivers to fix this.

Nope, it doesn't mean the hardware's OK, although it's likely to be a driver problem. If pressed, I'd say it was 90% likely to be a driver and not hardware - but that's just a guess on my part. This is the first BugCheck 101 that I've ever seen.
My browser caused a flood of traffic, sio my IP address was banned. Hope to fix it soon. Will get back to posting as soon as Im able.

- John  (my website: http://www.carrona.org/ )**If you need a more detailed explanation, please ask for it. I have the Knack. **  If I haven't replied in 48 hours, please send me a message. My eye problems have recently increased and I'm having difficult reading posts. (23 Nov 2017)FYI - I am completely blind in the right eye and ~30% blind in the left eye.<p>If the eye problems get worse suddenly, I may not be able to respond.If that's the case and help is needed, please PM a staff member for assistance.

#7 fallout

fallout
  • Topic Starter

  • Members
  • 6 posts
  • OFFLINE
  •  
  • Local time:01:39 AM

Posted 09 June 2007 - 04:51 PM

All my drivers are installed correctly and are the latest versions so i dont know what more i can do extra on the driver side :S

I also dont think its a problem with winAvi since i've also tried using Xilisoft video converter and i get the same bsod.

However if i set the affinity of the process it seems to improve matters, it slows down any conversions but i get a bsod less often, also its a different bsod i'll try get details of it and post them next time the problem occurs.

cheers
Nearly Crazy
fallout

#8 fallout

fallout
  • Topic Starter

  • Members
  • 6 posts
  • OFFLINE
  •  
  • Local time:01:39 AM

Posted 09 June 2007 - 05:57 PM

Well i dont think this problem can be fixed is there any way to force vista to run on a single core?




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users