Pentium 4 w/ HyperThreading w/Asrock P4VT8+ BSODs (solved)

for everything else

Pentium 4 w/ HyperThreading w/Asrock P4VT8+ BSODs (solved)

PostPosted by JH2k » Sat Jan 09, 2010 7:04 pm

Guys, for n-time I tried to cut the BSODs you already read to me lately and I came to an state I already were time ago, trying to find a microcode update or how to update or how to trash my f***** motherboard and/or, and/or...

And the fun subject to this topic comes because I found an updated update.sys file and when I had a look to the version I read... "(C) 2009 BlackWingCat" :lol: :lol: :lol: :lol: :lol: :lol: Oh my god, I know this guy... :lol:

Anyway, I'm going to give a try (after I write this), look if in the regitry and with the Intel CPUID utility the microcode gets updated and if this is the end of all the BSODs... Let's cross fingers. I'm going to fix some mess and make a registry backup first and I tell you in few minutes.

I also find this time (it's spectacular how you find new information time to time in the Internet) that latest Microsoft update.sys file for Windows 2000 doesn't include the latest Northwood updates... and maybe this update could help because I have one of the latest Northwoods out there.

By the way, tell me the url (as you blogs is in japanese) to get updated microcodes. The one I found stands as 5.0.2195.7155.


P.S.: I never know how to treat this topics, as offtopic or application fixes.
Last edited by JH2k on Sun Sep 26, 2010 4:02 pm, edited 9 times in total.
JH2k
 
Posts: 140
Joined: Sat Nov 29, 2008 9:23 pm

Re: BlackWingCat I'm going to kill you :P

PostPosted by OldBoy2k » Sat Jan 09, 2010 7:26 pm

JH2k wrote:I never know how to treat this topics, as offtopic or application fixes.


That mostly depends on the title description :lol:

good luck with your BSOD driver experiments and take care cauz we like to see ya back online, dude :P

BR
OldBoy2k
 
Posts: 1351
Joined: Fri Feb 15, 2008 5:10 pm

Re: Thanks BlackWingCat

PostPosted by JH2k » Sat Jan 09, 2010 7:33 pm

OldBoy2k wrote:
JH2k wrote:I never know how to treat this topics, as offtopic or application fixes.


That mostly depends on the title description :lol:

So, this is offtopic :lol:


Well, here I'm again and with good news. The registry shows that Windows got the microcode update and the Intel utility shows the version change too. From 17 to 2E, nothing to underestimate, I hope...

Let's see if in the upcoming days or ours because the BSODs are totally random (you can have in hours or even weeks), I stop having them. Let's cross fingers again then.

Oh, and thanks BlackWingCat... if this works, of course, if not, I will go to your home and... :twisted: :lol: well, and maybe I'd do a visit to Asrock first to place a bomb and kill them and their bad support.
Last edited by JH2k on Fri Jun 18, 2010 6:23 pm, edited 1 time in total.
JH2k
 
Posts: 140
Joined: Sat Nov 29, 2008 9:23 pm

Re: BlackWingCat I'm going to kill you :P

PostPosted by OldBoy2k » Sat Jan 09, 2010 7:40 pm

One last info.If you like you can go into advanced driver fixing with Dependency Walker.Just open the driver (*.sys extension) and check for its compatibility.This way you can sometimes figure out if the driver is compatible with win2k or not.

BR
OldBoy2k
 
Posts: 1351
Joined: Fri Feb 15, 2008 5:10 pm

Re: Thanks BlackWingCat

PostPosted by JH2k » Sat Jan 09, 2010 8:23 pm

If you tell that referring to the Audigy's topic, I thought it too few days after install it that I could do that. They don't bring problems with Dependency walker.

Yes, it's a nice tip :idea: for everyone with every software :)

But to tell the history in a short way, my problems are not extrictly related to drivers.

The problem comes in a strange way. If you install a non-HT (Hyper Threading) processor on this motherboard (Asrock P4VT8+), then zero problems. If you put an HT again, random BSODs. Those HT processors (I have 2, obtained in my path to "fix" my problem), with other motherboards/systems, don't bring problems. But my old, second hand, motherboard (ASUS P4C800) which fixed the issue died.

The BSODs had, mainly, two common things from the minidumps:
1) DEFAULT_BUCKET_ID: INTEL_CPU_MICROCODE_ZERO <------ there is where it comes the idea of the microcode update that I never was able to do, until today (let's see the upcoming days) along with some of the "BUCKET ID"s.

2) the last call of the STACK TEXT and, sometimes, the BUCKET ID that is nt!KiDispatchException+0x30e related to the IRQL 2 level (dispatch) and how the multi-processors manage threads.

And, all of this, in... over 5 five years. Of course not ever, because, before this, I decided several times to use my non-HT processor and I lived with that, but it is a 2.4Ghz and this one is 3.2Ghz... As a side note, all Northwood... but the non-HT didn't bring problems.

I hope you could understand all. My english sucks as the time passes.
Last edited by JH2k on Fri Jun 18, 2010 6:24 pm, edited 1 time in total.
JH2k
 
Posts: 140
Joined: Sat Nov 29, 2008 9:23 pm

