Help My Mate!

Vandango · Post by **Vandango** » Fri Sep 21, 2007 9:52 am

Ok...
my mate who is sitting right next to me and while the teacher is boring me with his html shit

he built his comp 3 days ago it was working perfectly up until last night upon starting vista he gets a BSOD!!!! with this error

Code: Select all

a Clock intruppt was recivied on a secondary processor with in the allocated time interval

Tech-

*** stop 0x00000101 (0x 000000101 , 0x00000000 , 0x85A1D120, 0x00000001)

Now we have identified this as a hardware problem because vista does not load up he can start the BIOS but as soon as vista loads up he gets a BSOD!

Now this is oblivious its the processor because it cannot be the motherboard because he can load up the BIOS

Stats of his comp

AMD Athlon AM2 64x Duel Core
5600
5.6 Ghz Of Processing power
Nvida 8600 GT
2 gig of ram
Windows Vista (32bit Edition)

Little help would be Apprciated ^^

cin · Post by **cin** » Fri Sep 21, 2007 9:54 am

idk bro.. maybe a process not dual core compatible?

[SD]Master_Wong · Post by **[SD]Master_Wong** » Fri Sep 21, 2007 10:15 am

is the processor compatable with the motherboard might want to check that

Vandango · Post by **Vandango** » Fri Sep 21, 2007 10:18 am

cin wrote:idk bro.. maybe a process not dual core compatible?

its vista ¬_¬

@wong

Yes we do know were tech students doing software dev were not ur regular customer at PC World

of course we looked at that issue

StealMySoda · Post by **StealMySoda** » Fri Sep 21, 2007 10:36 am

Karlos Vandango wrote:
cin wrote:idk bro.. maybe a process not dual core compatible?

its vista ¬_¬

@wong

Yes we do know were tech students doing software dev were not ur regular customer at PC World

of course we looked at that issue

Sorry to say this Vandango, but hes just trying to help you.

Crumpets · Post by **Crumpets** » Fri Sep 21, 2007 10:43 am

That error 75% of the time has to do with incompaitble drivers for nvidia cards.

Can he boot in safe and re download and make sure 100% he had VISTA drivers. If not uhmm it could be voltage and or temp readings being displayed wrong. Ie. check if he actually has enough power to handle it all.

Also .. you said he made a new pc uhmm was he using the pc beforehand? If so ... I hope he did a fresh install of vista or xp or whatever, cause that could be 'triggering' the problems.

Innovacious · Post by **Innovacious** » Fri Sep 21, 2007 12:38 pm

StealMySoda wrote:
Karlos Vandango wrote:
cin wrote:idk bro.. maybe a process not dual core compatible?

its vista ¬_¬

@wong

Yes we do know were tech students doing software dev were not ur regular customer at PC World

of course we looked at that issue

Sorry to say this Vandango, but hes just trying to help you.

if you have ever had to call up a company for support and they treat you like your a moron and you know nothing then it is easy to get annoyed by people who give you answers you think are obvious.

Vandango · Post by **Vandango** » Fri Sep 21, 2007 12:41 pm

StealMySoda wrote:
Karlos Vandango wrote:
cin wrote:idk bro.. maybe a process not dual core compatible?

its vista ¬_¬

@wong

Yes we do know were tech students doing software dev were not ur regular customer at PC World

of course we looked at that issue

Sorry to say this Vandango, but hes just trying to help you.

sry fridays are so stressful for me ¬_¬

That error 75% of the time has to do with incompaitble drivers for nvidia cards.

Can he boot in safe and re download and make sure 100% he had VISTA drivers. If not uhmm it could be voltage and or temp readings being displayed wrong. Ie. check if he actually has enough power to handle it all.

Also .. you said he made a new pc uhmm was he using the pc beforehand? If so ... I hope he did a fresh install of vista or xp or whatever, cause that could be 'triggering' the problems.

no this is not a video card issue he cant even boot in safe mode
and i dont get the last part

