re: BSOD, win32k.sys
Thursday, August 26, 2004 at 3:52 am
Windows XP Annoyances Discussion Forum
Posted by Paul
(5 messages posted)
As an update - I'm still finding problems with memdiag. Time to change the motherboard
- I know the memory is good.
Here's my specs - I wonder if it's a compatibility issue of the mb & memory:
Gigabyte 8KNXP P4 Titan motherboard (Intel 875P chipset) Revision 1.0
Intel Pentium 4 2.8GHZ CPU w/Hyperthreading
1GB Kingston HyperX memory (2x512MB)
XFX GeForce FX 5600 256MB video card
We'll see what happens....
Paul
On Saturday, August 21, 2004 at 9:36 am, Paul wrote:
>I know it's not anything installed - I have gone through at least 5-6 complete reinstalls
>(low-leveled) during the time I've experienced these random blue screens. I've
had
>pretty much every single BSOD on that has been mentioned here.
>
>I have a LOT of background with these kind of issues - I'm an MSCE with lots of
experience
>- and this is by far the hardest or worst problem I have ever come across (worse
>than many server problems!). I've put countless hours into this to come to these
>realizations:
>
>1. XP simply has a design flaw. I have had the problem with XP Gold, SP1, SP2.
>I'm sure other OS's would work ok, but like most of the other people on this board,
>it's too much trouble to switch OS's due to applications and compatibility with
other
>systems. Not to mention it's not extremely simple to just jump over to a whole
new
>platform.
>2. It could be a memory problem - I have a complete replacement of my Kingston HyperX
>memory - problem didn't go away. A while back I ordered another 1gb (512x2) and
>the system blue screened even faster. (I have 1gb now - at that time it was 2gb).
> I had less problems with one stick of my 1gb in at a time- but it still blue screened
>randomly (each stick!). Memdiag had shown errors, but ONLY when in DUAL CHANNEL.
> I take one out, run it for hours on end, no problems. I never got to the point
>where the failure was predictable. Hence, Kingston took back both modules - I would
>be hard-pressed to believe it's directly memory because I can duplicate the problem
>(randomly) on the new memory.
>
>3. It may be video-card related (most likely driver). It's not hard to point out
>that most of us have Nvidia chipsets - I'm to the point when I'm going to buy a
non-Nvidia
>card - but it still bugs me that even other cards may not fix the problem.
>
>4. I may be looking at a motherboard replacement - I would pick a different model
>for sure - but I want to do this as a last resort. From my findings it is a possibility,
>but hard to back up with evidence.
>
>We'll see what happens in time...
>
>Paul
>my specs: http://www.fxpcs.com/pc/
>
>
>
- Written in response to:
- re: BSOD, win32k.sys (Paul: Saturday, August 21, 2004 at 9:36 am)
Responses to this message:
|
|
All messages in this thread [show all]
 |  | | | | |  | Confused (Adri1456: Fri, May 14, 2004, 3:29 pm) |
| | | | | |  | Crash (greine12: Tue, Apr 6, 2004, 4:57 pm) |
| | | | | | | | | re: Crash (MadMan: Sat, Apr 10, 2004, 1:19 pm) |
| | | | | | | re: BSOD, win32k.sys (Paul: Thu, Aug 26, 2004, 3:52 am) |
| |
| |
| |
Return to the Windows XP Discussion Forum
|
|