Re: Thanks BlackWingCat

PostPosted by JH2k » Sat Jan 09, 2010 9:07 pm

For those who are bored, I offer my Minidumps for the year 2009: 125 from May.

Some are corrupted because the system got frozen while dumping.

http://www.megaupload.com/?d=JVUPVA1S
Last edited by JH2k on Fri Jun 18, 2010 6:24 pm, edited 1 time in total.
JH2k
 
Posts: 140
Joined: Sat Nov 29, 2008 9:23 pm

Re: Thanks BlackWingCat

PostPosted by JH2k » Fri Jan 15, 2010 3:13 pm

Just when I was thinking to dare to say "great, looks that the fix is working"... today or tomorrow (1 week "anniversary ") I just had a random BSOD :/

It's not bad that I've been six days without crashes, but not very special. It wouldn't be the first time that long space of time of "stability".

Now that seemed to be like the microcode update also added some better performance (and other things I was feeling)... crash! :( But I don't miss hope. I hope this is, at least, a decreasing probability of crashes. That would be "enough". I'll inform in the future to this topic if things get wrong or things get better or... who knows.

Anyway, thanks, BlackWingCat, to make this kind of updates for the Windows 2000 users around the world :)

For anyone that has an old BIOS update and needs an updated microcode, the pages I found in BlackWingCat's blog are these:
Version 3 update.sys:
http://blog.livedoor.jp/blackwingcat/ar ... 68694.html
Version 4 update.sys:
http://blog.livedoor.jp/blackwingcat/ar ... 72749.html
Last edited by JH2k on Fri Jun 18, 2010 6:25 pm, edited 1 time in total.
JH2k
 
Posts: 140
Joined: Sat Nov 29, 2008 9:23 pm

Testings log 10-02-06

PostPosted by JH2k » Sat Feb 06, 2010 5:18 pm

I hope I don't bother with my problems ;)

Well, I was continuing with testings, now applying the Rollup hotfix and all started to look nice, 3 and a half days without hangs and without rebooting... Incredible... Two BSODs in 10 days, and one of them of a known friend (Kerio 2.1.5 sometimes gets dumb with multiprocessors), yay!.


But... suddenly, I decided to install "Dead Space" yesterday, I uninstalled because I found I didn't like at all and I don't know what the hell came with this game, what messed up in the system but I started to have weird things such as the keyboard not responding as it should :S

Damn! I didn't have a registry backup before install it and with the Rollup :roll: . So I had to uninstall the Rollup before restore System registry portion to avoid more mess and it didn't fix. The affected portion of the registry config was in ntuser.dat (I should check that in other users all was working fine first). Anyway, I had to go back ten days in registry configs on ntuser.dat and System, apply again the Rollup and... god, I hope that the OS current status is as the last 10 days of stability...

I don't know what crap left "Dead Space" on the system (on user config, to be exact), but be aware of it :S When I was installing it I though that I should make a registry backup :/, but, what harm could come from a game? Never happened something like this. Damn it!
JH2k
 
Posts: 140
Joined: Sat Nov 29, 2008 9:23 pm