Post by **dom** » Fri Sep 21, 2007 1:03 pm

The numbers are to make it easier for you to search for the problem, all you have to do is google: 0x00000101

The first answer on the list is:
http://msdn2.microsoft.com/en-us/library/aa469194.aspx

The problem is:
The specified processor is not processing interrupts. Typically, this occurs when the processor is nonresponsive or is deadlocked.

This is a problem with the processor.

Innovacious · Post by **Innovacious** » Fri Sep 21, 2007 1:07 pm

dom wrote:The numbers are to make it easier for you to search for the problem, all you have to do is google: 0x00000101

The first answer on the list is:
http://msdn2.microsoft.com/en-us/library/aa469194.aspx

The problem is:
The specified processor is not processing interrupts. Typically, this occurs when the processor is nonresponsive or is deadlocked.

This is a problem with the processor.

yeah, cus they didnt know that did they ¬_¬

they dont know how to reslove it

IceCrash · Post by **IceCrash** » Fri Sep 21, 2007 1:07 pm

dom wrote:The numbers are to make it easier for you to search for the problem, all you have to do is google: 0x00000101

The first answer on the list is:
http://msdn2.microsoft.com/en-us/library/aa469194.aspx

The problem is:
The specified processor is not processing interrupts. Typically, this occurs when the processor is nonresponsive or is deadlocked.

This is a problem with the processor.

Wow, very nice dom, that is actually gonna help me in futur problems!
Thanks, i guess that one part of the problem's done now

Innovacious wrote:
dom wrote:The numbers are to make it easier for you to search for the problem, all you have to do is google: 0x00000101

The first answer on the list is:
http://msdn2.microsoft.com/en-us/library/aa469194.aspx

The problem is:
The specified processor is not processing interrupts. Typically, this occurs when the processor is nonresponsive or is deadlocked.

This is a problem with the processor.

yeah, cus they didnt know that did they ¬_¬

they dont know how to reslove it

Oh...well, then why not go to a technical or whatever u call it forum and ask? >.>

Post by **dom** » Fri Sep 21, 2007 1:12 pm

Before anything, it would be best for you guys to test the processor in another motherboard, to assure yourselves that it isn't the processor that is faulty.

Afterwards, if it works, I would flash the bios and hope for the best. You might of WTFPWNED the processor with a bad power supply, or fried it by accident with wires hanging around, or you touching your case without de-static'ing.

Vandango · Post by **Vandango** » Fri Sep 21, 2007 4:25 pm

Proplem is
We dont have another motherboard compatible with the processor lol....

[SD]Master_Wong · Post by **[SD]Master_Wong** » Fri Sep 21, 2007 4:27 pm

another simple thing have you checked

the rig is plugged in right, power cable secure, processor slotted in right, no wires touching motherboard, bios plugged in securly

Snudge · Post by **Snudge** » Fri Sep 21, 2007 5:08 pm

I read "Help Me Mate!" rofl.

Post by **dom** » Fri Sep 21, 2007 6:19 pm

Karlos Vandango wrote:Proplem is
We dont have another motherboard compatible with the processor lol....

I would then return the processor and tell them it doesn't function properly: it's faulty. If the new one still doesn't work, it means that it's not the processor.

Defyance™ · Post by **Defyance™** » Fri Sep 21, 2007 6:39 pm

maybe he tried to overclock the processor and only did it on one core, so their interfearing with running processes

i think is fits the error discription

dE4 · Post by **dE4** » Fri Sep 21, 2007 10:17 pm

test both cores individually by disabling one in bios

-check 3.3v rail and core volts
-check temps
-try underclocking by lowering fsb not mp and/or cranking op vcore(me fav) ^^

when you get to windows bench each core for 6hours(24h preferred) straight and log volts and temps while doing so

if you dont make it past login screen then consider reinstalling, rebuilding hardware and running dos based benches for cpu, mem and graph card