Annoyances.org
Home » Windows XP Discussion Forum » Message 1080082832 Search | Help | Home
  
Tip: Run a free scan for common Windows errors ad

re: My solution... A FIX THAT WORKED FOR ME!
Tuesday, March 23, 2004 at 3:00 pm
Windows XP Annoyances Discussion Forum
Posted by Nick (1 messages posted)


I have valuable information but not a solution, however this may help someone (maybe an Asus firmware guy if he's reading this) fix the problem. Because I see so many similar responses, I think this may have to do with the A7N8X Deluxe memory bus architecture and the type of RAM that you use. I too use the A7N8X Deluxe (PCB ver. 1.04), flashed to the latest BIOS (released in October 2003) and have had the same type of problem. I do not get blue screens, however I will get reboots. Like many others, I get the reboots whenever I have my memory timings set to the most aggressive yet acceptable (or so we think) speeds. I have one stick of Kingston [Samsung] 512MB PC2700 memory in the isolated black DIMM slot and two sticks of Kingston [Hynix] 256MB PC2700 memory in the paired blue/black slots. Reboots seem to occur when I am seeking through a Windows Media video file or large AVI file, or when I'm playing a game like Unreal Tournament 2004, when it starts to swap different map data into memory when I'm moving. It resets as soon as it buffers. One time it just reset while I was standing in the same place shooting my gun, which I still do not understand. Setting timings to optimal seemed to fix this problem, but then again, it still has happened a couple times -- but it is more of a rare thing now. With aggressive timings it would happen almost every time I played or seeked through a video. This is where things get a bit confusing so bear with me... I have not been able to determine if this problem is with a. the isolated black DIMM slot, b. certain kinds of memory in the isolated black DIMM slot or c. the isolated black DIMM slot altogether. Prior to upgrading to a gig of memory, all I had was my Kingston [Samsung] 512MB PC2700 DIMM. It was NOT in the isolated slot, but in one of the paired slots (I'm pretty sure it was the blue one). I was able to run that stick with the most aggressive memory timings without _any_ instability whatsoever. It never reset on me, not once. When I ordered my two 256MB DIMMs, I moved my 512MB DIMM to the isolated black slot. As soon as I did that, the instability occured. Keep in mind that this was still before the memory I had ordered arrived, so I was still using just one 512MB DIMM. This could mean that the slot itself will only work best with certain types of memory, Samsung made for Kingston being one of them. I highly doubt this however, because if you go to the official spec sheet for the A7N8X Deluxe at Asus's website, Samsung is one of their suggested memory module manufacturers! So, this could also mean that the memory bus architecture for most A7N8X Deluxe boards are just not reliable, period. I will say that when the two 256MB Kingston [Hynix] DIMMs arrived, and I put them in the paired slots, performance (on aggressive) was more stable, and things are now less likely to reboot with these timings, but it STILL happens regardless. The only thing that fixes it almost completely is by changing your timings from aggressive to optimal. Rarely do I get a reboot, and I'm sure this has something to do with my Radeon video driver (let's hope so anyway). Although, you never know, it could be my memory. I should try removing my 512MB DIMM and just let the two 256MB DIMMs run by themselves (in the stable paired slots) and see if I get another reboot on aggressive. If I don't, then I know it HAS to be either the isolated black DIMM slot or my Kingston [Samsung] DIMM being incompatible... but why would Asus suggest Samsung if that was the case? Especially if it is mentioned specifically for my board. By the way, I have also run memtest86 and it found no errors. Hope this helps, Nick


Written in response to:
re: My solution... A FIX THAT WORKED FOR ME! (nags: Saturday, March 20, 2004 at 9:01 pm)

There are presently no replies to this message.

All messages in this thread [show all]
-BSOD, win32k.sys (ed: Fri, Sep 6, 2002, 5:38 am)
-re: BSOD, win32k.sys (Gavin: Sun, Jan 5, 2003, 1:37 pm)
-re: BSOD, win32k.sys (Jeff: Mon, Jan 6, 2003, 8:55 pm)
-re: BSOD, win32k.sys (Andrew Cartine: Mon, Jan 13, 2003, 5:02 pm)
-re: BSOD, win32k.sys (Olivier Hubert: Tue, Jan 14, 2003, 8:50 pm)
-re: BSOD, win32k.sys (sac: Thu, Jan 16, 2003, 5:47 pm)
-re: BSOD, win32k.sys (ryan: Sun, Jan 19, 2003, 11:58 am)
-re: BSOD, win32k.sys (Jim: Mon, Jan 20, 2003, 5:36 pm)
-re: BSOD, win32k.sys (Olivier Hubert: Mon, Jan 20, 2003, 9:47 pm)
*re: BSOD, win32k.sys (NH: Tue, Jan 21, 2003, 7:13 am)
*re: BSOD, win32k.sys (loco: Wed, Jan 22, 2003, 3:35 pm)
-re: BSOD, win32k.sys (SkullFace: Mon, Jul 21, 2003, 7:23 pm)
*re: BSOD, win32k.sys (Guy: Sat, Feb 7, 2004, 4:02 pm)
*re: BSOD, win32k.sys (goliathdrakken: Fri, Sep 5, 2003, 11:00 pm)
*re: BSOD, win32k.sys (yann: Fri, Oct 10, 2003, 6:24 am)
*Solution!!!!!!!!!!!!!!!!!!! (Marcus: Wed, Mar 31, 2004, 3:07 pm)
-re: BSOD, win32k.sys (Richard: Tue, Aug 17, 2004, 3:35 pm)
*re: BSOD, win32k.sys (ME?: Fri, Aug 20, 2004, 2:48 pm)
-re: BSOD, win32k.sys (keith blake: Sat, May 14, 2005, 5:34 pm)
*re: BSOD, win32k.sys (me: Mon, May 16, 2005, 5:06 pm)
*re: BSOD, win32k.sys (Jeffrey K: Sun, Nov 20, 2005, 12:56 pm)
*re: BSOD, win32k.sys (MadMonkee: Tue, Jun 24, 2003, 10:33 pm)
-re: BSOD, win32k.sys (Louis Klampfer: Tue, Feb 21, 2006, 4:23 am)
-re: BSOD, win32k.sys (Vlad: Wed, Apr 5, 2006, 7:08 am)
-re: BSOD, win32k.sys (jtomlin: Mon, Apr 17, 2006, 5:40 am)
-re: BSOD, win32k.sys (yiren: Sat, Apr 22, 2006, 3:42 pm)
*re: BSOD, win32k.sys (Dave: Sun, Apr 23, 2006, 9:19 pm)
*re: BSOD, win32k.sys (Brian: Fri, Nov 2, 2007, 4:05 pm)
*re: BSOD, win32k.sys (john: Fri, Jan 2, 2009, 3:55 pm)
-re: BSOD, win32k.sys (Pete: Sun, Jun 1, 2003, 6:57 am)
*re: BSOD, win32k.sys (ryan: Mon, Jun 2, 2003, 5:31 pm)
-re: BSOD, win32k.sys (Dave: Mon, Aug 18, 2008, 7:40 am)
-re: BSOD, win32k.sys (Xeno1: Fri, Aug 29, 2008, 1:10 am)
-re: BSOD, win32k.sys, at the end of my chain (Yourmicrowhat: Sun, Aug 31, 2008, 11:23 pm)
-re: BSOD, win32k.sys, at the end of my chain (Xeno1: Mon, Sep 1, 2008, 11:49 am)
-re: BSOD, win32k.sys, at the end of my chain (Yourmicrowhat: Tue, Sep 2, 2008, 8:00 pm)
-re: BSOD, win32k.sys, at the end of my chain (Xeno1: Tue, Sep 2, 2008, 8:29 pm)
-re: BSOD, win32k.sys, at the end of my chain (Yourmicrowhat: Wed, Sep 3, 2008, 11:15 am)
*re: BSOD, win32k.sys, at the end of my chain (Yourmicrowhat: Thu, Sep 4, 2008, 1:14 pm)
*re: BSOD, win32k.sys, at the end of my chain (Jill Heayn: Sun, Sep 7, 2008, 10:50 am)
-re: BSOD, win32k.sys (Cynthia: Thu, Jan 24, 2008, 3:22 pm)
-re: BSOD, win32k.sys (Joe: Sat, Feb 9, 2008, 2:41 pm)
-BSOD, win32k.sys (Dan: Thu, Jun 12, 2008, 3:58 pm)
-re: BSOD, win32k.sys (samreay: Wed, Jul 30, 2008, 3:47 am)
*re: BSOD, win32k.sys (Dan: Wed, Jul 30, 2008, 7:41 pm)
*re: BSOD, win32k.sys (Vectronx: Sun, Aug 10, 2003, 1:22 pm)
*re: BSOD, win32k.sys (Ian Roberts: Wed, Jan 28, 2004, 1:19 pm)
-re: BSOD, win32k.sys (Tom McLaughlin: Wed, Aug 10, 2005, 11:32 am)
-re: BSOD, win32k.sys (Kev: Wed, Aug 10, 2005, 2:43 pm)
*re: BSOD, win32k.sys (Tom McLaughlin: Thu, Aug 11, 2005, 10:13 pm)
*re: BSOD, win32k.sys (blazewing: Mon, Sep 28, 2009, 1:27 am)
-re: BSOD, win32k.sys (Craig: Mon, Jun 2, 2003, 9:25 pm)
-re: BSOD, win32k.sys (Jim: Fri, Aug 8, 2003, 1:12 pm)
*re: BSOD, win32k.sys (Roger Labonté: Tue, Dec 23, 2003, 1:57 pm)
*re: BSOD, win32k.sys (neu12rie: Wed, Jul 9, 2003, 5:35 pm)
*re: BSOD, win32k.sys (Tom: Sat, Jul 24, 2004, 7:02 pm)
*re: BSOD, win32k.sys (heikki: Mon, Jul 7, 2003, 5:42 am)
-re: BSOD, win32k.sys (will: Sun, Apr 18, 2004, 3:06 am)
*BSOD & multiple_irp_complete_requests (mic4559: Sun, Apr 18, 2004, 10:32 pm)
-re: BSOD, win32k.sys (Mike: Thu, May 13, 2004, 9:59 am)
-re: BSOD, win32k.sys (joyce: Thu, May 13, 2004, 10:40 am)
-re: BSOD, win32k.sys (Mike: Thu, May 13, 2004, 10:52 pm)
*Confused (Adri1456: Fri, May 14, 2004, 3:29 pm)
-re: Yes but anyone got a solution? (sigh) (darren: Sun, May 4, 2003, 7:59 am)
-re: Yes but anyone got a solution? (sigh) (Prince_Saiyan: Mon, May 19, 2003, 2:33 pm)
-re: Yep, I have a solution for me!! (Nick: Wed, May 21, 2003, 6:44 am)
-still need help (Gary: Tue, May 27, 2003, 12:36 pm)
-re: still need help (chris: Tue, May 27, 2003, 10:22 pm)
*re: still need help (Neil Cook: Mon, Jul 21, 2003, 2:26 am)
-re: still need help (derek: Wed, May 28, 2003, 10:26 am)
-re: still need help (Ben Earhart: Tue, Jun 3, 2003, 6:12 pm)
*re: still need help (Ben Earhart: Sun, Jun 8, 2003, 12:50 am)
*re: still need help (Dan Bemowski: Fri, Dec 23, 2011, 9:46 am)
*re: still need help (Gary: Tue, Jun 10, 2003, 5:14 pm)
-re: still need help (Jux: Mon, Apr 18, 2005, 8:53 pm)
-re: still need help (Tyrian: Tue, Apr 19, 2005, 5:58 am)
-win32k.sys but different (zerovich: Fri, Apr 22, 2005, 7:28 am)
-re: win32k.sys but different (Tyrian: Fri, Apr 22, 2005, 1:42 pm)
*re: win32k.sys but different (zerovich: Sat, Apr 23, 2005, 5:13 am)
-re: Yes but anyone got a solution? (sigh) (aleXlee: Mon, Jun 2, 2003, 7:02 am)
-I think this is a northbridge overheating problem (jetface: Tue, Jun 3, 2003, 6:59 am)
-re: I think this is a northbridge overheating problem (manus: Tue, Jun 3, 2003, 2:27 pm)
-re: I think this is a northbridge overheating problem (jetface: Wed, Jun 4, 2003, 6:41 am)
-re: I think this is a northbridge overheating problem (Kevin Torvalds: Wed, Nov 23, 2005, 5:48 pm)
-No more bluescreens (Harry Stottle: Sat, Dec 3, 2005, 5:12 pm)
-re: No more bluescreens (Jim: Fri, Feb 10, 2006, 6:36 am)
*BSOD, win32k.sys, clogged fan and bad memory (Ed: Sat, Feb 11, 2006, 8:27 am)
*512 DDR Kingston Ram, ASUS A7V600 Motherboard and Winfast A340 TD (Justin: Sat, Oct 11, 2003, 9:02 pm)
-re: Yes but anyone got a solution? (sigh) (Dialmedia: Fri, Aug 1, 2003, 4:05 am)
*re: Yes but anyone got a solution? (sigh) (Jim: Fri, Aug 8, 2003, 1:18 pm)
-BSOD win32k.sys among others (Paul: Tue, Sep 9, 2008, 7:03 am)
*re: BSOD win32k.sys among others (Chris Robertson: Mon, Nov 24, 2008, 10:22 am)
-re: BSOD, win32k.sys (Moises: Fri, May 30, 2003, 1:48 am)
-re: BSOD, win32k.sys (Subz: Mon, Jun 16, 2003, 3:40 am)
-re: BSOD, win32k.sys (Subz: Tue, Jun 17, 2003, 2:17 am)
*re: BSOD, win32k.sys (Ky: Mon, Jun 23, 2003, 11:00 pm)
*re: BSOD, win32k.sys (Miss Shamen: Sat, Sep 13, 2003, 4:49 pm)
-re: BSOD, win32k.sys (Jim: Thu, Mar 12, 2009, 9:48 pm)
*re: BSOD, win32k.sys (jaakske: Sun, Mar 22, 2009, 9:25 am)
-re: BSOD, win32k.sys (gibby: Fri, May 1, 2009, 2:38 pm)
-re: BSOD, win32k.sys (TimMoore: Tue, Nov 17, 2009, 8:21 pm)
-re: BSOD, win32k.sys (MartinM: Tue, Nov 17, 2009, 10:17 pm)
*re: BSOD, win32k.sys (igor: Mon, Aug 8, 2011, 12:56 pm)
*re: BSOD, win32k.sys (Skud: Thu, Jun 26, 2003, 9:01 am)
-re: BSOD, win32k.sys (David R: Tue, Jul 1, 2003, 7:36 pm)
-re: BSOD, win32k.sys (Crickey: Sun, Jul 27, 2003, 4:50 pm)
*re: BSOD, win32k.sys (Dialmedia: Fri, Aug 1, 2003, 4:26 am)
*re: BSOD, win32k.sys (kdog: Sun, Jan 4, 2009, 7:07 am)
*re: BSOD, win32k.sys (Inhops: Thu, Jul 3, 2003, 9:48 pm)
-No more BSOD, win32k.sys (Dominique: Thu, Jul 10, 2003, 8:52 am)
-re: No more BSOD, win32k.sys (Bryan: Thu, Jul 10, 2003, 10:02 pm)
-re: No more BSOD, win32k.sys (Tony: Wed, Jul 23, 2003, 6:37 am)
-re: BSOD, win32k.sys (Billy: Wed, Aug 6, 2003, 6:56 pm)
*re: BSOD, win32k.sys (Digitair: Tue, Aug 12, 2003, 7:24 am)
-re: BSOD, win32k.sys (Walt D in LV: Wed, Aug 13, 2003, 6:59 pm)
-re: BSOD, win32k.sys (Matt: Thu, Sep 4, 2003, 8:30 am)
-re: BSOD, win32k.sys (Danny: Sat, Sep 13, 2003, 5:35 am)
-re: BSOD, win32k.sys (Steven Z: Mon, Sep 15, 2003, 7:19 pm)
-re: BSOD, win32k.sys (Wizlil: Tue, Sep 16, 2003, 10:11 pm)
-re: BSOD, win32k.sys (Davis: Wed, Sep 17, 2003, 12:21 pm)
*re: BSOD, win32k.sys (Wizlil: Wed, Sep 17, 2003, 3:31 pm)
*re: BSOD, win32k.sys (Lexy: Sun, Sep 21, 2003, 11:54 am)
-re: BSOD, win32k.sys (Steven Z: Tue, Sep 30, 2003, 2:32 pm)
-re: BSOD, win32k.sys (Ryan Ruckel: Fri, Oct 3, 2003, 5:24 am)
-re: BSOD, win32k.sys (Steven Z: Fri, Oct 3, 2003, 12:40 pm)
*re: BSOD, win32k.sys (Ryan Ruckel: Sat, Oct 4, 2003, 7:44 am)
*re: BSOD, win32k.sys (jose: Sun, Oct 5, 2003, 12:53 am)
-re: BSOD, win32k.sys (Larry: Sun, Oct 5, 2003, 7:58 pm)
-re: BSOD, win32k.sys (Murray: Wed, Oct 8, 2003, 1:13 pm)
-re: BSOD, win32k.sys (Clark: Sun, Jan 18, 2004, 9:14 am)
*re: BSOD, win32k.sys (daniel: Sat, Jan 31, 2004, 9:19 am)
-Q827663 - Random ''0x0000008E'' Error Message on a Blue Screen in Windows XP - Solution (Bashar Hamdan: Sun, Oct 12, 2003, 9:08 pm)
-re: Q827663 - Random ''0x0000008E'' Error Message on a Blue Screen in Windows XP - Solution (Steven Z: Wed, Oct 22, 2003, 12:29 pm)
-re: Q827663 - Random ''0x0000008E'' Error Message on a Blue Screen in Windows XP - Solution (Masterofe55: Sat, Nov 1, 2003, 9:43 am)
*re: Q827663 - Random ''0x0000008E'' Error Message on a Blue Screen in Windows XP - Solution (Steven Z: Wed, Nov 12, 2003, 9:25 pm)
-re: Q827663 - Random ''0x0000008E'' Error Message on a Blue Screen in Windows XP - Solution (Tracy S Gosdis: Thu, Dec 4, 2003, 7:32 am)
-re: Q827663 - Random ''0x0000008E'' Error Message on a Blue Screen in Windows XP - Solution (Mikey G: Mon, Feb 2, 2004, 11:26 am)
-re: Q827663 - Random ''0x0000008E'' Error Message on a Blue Screen in Windows XP - Solution (Andrew Salvona: Sat, Feb 7, 2004, 4:33 am)
*re: Q827663 - Random ''0x0000008E'' Error Message on a Blue Screen in Windows XP - Solution (Richard Shepherd: Mon, Feb 16, 2004, 2:33 pm)
*Q827663 - Random ''0x0000008E'' Error Message on a Blue Screen in Windows XP - Microsoft Solution (Phyto: Tue, Feb 17, 2004, 4:50 am)
-My solution... (NightCrawler: Tue, Feb 17, 2004, 8:07 am)
-re: My solution... (CraigR: Wed, Feb 25, 2004, 3:30 am)
-re: My solution... A FIX THAT WORKED FOR ME! (Peter Smith: Fri, Feb 27, 2004, 5:36 am)
-re: My solution... A FIX THAT WORKED FOR ME! (nags: Fri, Feb 27, 2004, 11:35 am)
-re: My solution... A FIX THAT WORKED FOR ME! (NightCrawler: Fri, Feb 27, 2004, 11:56 am)
-re: My solution... A FIX THAT WORKED FOR ME! (nags: Fri, Feb 27, 2004, 2:17 pm)
-re: My solution... A FIX THAT WORKED FOR ME! (Ryan Lynn: Fri, Feb 27, 2004, 5:42 pm)
*re: My solution... A FIX THAT WORKED FOR ME! (BeBe: Sat, Feb 28, 2004, 4:04 pm)
-re: My solution... A FIX THAT WORKED FOR ME! (nags: Sat, Mar 20, 2004, 9:01 pm)
*re: My solution... A FIX THAT WORKED FOR ME! (Nick: Tue, Mar 23, 2004, 3:00 pm)
*re: My solution... A FIX THAT WORKED FOR ME! (Peter Smith: Mon, Mar 1, 2004, 3:17 pm)
-re: My solution... A FIX THAT WORKED FOR ME! (nags: Sat, Mar 20, 2004, 9:00 pm)
-re: My solution... A FIX THAT WORKED FOR ME! (Si Gross: Fri, Mar 26, 2004, 3:56 am)
-re: My solution... A FIX THAT WORKED FOR ME! (nags: Fri, Mar 26, 2004, 9:00 am)
-re: My solution... A FIX THAT WORKED FOR ME! (Si Gross: Fri, Mar 26, 2004, 9:13 am)
*re: My solution... A FIX THAT WORKED FOR ME! (nags: Fri, Mar 26, 2004, 9:26 am)
-re: My solution... (Lisa: Sun, Feb 29, 2004, 6:17 am)
-re: My solution... (mrsnrub: Mon, Mar 1, 2004, 9:04 pm)
*Another case (Tom Gleadall: Mon, Mar 8, 2004, 4:34 pm)
-re: BSOD, win32k.sys - Might be unfixable (dean: Thu, Mar 11, 2004, 8:32 am)
-re: BSOD, win32k.sys - Might be unfixable (BradleyT: Sat, Mar 20, 2004, 12:36 am)
-re: BSOD, win32k.sys - FIX Access?? (peter: Tue, Mar 30, 2004, 4:56 am)
-No crashes in a few days!!! (Kirstu: Thu, Apr 1, 2004, 10:20 am)
*Solution!!!!!!! (cesar: Fri, Apr 2, 2004, 5:49 am)
-re: No crashes in a few days!!! (Johann: Fri, Apr 2, 2004, 6:07 am)
-Crash (greine12: Tue, Apr 6, 2004, 4:57 pm)
-re: Crash (Tomz: Wed, Apr 7, 2004, 1:38 pm)
-re: Crash (MadMan: Sat, Apr 10, 2004, 1:19 pm)
-No Crashes for Weeks (Tom Gleadall: Sun, Apr 11, 2004, 3:00 am)
*re: No Crashes for Weeks (BOW: Wed, Apr 14, 2004, 11:32 pm)
*re: No Crashes for Weeks (Tony: Thu, Apr 15, 2004, 8:21 am)
-re: No Crashes for Weeks (Tom Gleadall: Fri, Apr 30, 2004, 6:31 am)
*re: No Crashes for Weeks (gibsonus: Fri, Apr 30, 2004, 7:35 pm)
*re: BSOD, win32k.sys - Might be unfixable (Will: Thu, Apr 15, 2004, 9:50 pm)
*re: BSOD, win32k.sys (Mike: Mon, Apr 26, 2004, 4:33 am)
-re: BSOD, win32k.sys (Mike: Sun, May 16, 2004, 5:36 pm)
*re: BSOD, win32k.sys (joyce: Mon, May 17, 2004, 5:36 am)
-what worked for me :) (Dead.Guy: Tue, May 18, 2004, 11:49 am)
-Haven´t had them before... (SiN: Wed, May 19, 2004, 9:51 am)
-re: Haven´t had them before... (R3ckl3ss: Tue, May 25, 2004, 9:37 pm)
*re: Haven´t had them before... (gonzie: Sun, May 30, 2004, 5:03 pm)
-re: BSOD, win32k.sys (Rmiller: Tue, Jun 1, 2004, 12:46 pm)
-re: BSOD, win32k.sys (larry: Wed, Jun 2, 2004, 4:45 pm)
-re: BSOD, win32k.sys (Luke: Sun, Jun 6, 2004, 5:23 pm)
*Dual Channel Memory (RdpC: Tue, Jun 8, 2004, 11:37 am)
*re: BSOD, win32k.sys (steve: Tue, Jun 8, 2004, 12:56 pm)
-re: BSOD, win32k.sys (peter shi: Sun, Jun 13, 2004, 8:02 am)
-re: BSOD, win32k.sys (Axl Myk: Wed, Jun 16, 2004, 5:26 pm)
*re: BSOD, win32k.sys (Sabyre: Fri, Jun 25, 2004, 7:20 am)
-re: BSOD, win32k.sys (SilverRope: Sat, Jun 26, 2004, 6:59 pm)
*re: BSOD, win32k.sys (wim: Tue, Jun 29, 2004, 3:56 pm)
*re: BSOD, win32k.sys (SilverRope: Wed, Jul 14, 2004, 2:01 pm)
-re: BSOD, win32k.sys (HairRazor: Wed, Jun 30, 2004, 11:01 pm)
-re: BSOD, win32k.sys (Axl Myk: Thu, Jul 8, 2004, 6:27 am)
*re: BSOD, win32k.sys (Van Thong: Tue, Jul 13, 2004, 4:57 pm)
-re: BSOD, win32k.sys (King Azog: Mon, Jan 31, 2005, 9:18 am)
-re: BSOD, win32k.sys (callum: Thu, Feb 10, 2005, 2:58 am)
-re: BSOD, win32k.sys (Matthew D. Healy: Thu, Feb 10, 2005, 4:35 am)
*re: BSOD, win32k.sys (Brandon: Wed, Feb 16, 2005, 7:12 am)
-re: BSOD, win32k.sys (Joe: Wed, Jul 28, 2004, 3:29 pm)
-re: BSOD, win32k.sys (Rustinator: Sun, Aug 1, 2004, 9:57 am)
-re: BSOD, win32k.sys (jamal: Mon, Aug 2, 2004, 7:03 pm)
-re: BSOD, win32k.sys (Todd: Tue, Aug 3, 2004, 9:55 am)
-Get it from the SP2 beta (NoGood: Wed, Aug 11, 2004, 2:56 pm)
-re: Get it from the SP2 beta (NoGood: Wed, Aug 11, 2004, 8:59 pm)
-re: Get it from the SP2 beta (Dee: Sun, Aug 15, 2004, 6:03 am)
-re: Get it from the SP2 beta (NoGood: Sun, Aug 15, 2004, 8:39 am)
*re: Get it from the SP2 beta (SilverRope: Sun, Aug 15, 2004, 11:31 am)
-re: BSOD, win32k.sys (Jeff in New Orleans: Fri, Aug 20, 2004, 9:10 pm)
-re: BSOD, win32k.sys (Paul: Sat, Aug 21, 2004, 8:08 am)
-re: BSOD, win32k.sys (Paul: Sat, Aug 21, 2004, 8:21 am)
-re: BSOD, win32k.sys (Jeff in New Orleans: Sat, Aug 21, 2004, 8:52 am)
-re: BSOD, win32k.sys (Paul: Sat, Aug 21, 2004, 9:36 am)
-re: BSOD, win32k.sys (Paul: Thu, Aug 26, 2004, 3:52 am)
-re: BSOD, win32k.sys (Robert: Mon, Aug 30, 2004, 12:28 pm)
-re: BSOD, win32k.sys (Dan: Tue, Sep 7, 2004, 4:50 pm)
-re: BSOD, win32k.sys (Ronald: Sun, Sep 12, 2004, 12:07 pm)
-Resolution!! (Paul: Fri, Sep 17, 2004, 8:29 am)
-re: Resolution!! (Ronald: Mon, Sep 20, 2004, 11:11 am)
*re: Resolution!! (Myob, stupid registrations: Wed, Oct 27, 2004, 12:54 am)
-re: Resolution!! (Jack Black: Wed, Oct 27, 2004, 1:09 pm)
-re: Resolution!! (Reynaert: Mon, Nov 22, 2004, 12:27 pm)
*My solution (Mogens: Fri, Dec 17, 2004, 2:20 am)
-re: Resolution!! (Infinity: Wed, Dec 22, 2004, 3:59 am)
-re: Resolution!! (Gareth Jones: Sat, Dec 25, 2004, 3:34 am)
-re: Resolution!! (Bleem: Sun, Jan 23, 2005, 12:59 pm)
*re: Resolution!! (Prasanna Balasubramanian: Wed, May 18, 2005, 6:59 am)
*re: BSOD, win32k.sys (M. Moulding: Fri, Dec 17, 2004, 11:52 am)
-re: BSOD, win32k.sys (Donna Price: Sun, Feb 20, 2005, 2:32 pm)
-re: BSOD, win32k.sys (fktrIbx: Thu, Feb 24, 2005, 11:37 am)
-re: BSOD, win32k.sys (Tyrian: Thu, Mar 3, 2005, 3:11 pm)
-BSOD only after overclocking (everica: Mon, Mar 7, 2005, 11:57 am)
*re: BSOD only after overclocking (Tyrian: Mon, Mar 7, 2005, 12:47 pm)
-re: BSOD and Memory on Athlons (Jack Gulley: Fri, Mar 11, 2005, 2:03 pm)
-re: BSOD and Memory on Athlons (Tyrian: Fri, Mar 11, 2005, 5:32 pm)
*re: BSOD and Memory on Athlons (Phu: Sun, Mar 20, 2005, 7:37 pm)
-re: BSOD, win32k.sys (Bret: Sun, May 22, 2005, 8:52 pm)
*re: BSOD, win32k.sys (Jerry Erbesfield: Sun, May 29, 2005, 9:26 pm)
-re: BSOD - many different ones (Kevin: Wed, Jun 1, 2005, 11:32 pm)
*BSOD - for no apperent reason (Alex: Tue, Jun 7, 2005, 2:04 pm)
-re: BSOD, win32k.sys (Eli Tabs: Sat, Jul 2, 2005, 3:20 pm)
-re: BSOD, win32k.sys (Geof Gibson: Tue, Jul 5, 2005, 10:44 am)
-re: BSOD, win32k.sys (annoyed at windows: Fri, Jul 8, 2005, 6:54 am)
-re: BSOD, win32k.sys (Kev: Thu, Jul 14, 2005, 2:38 pm)
-re: BSOD, win32k.sys (Falcon: Thu, Jul 14, 2005, 2:58 pm)
*re: BSOD, win32k.sys (Paul Cooper: Tue, Jul 26, 2005, 7:17 am)
*re: BSOD, win32k.sys (Ryan Tucker: Sat, Jul 30, 2005, 8:09 pm)
-re: BSOD, win32k.sys (greggg: Sun, Aug 14, 2005, 6:59 pm)
-re: BSOD, win32k.sys (greggg: Tue, Aug 16, 2005, 2:55 pm)
-re: BSOD, win32k.sys (Baron French: Tue, Aug 23, 2005, 8:59 am)
*re: BSOD, win32k.sys (georgemason: Thu, Sep 22, 2005, 10:57 am)
*re: BSOD, win32k.sys (yasser: Wed, Oct 26, 2005, 6:13 pm)
-re: BSOD, win32k.sys (Jim Fromageons: Wed, Oct 26, 2005, 6:41 pm)
-re: BSOD, win32k.sys (codemyyster: Wed, Nov 2, 2005, 10:20 pm)
-re: BSOD, win32k.sys (Gary W: Thu, Nov 3, 2005, 4:53 am)
-re: BSOD, win32k.sys (Claudio: Sat, Nov 12, 2005, 3:15 pm)
-re: BSOD, win32k.sys (Steve O: Thu, Nov 17, 2005, 9:14 am)
*re: BSOD, win32k.sys (Steve O: Thu, Nov 17, 2005, 9:30 am)
-re: BSOD, win32k.sys (ironic_8b49: Thu, May 25, 2006, 7:59 am)
-re: BSOD, win32k.sys (kresnack: Sun, May 28, 2006, 6:03 am)
-re: BSOD, win32k.sys (Cerberus: Tue, May 30, 2006, 5:21 am)
-re: BSOD, win32k.sys (koyak: Fri, Jun 23, 2006, 9:16 am)
-re: BSOD, win32k.sys (koyak: Fri, Jun 23, 2006, 9:50 am)
-The key to a BSOD! This is what you have been looking for. (Josh: Thu, Jun 29, 2006, 10:02 pm)
-The key to a BSOD! This is what you have been looking for. (Josh: Fri, Jun 30, 2006, 1:14 am)
-re: The key to a BSOD! XP is Def, SB16 not to blame (Cal: Sat, Jul 15, 2006, 3:20 am)
-re: The key to a BSOD! XP is Def, SB16 not to blame (Kyle: Mon, Jul 17, 2006, 6:42 pm)
-Core Problem WIN32K.SYS Cause Effect and Repair MyEppliance (myeppliance: Sun, Oct 8, 2006, 8:27 am)
-re: Core Problem WIN32K.SYS Cause Effect and Repair MyEppliance (chris: Wed, Nov 8, 2006, 3:58 pm)
-re: Core Problem WIN32K.SYS (MaJiX04: Tue, Dec 12, 2006, 8:06 am)
-re: Core Problem WIN32K.SYS (Bee Welbourne: Mon, Dec 25, 2006, 4:28 pm)
-re: Core Problem WIN32K.SYS (cloudsBro: Tue, Jan 16, 2007, 9:32 am)
-re: Core Problem WIN32K.SYS (sal: Thu, Feb 1, 2007, 4:16 pm)
*re: Core Problem WIN32K.SYS (SomeGuy: Tue, May 1, 2007, 12:17 am)
*re: The key to a BSOD! This is what you have been looking for. (Mr.T: Tue, Aug 14, 2007, 8:58 am)
-re: BSOD, win32k.sys (Vtornik: Sat, Nov 3, 2007, 9:58 pm)
-re: BSOD, win32k.sys (Davey Nelson: Tue, Nov 13, 2007, 1:53 pm)
-re: BSOD, win32k.sys (tommmy: Tue, Dec 18, 2007, 10:30 am)
*re: BSOD, win32k.sys (faeriedragon: Sun, Dec 30, 2007, 4:17 pm)
*re: BSOD, win32k.sys (JohnTrota: Sat, Sep 24, 2011, 2:20 pm)
-re: BSOD, win32k.sys (nelson: Thu, Dec 22, 2011, 3:16 am)
*SPAM spam SPAM (MartinM: Fri, Dec 23, 2011, 11:08 am)
Return to the Windows XP Discussion Forum


All content at Annoyances.org is Copyright ©1995-2012 Creative Elementtm All rights reserved.
Please do not plagiarize; redistributing these pages without permission is strictly prohibited.