Re: Thanks BlackWingCat (it was: I'm going to kill you :P)

PostPosted by OldBoy2k » Sat Feb 06, 2010 7:09 pm

Check if theres a Xinput1_3.dll and some of the XP X3Daudio files installed/replaced in your system root directory.Had similar mouse behaviour with Risen Demo before.

Rollup is a pain and i don't trust it at all.Did you installed the update rollup 1 v2 which got released 3 month later?

BR
OldBoy2k
 
Posts: 1351
Joined: Fri Feb 15, 2008 5:10 pm

Re: Thanks BlackWingCat

PostPosted by JH2k » Sat Feb 06, 2010 7:17 pm

No, all is ok but a good tip.

Next time I'll try to re-run the bat to register dlls.

But I think that the dlls (any library, indeed) aren't registered under current_user, and that is the way it got fixed... :-?

Rollup is a pain and i don't trust it at all.Did you installed the update rollup 1 v2 which got released 3 month later?


I know, I don't trust it either, but I'm just testing and it looks more stable now, with the company of the updated microcode. I have the v2.
Windows2000-KB891861-v2-x86(lang).exe
Last edited by JH2k on Fri Jun 18, 2010 6:26 pm, edited 1 time in total.
JH2k
 
Posts: 140
Joined: Sat Nov 29, 2008 9:23 pm

Re: Thanks BlackWingCat

PostPosted by JH2k » Wed Feb 24, 2010 7:17 pm

Well, looks that the combination of the Microcode update and the Rollup ended with the randomness of the BSODs and a little of the frequency of them.

Now (forgetting Kerio ones, which are one each 2 months or so), I'm having BSODs localized on HIDCLASS!HidpIrpMajorClose routine. One, two each week. But, even if the Rollup is not helping on this, as with the microcode looks that it was the only one left, looks that helps to decrease the amount of BSODs.

Testing if removing the gamepad from game devices, as even disconnected is on the Devices Manager as a HID device, stop crashes.

I'm feeling I'm near of, if not getting rid of all crashes, reduce them to the minimal expression.
Last edited by JH2k on Fri Jun 18, 2010 6:27 pm, edited 1 time in total.
JH2k
 
Posts: 140
Joined: Sat Nov 29, 2008 9:23 pm

Re: Thanks BlackWingCat (it was: I'm going to kill you :P)

PostPosted by BlackWingCat » Thu Feb 25, 2010 1:53 am

Hi.

I think this problem only comes from CPU over heat, not related with micro code update.
Because Microsoft update.sys does not need and not load if your BIOS includes microcode fix.

Did you apply following registry fix ?
http://support.microsoft.com/kb/835730/
http://support.microsoft.com/kb/919521/

It occurs when you apply windows 2000 SP4 security rollup package1 v2 and you use HTT or Dual Core cpu .
BlackWingCat
 
Posts: 75
Joined: Sat Mar 07, 2009 7:20 am
Location: Kanagawa, Japan

Re: Thanks BlackWingCat

PostPosted by JH2k » Thu Feb 25, 2010 4:39 am

BlackWingCat wrote:Hi.
[...]
Because Microsoft update.sys does not need and not load if your BIOS includes microcode fix.

That's the thing. The BIOS microcode is quite old and Asrock didn't update anymore. I requested it and they didn't reply. Well, they replied me, but their reply was "no, no, the motherboard supports your processor"... until now, that the current situation give me the reason.

Believe me that after install your update.sys I stopped having several random BSODs, from ntsokrnl, win32k.sys, memory corruptioms, virtual memory and hardware (no process) to what I have now, localized all to the one I told in the last message.

Before you reply, no, I tested the memory more than anyone on the internet saying it has used Memtest or any other tool. My memory is perfectly. It's a relation between the motherboard and the processor. You can read a brief in my other message on this thread

BlackWingCat wrote:Did you apply following registry fix ?
http://support.microsoft.com/kb/835730/

I already have hal.dll versions over the hotfix one by the rollup, indeed. (Internal name halmacpi.dll)

BlackWingCat wrote:http://support.microsoft.com/kb/919521/

It occurs when you apply windows 2000 SP4 security rollup package1 v2 and you use HTT or Dual Core cpu .

BlackWingCat wrote:I think this problem only comes from CPU over heat, not related with micro code update.

I know, it's not the first time I use the rollup. I installed and uninstalled several times across the years while I was using this motherboard trying to fix with the updates inside it.


It's the first thing I did the first time I tried the rollup. My CPU, even playing in summer has a temperature, as much, of 52-55ºC. So I run to find the fix almost instantly.
Last edited by JH2k on Fri Jun 18, 2010 6:27 pm, edited 1 time in total.
JH2k
 
Posts: 140
Joined: Sat Nov 29, 2008 9:23 pm

Re: Thanks BlackWingCat (it was: I'm going to kill you :P)

PostPosted by BlackWingCat » Thu Feb 25, 2010 8:08 am

JH2k wrote:
BlackWingCat wrote:Did you apply following registry fix ?
http://support.microsoft.com/kb/835730/
http://support.microsoft.com/kb/919521/
It occurs when you apply windows 2000 SP4 security rollup package1 v2 and you use HTT or Dual Core cpu .


I think this problem only comes from CPU over heat, not related with micro code update.
already have hal.dll versions over the hotfix one by the rollup, indeed. (Internal name halmacpi.dll)

I know, it's not the first time I use the rollup. I installed and uninstalled several times across the years while I was using this motherboard trying to fix with the updates inside it.


It's wrong.
The hot fix can't resolve this problem.
It raises by SP4 Rollup.
If you want resolve CPU Heating problem, you must create reg file and apply it.
My mother board which has'nt applied the registry fix broke down just 14 monthes. :(

JH2k wrote:Believe me that after install your update.sys I stopped having several random BSODs, from ntsokrnl, win32k.sys, memory corruptioms, virtual memory and hardware (no process) to what I have now, localized all to the one I told in the last message.


if BSoD cause from update.sys, Recover your system since you delete update.sys or overwrite win2000 native one.

CPU has native micro code and use it, if there is no patch.
At first CPU loaded from BIOS to NV-RAM(CPU volatile memory), if it find same cpu id micro code.
Windows loads Update.sys and overwrite CPU NV-RAM, if exists update.sys and find same cpuid.

Of course If you tell me your CPU ID, I can research it.
BlackWingCat
 
Posts: 75
Joined: Sat Mar 07, 2009 7:20 am
Location: Kanagawa, Japan

Re: Thanks BlackWingCat (it was: I'm going to kill you :P)

PostPosted by OldBoy2k » Thu Feb 25, 2010 9:06 am

BlackWingCat wrote:[The hot fix can't resolve this problem.
It raises by SP4 Rollup.
If you want resolve CPU Heating problem, you must create reg file and apply it.
My mother board which has'nt applied the registry fix broke down just 14 monthes. :(


What kind of reg file/registry fix?

greetings
OldBoy2k
 
Posts: 1351
Joined: Fri Feb 15, 2008 5:10 pm

Next

Return to Offtopic

Who is online

Users browsing this forum: No registered users and 1 guest

cron