Jump to content
Strawberry Orange Banana Lime Leaf Slate Sky Blueberry Grape Watermelon Chocolate Marble
Strawberry Orange Banana Lime Leaf Slate Sky Blueberry Grape Watermelon Chocolate Marble

MSFN is made available via donations, subscriptions and advertising revenue. The use of ad-blocking software hurts the site. Please disable ad-blocking software or set an exception for MSFN. Alternatively, register and become a site sponsor/subscriber and ads will be disabled automatically. 


Sign in to follow this  
AnX

Has anyone ever experienced this under Win2k?

Recommended Posts

I was browsing the web, and came across an article which points to a flaw under Win2k that could cause it to BSOD with the 1E error "under a processor that is very fast or with a large L3 cache".
https://support.microsoft.com/en-us/kb/924439

So, I was wondering if anyone over here has actually experienced this anomaly with Win2k. I will admit that I got some KMODE_EXCEPTION_NOT_HANDLED errors on my FX-8320 when I tried to install an HPET driver, but without it, Win2k runs solid there.

Edited by AnX

Share this post


Link to post
Share on other sites

Hi.

I found these article.

http://www.hivmr.com/db/z9s91spc7pzm7xz1ss83fpdppdc9dmpm

http://h20564.www2.hpe.com/hpsc/doc/public/display?docId=emr_na-c01812788&lang=en-us&cc=us

Your PC has 8 core - 8MB L3 cache.

This case is 2 core - 16MB L3 cache.

Is there Crash Dump ?

How about changing /numproc  option on boot.ini ?

Is Your afd.sys version 5.0.2195.7204 ?

Edited by blackwingcat

Share this post


Link to post
Share on other sites

I checked afd.sys

  		call	[NTOSKRNL.EXE!KeWaitForSingleObject]
  		jmp	L000257E3
 L000257A2:
  		mov	ecx,C0000000h
  		and	eax,ecx
  		cmp	eax,ecx
  		jz 	L000257E3
  		lea	eax,[ebp-18h]
  		push	eax
  		call	[NTOSKRNL.EXE!KeReadStateEvent]
  		test	eax,eax
  		jnz	L000257E3
  		push	SSZ0002563C_________________________________
  		call	jmp_NTOSKRNL.EXE!DbgPrint
  		pop	ecx
  		push	ebx
  		push	SSZ00025670__AFD__IoCallDriver_returned_STAT
  		call	jmp_NTOSKRNL.EXE!DbgPrint
  		pop	ecx
  		pop	ecx
  		push	SSZ000256CC_________________________________
  		call	jmp_NTOSKRNL.EXE!DbgPrint
  		pop	ecx
  		call	jmp_NTOSKRNL.EXE!DbgBreakPoint
 L000257E3:
  		xor	eax,eax

v5.0.2195.6608

  		call	[ntoskrnl.exe!KeWaitForSingleObject]
  		jmp	L000250CE
 L00025092:
  		mov	ecx,C0000000h
  		and	eax,ecx
  		cmp	eax,ecx
  		jz 	L000250CE
  		lea	eax,[ebp-18h]
  		push	eax
  		call	[ntoskrnl.exe!KeReadStateEvent]
  		test	eax,eax
  		jnz	L000250CE
  		push	SSZ00024F2C_________________________________
  		call	jmp_ntoskrnl.exe!DbgPrint
  		pop	ecx
  		push	ebx
  		push	SSZ00024F60__AFD__IoCallDriver_returned_STAT
  		call	jmp_ntoskrnl.exe!DbgPrint
  		pop	ecx
  		pop	ecx
  		push	SSZ00024FBC_________________________________
  		call	jmp_ntoskrnl.exe!DbgPrint
  		pop	ecx
 L000250CE:
  		xor	eax,eax
 L000250D0:

v5.0.2195.7204

It seems to be fixed :3

  • Upvote 1

Share this post


Link to post
Share on other sites

Thanks for the heads up, BWC. It's really a shame how MS let Windows 2000 to die off. The fact that they claimed 2000 had an issue which was fixed just so they could sell more copies of server 2003 is downright misleading. Furthermore, I'm relived that Windows 2000 supports high cache CPUs, as I run it on an FX-8320 box because of my 26 year old compiler that hates modern OSes (and virtual machines). I would run XP, but XP simply produced issues of all sorts on that machine for whatever reason.

Also, I must clarify that the BSOD only happened while installing a sketchy HPET driver. My simple solution is to simply disable the device altogether, and Windows 2000 runs solid as a rock.

Additionally, my AFD.SYS is version 7204, the fixed version.

Edited by AnX

Share this post


Link to post
Share on other sites
On 2/1/2017 at 9:39 AM, AnX said:

Thanks for the heads up, BWC. It's really a shame how MS let Windows 2000 to die off. The fact that they claimed 2000 had an issue which was fixed just so they could sell more copies of server 2003 is downright misleading. Furthermore, I'm relived that Windows 2000 supports high cache CPUs, as I run it on an FX-8320 box because of my 26 year old compiler that hates modern OSes (and virtual machines). I would run XP, but XP simply produced issues of all sorts on that machine for whatever reason.

Also, I must clarify that the BSOD only happened while installing a sketchy HPET driver. My simple solution is to simply disable the device altogether, and Windows 2000 runs solid as a rock.

Additionally, my AFD.SYS is version 7204, the fixed version.

which issue have you faced on XP? I wish to know so that it can be fixed .

Share this post


Link to post
Share on other sites
14 minutes ago, Dibya said:

which issue have you faced on XP? I wish to know so that it can be fixed .

I have a feeling this would be more appropriate on the XP forum, but regardless, it had to do with it popping up some strange storage related errors. Even updating AHCI drivers did nothing. I'll install XP again as a secondary OS and see if I can get it working the next time around.

Share this post


Link to post
Share on other sites
22 hours ago, AnX said:

I have a feeling this would be more appropriate on the XP forum, but regardless, it had to do with it popping up some strange storage related errors. Even updating AHCI drivers did nothing. I'll install XP again as a secondary OS and see if I can get it working the next time around.

okay

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Sign in to follow this  

  • Recently Browsing   0 members

    No registered users viewing this page.

×
×
  • Create New...