QUOTE(eclectice @ Oct 12 2008, 10:31 AM)
Hello, horcruxes.
I revisited your problem.
Microcode or microprogramming is like designing a "firmware" for microcontroller (MCU) or in this case, Intel CPU Pentium Prescott. There is a small size of programmable grid arrays (PGA) in Intel CPU Pentium Prescott. This "small" software (low-level coding), is emulating certain hardware functionality. Why Intel decided to create a microcode to emulate CPU hardware-level functionality is beyond my limited knowledge.
It seems that this microcode is unstable, maybe due to excessive heat which causing the memory area that stores this microcode to accidentally erase the microcode. That is why your crash reports keep showing zero-length CPU microcode bucket error. The memory area is quite volatile. Or, the way the user programs are using this microcode memory is triggering the crash.
The problem of instability occurs with Windows XP SP2.
I suggest you to update to Windows XP SP3 to alleviate the problem as I see you use Windows XP SP2 as evident in your crash reports.
Upgrading to SP3 for victims still persist problem. As i mentioned above refer to dump 101008-05 whereby he already installed to SP3 but error is on memory corruption. Victims RAM somehow is faulty and might need to be changed. Other than that will be the driver issue, with SP3. victims still using some of the driver that dated back to 2001 and 2004. This is somehow incompatible with the SP3 system.I revisited your problem.
Microcode or microprogramming is like designing a "firmware" for microcontroller (MCU) or in this case, Intel CPU Pentium Prescott. There is a small size of programmable grid arrays (PGA) in Intel CPU Pentium Prescott. This "small" software (low-level coding), is emulating certain hardware functionality. Why Intel decided to create a microcode to emulate CPU hardware-level functionality is beyond my limited knowledge.
It seems that this microcode is unstable, maybe due to excessive heat which causing the memory area that stores this microcode to accidentally erase the microcode. That is why your crash reports keep showing zero-length CPU microcode bucket error. The memory area is quite volatile. Or, the way the user programs are using this microcode memory is triggering the crash.
The problem of instability occurs with Windows XP SP2.
I suggest you to update to Windows XP SP3 to alleviate the problem as I see you use Windows XP SP2 as evident in your crash reports.
Added on October 12, 2008, 12:20 pm
QUOTE(doom89757 @ Oct 12 2008, 12:08 AM)
Well is ok, @ least there some one to help me to sort out the problem so i no need to reformat my pc
Ok here my event viewer
Hi there,Ok here my event viewer
You never mentioned to me that you have netlimiter2 installed in your system.
That is crucial for me to know as if i do not ask you, your problem will not solve.
Luckily your Event Viewer provide the information to me.
Refer below link for similar issue
http://www.techspot.com/vb/all/windows/t-2...BSOD-Crash.html
http://www.techspot.com/vb/showthread.php?...1684#post241684
http://www.techspot.com/vb/topic38458.html
Please uninstall NETLIMITER2 from your system.
Thanks
This post has been edited by francischuahcw: Oct 12 2008, 12:20 PM
Oct 12 2008, 12:11 PM

Quote


0.0217sec
0.53
6 queries
GZIP Disabled