Tip: Run a free scan for common Windows errors ad

re: BSOD, win32k.sys Sunday, January 5, 2003 at 1:37 pm Posted by Gavin (1 messages posted) edu, have you managed to solve this problem?... I am getting this error too along with the error code 0x0000008e and paged_fault_in_nonpaged_area. (Athlon 1.4 GHZ, 512MB DDRAM, Geforce 4 4200ti...) Having problems trying to resolve.... everyone has the same error code but with different file!! Please help if you can. On Friday, September 6, 2002 at 5:38 am, edu wrote: >Periodically I get BSOD's identifying the driver win32k.sys in the message... When >they appear I'm not doing anything in particular or using any particular program... >anyone know why this happens? (Athlon 1.4 GHZ, 256MB DDRAM, Geforce Mx-400...) [Reply or follow-up to this message] re: BSOD, win32k.sys Monday, January 6, 2003 at 8:55 pm Posted by Jeff (18 messages posted) BSOD Win32k.sys Stop 0x0000008 addr BF8B56B0 Ya its repeatable. Its software. It happens when i'm running either a movie, or changing video modes. It's only started recently. I just started running mIrc lately too... (AMD 1600, 512mb, SIS chipset, GForce2 card) On Sunday, January 5, 2003 at 1:37 pm, Gavin wrote: >edu, > >have you managed to solve this problem?... I am getting this error too along with >the error code 0x0000008e and paged_fault_in_nonpaged_area. >(Athlon 1.4 GHZ, 512MB DDRAM, Geforce 4 4200ti...) > >Having problems trying to resolve.... everyone has the same error code but with different >file!! > >Please help if you can. > > [Reply or follow-up to this message] re: BSOD, win32k.sys Monday, January 13, 2003 at 5:02 pm Posted by Andrew Cartine (1 messages posted) I am getting the same thing. I just installed an NVIDIA ti4600 and it is giving me BSOD. It sometimes says the nv4_disp.dll driver is the cause, but now it blames win32k.sys. It's always PAGE_FAULT_IN_NONPAGED_AREA Stop: 0x00000050 P4 533FSB 2400, 512MB DDR400 On Monday, January 6, 2003 at 8:55 pm, Jeff wrote: >BSOD Win32k.sys Stop 0x0000008 addr BF8B56B0 Ya its repeatable. Its software. It >happens when i'm running either a movie, or changing video modes. It's only started >recently. I just started running mIrc lately too... (AMD 1600, 512mb, SIS chipset, >GForce2 card) > > [Reply or follow-up to this message] re: BSOD, win32k.sys Tuesday, January 14, 2003 at 8:50 pm Posted by Olivier Hubert (2 messages posted) Ok I'm relieved now, I thought I was the only one going mad with this. I have had BSOD's for a week now and don't know why. The only thing our computers have in common (that I see at first glance) is the GeForce4 card... My BSOD's show STOP 0x00000050 or 0x0000008E with PAGE_FAULT_IN_NONPAGED_AREA. Sometimes nv4_disp.dll is faulty and sometimes win32k.sys and even wmaud.sys once (I think). Athlon 2400+ Asus A7N8X (nForce2 chipset) 512 MB DDR 2700 Asus GeForce4 Ti4600 On Monday, January 13, 2003 at 5:02 pm, Andrew Cartine wrote: >I am getting the same thing. > >I just installed an NVIDIA ti4600 and it is giving me BSOD. It sometimes says the >nv4_disp.dll driver is the cause, but now it blames win32k.sys. > >It's always PAGE_FAULT_IN_NONPAGED_AREA > >Stop: 0x00000050 > >P4 533FSB 2400, 512MB DDR400 > [Reply or follow-up to this message] re: BSOD, win32k.sys Thursday, January 16, 2003 at 5:47 pm Posted by sac (1 messages posted) I am also getting the win32k.sys fault. I also have a geforce video card. As far as I understand from reading about it online, a lot of people are getting this fault and I haven't found the cure for it yet. if anyone knows how to fix it please let me know On Tuesday, January 14, 2003 at 8:50 pm, Olivier Hubert wrote: >Ok I'm relieved now, I thought I was the only one going mad with this. I have had >BSOD's for a week now and don't know why. The only thing our computers have in common >(that I see at first glance) is the GeForce4 card... > >My BSOD's show STOP 0x00000050 or 0x0000008E with PAGE_FAULT_IN_NONPAGED_AREA. Sometimes >nv4_disp.dll is faulty and sometimes win32k.sys and even wmaud.sys once (I think). > >Athlon 2400+ >Asus A7N8X (nForce2 chipset) >512 MB DDR 2700 >Asus GeForce4 Ti4600 > > [Reply or follow-up to this message] re: BSOD, win32k.sys Sunday, January 19, 2003 at 11:58 am Posted by ryan (7 messages posted) I'm getting this error too, however i DON'T have a geforce video card....my system is a 1.4 GHz Athlon 512 MB ram and an old old old old video card of which i don't even know the name. win32k.sys is usually (but not always) named along with the PAGE_FAULT_IN_NON_PAGED_AREA error. I also get these other errors: DRIVER_IRQL_NOT_LESS_OR_EQUAL_TO IRQL_NOT_LESS_OR_EQUAL_TO BAD_POOL_CALLER These errors have each implicated different .sys and .dll files at different times. I'd recommend searching through the post on this forum which deals with the IRQL errors. Some posters on there have had success with switching cards to different PCI slots and replacing their ram. I don't know if any of these problems are related (in fact I doubt it), but I hope we get to the bottom of this soon. Check Here http://www.annoyances.org/exec/forum/winxp/n1022109789 [Reply or follow-up to this message] re: BSOD, win32k.sys Monday, January 20, 2003 at 5:36 pm Posted by Jim (4 messages posted) Same Problem here too. I have an ATI Radeon 7000 video card, 850mhz AMD Duron. Any help would be appreciated. On Sunday, January 19, 2003 at 11:58 am, ryan wrote: >I'm getting this error too, however i DON'T have a geforce video card....my system >is a 1.4 GHz Athlon 512 MB ram and an old old old old video card of which i don't >even know the name. win32k.sys is usually (but not always) named along with the PAGE_FAULT_IN_NON_PAGED_AREA >error. I also get these other errors: > >DRIVER_IRQL_NOT_LESS_OR_EQUAL_TO > >IRQL_NOT_LESS_OR_EQUAL_TO > >BAD_POOL_CALLER > >These errors have each implicated different .sys and .dll files at different times. >I'd recommend searching through the post on this forum which deals with the IRQL >errors. Some posters on there have had success with switching cards to different >PCI slots and replacing their ram. I don't know if any of these problems are related >(in fact I doubt it), but I hope we get to the bottom of this soon. > >Check Here http://www.annoyances.org/exec/forum/winxp/n1022109789 [Reply or follow-up to this message] re: BSOD, win32k.sys Monday, January 20, 2003 at 9:47 pm Posted by Olivier Hubert (2 messages posted) Ok, I solved my problem, but my solution probably won't apply to all (if any) of you guys. I have an option with my board (Asus A7N8X) for RAM timing and I only had to change the RAM timing from "Optimal" to "Sync", which effectively lowers the RAM speed. For those without this option, try lowering your memory speed (133Mhz worked for me) or try switching RAM Dimms/Simms. There errors are usually symptoms of memory problems. Also try to test you RAM using memtest-86 (http://www.memtest86.com/), it found some errors while my RAM was using a higher clock speed but none with my current 133Mhz. HTH Olivier On Monday, January 20, 2003 at 5:36 pm, Jim wrote: >Same Problem here too. I have an ATI Radeon 7000 video card, 850mhz AMD Duron. >Any help would be appreciated. > > [Reply or follow-up to this message] re: BSOD, win32k.sys Tuesday, January 21, 2003 at 7:13 am Posted by NH (1 messages posted) Im also getting the win32k.sys, using a Asus A7n8x and geforce 2 pro. It seems to be something to do with the cpu speed, if i overclocked by old CPU to over 1500mhz it happened, and when I use an athlon XP2100+ it does it to. On Monday, January 20, 2003 at 9:47 pm, Olivier Hubert wrote: >Ok, I solved my problem, but my solution probably won't apply to all (if any) of >you guys. I have an option with my board (Asus A7N8X) for RAM timing and I only had >to change the RAM timing from "Optimal" to "Sync", which effectively lowers the RAM >speed. > >For those without this option, try lowering your memory speed (133Mhz worked for >me) or try switching RAM Dimms/Simms. There errors are usually symptoms of memory >problems. Also try to test you RAM using memtest-86 (http://www.memtest86.com/), >it found some errors while my RAM was using a higher clock speed but none with my >current 133Mhz. > >HTH > >Olivier > > [Reply or follow-up to this message] re: BSOD, win32k.sys Wednesday, January 22, 2003 at 3:35 pm Posted by loco (6 messages posted) Thanks Oliver - that was good advise, I have the Asus A7N8X also and was getting the win32k.sys BSOD. I was running a Kingston 512 chip (KVR400X64C25/512) and memtest86 recorded 50,000+ errors at the optimal setting. I switched to snyc mode and the errors went down to 1313. So today, I bought the correct memory (on the Asus recommended list) Corsair CRS-CMX512-3200C2 and recorded NO errors at the optimal (200Mhz) setting. So far no win32k.sys errors either. Thanks again..... On Monday, January 20, 2003 at 9:47 pm, Olivier Hubert wrote: >Ok, I solved my problem, but my solution probably won't apply to all (if any) of >you guys. I have an option with my board (Asus A7N8X) for RAM timing and I only had >to change the RAM timing from "Optimal" to "Sync", which effectively lowers the RAM >speed. > >For those without this option, try lowering your memory speed (133Mhz worked for >me) or try switching RAM Dimms/Simms. There errors are usually symptoms of memory >problems. Also try to test you RAM using memtest-86 (http://www.memtest86.com/), >it found some errors while my RAM was using a higher clock speed but none with my >current 133Mhz. > >HTH > >Olivier > > [Reply or follow-up to this message] re: Yes but anyone got a solution? (sigh) Sunday, May 4, 2003 at 7:59 am Posted by darren (2 messages posted) Yeh we know that there are loads of poepl out there with this same annoying problem lol But has anyojne found a solution yet please? its totally doing my head in :( daz On Friday, September 6, 2002 at 5:38 am, edu wrote: >Periodically I get BSOD's identifying the driver win32k.sys in the message... When >they appear I'm not doing anything in particular or using any particular program... >anyone know why this happens? (Athlon 1.4 GHZ, 256MB DDRAM, Geforce Mx-400...) [Reply or follow-up to this message] re: Yes but anyone got a solution? (sigh) Monday, May 19, 2003 at 2:33 pm Posted by Prince_Saiyan (1 messages posted) you guys can help eliminate this problem by downloading the new 44.03 Detonator Driver for your nVidia Cards (like GeForce). A friend of mine had EXACTLY those problems with PAGE_FAULT_IN_NONPAGED_AREA and win32k.sys. but NEVER again after he updated the Detonator drivers. Try it... On Sunday, May 4, 2003 at 7:59 am, darren wrote: >Yeh we know that there are loads of poepl out there with this same annoying problem >lol > >But has anyojne found a solution yet please? its totally doing my head in :( > >daz > > [Reply or follow-up to this message] re: Yep, I have a solution for me!! Wednesday, May 21, 2003 at 6:44 am Posted by Nick (1 messages posted) What I found the problem to be for me was that I had an Abit NF7-M board with integrated Video card (GPU). This shared system memory (Fine for me as this machine was only a workstation not for gaming). The BSOD sometimes referenced NV4_disp.dll in the message and sometimes win32k.sys. At first I thought it was a video problem, but after running the system memory at all speeds between 133MHz - 400MHz I discovered that swapping said memory for a decent branded stick (Crucial XMS 3200) all my problems went away. The bizarre bit is the suspect stick of memory works brilliantly @ 333MHz in my gaming machine (Abit KX7-333). All I can imagine is that motherboards using the Nforce 2 chipset (particularly those with built in GPU's) are very fussy about the memory that is fitted. Try downloading Memtest86 from http://www.memtest86.com/ (It creates a bootable DOS disk) and see how many errors you are getting - your memory may be the root of all your problems. On Monday, May 19, 2003 at 2:33 pm, Prince_Saiyan wrote: > >you guys can help eliminate this problem by downloading the new 44.03 Detonator Driver >for your nVidia Cards (like GeForce). A friend of mine had EXACTLY those problems >with PAGE_FAULT_IN_NONPAGED_AREA and win32k.sys. but NEVER again after he updated >the Detonator drivers. Try it... > [Reply or follow-up to this message] still need help Tuesday, May 27, 2003 at 12:36 pm Posted by Gary (2 messages posted) I'm having a similar problem, but I still need a little help in resolving it. (It has been lots of fun just trying to complete this message before my system crashes again.) My Intel D845 GRG board doesn’t seem to offer the option of changing the RAM timing from "Optimal" to "Sync" as someone suggested. At least I couldn’t find it in the BIOS settings. Someone suggested lowering the memory speed. I assume that means buying lower speed RAM. (I am already using the lowest speed available for my board.) I have onboard video, so some of those solutions won't help. It looks like the solution is new RAM, so I'm open to suggestions of what to look for (or avoid). My board will only take DDR. Right now I have 256 MB 266 MHz PC 2100. (Windows XP / 1.8 Celeron) Thanks. [Reply or follow-up to this message] re: still need help Tuesday, May 27, 2003 at 10:22 pm Posted by chris (1 messages posted) ok, i think that we are just discusted with all of this. i have a simalar poblem of what has been mentioned in all of these messages. i hava a :jetway mother board a +2000 amd atholan and a geforce 2 mx 400. i am getting blue screens of the "0xe, 0x50, oxd1, 0xf1" lots of witch have the "nv4_mini.sys" or the "mup.sys" or the "paged in non paged area" i have replaced both ream modulels and i have noteced that when i go into into dxdiag and into the display tab it list the "nv4_mini.sys" i have the latet drivers and all of that other junk!!!!. please help!!!!!!!!!!! On Tuesday, May 27, 2003 at 12:36 pm, Gary wrote: >I'm having a similar problem, but I still need a little help in resolving it. (It >has been lots of fun just trying to complete this message before my system crashes >again.) My Intel D845 GRG board doesn’t seem to offer the option of changing the >RAM timing from "Optimal" to "Sync" as someone suggested. At least I couldn’t find >it in the BIOS settings. Someone suggested lowering the memory speed. I assume >that means buying lower speed RAM. (I am already using the lowest speed available >for my board.) I have onboard video, so some of those solutions won't help. It >looks like the solution is new RAM, so I'm open to suggestions of what to look for >(or avoid). My board will only take DDR. Right now I have 256 MB 266 MHz PC 2100. >(Windows XP / 1.8 Celeron) >Thanks. [Reply or follow-up to this message] re: still need help Wednesday, May 28, 2003 at 10:26 am Posted by derek (1 messages posted) hi did you solve the problem with the ram as i have the very same description as you , lets us know please. On Tuesday, May 27, 2003 at 12:36 pm, Gary wrote: >I'm having a similar problem, but I still need a little help in resolving it. (It >has been lots of fun just trying to complete this message before my system crashes >again.) My Intel D845 GRG board doesn’t seem to offer the option of changing the >RAM timing from "Optimal" to "Sync" as someone suggested. At least I couldn’t find >it in the BIOS settings. Someone suggested lowering the memory speed. I assume >that means buying lower speed RAM. (I am already using the lowest speed available >for my board.) I have onboard video, so some of those solutions won't help. It >looks like the solution is new RAM, so I'm open to suggestions of what to look for >(or avoid). My board will only take DDR. Right now I have 256 MB 266 MHz PC 2100. >(Windows XP / 1.8 Celeron) >Thanks. [Reply or follow-up to this message] re: BSOD, win32k.sys Friday, May 30, 2003 at 1:48 am Posted by Moises (1 messages posted) Well, I have found a solution to fix it. Though Microsoft told me that the only one solution is format and windows xp sometimes doesn't allow me to go into recovery mode... I did it!! Once I could step to recovery mode and a simple chkdsk fixed the problem... Bye from Spain On Friday, September 6, 2002 at 5:38 am, edu wrote: >Periodically I get BSOD's identifying the driver win32k.sys in the message... When >they appear I'm not doing anything in particular or using any particular program... >anyone know why this happens? (Athlon 1.4 GHZ, 256MB DDRAM, Geforce Mx-400...) [Reply or follow-up to this message] re: BSOD, win32k.sys Sunday, June 1, 2003 at 6:57 am Posted by Pete (2 messages posted) The DRIVER_IRQL_NOT_LESS_OR_EQUAL_TO error can be solved be going back to the last set of drivers that you had changed. So, if you just changed the drivers for item X (video, sound, etc), then you either need to boot with Last Known Good Config (if you haven't logged on), or start in safe mode or safe mode with vga (if it was a video driver) and uninstall the newer driver and reinstall the older one that worked. On Sunday, January 19, 2003 at 11:58 am, ryan wrote: >I'm getting this error too, however i DON'T have a geforce video card....my system >is a 1.4 GHz Athlon 512 MB ram and an old old old old video card of which i don't >even know the name. win32k.sys is usually (but not always) named along with the PAGE_FAULT_IN_NON_PAGED_AREA >error. I also get these other errors: > >DRIVER_IRQL_NOT_LESS_OR_EQUAL_TO > >IRQL_NOT_LESS_OR_EQUAL_TO > >BAD_POOL_CALLER > >These errors have each implicated different .sys and .dll files at different times. >I'd recommend searching through the post on this forum which deals with the IRQL >errors. Some posters on there have had success with switching cards to different >PCI slots and replacing their ram. I don't know if any of these problems are related >(in fact I doubt it), but I hope we get to the bottom of this soon. > >Check Here http://www.annoyances.org/exec/forum/winxp/n1022109789 [Reply or follow-up to this message] re: Yes but anyone got a solution? (sigh) Monday, June 2, 2003 at 7:02 am Posted by aleXlee (1 messages posted) I don't think so cause i have that problam since i update my driver to the new 44.03 Detonator Driver. is anyone know why? or how to solve it On Monday, May 19, 2003 at 2:33 pm, Prince_Saiyan wrote: > >you guys can help eliminate this problem by downloading the new 44.03 Detonator Driver >for your nVidia Cards (like GeForce). A friend of mine had EXACTLY those problems >with PAGE_FAULT_IN_NONPAGED_AREA and win32k.sys. but NEVER again after he updated >the Detonator drivers. Try it... > [Reply or follow-up to this message] re: BSOD, win32k.sys Monday, June 2, 2003 at 5:31 pm Posted by ryan (7 messages posted) Actually, in my case, I believe all of these problems were caused by a bad stick of RAM. Removing it eliminated all blue screen errors. Other system instability problem were attributed to an old motherboard, the replacement of which has made my system rock solid. [Reply or follow-up to this message] re: BSOD, win32k.sys Monday, June 2, 2003 at 9:25 pm Posted by Craig (1 messages posted) I'm having the same problem with the nv4_disp.dll. Microsoft recommends updating your video driver. I have not yet, but I will. Read this Knowledge Base Article: http://support.microsoft.com/?kbid=325730 On Monday, January 13, 2003 at 5:02 pm, Andrew Cartine wrote: >I am getting the same thing. > >I just installed an NVIDIA ti4600 and it is giving me BSOD. It sometimes says the >nv4_disp.dll driver is the cause, but now it blames win32k.sys. > >It's always PAGE_FAULT_IN_NONPAGED_AREA > >Stop: 0x00000050 > >P4 533FSB 2400, 512MB DDR400 > [Reply or follow-up to this message] I think this is a northbridge overheating problem Tuesday, June 3, 2003 at 6:59 am Posted by jetface (2 messages posted) I used to have this problem on my old AMD K6-2 550 MHz with a GeForce2. It would always happen when I was doing anything graphic intensive. I tried all kinds of solutions, drivers, BIOS settings, switching out hardware, then finally I believe I figured out what it was. My northbridge was overheating (VIA MVP3 chipset). The last time I got BSOD I felt the northbridge (make sure power supply is off, touch the case first or you might zap something) and it was more than warm. I stuck a fan in the side of my case blowing right on the sucker and now it never happens. I am also running a nforce2 chipset board with a Geforce4 4200 Ti and I haven't encountered one yet ( had it for 6 months). I think it is because my board came standard with a nice passive northbridge cooling setup. I believe lowering your memory timings work because it is slowing your system down and therefore probably not heating things up as much. Its not too hard to stick a fan somewhere to blow on the northbridge. When I first tested it out, I just used a bunch of zip ties to basically hang it in the right vicinity. This is just my opinion, maybe it will work for you. [Reply or follow-up to this message] re: I think this is a northbridge overheating problem Tuesday, June 3, 2003 at 2:27 pm Posted by manus (1 messages posted) Thx for your message whitch can explain all the precedent ones. In my case, on my laptop with PIII and GeForce2, after having BSOD, it happens really often that I can't reboot. After 5 or 6 tentatives, the reboot occurs and the fan is at its maxi speed immediately. But how cooler le laptop ... And my BIOS doesn't allow me to reduce clock speed ... any help ? On Tuesday, June 3, 2003 at 6:59 am, jetface wrote: >I used to have this problem on my old AMD K6-2 550 MHz with a GeForce2. It would >always happen when I was doing anything graphic intensive. I tried all kinds of >solutions, drivers, BIOS settings, switching out hardware, then finally I believe >I figured out what it was. My northbridge was overheating (VIA MVP3 chipset). The >last time I got BSOD I felt the northbridge (make sure power supply is off, touch >the case first or you might zap something) and it was more than warm. I stuck a >fan in the side of my case blowing right on the sucker and now it never happens. > I am also running a nforce2 chipset board with a Geforce4 4200 Ti and I haven't >encountered one yet ( had it for 6 months). I think it is because my board came >standard with a nice passive northbridge cooling setup. I believe lowering your >memory timings work because it is slowing your system down and therefore probably >not heating things up as much. Its not too hard to stick a fan somewhere to blow >on the northbridge. When I first tested it out, I just used a bunch of zip ties >to basically hang it in the right vicinity. This is just my opinion, maybe it will >work for you. [Reply or follow-up to this message] re: still need help Tuesday, June 3, 2003 at 6:12 pm Posted by Ben Earhart (2 messages posted) My machine does this occasionally. Funnily enough, usually in the mornings - I think before its heated up. From what I can tell, these STOPs are memory related. One thing you can always try (I just did yesterday) is cleaning the contacts on your ram sticks. To clean the contacts you remove the stick (this works for cards as well), use a pencil eraser and rub all of the gold contacts thoroughly. After that, take a cotton swap (q-tip) soaked with alcohol (90% isopropyl is great) and clean by rubbing the swap back and forth across the contacts. Dry and give it a good blow (no spittle!) to get rid of any stray cotton bits. Replace RAM. You'd be surprised at how often this works. On Wednesday, May 28, 2003 at 10:26 am, derek wrote: >hi did you solve the problem with the ram as i have the very same description as >you , lets us know please. > > [Reply or follow-up to this message] re: I think this is a northbridge overheating problem Wednesday, June 4, 2003 at 6:41 am Posted by jetface (2 messages posted) Sorry, manus, I am not too familiar with cooling down a laptop chipset. You might be able to find some information on the internet, though. That's one of the drawbacks of laptops, unfortunately, not enough space to get in there and mess around. You might try setting it on a wire shelf or something so the bottom can exchange heat with the surroundings. A few years ago, when my TNT2 wasn't keeping up and overheating, I put a floor fan next to my computer to improve circulation around the whole box. It actually worked and might work for you. It is important to have good circulation around any computer. But, like I said, I haven't had any experience cooling laptops, but I'm sure someone out there has. Good luck! On Tuesday, June 3, 2003 at 2:27 pm, manus wrote: >Thx for your message whitch can explain all the precedent ones. >In my case, on my laptop with PIII and GeForce2, after having BSOD, it happens really >often that I can't reboot. After 5 or 6 tentatives, the reboot occurs and the fan >is at its maxi speed immediately. >But how cooler le laptop ... >And my BIOS doesn't allow me to reduce clock speed ... >any help ? > > [Reply or follow-up to this message] re: still need help Sunday, June 8, 2003 at 12:50 am Posted by Ben Earhart (2 messages posted) So far so good! cleaned the RAM sticks and no crashes yet! On Tuesday, June 3, 2003 at 6:12 pm, Ben Earhart wrote: >My machine does this occasionally. Funnily enough, usually in the mornings - I think >before its heated up. From what I can tell, these STOPs are memory related. One >thing you can always try (I just did yesterday) is cleaning the contacts on your >ram sticks. To clean the contacts you remove the stick (this works for cards as >well), use a pencil eraser and rub all of the gold contacts thoroughly. After that, >take a cotton swap (q-tip) soaked with alcohol (90% isopropyl is great) and clean >by rubbing the swap back and forth across the contacts. Dry and give it a good blow >(no spittle!) to get rid of any stray cotton bits. Replace RAM. You'd be surprised >at how often this works. > [Reply or follow-up to this message] re: still need help Tuesday, June 10, 2003 at 5:14 pm Posted by Gary (2 messages posted) I was just recently able to get new RAM and install it. I've only been using the new RAM for a couple of days, but my system hasn't crashed once. Hopefully that has solved the problem. On Wednesday, May 28, 2003 at 10:26 am, derek wrote: >hi did you solve the problem with the ram as i have the very same description as >you , lets us know please. > > [Reply or follow-up to this message] re: BSOD, win32k.sys Monday, June 16, 2003 at 3:40 am Posted by Subz (4 messages posted) I've just started to get this problem. Five days after installing XP Pro (with SP-1 built in - grr!) I was happily playing GTA:VC when it hung. I restarted and got the offending PAGE_FAULT bluey. I tried the chkdsk fix and it didn't. This seems to be slippery problem. My system is an EPoX 4SD5A+, iP4 2.4B, 512Mb Corsair XMS Platinum, Sapphire Radeon 9500 Pro, SB Live 5.1., ATA133 Maxtor 8 (40Gb). Now what got me is that I had been using a friends spare XP Pro (he had upgrade to Server 2003 for some reason) to "preview" it before whacking down £150+ for the OS. His version of XP does not contain SP1. Lo & behold... It worked fine for the 20+ days I ran it before the activation came up. So "I'll have me some of that." thinks I. Buys XP Pro (SP-1) and suffers all these PAGE_FAULT errors. They occur randomly but most interestingly on Shutdowns! They never mention any drivers either. I have ran the memory through a thirty minute hardware test with no problems. I remove the soundcard. I "flattened" the hard drive and tried FAT32 instead of NTFS. The problem still occurs. Tonight I'm going to stick the old copy of XP Pro one and see if it works. (After checking my Radeon drivers to see if they are up to date - 7.88) If this works, I proves what I am supsecting, that SP-1 is once again at fault. I may also try 98SE and ME and see if they work but to be honest, I'm getting pretty pee'd off with all of this. I will report back with my findings. ;o) Cheers, Subz On Friday, May 30, 2003 at 1:48 am, Moises wrote: > > >Well, I have found a solution to fix it. Though Microsoft told me that the only one >solution is format and windows xp sometimes doesn't allow me to go into recovery >mode... I did it!! Once I could step to recovery mode and a simple chkdsk fixed the >problem... > >Bye from Spain [Reply or follow-up to this message] re: BSOD, win32k.sys Tuesday, June 17, 2003 at 2:17 am Posted by Subz (4 messages posted) Worked fine with XP Pro (not SP-1)! Checked the drivers for the Radeon and found it was actually 7.84, not 7.88. Reinstalled XP Pro (with SP-1) and installed the very latest drivers and so far, no problems either. Very odd. I don't think I've seen the last of this error though. Cheers, Subz - "It'll never work" - (The Eternal Cynic) On Monday, June 16, 2003 at 3:40 am, Subz wrote: >I've just started to get this problem. Five days after installing XP Pro (with SP-1 >built in - grr!) I was happily playing GTA:VC when it hung. I restarted and got the >offending PAGE_FAULT bluey. > >I tried the chkdsk fix and it didn't. This seems to be slippery problem. > >My system is an EPoX 4SD5A+, iP4 2.4B, 512Mb Corsair XMS Platinum, Sapphire Radeon >9500 Pro, SB Live 5.1., ATA133 Maxtor 8 (40Gb). > >Now what got me is that I had been using a friends spare XP Pro (he had upgrade to >Server 2003 for some reason) to "preview" it before whacking down £150+ for the OS. >His version of XP does not contain SP1. Lo & behold... It worked fine for the 20+ >days I ran it before the activation came up. So "I'll have me some of that." thinks >I. Buys XP Pro (SP-1) and suffers all these PAGE_FAULT errors. > >They occur randomly but most interestingly on Shutdowns! They never mention any drivers >either. >I have ran the memory through a thirty minute hardware test with no problems. I remove >the soundcard. I "flattened" the hard drive and tried FAT32 instead of NTFS. The >problem still occurs. > >Tonight I'm going to stick the old copy of XP Pro one and see if it works. (After >checking my Radeon drivers to see if they are up to date - 7.88) > >If this works, I proves what I am supsecting, that SP-1 is once again at fault. I >may also try 98SE and ME and see if they work but to be honest, I'm getting pretty >pee'd off with all of this. > >I will report back with my findings. ;o) > >Cheers, >Subz > > [Reply or follow-up to this message] re: BSOD, win32k.sys Monday, June 23, 2003 at 11:00 pm Posted by Ky (1 messages posted) ok I had a major issue with this win32k.sys also, after about 7 month's of no issue's what so ever. A few weeks ago it starts, just as my subscription ran out, now it happen about 30-3hr's with no given time or reason why, then after digging into it for 6 hr's of looking here and even debugging with no luck I Find a Possible Clue MICROTREND(Pcillion2002)...... IE antivirus so i uninstalled it.... now i have been up for 8 hr's not a single blue screen yet :) Hope this helps a few, damn i hope that was it !!!!! On Tuesday, June 17, 2003 at 2:17 am, Subz wrote: >Worked fine with XP Pro (not SP-1)! >Checked the drivers for the Radeon and found it was actually 7.84, not 7.88. > >Reinstalled XP Pro (with SP-1) and installed the very latest drivers and so far, >no problems either. Very odd. > >I don't think I've seen the last of this error though. > >Cheers, >Subz - "It'll never work" - (The Eternal Cynic) > [Reply or follow-up to this message] re: BSOD, win32k.sys Tuesday, June 24, 2003 at 10:33 pm Posted by MadMonkee (3 messages posted) HELP ME WITH THIS PROBLEM! I AM GOING CRAZY! I am having the same set of errors, for a reason I am not aware of. And it's nothing specific, it just does it in the middle of anything! I updated everyfile about my mainboard, updated BIOS, downloaded latest Intel files NOTHING fixes it! I even formatted the whole hard-disk and installed Xp all over again it keeps doing it. I bought new fans, PC cooler. I cleaned all my hardware. No luck at all. I know one thing for certain though, these problems started when I changed my motherboard to MSI (MS-6528 Intel 845 Chipset). I have Sound Blaster Live! sound card And GeForce Ti4400 display. It also seems to me like everyone who has this problem owns an Nvidia GeForce, I hope it has nothing to do with that. I am even typing this reply as fast as I can because I really don't know when the system is gonna crash! HEEEEEEEEEELP!!! On Monday, January 20, 2003 at 5:36 pm, Jim wrote: >Same Problem here too. I have an ATI Radeon 7000 video card, 850mhz AMD Duron. >Any help would be appreciated. > > [Reply or follow-up to this message] re: BSOD, win32k.sys Thursday, June 26, 2003 at 9:01 am Posted by Skud (1 messages posted) Hello all. I have just read all the posts in this thread and did some searching. I came up with the following link that is a bit over my head but thought it might give someone else a good troubleshooting starting point. I am getting the BSOD's and will try switching RAM and cooling first. Skud http://www.fengyuan.com/article/win32ksyscall.html On Friday, September 6, 2002 at 5:38 am, edu wrote: >Periodically I get BSOD's identifying the driver win32k.sys in the message... When >they appear I'm not doing anything in particular or using any particular program... >anyone know why this happens? (Athlon 1.4 GHZ, 256MB DDRAM, Geforce Mx-400...) [Reply or follow-up to this message] re: BSOD, win32k.sys Tuesday, July 1, 2003 at 7:36 pm Posted by David R (1 messages posted) Success! I can echo the experiences of everyone here. The actual circumstance was never consistent, and rarely repeatable, but included application hangs and spontaneous reboots with references to win32k.sys, various explorer files, various dll files, invalid page faults, PAGE_FAULT_IN_NONPAGED_AREA, DRIVER_IRQL_NOT_LESS_OR_EQUAL ... the list goes on and on. This has been going on since I built this machine in November 2002. I feel like I've followed every suggestion feasible with no success. However, when people continued to bring up overheating, I wrongly assumed they were talking about the well known Athlon overheating issue. I installed a fan in front, one in back, the built in fan in the power supply and a Thermaltake Volcano 7 on the processor. By the way, my setup is: MSI KT3 Ultra-ARU, Athlon 1800+, ABIT Siluro GEForce3 Ti200, Soundblaster Audigy, 512MB PC2700 RAM, 300w Power Supply So, it turns out that it wasn't my processor that was overheating, it was my video card. The card has its own cooling fan built in, so I figured it could take care of itself. However, my sound card was in the next slot below the video card, leaving just a few mm clearance between the two. Furthermore, I noticed the ribbon cables were further blocking airflow over the video card. When I think back, the only common thing about my problems was that they all happened while the video card was painting a window. To test if this is your problem also, take the side off your PC and use a box fan to make sure there's plenty of circulation around your video card. My PC has been up and running for almost a week now, and I've been beating up on it with everything I can think of (this PC has never run for this long before). To fix it, I didn't do anything except move my sound card down one slot. Excuse me my long-windedness, but I feel like shouting it from the rooftops. I can't believe I finally fixed this, the most exasperating problem of my PC-based life. [Reply or follow-up to this message] re: BSOD, win32k.sys Thursday, July 3, 2003 at 9:48 pm Posted by Inhops (1 messages posted) My system has been crashing for the past month. I have gone back to previous restore points with no luck. The past few days it has been crashing every 5 minutes. I read through these posts which lead me in the faulty hardware direction. I downloaded the memory test (memtest86.com) and it found errors. I removed the two RAM sticks individually and did the test on each. It found errors on only one stick. I have removed that stick from my system and have been VERY stable!!! No Crashes yet!! Thanks for the help & I hope my comments can help someone else. [Reply or follow-up to this message] re: BSOD, win32k.sys Monday, July 7, 2003 at 5:42 am Posted by heikki (1 messages posted) i had two problems, bsods and freezing MSI KT4 Ultra 2 AMD xp 1800 Nvidia Geforce 2 mx 1 kpl kingston ddr333 512 MB, 1 kpl kingston ddr333 256 MB freezing was caused by xp default driver for geforce 2 mx. nvidias own driver worked fine bsods was caused by bad 512 MB ram module. -heikki [Reply or follow-up to this message] re: BSOD, win32k.sys Wednesday, July 9, 2003 at 5:35 pm Posted by neu12rie (1 messages posted) Hi to all. I have read all posts and I agree with those saying that SP1 is to blame. I have an AV7133 with Athlon XP2000+, BIOS 1009, GeForceMX440, 4HDD(2 in mirror mode on raid controller), dvd and writter, modem int motorola, lan intel100 and sound PCI128. I have installed along with XPPRO-SP1, WIN2000PRO and SUSE 7.1 which work more than fine. So I cannot accept any memory or vga or whatever problems. It's only SP1. Without it XP work fine. With SP1 installed I get stop error 8e at win32k.sys while I 'm watching a movie or surfing or playing a game or listen to music or even when I do nothing (I even tried this, just turn on PC on XP and wait and I was still getting BSOD, amazing!!!). So don't bother to find solution, just don't install SP1. On Monday, January 13, 2003 at 5:02 pm, Andrew Cartine wrote: >I am getting the same thing. > >I just installed an NVIDIA ti4600 and it is giving me BSOD. It sometimes says the >nv4_disp.dll driver is the cause, but now it blames win32k.sys. > >It's always PAGE_FAULT_IN_NONPAGED_AREA > >Stop: 0x00000050 > >P4 533FSB 2400, 512MB DDR400 > [Reply or follow-up to this message] No more BSOD, win32k.sys Thursday, July 10, 2003 at 8:52 am Posted by Dominique (1 messages posted) PC Medion, MSI motherboard, 512 DDRam, NvidiaGeForce4 64Mo, all drivers updated. BSOD in the same manner -> I've disabled "Video RAM Cacheable" in the BIOS and since, no more BSOD at all. Try that ! On Friday, September 6, 2002 at 5:38 am, edu wrote: >Periodically I get BSOD's identifying the driver win32k.sys in the message... When >they appear I'm not doing anything in particular or using any particular program... >anyone know why this happens? (Athlon 1.4 GHZ, 256MB DDRAM, Geforce Mx-400...) [Reply or follow-up to this message] re: No more BSOD, win32k.sys Thursday, July 10, 2003 at 10:02 pm Posted by Bryan (1 messages posted) i have had ever single error on this page 5 times a peice each, everyday since i reisntall windows xp pro. including this cool error i dont think i have seen yet, multiple_irp_complete_requests. i am even getting blue screens.. yes, just BLUE, nothing on it. cool eh? Running Giga-byte P4 titan 667 MoBo, P4 2.5 ghz,ATI 9700 pro, gig of DDR 400, audigy 2, and a ATI TV VE card, ATA 133 80GB WD. I am ready to take a crap inside the chassi and get out the ol' AR-15... [Reply or follow-up to this message] re: still need help Monday, July 21, 2003 at 2:26 am Posted by Neil Cook (1 messages posted) I've had this problem since installing an AMD XP2100+ Processor. I've replaced the Motherboard (twice), Memory modules (Twice), and Processor (three times), still getting the same error. The experts say: Could be IDE Cable, could be heat problem, could be a Bios problem , could be.......I have basically given up since I sent the crash report to Microsoft and they say they can't tell me what the core dump means!!!. I spoke to a couple of fiorned who I reckon really know their stuff, guess what, they reckon that the problem is between the AMD architecture and Windows Xp, it's fundamental issue which they say Microsoft and AMD are not openly admitting to. If your machine works fine after a single crash - i.e. you have to reboot once after the blue screen then it works fine, then you can summise it's a driver problem which the Windows kernel works out only after letting the proble occur (1st boot) and then resolving on a warm start. Thats what I've been told, and frankly I'm just too fed up to do anything (9 months on!!). I've downloaded every Windows Update, driver update etc etc. Replaced every bit of hardware, where do you stop?, Neil On Tuesday, May 27, 2003 at 10:22 pm, chris wrote: > > >ok, i think that we are just discusted with all of this. i have a simalar poblem >of what has been mentioned in all of these messages. i hava a :jetway mother board >a +2000 amd atholan and a geforce 2 mx 400. i am getting blue screens of the "0xe, >0x50, oxd1, 0xf1" lots of witch have the "nv4_mini.sys" or the "mup.sys" or the "paged >in non paged area" i have replaced both ream modulels and i have noteced that when >i go into into dxdiag and into the display tab it list the "nv4_mini.sys" i have >the latet drivers and all of that other junk!!!!. please help!!!!!!!!!!! [Reply or follow-up to this message] re: BSOD, win32k.sys Monday, July 21, 2003 at 7:23 pm Posted by SkullFace (1 messages posted) On Monday, January 20, 2003 at 9:47 pm, Olivier I got a (Asus A7N8X) motherboard and like you said I set the ram to 133 and all is good now....thanks [Reply or follow-up to this message] re: No more BSOD, win32k.sys Wednesday, July 23, 2003 at 6:37 am Posted by Tony (1 messages posted) I was having the same kinds of errors, whether it be win32k, irq_not_less_or_equal, etc, etc, and my machine was brand new, pentium 3ghz, 512ddr400 ram, gigabyte motherboard, geforce 4 fx5200, 80gig HDD...i reinstalled win XP and still the same thing, same random crashes, my cpu wasnt overheating, reaching pretty much a max temp of 60 degrees and yeah, i had no idea, i'd downloaded every driver update i could find and scoured the microsoft website for a solution, downloading a couple of patches and stuff along the way... But, in the end, a read of the manual for my motherboard solved my prob. Even though my manual supported ddr400 ram, it was only for specific brands of it, why, i dunno, go ask gigabyte, so i knocked down my ram speed in bios to 333mhz and havent had any problem since, whether this keeps the heat in my system low so that it doesnt overheat as has been suggested earlier in this thread, i dunno, but it's done the trick for me, and my machines working perfect...so, hope that works for you...good luck. On Thursday, July 10, 2003 at 10:02 pm, Bryan wrote: >i have had ever single error on this page 5 times a peice each, everyday since i >reisntall windows xp pro. >including this cool error i dont think i have seen yet, multiple_irp_complete_requests. > i am even getting blue screens.. yes, just BLUE, nothing on it. cool eh? >Running Giga-byte P4 titan 667 MoBo, P4 2.5 ghz,ATI 9700 pro, gig of DDR 400, audigy >2, and a ATI TV VE card, ATA 133 80GB WD. >I am ready to take a crap inside the chassi and get out the ol' AR-15... > [Reply or follow-up to this message] re: BSOD, win32k.sys Sunday, July 27, 2003 at 4:50 pm Posted by Crickey (1 messages posted) I suspected overheating when this first started happening to me last summer. I was still under support from Dell. They had me format my harddrive a couple times. After about a week of dealing with me, it finally worked. I thought it was overheating since it only happened after the PC had been on for awhile. It then would start getting the errors, or just rebooting. I would turn it off and wait. Then it would for fine for awhile. Of course the Dell guys wouldn't listen. After the week of working with him, the weather cooled, and of course I had no problems. Now here it is July again, in the 90's and I am seeing the problem again. This time I just opened the case, but a 12 inch, 3 speed, osolating fan pointed on it. Seems to be working fine. I supposed I should invest in a better cooling system. On Tuesday, July 1, 2003 at 7:36 pm, David R wrote: >Success! I can echo the experiences of everyone here. The actual circumstance was >never consistent, and rarely repeatable, but included application hangs and spontaneous >reboots with references to win32k.sys, various explorer files, various dll files, >invalid page faults, PAGE_FAULT_IN_NONPAGED_AREA, DRIVER_IRQL_NOT_LESS_OR_EQUAL ... >the list goes on and on. > >This has been going on since I built this machine in November 2002. I feel like >I've followed every suggestion feasible with no success. However, when people continued >to bring up overheating, I wrongly assumed they were talking about the well known >Athlon overheating issue. I installed a fan in front, one in back, the built in >fan in the power supply and a Thermaltake Volcano 7 on the processor. By the way, >my setup is: MSI KT3 Ultra-ARU, Athlon 1800+, ABIT Siluro GEForce3 Ti200, Soundblaster >Audigy, 512MB PC2700 RAM, 300w Power Supply > >So, it turns out that it wasn't my processor that was overheating, it was my video >card. The card has its own cooling fan built in, so I figured it could take care >of itself. However, my sound card was in the next slot below the video card, leaving >just a few mm clearance between the two. Furthermore, I noticed the ribbon cables >were further blocking airflow over the video card. When I think back, the only common >thing about my problems was that they all happened while the video card was painting >a window. > >To test if this is your problem also, take the side off your PC and use a box fan >to make sure there's plenty of circulation around your video card. My PC has been >up and running for almost a week now, and I've been beating up on it with everything >I can think of (this PC has never run for this long before). To fix it, I didn't >do anything except move my sound card down one slot. Excuse me my long-windedness, >but I feel like shouting it from the rooftops. I can't believe I finally fixed this, >the most exasperating problem of my PC-based life. > [Reply or follow-up to this message] re: Yes but anyone got a solution? (sigh) Friday, August 1, 2003 at 4:05 am Posted by Dialmedia (2 messages posted) I don't agree with you, I am a rare case of this problem. I installed the 44.03 drivers when the nvidia oficially lauch but the problem with win32k.sys only has happened when I installed DFBHD, since there on every game my pc or crash or happear the blue screen, but never the .dll happeared. Oh, at some time ago I think I was the same problem ONLY with Midtown madness 2, but with the update that microsoft launched for the game the problem was fixed. I can say too the win32k.sys isn't a problem of the nvidia cards, because the win32k.sys have appear in me when I was talking in MSN (And what I know MSN don't use a graphics card to work o_O). Oh, btw everybody with win32k.sys has 512mb ram? One of my friends says that people with more than 256mb, the win32k.sys error could be because of too much memory in an application, solution? Disable Virtual Memory, it worked with some people but not with me... On Monday, May 19, 2003 at 2:33 pm, Prince_Saiyan wrote: > >you guys can help eliminate this problem by downloading the new 44.03 Detonator Driver >for your nVidia Cards (like GeForce). A friend of mine had EXACTLY those problems >with PAGE_FAULT_IN_NONPAGED_AREA and win32k.sys. but NEVER again after he updated >the Detonator drivers. Try it... > [Reply or follow-up to this message] re: BSOD, win32k.sys Friday, August 1, 2003 at 4:26 am Posted by Dialmedia (2 messages posted) Agreed, I have a poor cooling system and inside my house there is about 40/42º degrees and my pc is often crashing with that error, I rebooted the machine and my pc temperature is 65º (With cooler for the processor, 3 air fluxers and 1 ventilator), I think the RAM problem is because the temperature, so if you low out the speed less temperature in the pc, I think isn't 100% the problem with win32k.sys is because of the temperature but it worked with me (for sometimes)... if the error is occuring with somebody in the winter (or if was a high PC temperature), try to take out the pc box and put in a open space and see if the problem continues. On Sunday, July 27, 2003 at 4:50 pm, Crickey wrote: >I suspected overheating when this first started happening to me last summer. I was >still under support from Dell. They had me format my harddrive a couple times. >After about a week of dealing with me, it finally worked. I thought it was overheating >since it only happened after the PC had been on for awhile. It then would start >getting the errors, or just rebooting. I would turn it off and wait. Then it would >for fine for awhile. Of course the Dell guys wouldn't listen. After the week of >working with him, the weather cooled, and of course I had no problems. Now here >it is July again, in the 90's and I am seeing the problem again. This time I just >opened the case, but a 12 inch, 3 speed, osolating fan pointed on it. Seems to be >working fine. I supposed I should invest in a better cooling system. > > > [Reply or follow-up to this message] re: BSOD, win32k.sys Wednesday, August 6, 2003 at 6:56 pm Posted by Billy (1 messages posted) Hey, I have been getting these STOP: 0x0000008E (0xc0000005, etc... and just got a win32k.sys BSOD. I am running a AMD XP1700+ o'clocked to 2100mhz (10.5 x 200), on an Abit NF7-S v2.0 with OCZ LL PC3200 memory (dual channel enabled) also at 200mhz (400mhz effective) timings set at turbo and a Radeon 7500. My cpu temps are never above 50c under 100% load when overclocked. I always run my memory and cpu at the default settings when loading the OS then turn up the OC. I ran Win2k w/ the above settings for the last 2months without any errors. Including running memtest for 12hrs straight..no errors and Prime95 torture test for 12hrs straight...no errors...all that being said...I loaded WinXP Pro w/ SP1 and was fine for a short time, then the BSODs came...not often but every now and then. Tried leaving the cpu at the default speed and just running the memory at 200mhz, changed the timings to optimal, then got prime95 to run for 11hrs w/ no errors. Then back to the OS for another few hrs...then BSOD! After almost 20hrs of no errors. Since then I've gotten a few more and finally the win32k.sys. This is top quality memory, running at it's default settings and WinXP can't hang! Win2k ran great at the turbo settings with the cpu o'ced to 2100.......MY CONCLUSION....IT HAS TO BE XP...everyone makes good points about slowing the memory down etc....but this is the default for this memory......oh, well...I'll try the slower speed, but it seems stupid.....I'll probably just go back to win2k on this machine......eventually....I want my pc3200 running at pc3200! On Wednesday, July 23, 2003 at 6:37 am, Tony wrote: >I was having the same kinds of errors, whether it be win32k, irq_not_less_or_equal, >etc, etc, and my machine was brand new, pentium 3ghz, 512ddr400 ram, gigabyte motherboard, >geforce 4 fx5200, 80gig HDD...i reinstalled win XP and still the same thing, same >random crashes, my cpu wasnt overheating, reaching pretty much a max temp of 60 degrees >and yeah, i had no idea, i'd downloaded every driver update i could find and scoured >the microsoft website for a solution, downloading a couple of patches and stuff along >the way... > >But, in the end, a read of the manual for my motherboard solved my prob. Even though >my manual supported ddr400 ram, it was only for specific brands of it, why, i dunno, >go ask gigabyte, so i knocked down my ram speed in bios to 333mhz and havent had >any problem since, whether this keeps the heat in my system low so that it doesnt >overheat as has been suggested earlier in this thread, i dunno, but it's done the >trick for me, and my machines working perfect...so, hope that works for you...good >luck. > > [Reply or follow-up to this message] re: BSOD, win32k.sys Friday, August 8, 2003 at 1:12 pm Posted by Jim (2 messages posted) I was having the same problem until i read up a bit. After i installed my new fx5200 graphics card i was getting the BSOD and the win32k.sys error. I sorted it by looking at my memory. I had a 128MB Memory stick and a 512MB in both made by different companies. I took out the 128 and have not had this problem again since. So check your memory and see if that works. Cheap answer for me anyhow :-) On Monday, June 2, 2003 at 9:25 pm, Craig wrote: >I'm having the same problem with the nv4_disp.dll. Microsoft recommends updating >your video driver. I have not yet, but I will. Read this Knowledge Base Article: > http://support.microsoft.com/?kbid=325730 > > > [Reply or follow-up to this message] re: Yes but anyone got a solution? (sigh) Friday, August 8, 2003 at 1:18 pm Posted by Jim (2 messages posted) I was having the same problem until i read up a bit. After i installed my new fx5200 graphics card i was getting the BSOD and the win32k.sys error. I sorted it by looking at my memory. I had a 128MB Memory stick and a 512MB in both made by different companies. I took out the 128 and have not had this problem again since. So check your memory and see if that works. Cheap answer for me anyhow :-) On Friday, August 1, 2003 at 4:05 am, Dialmedia wrote: >I don't agree with you, I am a rare case of this problem. I installed the 44.03 drivers >when the nvidia oficially lauch but the problem with win32k.sys only has happened >when I installed DFBHD, since there on every game my pc or crash or happear the blue >screen, but never the .dll happeared. Oh, at some time ago I think I was the same >problem ONLY with Midtown madness 2, but with the update that microsoft launched >for the game the problem was fixed. I can say too the win32k.sys isn't a problem >of the nvidia cards, because the win32k.sys have appear in me when I was talking >in MSN (And what I know MSN don't use a graphics card to work o_O). > >Oh, btw everybody with win32k.sys has 512mb ram? One of my friends says that people >with more than 256mb, the win32k.sys error could be because of >too much memory in an application, solution? Disable Virtual Memory, it worked with >some people but not with me... > [Reply or follow-up to this message] re: BSOD, win32k.sys Sunday, August 10, 2003 at 1:22 pm Posted by Vectronx (1 messages posted) At second glance, all computers have in common an AMD Processor AND a Geforce (I have a Geforce 2), a bug from Windows GDI, AMD compatibility with Nvidia drivers, who can say.. On Tuesday, January 14, 2003 at 8:50 pm, Olivier Hubert wrote: >Ok I'm relieved now, I thought I was the only one going mad with this. I have had >BSOD's for a week now and don't know why. The only thing our computers have in common >(that I see at first glance) is the GeForce4 card... > >My BSOD's show STOP 0x00000050 or 0x0000008E with PAGE_FAULT_IN_NONPAGED_AREA. Sometimes >nv4_disp.dll is faulty and sometimes win32k.sys and even wmaud.sys once (I think). > >Athlon 2400+ >Asus A7N8X (nForce2 chipset) >512 MB DDR 2700 >Asus GeForce4 Ti4600 > > [Reply or follow-up to this message] re: BSOD, win32k.sys Tuesday, August 12, 2003 at 7:24 am Posted by Digitair (1 messages posted) Hi there, I've read about this problem. I heard that a solution could be (for some people): change the voltage setting on the MB from 3.45V (Default) to 3.3V Heard good things about this solution... On Wednesday, August 6, 2003 at 6:56 pm, Billy wrote: >Hey, I have been getting these STOP: 0x0000008E (0xc0000005, etc... and just got >a win32k.sys BSOD. I am running a AMD XP1700+ o'clocked to 2100mhz (10.5 x 200), >on an Abit NF7-S v2.0 with OCZ LL PC3200 memory (dual channel enabled) also at 200mhz >(400mhz effective) timings set at turbo and a Radeon 7500. My cpu temps are never >above 50c under 100% load when overclocked. I always run my memory and cpu at the >default settings when loading the OS then turn up the ......... [Reply or follow-up to this message] re: BSOD, win32k.sys Wednesday, August 13, 2003 at 6:59 pm Posted by Walt D in LV (3 messages posted) I was having the same problem and it was driving me CRAZY! I'm having the same problem.. BSOD with win32k.sys as the culprit, AND PAGE_FAULT_IN_NONPAGED_AREA followed by a restart. I have a MSI 651 combo motherboard 512 MB DDR RAM (333) on-board video (SIS 651) Audigy2 Platinum sound card Pentium 4 2400 Mhz I've tried changing out the memory to a 256 MB SDRam, updated video driver.. I AM having trouble with the USB 2 driver install. Seems I can MAKE the BSOD happen with Microsoft's Zoo Tycoon (dinosaur digs), or running the DVD player. The BSOD usually happens at about 10 minutes or less. Yes, not right away. Okay! So finally.. 8-13-03.. I seem to have fixed it but changing my 512 MB 333 DDR ram(2700) with 512 MB Kingston-brand 2100 DDR. All seems to be working fine now. Good luck.. I say Keep trying different RAM and RAM configurations! Two weeks of headache was solved by $70 in RAM. Oh, and the store I bought it from (Fry's) said they'd take it back if I didn't need/want it! [Reply or follow-up to this message] re: BSOD, win32k.sys Thursday, September 4, 2003 at 8:30 am Posted by Matt (1 messages posted) I have the same BSOD using the MSI and SiS 651 video..Seems to be a conection there..Mine are in a notebook, so heating may be a big factor or not. Lets keep looking. On Wednesday, August 13, 2003 at 6:59 pm, Walt wrote: >I was having the same problem and it was driving me CRAZY! > >I'm having the same problem.. >BSOD with win32k.sys as the culprit, AND >PAGE_FAULT_IN_NONPAGED_AREA >followed by a restart. > >I have a MSI 651 combo motherboard >512 MB DDR RAM (333) >on-board video (SIS 651) >Audigy2 Platinum sound card >Pentium 4 2400 Mhz > >I've tried changing out the memory to a 256 MB SDRam, updated video driver.. > >I AM having trouble with the USB 2 driver install. > >Seems I can MAKE the BSOD happen with Microsoft's Zoo Tycoon (dinosaur digs), or >running the DVD player. The BSOD usually happens at about 10 minutes or less. Yes, >not right away. > >Okay! So finally.. 8-13-03.. I seem to have fixed it but changing my 512 MB 333 DDR >ram(2700) with 512 MB Kingston-brand 2100 DDR. All seems to be working fine now. > >Good luck.. I say Keep trying different RAM and RAM configurations! Two weeks of >headache was solved by $70 in RAM. Oh, and the store I bought it from (Fry's) said >they'd take it back if I didn't need/want it! > > [Reply or follow-up to this message] re: BSOD, win32k.sys Friday, September 5, 2003 at 11:00 pm Posted by goliathdrakken (1 messages posted) unfortuntely i couldnt change those settings on my board, i was able to fix the problem by changing the jumpers on my master hard disk. On Monday, January 20, 2003 at 9:47 pm, Olivier Hubert wrote: >Ok, I solved my problem, but my solution probably won't apply to all (if any) of >you guys. I have an option with my board (Asus A7N8X) for RAM timing and I only had >to change the RAM timing from "Optimal" to "Sync", which effectively lowers the RAM >speed. > >For those without this option, try lowering your memory speed (133Mhz worked for >me) or try switching RAM Dimms/Simms. There errors are usually symptoms of memory >problems. Also try to test you RAM using memtest-86 (http://www.memtest86.com/), >it found some errors while my RAM was using a higher clock speed but none with my >current 133Mhz. > >HTH > >Olivier > > [Reply or follow-up to this message] re: BSOD, win32k.sys Saturday, September 13, 2003 at 5:35 am Posted by Danny (1 messages posted) HEre's a new member of the clan with tis problem! new computer bought a week ago - built it myself. Windows XP (no sp1) - Running an Athlon XP2500+, MSI geforce 4 Ti4200, 2x256 mb geil pc3200 ultra ram, asus kt600 m/b, seagate s/ata hard drive, sb live... I can't say I ever got the BSODs indicating nvdisp as error. I did get all the other BSODS though. But, I have changed the memory frequency for the ram from 'auto' to 333 mhz in the bios, and am trying it out... The athlon xp2500 only runs at 333 mhz bus anyway... but, perhaps the whole idea is balancing out the system, basing it around the processor bus speed. i.e if bus speed of processor is 266, ram should be the same etc... The only athlon you should run 3200 ram at full speed with with is an athlon 3200+ as it's the only one that supports 400 mhz ram! p.s all my drivers are default drivers, but as i've changed the bus speed of the ram to the same speed as the processor, it's running for longer than it has before without crashing... (fingers crossed) My tip is to just make your entire computer as even as possible when it comes to speed... It might solve the problems. p.p.s you guys have given me a great deal of moral support by letting me know I wasn't the only one with the frustration! p.p.p.s I NEVER WANT TO SE ANOTHER BLUE SCREEN AGAIN IN MY LIFE!!!!!!!!!!!!!!!!!!!!! On Thursday, September 4, 2003 at 8:30 am, Matt wrote: >I have the same BSOD using the MSI and SiS 651 video..Seems to be a conection there..Mine >are in a notebook, so heating may be a big factor or not. Lets keep looking. > > [Reply or follow-up to this message] re: BSOD, win32k.sys Saturday, September 13, 2003 at 4:49 pm Posted by Miss Shamen (1 messages posted) Greetings everyone, I too was having this problem, and it seemed to be totally random, but in fact, it is not. I am using a Asus a7v333 board AMD xp 2400+ CPU 1 gig of ddr memory 128mb geforce 4 ti4200 agp card. etc. Ever since i built this machine up, I have had that problem with win32k.sys It is a heat related problem, and here is how i know. I noticed that whenever i watched mpg's it would crash, if i played games it crashed, or if i was looking or working on pictures it crashed. and it crashed less at night cause i normally have windows open at night, so room was cooler. I installed a program called CPU cooler, got it from the fosi site: http://fosi.da.ru Since that helps cool the processor down, i noticed the crashes were less frequent. Then I stripped my machine down, and fitted a case fan, and move my sound card two slots away from my vid card, so the fan on vid card had plenty of room to do it's work, now at that point, the crashes got very rare, but still happened. So, I thought, what else could be wrong? and decided to buy a copper cooler which fits on top of cpu, bloody big thing it is, you can see what it is from this link. http://prices.cclcomputers.co.uk/specs/cooler/zalman/CNPS6000CU/spec.htm I fitted that, and now i have been downloading from mirc while playing diablo2 expansion online, watching vids etc, and so far not one crash. And I am running winxp professional with all updates on. So I can honestly say, it is a heat related problem, and i can seriously recommend that copper cooler, my machine is seriously cool now. You can download cpu cooler from this link. http://64.224.86.74/555/fosi/new-test/fo-idl6b.zip Hope that helps you all, and a big thank you to everyone who has posted to this subject. All the best Leandra XxX On Tuesday, June 17, 2003 at 2:17 am, Subz wrote: >Worked fine with XP Pro (not SP-1)! >Checked the drivers for the Radeon and found it was actually 7.84, not 7.88. > >Reinstalled XP Pro (with SP-1) and installed the very latest drivers and so far, >no problems either. Very odd. > >I don't think I've seen the last of this error though. > >Cheers, >Subz - "It'll never work" - (The Eternal Cynic) > [Reply or follow-up to this message] re: BSOD, win32k.sys Monday, September 15, 2003 at 7:19 pm Posted by Steven Z (5 messages posted) Here is one for you guys. This refutes a good deal of the suggestions that are up here (sorry). I am running a watercooling system on a P4 2.4GhzC with a GeforceFX 5900 and 512meg of dual channel Corsair matched pair XMS pc3200. Nothing is overclocked. I have tried MSI drivers for my card (44.03 specifically made for MSI cards by MSI) I have tried the latest detonators. I have tried WHQL certified drivers. I have tried the original drivers WinXP(SP-1 with all updates). I have tried updating my system bios as well as all the applications in use when the system crashed. Mostly I would get PAGE_FAULT error with nothing specified but a few times I got win32k.sys and nv4_disp.dll. I downloaded the debugging tools from microsoft and ran a debug on the MINIDUMP file that was written. I can tell you where/how to get these as well as the command line needed to run to recognized what specifically caused the crash. I can tell this is not a heat problem for me as my temp never goes over 30C. All the parts are brand new in this machine. It is not hardware. The only thing this could be that people have suggested is the service pack 1 or the video drivers. Anyone have any other ideas?? or comments on my experience? On Saturday, September 13, 2003 at 5:35 am, Danny wrote: >HEre's a new member of the clan with tis problem! new computer bought a week ago >- built it myself. Windows XP (no sp1) - Running an Athlon XP2500+, MSI geforce 4 >Ti4200, 2x256 mb geil pc3200 ultra ram, asus kt600 m/b, seagate s/ata hard drive, >sb live... I can't say I ever got the BSODs indicating nvdisp as error. I did get >all the other BSODS though. But, I have changed the memory frequency for the ram >from 'auto' to 333 mhz in the bios, and am trying it out... The athlon xp2500 only >runs at 333 mhz bus anyway... but, perhaps the whole idea is balancing out the system, >basing it around the processor bus speed. i.e if bus speed of processor is 266, ram >should be the same etc... The only athlon you should run 3200 ram at full speed with >with is an athlon 3200+ as it's the only one that supports 400 mhz ram! > >p.s all my drivers are default drivers, but as i've changed the bus speed of the >ram to the same speed as the processor, it's running for longer than it has before >without crashing... (fingers crossed) My tip is to just make your entire computer >as even as possible when it comes to speed... It might solve the problems. > >p.p.s you guys have given me a great deal of moral support by letting me know I wasn't >the only one with the frustration! > >p.p.p.s I NEVER WANT TO SE ANOTHER BLUE SCREEN AGAIN IN MY LIFE!!!!!!!!!!!!!!!!!!!!! > > > > [Reply or follow-up to this message] re: BSOD, win32k.sys Tuesday, September 16, 2003 at 10:11 pm Posted by Wizlil (2 messages posted) Hi all, September for me too :) and STILL this boring PAGE_FAULT blue screen msg. ALWAYS win32k.sys, but... ...I got some news for you (don't know if bad or good). I'm having this prob NOW with Xp sp1, but I had it with Xp (no sp1) TOO ! And what's more, I DON'T have AMD but I have INTEL cpu, PIII, 1 Ghz, Matrox G550 and SBLive Platinum. NOTHING ELSE... No software installed...(just to check and hopefully SOLVE this prob). No overheating (around 30°)... I've checked my RAM (SDRAM PC 133) and found 2 of them working bad.....so I removed 'em (512 Mb lost....) Now I'm testing your last advice : I'm using only ONE 256 Mb Ram, coz after AIDA's report I discovered that my last two RAM's were made by DIFFERENT producers..... Hope THIS could be the REAL solution.....but I wonder....will I solve evrything only buying Ram modules from a unique producer ??? Or have I to suspect that it works only with ONE RAM bank ?? I mean...... I had 4 banks.... 2 were damaged....(and removed) The other two were GREAT !!!!! .... But XP seem not to crash no more only using ONE of them !!!!!!!!! Have I REALLY to lose 3x256Mb RAM banks ??? I had 1 GB............I STILL WANT 1 Gb !!!!!!!!! On Monday, September 15, 2003 at 7:19 pm, Steven Z wrote: >Here is one for you guys. This refutes a good deal of the suggestions that are up >here (sorry). I am running a watercooling system on a P4 2.4GhzC with a GeforceFX >5900 and 512meg of dual channel Corsair matched pair XMS pc3200. Nothing is overclocked. > I have tried MSI drivers for my card (44.03 specifically made for MSI cards by MSI) >I have tried the latest detonators. I have tried WHQL certified drivers. I have >tried the original drivers WinXP(SP-1 with all updates). I have tried updating my >system bios as well as all the applications in use when the system crashed. Mostly >I would get PAGE_FAULT error with nothing specified but a few times I got win32k.sys >and nv4_disp.dll. I downloaded the debugging tools from microsoft and ran a debug >on the MINIDUMP file that was written. I can tell you where/how to get these as >well as the command line needed to run to recognized what specifically caused the >crash. I can tell this is not a heat problem for me as my temp never goes over 30C. > All the parts are brand new in this machine. It is not hardware. The only thing >this could be that people have suggested is the service pack 1 or the video drivers. > Anyone have any other ideas?? or comments on my experience? > > [Reply or follow-up to this message] re: BSOD, win32k.sys Wednesday, September 17, 2003 at 12:21 pm Posted by Davis (4 messages posted) I'd really like to know whether or not using more than one module has been the source of the problem for anyone else. I just upgraded my single module (factory installed) of 256k with two 512k modules (from crucial.com) and had the same problems with Stop errors. I have NEVER had them before, so it's freaking me out. I removed one of the 512k modules, so test run them and see if one was causing a problem...but now you've made me wonder if it's the fact that I was using both slots. *sigh* There are so many "possible" solutions...it's making my head swim. I don't buy the "overheating" thing for my system. I'm in Mississippi, and this room has been AT LEAST 15-20 degrees hotter on July afternoons than it was yesterday when I started having the problem.....within 1hour of installing the new RAM modules. I took out one of the modules last night, and turned the computer back on this morning. I've been running for 8 hours with no problems. I even left the 512K module in the 2nd slot, whereas my old 256K module had been seated in the 1st slot. Things look fine now...but...I'm going to run a tester on each module....and, if I don't find errors on either one...I want to know if I'm just stuck with just being able to use one memory slot. This sucks On Tuesday, September 16, 2003 at 10:11 pm, Wizlil wrote: >Hi all, >September for me too :) and STILL this boring PAGE_FAULT blue screen msg. >ALWAYS win32k.sys, but... > >...I got some news for you (don't know if bad or good). >I'm having this prob NOW with Xp sp1, but I had it with Xp (no sp1) TOO ! >And what's more, I DON'T have AMD but I have INTEL cpu, PIII, 1 Ghz, Matrox G550 >and SBLive Platinum. >NOTHING ELSE... > >No software installed...(just to check and hopefully SOLVE this prob). >No overheating (around 30°)... > >I've checked my RAM (SDRAM PC 133) and found 2 of them working bad.....so I removed >'em (512 Mb lost....) >Now I'm testing your last advice : I'm using only ONE 256 Mb Ram, coz after AIDA's >report I discovered that my last two RAM's were made by DIFFERENT producers..... > >Hope THIS could be the REAL solution.....but I wonder....will I solve evrything only >buying Ram modules from a unique producer ??? >Or have I to suspect that it works only with ONE RAM bank ?? > >I mean...... > >I had 4 banks.... > >2 were damaged....(and removed) > >The other two were GREAT !!!!! .... > >But XP seem not to crash no more only using ONE of them !!!!!!!!! > >Have I REALLY to lose 3x256Mb RAM banks ??? > >I had 1 GB............I STILL WANT 1 Gb !!!!!!!!! > > > > [Reply or follow-up to this message] re: BSOD, win32k.sys Wednesday, September 17, 2003 at 3:31 pm Posted by Wizlil (2 messages posted) Well, the only thing I can say is that after 10 days of tests, now I have NO crashes simply using ONE module..... 'Coz using even just TWO tested and good working modules, crashes start again......... Interesting..... :) But I HATE to have to leave the ohter three slots WITHOUT RAM !!!!!!!!........ On Wednesday, September 17, 2003 at 12:21 pm, Davis wrote: >I'd really like to know whether or not using more than one module has been the source >of the problem for anyone else. I just upgraded my single module (factory installed) .......... [Reply or follow-up to this message] re: BSOD, win32k.sys Sunday, September 21, 2003 at 11:54 am Posted by Lexy (1 messages posted) I, too, have the same problems described in this list to one varying degree or another. My system is self-built with MSI-645 ultra mb, p4 1.6ghz northwood, 512mb RAM ddr333, nvidia geForce4 mx 440 video card (prev ATI rage fury) running XP pro not updated to SR1. Recently patched XP with security updates. I have turned myself inside out trying to find a "cure" for this beast. For the most part, everyone here seems sure it's NOT hardware related. However, I see a lot of MSI motherboards and I'm wondering if it's not a bad board. Anyone have a suggestion for a *good* utility to test a board. (I did 48 hrs of burn in after getting my box together, but that was almost a year ago, board could have corrupted in some way) I have had periods where to problem becomes minimal, and periods where it's several times an hour. I'm in a "several-times-an-hour" period now, after installing a ton of XP security updates, not sp1 and different antivirus software due to the recent worm threats. At first, I thought maybe a virus, but thorough scanning results are negative. Also uninstalled antivirus to see if the problem went away, and it didn't. Reinstalled different software, problem doesn't seem be affected. Someone suggested AMD/XP incompatibility, however I have an intel. All roads seem to point back to XP, but yet some of you have had success with hardware modification thru bios or cooling or one stick of ram. i still think it's a bad motherboard but my experience isn't in circuitry so it's only a guess. any knowledgeable motherboard people out there, give us some feedback please. this problem has me craaazzzy. On Wednesday, September 17, 2003 at 12:21 pm, Davis wrote: >I'd really like to know whether or not using more than one module has been the source >of the problem for anyone else. I just upgraded my single module (factory installed) >of 256k with two 512k modules (from crucial.com) and had the same problems with Stop >errors. I have NEVER had them before, so it's freaking me out. I removed one of >the 512k modules, so test run them and see if one was causing a problem...but now >you've made me wonder if it's the fact that I was using both slots. *sigh* There >are so many "possible" solutions...it's making my head swim. >I don't buy the "overheating" thing for my system. I'm in Mississippi, and this >room has been AT LEAST 15-20 degrees hotter on July afternoons than it was yesterday >when I started having the problem.....within 1hour of installing the new RAM modules. >I took out one of the modules last night, and turned the computer back on this morning. > I've been running for 8 hours with no problems. I even left the 512K module in >the 2nd slot, whereas my old 256K module had been seated in the 1st slot. Things >look fine now...but...I'm going to run a tester on each module....and, if I don't >find errors on either one...I want to know if I'm just stuck with just being able >to use one memory slot. >This sucks > > [Reply or follow-up to this message] re: BSOD, win32k.sys Tuesday, September 30, 2003 at 2:32 pm Posted by Steven Z (5 messages posted) Here is the link for the debugging tools: http://www.microsoft.com/whdc/ddk/debugging/default.mspx Here is the command line that I use with it: windbg -y SRV*c:\symbols*http://msdl.microsoft.com/download/symbols -i c:\i386 -z C:\WINDOWS\Minidump\Mini092903-02.dmp that is using the default minidump directory and using a symbol path of C:\symbols. The symbols are dld from the url you see. This will give you the information you need. A lot of times I get "memory_corruption" as the cause. Sometimes i get win32k.sys sometimes nv4_disp.dll I am still narrowing down the problem. Good luck! On Monday, September 15, 2003 at 7:19 pm, Steven Z wrote: >Here is one for you guys. This refutes a good deal of the suggestions that are up >here (sorry). I am running a watercooling system on a P4 2.4GhzC with a GeforceFX >5900 and 512meg of dual channel Corsair matched pair XMS pc3200. Nothing is overclocked. > I have tried MSI drivers for my card (44.03 specifically made for MSI cards by MSI) >I have tried the latest detonators. I have tried WHQL certified drivers. I have >tried the original drivers WinXP(SP-1 with all updates). I have tried updating my >system bios as well as all the applications in use when the system crashed. Mostly >I would get PAGE_FAULT error with nothing specified but a few times I got win32k.sys >and nv4_disp.dll. I downloaded the debugging tools from microsoft and ran a debug >on the MINIDUMP file that was written. I can tell you where/how to get these as >well as the command line needed to run to recognized what specifically caused the >crash. I can tell this is not a heat problem for me as my temp never goes over 30C. > All the parts are brand new in this machine. It is not hardware. The only thing >this could be that people have suggested is the service pack 1 or the video drivers. > Anyone have any other ideas?? or comments on my experience? > > [Reply or follow-up to this message] re: BSOD, win32k.sys Friday, October 3, 2003 at 5:24 am Posted by Ryan Ruckel (2 messages posted) System ran fine till I tried Planetside, which I thought just didn't like WinME. Installed XPPro on blank partition and updated to SP1, still hangs in PS but also in BattleField1942 (and various BF mods), which it never did under WinME (go figure). Have 80 mm fan sitting on the Ti4400 blowing on back of GPU/vidmemory as well as memory and CPU (clever placement is key). Doesn't help. Removing sound card completely from the case and all drivers very carefully as per "cleansweep" instructions at creative.com did not help, nor did setting ALL BIOS settings to "failsafe" or "optimized" or using EVGA video troubleshooting settings. Latest trick is to use this option to completely remove Detonator driver remains for the Ti: *remove the software from add/remove *remove the card from hardware list *restart in safe mode and search for nv*.* files *delete them all, Nvidia folder, empty trash, and clean temp files in windows\temp and c:\temp if you have them. May not work, but will help rule out "sticky" drivers--I was surprised that detonator destroyer and detonator RIP had not gotten a LOT of nv*.* files... will post results. Thanks for the debugging info and ALL the other posts. Next is remove memory, which is in three sticks of Crucial PC2700 (2x256, 1x512)--Crucial tech told me this memory config on this board should make no difference. Making me cranky, this prob. In case it helps, here's some specs: Self-built AMD system: XP2400+ w. Speeze copper slug cooler (Winbond HW monitor has it running in the 40's C), Abit Kx-333R (w/o RAID eneabled), 1Gig Crucial PC2700 memory running at diff timings--currently maxed because basic timings did not help), GF4Ti4400 (EVGA) 128, Audigy, but removed/replaced w. CMI8738 CheeseyCard... etc. All latest Via drivers, carefully installed, Dx9.0b, etc. On Tuesday, September 30, 2003 at 2:32 pm, Steven Z wrote: >Here is the link for the debugging tools: >http://www.microsoft.com/whdc/ddk/debugging/default.mspx > >Here is the command line that I use with it: >windbg -y SRV*c:\symbols*http://msdl.microsoft.com/download/symbols -i c:\i386 -z >C:\WINDOWS\Minidump\Mini092903-02.dmp > >that is using the default minidump directory and using a symbol path of C:\symbols. > The symbols are dld from the url you see. This will give you the information you >need. A lot of times I get "memory_corruption" as the cause. Sometimes i get win32k.sys >sometimes nv4_disp.dll >I am still narrowing down the problem. Good luck! > [Reply or follow-up to this message] re: BSOD, win32k.sys Friday, October 3, 2003 at 12:40 pm Posted by Steven Z (5 messages posted) Just a thought/question I had along with some other info. What antivirus are you guys running? Im running kaspersky but ever since i turned it off i haven't crashed. but sadly i updated video drivers at the same time. to the det 4533 i do believe. Anyone with nvidia cards go to www.guru3d.com and get the latest or fool around with other versions. Also here's a link http://support.microsoft.com/?kbid=329052#appliesto http://support.microsoft.com/default.aspx?scid=kb;en-us;329293 On Friday, October 3, 2003 at 5:24 am, Ryan Ruckel wrote: >System ran fine till I tried Planetside, which I thought just didn't like WinME. > Installed XPPro on blank partition and updated to SP1, still hangs in PS but also >in BattleField1942 (and various BF mods), which it never did under WinME (go figure). > > >Have 80 mm fan sitting on the Ti4400 blowing on back of GPU/vidmemory as well as >memory and CPU (clever placement is key). Doesn't help. Removing sound card completely >from the case and all drivers very carefully as per "cleansweep" instructions at >creative.com did not help, nor did setting ALL BIOS settings to "failsafe" or "optimized" >or using EVGA video troubleshooting settings. > >Latest trick is to use this option to completely remove Detonator driver remains >for the Ti: >*remove the software from add/remove >*remove the card from hardware list >*restart in safe mode and search for nv*.* files >*delete them all, Nvidia folder, empty trash, and clean temp files in windows\temp >and c:\temp if you have them. >May not work, but will help rule out "sticky" drivers--I was surprised that detonator >destroyer and detonator RIP had not gotten a LOT of nv*.* files... will post results. > > >Thanks for the debugging info and ALL the other posts. Next is remove memory, which >is in three sticks of Crucial PC2700 (2x256, 1x512)--Crucial tech told me this memory >config on this board should make no difference. > >Making me cranky, this prob. > >In case it helps, here's some specs: >Self-built AMD system: XP2400+ w. Speeze copper slug cooler (Winbond HW monitor has >it running in the 40's C), Abit Kx-333R (w/o RAID eneabled), 1Gig Crucial PC2700 >memory running at diff timings--currently maxed because basic timings did not help), >GF4Ti4400 (EVGA) 128, Audigy, but removed/replaced w. CMI8738 CheeseyCard... etc. > All latest Via drivers, carefully installed, Dx9.0b, etc. > > [Reply or follow-up to this message] re: BSOD, win32k.sys Saturday, October 4, 2003 at 7:44 am Posted by Ryan Ruckel (2 messages posted) *laughing*: Ok, so what does THIS MEAN? "CAUSE A null pointer may be used for pwndStart if all the child windows of the desktop are topmost windows, and this null pointer causes the access violation. STATUS Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article. " Just using Norton AV but it's disabled. My other (most irksome) symptoms are frequent crashes to desktop in BF42. On Friday, October 3, 2003 at 12:40 pm, Steven Z wrote: > >Just a thought/question I had along with some other info. > >What antivirus are you guys running? Im running kaspersky but ever since i turned >it off i haven't crashed. but sadly i updated video drivers at the same time. to >the det 4533 i do believe. Anyone with nvidia cards go to www.guru3d.com and get >the latest or fool around with other versions. Also here's a link > >http://support.microsoft.com/?kbid=329052#appliesto > >http://support.microsoft.com/default.aspx?scid=kb;en-us;329293 > [Reply or follow-up to this message] re: BSOD, win32k.sys Sunday, October 5, 2003 at 12:53 am Posted by jose (1 messages posted) >p.p.p.s I NEVER WANT TO SE ANOTHER BLUE SCREEN AGAIN IN MY LIFE!!!!!!!!!!!!!!!!!!!!! then go with linux, man [Reply or follow-up to this message] re: BSOD, win32k.sys Sunday, October 5, 2003 at 7:58 pm Posted by Larry (1 messages posted) This is in response to the the entire forum concerning the BSOD, stop messages of page fault, ati3d2ag.dll, ati2dvag.dll, win32k.sys and others. I was getting the BSOD with one nessage or the other at least 4 times an hour: when I would click a link, attempt a virus scan, send an email, just about anything. Everytime I would come into the room it would be on BSOD. But, THANKS to the very perceptive people on this forum, my problem has been solved. I have Win XP Pro running on Athlon XP 1.8 gb, 2X256 mb 2700 ram (made in China), 120 gb hd, radeon 9000 graphics. I ordered and installed 512 mb Crucial 3200 and am happy and delighted to say that it has now been 80 hours and not once has it locked up. From the way the forum read, ram seems to be the most prevalent constant. For $93 it is up and running. From reading this, you can tell I am not a techie, just an old duffer. In fact, that was the first time I had had the back off of a computer. Thanks again, Larry. On Friday, September 6, 2002 at 5:38 am, edu wrote: >Periodically I get BSOD's identifying the driver win32k.sys in the message... When >they appear I'm not doing anything in particular or using any particular program... >anyone know why this happens? (Athlon 1.4 GHZ, 256MB DDRAM, Geforce Mx-400...) [Reply or follow-up to this message] re: BSOD, win32k.sys Wednesday, October 8, 2003 at 1:13 pm Posted by Murray (1 messages posted) Been havin this prob for a while now really getttin to me, has anyone found a solution yet? Cheers Murray On Sunday, October 5, 2003 at 7:58 pm, Larry wrote: > This is in response to the the entire forum concerning the BSOD, stop messages of >page fault, ati3d2ag.dll, ati2dvag.dll, win32k.sys and others. I was getting the >BSOD with one nessage or the other at least 4 times an hour: when I would click a >link, attempt a virus scan, send an email, just about anything. Everytime I would >come into the room it would be on BSOD. But, THANKS to the very perceptive people >on this forum, my problem has been solved. I have Win XP Pro running on Athlon >XP 1.8 gb, 2X256 mb 2700 ram (made in China), 120 gb hd, radeon 9000 graphics. I >ordered and installed 512 mb Crucial 3200 and am happy and delighted to say that >it has now been 80 hours and not once has it locked up. From the way the forum read, >ram seems to be the most prevalent constant. For $93 it is up and running. From >reading this, you can tell I am not a techie, just an old duffer. In fact, that >was the first time I had had the back off of a computer. Thanks again, Larry. > > [Reply or follow-up to this message] re: BSOD, win32k.sys Friday, October 10, 2003 at 6:24 am Posted by yann (1 messages posted) Sorry, I haven't seen your solution... Forget my message. Thks. (what about SQLI ?) [Reply or follow-up to this message] 512 DDR Kingston Ram, ASUS A7V600 Motherboard and Winfast A340 TD Saturday, October 11, 2003 at 9:02 pm Posted by Justin (1 messages posted) I have an Athlon 2400, 512 DDR Kingston Ram, ASUS A7V600 Motherboard and Winfast A340 TD all running on windows XP (built myself). I had all the above mentioned errors so I got the latest drivers and tested the hardware. I still had errors. I tried numerous suggestions from the VIArena to fix it (I knew it was memory). The problem was that my ram was auto set to 400mhz and the motherboard was 333mhz bus and didnt like it. So that and reducing the virtual memeroy in windows XP fixed it all and I have never had a blue screen since. If you have the same setup and need help (I wish I could have emailed someone) then remove the nospam from my addy and email. [Reply or follow-up to this message] Q827663 - Random ''0x0000008E'' Error Message on a Blue Screen in Windows XP - Solution Sunday, October 12, 2003 at 9:08 pm Posted by Bashar Hamdan (1 messages posted) There is a solution for this stupid problem we are all having: there is an updated win32k.sys file instead of the current one causing the issue. The rsoultion is at the microsoft technet site under article Q827663. The filedate is Aug 2003, so it's new. You can access it here: http://support.microsoft.com/default.aspx?scid=kb;en-us;827663 Catch is they say it is provided on 'as needed bases' not a simple download. If anyone would be kind enough as to call them or email them and get this file please share the wealth and email it to me at bashsoft@yahoo.com and I'll be indebted to you. Thanks [Reply or follow-up to this message] re: Q827663 - Random ''0x0000008E'' Error Message on a Blue Screen in Windows XP - Solution Wednesday, October 22, 2003 at 12:29 pm Posted by Steven Z (5 messages posted) Bashar thank you for the heads up. I did some searching and came across some pre servicepack 2 patches in this document http://www.gc.peachnet.edu/www/wbeck/Patches/XP_Patches_Ver1.3.doc in here you will find a link to a patch that replaces win32k.sys. now keep in mind that this is a security patch and not a patch for the exact problem we're having. but i figured they couldn't make that many versions of win32k.sys and i am assuming that this is the version you found in that knowledgebase article. i have applied it and will report here if i see any "unusual" stability lol. thanks keep this community going we'll fix our problems yet! On Sunday, October 12, 2003 at 9:08 pm, Bashar Hamdan wrote: >There is a solution for this stupid problem we are all having: there is an updated >win32k.sys file instead of the current one causing the issue. The rsoultion is at >the microsoft technet site under article Q827663. The filedate is Aug 2003, so it's >new. You can access it here: >http://support.microsoft.com/default.aspx?scid=kb;en-us;827663 > >Catch is they say it is provided on 'as needed bases' not a simple download. If anyone >would be kind enough as to call them or email them and get this file please share >the wealth and email it to me at bashsoft@yahoo.com and I'll be indebted to you. > >Thanks [Reply or follow-up to this message] re: Q827663 - Random ''0x0000008E'' Error Message on a Blue Screen in Windows XP - Solution Saturday, November 1, 2003 at 9:43 am Posted by Masterofe55 (1 messages posted) Can't wait for the SP2 to arrive! I'm done with XP since I tried every Version of it: XP Home, Pro, w/SP1, w/o SP1! I 'm glad I'm not the only person ecountering this problem! My Sys: XP 1900+ (Palomino) Asus A7S333 1006 Bios 512 MB Samsung DDR333 Cl2.5 Samsung 1604 160 GB Radeon 8500 128MB DDR OS: Win2k + Linux :-)! I hope I can switch back to XP whenever SP2 is available! I am really tired of 2k! On Wednesday, October 22, 2003 at 12:29 pm, Steven Z wrote: >Bashar thank you for the heads up. I did some searching and came across some pre >servicepack 2 patches in this document > >http://www.gc.peachnet.edu/www/wbeck/Patches/XP_Patches_Ver1.3.doc > >in here you will find a link to a patch that replaces win32k.sys. now keep in mind >that this is a security patch and not a patch for the exact problem we're having. > but i figured they couldn't make that many versions of win32k.sys and i am assuming >that this is the version you found in that knowledgebase article. i have applied >it and will report here if i see any "unusual" stability lol. > >thanks > >keep this community going we'll fix our problems yet! > > [Reply or follow-up to this message] re: Q827663 - Random ''0x0000008E'' Error Message on a Blue Screen in Windows XP - Solution Wednesday, November 12, 2003 at 9:25 pm Posted by Steven Z (5 messages posted) Well my problem is fixed. It turns out that there was an issue with my bios version F6 for the giga-byte motherboard 8knxp and corsair XMS modules. This solution was only possible thanks to the people at www.amdmb.com and www.houseofhelp.com I hope you all find a resolution too... On Saturday, November 1, 2003 at 9:43 am, Masterofe55 wrote: >Can't wait for the SP2 to arrive! I'm done with XP since I tried every Version of >it: XP Home, Pro, w/SP1, w/o SP1! >I 'm glad I'm not the only person ecountering this problem! > >My Sys: >XP 1900+ (Palomino) >Asus A7S333 1006 Bios >512 MB Samsung DDR333 Cl2.5 >Samsung 1604 160 GB >Radeon 8500 128MB DDR >OS: Win2k + Linux :-)! > >I hope I can switch back to XP whenever SP2 is available! I am really tired of 2k! > > [Reply or follow-up to this message] re: Q827663 - Random ''0x0000008E'' Error Message on a Blue Screen in Windows XP - Solution Thursday, December 4, 2003 at 7:32 am Posted by Tracy S Gosdis (1 messages posted) I tried everything. Updates, SP1, no SP1, reinstalls, memory swapping, video card swapping, EVERYTHING. It started to get worse and so as a last ditch effort I replaced my motherboard. I run my pc 24/7 and since I swapped motherboards 4 months ago I haven't had even one crash. Good luck all! On Saturday, November 1, 2003 at 9:43 am, Masterofe55 wrote: >Can't wait for the SP2 to arrive! I'm done with XP since I tried every Version of >it: XP Home, Pro, w/SP1, w/o SP1! >I 'm glad I'm not the only person ecountering this problem! > >My Sys: >XP 1900+ (Palomino) >Asus A7S333 1006 Bios >512 MB Samsung DDR333 Cl2.5 >Samsung 1604 160 GB >Radeon 8500 128MB DDR >OS: Win2k + Linux :-)! > >I hope I can switch back to XP whenever SP2 is available! I am really tired of 2k! > > [Reply or follow-up to this message] re: BSOD, win32k.sys Tuesday, December 23, 2003 at 1:57 pm Posted by Roger Labonté (1 messages posted) I assembled a machine with a P4 2.60GHz, an ASUS P4S800, 512Mb of generic RAM and an ASUS FX-5200 Majic. I was getting the stupid BSOD with the page fault error in nv4_disp.dll every time Windows XP (w SP1) would try to boot in a mode other that VGA. Changing the resolution or refresh rate while Windows was in VGA mode would result in a cute matrix of ASCII characters... I solved the problem by removing a PCI Fastrak 66 RAID controller that was connected to my motherboard. Hope this helps somebody some day. David, Quebec City. On Friday, August 8, 2003 at 1:12 pm, Jim wrote: >I was having the same problem until i read up a bit. >After i installed my new fx5200 graphics card i was getting the BSOD and the win32k.sys >error. >I sorted it by looking at my memory. I had a 128MB Memory stick and a 512MB in both >made by different companies. I took out the 128 and have not had this problem again >since. >So check your memory and see if that works. >Cheap answer for me anyhow :-) > > [Reply or follow-up to this message] re: BSOD, win32k.sys Sunday, January 18, 2004 at 9:14 am Posted by Clark (1 messages posted) Try the procedure in the URL I've provided at the end of this message. This fixed a consistent BSOD from win32k.sys and "page fault in nonpaged area" errors in XP Home I started getting after upgrading Acrobat Reader. I didn't do all the steps, just the ones where the boot files are copied from the XP Repair directory. System then booted OK and I grabbed a System Restore point. Clark On Wednesday, October 8, 2003 at 1:13 pm, Murray wrote: >Been havin this prob for a while now really getttin to me, has anyone found a solution >yet? > >Cheers Murray > > http://www.digitalwebcast.com/2002/03_mar/tutorials/cw_boot_toot.htm [Reply or follow-up to this message] re: BSOD, win32k.sys Wednesday, January 28, 2004 at 1:19 pm Posted by Ian Roberts (1 messages posted) What version is your BIOS? I just updated to C18E1008 for my A7N8X-E Deluxe. No more BSODs. On Tuesday, January 14, 2003 at 8:50 pm, Olivier Hubert wrote: >Ok I'm relieved now, I thought I was the only one going mad with this. I have had >BSOD's for a week now and don't know why. The only thing our computers have in common >(that I see at first glance) is the GeForce4 card... > >My BSOD's show STOP 0x00000050 or 0x0000008E with PAGE_FAULT_IN_NONPAGED_AREA. Sometimes >nv4_disp.dll is faulty and sometimes win32k.sys and even wmaud.sys once (I think). > >Athlon 2400+ >Asus A7N8X (nForce2 chipset) >512 MB DDR 2700 >Asus GeForce4 Ti4600 > > [Reply or follow-up to this message] re: BSOD, win32k.sys Saturday, January 31, 2004 at 9:19 am Posted by daniel (1 messages posted) I SOLVE MY PROBLEM BY CHANGING THE IRQ ON MY SOUNDCARD. IT HAD THE SAME IRQ AS MY GRAPHIC CARD. THEY WERE HAVING A CONFLICT WITH EACH OTHER. THAT COULD BE A SOLOUTION TO WHY THE BLUE SCREEN POPS UP! HOPE IT HELPS!!!! On Sunday, January 18, 2004 at 9:14 am, Clark wrote: >Try the procedure in the URL I've provided at the end of this message. This fixed >a consistent BSOD from win32k.sys and "page fault in nonpaged area" errors in XP >Home I started getting after upgrading Acrobat Reader. I didn't do all the steps, >just the ones where the boot files are copied from the XP Repair directory. System >then booted OK and I grabbed a System Restore point. > >Clark > > [Reply or follow-up to this message] re: Q827663 - Random ''0x0000008E'' Error Message on a Blue Screen in Windows XP - Solution Monday, February 2, 2004 at 11:26 am Posted by Mikey G (1 messages posted) I was having the same problem with my recent PC build - Asus K8V Deluxe - AMD 64 3200+, Audigy ZS Platinum, Asylum 5700 Ultra, 1G of DDR PC3200. It seemed to go from bad to worse this weekend giving me a BSOD every time I opened my account. Curiously I logged into my girlfriends account and she wasn't getting the BSODs. After much fannying about with fan positions, memory tests etc. I ended up deleting and recreating my account, going to AMD and downloading the 64 Updates for XP, also the Utilities from the CD with my Motherboard (Heat, Fan monitor) and all seems to be OK now. It boots fine and runs Call of Duty like a dream. I spent hours chasing the heat and memory issues but it appears that by simply ensuring every component was up to date via the manufacturer fixed my problem. By the way, that Motherboard Utility (Asusprobe) is very nice. It put my mind to rest as to how hot I should be running. I'm sure the build is an ongoing process (BIOS settings, SATA RAID etc.) but I'm glad the BSODs are sorted. for the time being anyway ! Hope this helps somebody. On Thursday, December 4, 2003 at 7:32 am, Tracy S Gosdis wrote: >I tried everything. Updates, SP1, no SP1, reinstalls, memory swapping, video card >swapping, EVERYTHING. It started to get worse and so as a last ditch effort I replaced >my motherboard. I run my pc 24/7 and since I swapped motherboards 4 months ago I >haven't had even one crash. > >Good luck all! > > [Reply or follow-up to this message] re: Q827663 - Random ''0x0000008E'' Error Message on a Blue Screen in Windows XP - Solution Saturday, February 7, 2004 at 4:33 am Posted by Andrew Salvona (1 messages posted) I have had many BSOD errors in windows xp and every time i changed my hardware (memory, Psu, Mobo, Cpu) the error took on another form. From experience i belive the problems to be caused by the system memory voltage. I'm now using ami bios and in it is an option not sure what it does but mentions DIMM voltage, see if u can find somthing similer. Hope this helps. On Monday, February 2, 2004 at 11:26 am, Mikey G wrote: >I was having the same problem with my recent PC build - Asus K8V Deluxe - AMD 64 >3200+, Audigy ZS Platinum, Asylum 5700 Ultra, 1G of DDR PC3200. It seemed to go from >bad to worse this weekend giving me a BSOD every time I opened my account. Curiously >I logged into my girlfriends account and she wasn't getting the BSODs. After much >fannying about with fan positions, memory tests etc. I ended up deleting and recreating >my account, going to AMD and downloading the 64 Updates for XP, also the Utilities >from the CD with my Motherboard (Heat, Fan monitor) and all seems to be OK now. It >boots fine and runs Call of Duty like a dream. I spent hours chasing the heat and >memory issues but it appears that by simply ensuring every component was up to date >via the manufacturer fixed my problem. By the way, that Motherboard Utility (Asusprobe) >is very nice. It put my mind to rest as to how hot I should be running. I'm sure >the build is an ongoing process (BIOS settings, SATA RAID etc.) but I'm glad the >BSODs are sorted. for the time being anyway ! > >Hope this helps somebody. > > > [Reply or follow-up to this message] re: BSOD, win32k.sys Saturday, February 7, 2004 at 4:02 pm Posted by Guy (1 messages posted) Yeah I was experiencing this error too, I sent in the error report and was told by m$ that it was most-likely a ram problem. Tested my ram found no probs, looked in my bios found it had o/c'd my ram. put it back to its intended fsb, and hello, no more stop errors On Monday, July 21, 2003 at 7:23 pm, SkullFace wrote: > > > [Reply or follow-up to this message] re: Q827663 - Random ''0x0000008E'' Error Message on a Blue Screen in Windows XP - Solution Monday, February 16, 2004 at 2:33 pm Posted by Richard Shepherd (1 messages posted) Hi there, Not actually having this problem myself ( *crosses fingers* ) - but i did used to get it when i first moved to XP on an old system. A few of my mates were getting it as well, and i managed to narrow it down to a combination of two, or more of the following things cause the problem ( in my experience) NVida graphics card ********* / These two being most common Via chipset on motherboard *** \ Cheap / substandard ram CAS latency set too high in bios. I found that getting latest 4 in 1 ( www.viaarena.com ) and latest card drivers ( www.nvidia.com ) worked for me, and mates had luck with swapping ram in banks, pulling dead / problem ram - and another with changing to an ATI card. Hope this helps people. Richard On Saturday, February 7, 2004 at 4:33 am, Andrew Salvona wrote: >I have had many BSOD errors in windows xp and every time i changed my hardware (memory, >Psu, Mobo, Cpu) the error took on another form. From experience i belive the problems >to be caused by the system memory voltage. I'm now using ami bios and in it is an >option not sure what it does but mentions DIMM voltage, see if u can find somthing >similer. >Hope this helps. > > [Reply or follow-up to this message] Q827663 - Random ''0x0000008E'' Error Message on a Blue Screen in Windows XP - Microsoft Solution Tuesday, February 17, 2004 at 4:50 am Posted by Phyto (1 messages posted) I have contacted Microsoft Support for the fix. I would email it to all of you, however this file is password protected with an expiration date. If you contact Microsoft Support, this Hotfix was provided to myself free of charge along with the password. Hope this helps in your quest for a resolution. Regards Phyto On Sunday, October 12, 2003 at 9:08 pm, Bashar Hamdan wrote: >There is a solution for this stupid problem we are all having: there is an updated >win32k.sys file instead of the current one causing the issue. The rsoultion is at >the microsoft technet site under article Q827663. The filedate is Aug 2003, so it's >new. You can access it here: >http://support.microsoft.com/default.aspx?scid=kb;en-us;827663 > >Catch is they say it is provided on 'as needed bases' not a simple download. If anyone >would be kind enough as to call them or email them and get this file please share >the wealth and email it to me at bashsoft@yahoo.com and I'll be indebted to you. > >Thanks [Reply or follow-up to this message] My solution... Tuesday, February 17, 2004 at 8:07 am Posted by NightCrawler (26 messages posted) I had the same problem on my system (AMD 1600, sound blaster platinum, GeForce2 graphics, 2x 256MB DDR RAM). I switched my ram over, and it got worse (a lot worse!). I pulled 1 RAM chip out, and it now runs like an angel on 256MB RAM. Answer... Play with different RAM configs until you get a stable platform. It worked for me!!! MadMan [Reply or follow-up to this message] re: My solution... Wednesday, February 25, 2004 at 3:30 am Posted by CraigR (1 messages posted) I completely agree with Madman here guys, I had the exact same problem with continual errors from win_32k.sys and nv4_disp.dll always shutting my system down. I bought two new stick of TwinMOS 512MD DDR400, and STILL had the same problems however after checking my BIOS, I found that it had Memory Frequency set at AUTO, I changed it to 356, running a bit slower than its full potential but since then, over a week now, NO CRASHES! It seems that this setting was overclocking my memory into an unstable state, I recommend to anyone having this problem that they check thier memory settings. I'm totally convinced that its all due to memory speed problems. Good luck. On Tuesday, February 17, 2004 at 8:07 am, MadMan wrote: >I had the same problem on my system (AMD 1600, sound blaster platinum, GeForce2 graphics, >2x 256MB DDR RAM). > >I switched my ram over, and it got worse (a lot worse!). I pulled 1 RAM chip out, >and it now runs like an angel on 256MB RAM. > >Answer... Play with different RAM configs until you get a stable platform. >It worked for me!!! > >MadMan [Reply or follow-up to this message] re: My solution... A FIX THAT WORKED FOR ME! Friday, February 27, 2004 at 5:36 am Posted by Peter Smith (7 messages posted) I seem to have been having very similar problems to many of you in this thread: lots of BSODs, with win32k.sys or a selection of nv*.* files as the causes. I have the apparently common hardware factors of AMD processor (XP3000+), ASUS & NVIDIA innards. My problems only began after I downloaded some Windows Updates, inc SP1 and - crucially - an NVIDIA driver upgrade. I got hold of the Win32k patch from Microsoft - it's still only a Beta and isn't on general download yet - but that DID NOT fix the problem, as some of you suggested it would. Having spotted the NVIDIA connection, I re-loaded my original drivers from the setup CD. As if by magic, the BSOD problem has gone away. I couldn't get the new NVIDIA drivers direct from their site as my IE has decided to randomly stop me downloading some things or accessing any secure sites since I went broadband. I hope this helps someone. It's certainly a simpler solution to many of the others proposed, and it most definitely worked for me. On Wednesday, February 25, 2004 at 3:30 am, CraigR wrote: >I completely agree with Madman here guys, I had the exact same problem with continual >errors from win_32k.sys and nv4_disp.dll always shutting my system down. I bought >two new stick of TwinMOS 512MD DDR400, and STILL had the same problems however after >checking my BIOS, I found that it had Memory Frequency set at AUTO, I changed it >to 356, running a bit slower than its full potential but since then, over a week >now, NO CRASHES! > >It seems that this setting was overclocking my memory into an unstable state, I recommend >to anyone having this problem that they check thier memory settings. I'm totally >convinced that its all due to memory speed problems. > >Good luck. > > [Reply or follow-up to this message] re: My solution... A FIX THAT WORKED FOR ME! Friday, February 27, 2004 at 11:35 am Posted by nags (2 messages posted) I am also getting the Win32k.sys blue screens but I seem to break all the rules. Abit motherboard, p4 2.4, Kingston Memory, and a Radeon video card... Any ideas? [Reply or follow-up to this message] re: My solution... A FIX THAT WORKED FOR ME! Friday, February 27, 2004 at 11:56 am Posted by NightCrawler (26 messages posted) The current themes are sp1 (have you recently installed it?) or RAM. My solution was RAM. Have you got good quality RAM in your machine? Try different RAM configs (inc speeds. Underclock it). Beg steal or borrow from your mates and try their RAM to see if that helps... Madman [Reply or follow-up to this message] re: My solution... A FIX THAT WORKED FOR ME! Friday, February 27, 2004 at 2:17 pm Posted by nags (2 messages posted) I've currently got a stick of 512mb Kingston memory in here. I have another stick on the way. I started to run the memory test but it was taking too long so I'm going to do it again tonight. On Friday, February 27, 2004 at 11:56 am, Madman wrote: >The current themes are sp1 (have you recently installed it?) or RAM. My solution >was RAM. Have you got good quality RAM in your machine? Try different RAM configs >(inc speeds. Underclock it). Beg steal or borrow from your mates and try their RAM >to see if that helps... > >Madman [Reply or follow-up to this message] re: My solution... A FIX THAT WORKED FOR ME! Friday, February 27, 2004 at 5:42 pm Posted by Ryan Lynn (1 messages posted) I have the same win32k.sys problem that everyone else is having. Here is my config and what I have done to temporarily get around the problem. DFI Lanparty NF2 Ultra Rev B (NF2 MCP-T Chipset) Athlon XP 3200+ (2) 512MB PC3200 (Running in Dual Channel Mode) 120Gig SATA HD ATI Radeon 9800 Pro I have tried single sticks of RAM, older sticks of RAM, putting them in different slots, and a whole slew of BIOS settings. The only thing that is working right now is to run my 3200+ processor at 100MHZ FSB, instead of 200MHZ. It has been ultra-stable since I've done this. Anyone got any suggestions on why? [Reply or follow-up to this message] re: My solution... A FIX THAT WORKED FOR ME! Saturday, February 28, 2004 at 4:04 pm Posted by BeBe (1 messages posted) I never had this problem until I noticed some extra processes running in the background: altsvc.exe lssas.exe (not to be confused with lsass.exe) msthost.exe Rootkit? Hacker Defender Rootkit? I found some related info at dslreports.com, go there and do a search for altsvc.exe. (see page 2 of link returned) Perchance, since you've been experiencing these blue screens have you also got these processes running? What makes it especially bad is that Windows 'thinks' that altsvc and msthost are prefetch files, which at some point they prolly were... On Friday, February 27, 2004 at 5:42 pm, Ryan Lynn wrote: >We all know what Ryan Lynn wrote! :) [Reply or follow-up to this message] re: My solution... Sunday, February 29, 2004 at 6:17 am Posted by Lisa (1 messages posted) Hi I agree with the memory probs. For over 8 months I have been struggling with my XP Pro SP1. I originally had 1 Kingmax 256Mb PC2700 stick and all ran like a dream until I got another stick (exactly the same) and all hell broke loose. I ended up buying a single 512Mb Stick and haven't looked back. Needles to say after looking at earlier posts, I may try the memory settings in the BIOS (changing from AUTO), just to see if I can have all Sticks in. I also found other newsgroups that have had similar probs with ASUS P4S333 motherboards doing the same thing, but no solution other than chaging out RAM for a single stick. [Reply or follow-up to this message] re: My solution... A FIX THAT WORKED FOR ME! Monday, March 1, 2004 at 3:17 pm Posted by Peter Smith (7 messages posted) If that's the only cause file, try contacting Microsoft for their win32k patch. The related KB article is 827663. I was also getting errors caused by video driver files, hence why reloading the originals worked. Other than that, there are all sorts of ideas in this discussion thread. Kingston RAM gets a mention somewhere. On Friday, February 27, 2004 at 11:35 am, nags wrote: >I am also getting the Win32k.sys blue screens but I seem to break all the rules. > Abit motherboard, p4 2.4, Kingston Memory, and a Radeon video card... > >Any ideas? [Reply or follow-up to this message] re: My solution... Monday, March 1, 2004 at 9:04 pm Posted by mrsnrub (2 messages posted) Hi all I too have been experiencing frequent BSOD's and each one was different but usually referred to some kind of memory problem. It would even reboot after a clean install of Windows with nothing more than all drivers installed. My system is a P4 3.0Ghz, Gigabyte 8KNXP m/b with 2GB (4x512MB Geil) ram and Windows XP SP1 and all updates installed. I have found that by completely disabling the Windows swap file I haven't had a single BSOD in over two weeks. Before disabling the swap file it would reboot several times a day. With 2GB of ram I think I can live without the swap file. [Reply or follow-up to this message] Another case Monday, March 8, 2004 at 4:34 pm Posted by Tom Gleadall (3 messages posted) Hi all Ive just read the entire thread and appreciate it's already long, so I'll try to be brief. - I have been getting the following STOP codes 0000008E C0000005 0000000A 00000050, with IRQL_NOT_LESS_OR_EQUAL, PAGE_FAULT_IN_NON_PAGED_AREA, and Win32k.sys thrown in for good measure. These errors happen infrequently (every few days), with the last two occuring when maximizing (from the taskbar/tray) applications in XP. - The errors started recently when i doubled my memory from 256MB to 512MB (i.e. two sticks instead of one) so mine must be a memory related problem. - I have used Memtest86 and only found errors when using both sticks. However i did get the occasional freeze (before bios etc) when using only one stick, which has been resolved by removing & replacing the stick (same slot) I would suggest MINE is a problem relating to slots and sticks, but i will run some more tests to confirm this. My bios is NOT updated, my Geforce 440mx IS, my XP is PRO-SP1. My machine has never crashed during a game. Hope this helps ;) Tom any requests: tommy_g003@hotmail.com [Reply or follow-up to this message] re: BSOD, win32k.sys - Might be unfixable Thursday, March 11, 2004 at 8:32 am Posted by dean (1 messages posted) I have gotten an answer that you many of you may not like. Most of the BSoD everyone here has been getting is a combination of Athlon XP processors, Nvidia chipset and/or a form of GeForce video card (most notably, GeForce 4 MX). There is an known issue at Microsoft between Windows XP and combinations of the hardware above. First thing to do is do a thorough check of the your RAM. Obviously bad RAM is probably the problem. Also update your motherboard BIOS and any video card BIOS (if applicable). If you are getting BSoD noting "0x0000008e" and "win32k.sys", you need to get in touch with Microsoft and install hotfix KB827663 (you can also read about this at Microsoft Knowledge Base article 827663 - http://support.microsoft.com/default.aspx?scid=kb;[LN];827663 ). That link also tells you how to contact Microsoft to get the fix. If that fix does not work, you have to get the file 90422_ENU_i386_zip.exe. That file is a Micorosoft hotfix but there is no article number, and it's only referenced as a part of SP2. The MS technician sent it to me, you'll have to be persistent when trying to get this fix. Both these hotfixes are password protected and the passwords have expiration dates so I can't give them to you. I worked with Microsoft and installed both hotfixes. My blue screen error changed from citing "win32k.sys" to the "nv4" nvidia video driver. At that point, Microsoft said I have to either wait until new Nvidia drivers come out, wait for Microsoft's SP2 for WIN XP, or buy another video card. I bought a new video card and my system runs flawlessly. I bought the new video card because I had to get my system up and running as soon as possible. Some other things that I would have tried had I more time would be to deinstall my video drivers and roll back to earlier releases from NVidia. Hopefully the first hotfix will work for you, and if not hopefully the second one will work. I personally have an Athlon XP 2500+, ASUS A7N8X-VM/400 with onboard GeForce 4MX, but now i'm using a Matrox video card. On Friday, September 6, 2002 at 5:38 am, ed wrote: >Periodically I get BSOD's identifying the driver win32k.sys in the message... When >they appear I'm not doing anything in particular or using any particular program... >anyone know why this happens? (Athlon 1.4 GHZ, 256MB DDRAM, Geforce Mx-400...) [Reply or follow-up to this message] re: BSOD, win32k.sys - Might be unfixable Saturday, March 20, 2004 at 12:36 am Posted by BradleyT (1 messages posted) I too was running my RAM (Kingston 512 PC 2700) at DDR-400 speeds with an AMD XP-2500 system. I've since lowered the RAM speed down to DDR-333 and haven't had a problem yet. But it's strange that I have 2 almost exact same computers and the one I'm on right now has 3 sticks of that Kingston RAM (1.5GB total) overclocked and I've never had a crash, while the one with a single stick was crashing. Same mobo, same cpu, etc... Check those RAM timings and clock speeds! [Reply or follow-up to this message] re: My solution... A FIX THAT WORKED FOR ME! Saturday, March 20, 2004 at 9:00 pm Posted by nags (4 messages posted) I was getting the impression that maybe I was recieving the blue screens due to an IRQ conflict... So I removed the only PCI card from my computer and now I'm still getting Blue screens!! ARGH! On Friday, February 27, 2004 at 11:35 am, nags wrote: >I am also getting the Win32k.sys blue screens but I seem to break all the rules. > Abit motherboard, p4 2.4, Kingston Memory, and a Radeon video card... > >Any ideas? [Reply or follow-up to this message] re: My solution... A FIX THAT WORKED FOR ME! Saturday, March 20, 2004 at 9:01 pm Posted by nags (4 messages posted) At the time I had one stick of Kingston 512mb ram. I ran memtest on it and recieved no errors.. I've since installed an Elixir 512mb stick as well On Friday, February 27, 2004 at 11:56 am, NightCrawler wrote: >The current themes are sp1 (have you recently installed it?) or RAM. My solution >was RAM. Have you got good quality RAM in your machine? Try different RAM configs >(inc speeds. Underclock it). Beg steal or borrow from your mates and try their RAM >to see if that helps... > >Madman [Reply or follow-up to this message] re: My solution... A FIX THAT WORKED FOR ME! Tuesday, March 23, 2004 at 3:00 pm 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 [Reply or follow-up to this message] re: My solution... A FIX THAT WORKED FOR ME! Friday, March 26, 2004 at 3:56 am Posted by Si Gross (2 messages posted) hello nags, I have had the same errors for over a month. I tried loads of things to sort it out. I solved the problem by changing my RAM because I had 512Mb of PC2700 (vdata) for a Athlon 2600+ and this was proving to be unstable but it passed all memory tests. I upgraded to 512Mb of PC3200 memory (crucial) and this stabilised my system. I haven't had any more random errors since I put the RAM in. I hope this helps. On Saturday, March 20, 2004 at 9:00 pm, nags wrote: >I was getting the impression that maybe I was recieving the blue screens due to an >IRQ conflict... So I removed the only PCI card from my computer and now I'm still >getting Blue screens!! ARGH! > > > >On Friday, February 27, 2004 at 11:35 am, nags wrote: >>I am also getting the Win32k.sys blue screens but I seem to break all the rules. >> Abit motherboard, p4 2.4, Kingston Memory, and a Radeon video card... >> >>Any ideas? [Reply or follow-up to this message] re: My solution... A FIX THAT WORKED FOR ME! Friday, March 26, 2004 at 9:00 am Posted by nags (4 messages posted) I'm on my 3rd stick of memory right now and still recieving them :( On Friday, March 26, 2004 at 3:56 am, Si Gross wrote: >hello nags, > >I have had the same errors for over a month. I tried loads of things to sort it out. >I solved the problem by changing my RAM because I had 512Mb of PC2700 (vdata) for >a Athlon 2600+ and this was proving to be unstable but it passed all memory tests. >I upgraded to 512Mb of PC3200 memory (crucial) and this stabilised my system. I haven't >had any more random errors since I put the RAM in. I hope this helps. > > > >On Saturday, March 20, 2004 at 9:00 pm, nags wrote: >>I was getting the impression that maybe I was recieving the blue screens due to >an >>IRQ conflict... So I removed the only PCI card from my computer and now I'm still >>getting Blue screens!! ARGH! >> >> >> >>On Friday, February 27, 2004 at 11:35 am, nags wrote: >>>I am also getting the Win32k.sys blue screens but I seem to break all the rules. > >>> Abit motherboard, p4 2.4, Kingston Memory, and a Radeon video card... >>> >>>Any ideas? [Reply or follow-up to this message] re: My solution... A FIX THAT WORKED FOR ME! Friday, March 26, 2004 at 9:13 am Posted by Si Gross (2 messages posted) The only other suggestion I have is to get the kb827663 hotfix from microsoft (you'll have to contact them directly for an email link and password) for the win32k.sys error. Are you using PC3200 memory? Have you disabled everything you don't use in your BIOS? On Friday, March 26, 2004 at 9:00 am, nags wrote: >I'm on my 3rd stick of memory right now and still recieving them :( [Reply or follow-up to this message] re: My solution... A FIX THAT WORKED FOR ME! Friday, March 26, 2004 at 9:26 am Posted by nags (4 messages posted) Yep, pc3200 memory.. I haven't messed with the bios too much. The errors sometimes suggest turning off shadowing or chaching but I dont see that in my bios On Friday, March 26, 2004 at 9:13 am, Si Gross wrote: >The only other suggestion I have is to get the kb827663 hotfix from microsoft (you'll >have to contact them directly for an email link and password) for the win32k.sys >error. Are you using PC3200 memory? Have you disabled everything you don't use in >your BIOS? > > > >On Friday, March 26, 2004 at 9:00 am, nags wrote: >>I'm on my 3rd stick of memory right now and still recieving them :( > [Reply or follow-up to this message] re: BSOD, win32k.sys - FIX Access?? Tuesday, March 30, 2004 at 4:56 am Posted by peter (1 messages posted) someone please email me the patches and i will upload them to a working address online to download... for everyone ....no other links seem to work [Reply or follow-up to this message] Solution!!!!!!!!!!!!!!!!!!! Wednesday, March 31, 2004 at 3:07 pm Posted by Marcus (1 messages posted) At least for me, I've read all the post in this forum, and nothing helped me. For me the problem was the abit NF7 motherboard. anyhow 2 weeks ago my computer broke down, it was the motherboard NF7, so I went to the dealer and got anew one one the guarantee, exactly the same, he said. BUT it wasnt, it was the same but the new one didnt work with my existing RAM memory because the motherboard didnt support them, so i got new ones and now it works perfect!!!! Call the abit support and ask if your motherboard supports your RAM.. Excuse my bad english , hope i helped someone On Monday, January 20, 2003 at 9:47 pm, Olivier Hubert wrote: > >Ok, I solved my problem, but my solution probably won't apply to all (if any) of >you guys. I have an option with my board (Asus A7N8X) for RAM timing and I only had >to change the RAM timing from "Optimal" to "Sync", which effectively lowers the RAM >speed. > >For those without this option, try lowering your memory speed (133Mhz worked for >me) or try switching RAM Dimms/Simms. There errors are usually symptoms of memory >problems. Also try to test you RAM using memtest-86 (http://www.memtest86.com/), >it found some errors while my RAM was using a higher clock speed but none with my >current 133Mhz. > >HTH > >Olivier > > [Reply or follow-up to this message] No crashes in a few days!!! Thursday, April 1, 2004 at 10:20 am Posted by Kirstu (1 messages posted) I had that same problem AND I had it many months. I tried EVERYTHING but nothing worked. Last thing I did was underclocking... Now my 2600+ runs as 2400+ BUT IT WORKS FINE!!!! I don't mind little loss of power when my pc works otherwise fine. AMD 2600+ (2400+) ASRock K7S8X Micro-one Radeon 9600 Kingston 512 DDR 2700 (x2) + the usual [Reply or follow-up to this message] Solution!!!!!!! Friday, April 2, 2004 at 5:49 am Posted by cesar (1 messages posted) Hi all!!! For the past few weeks I've been reading all the posts as I was having the same BSOD problem on a ABIT VI7 PT800, a P4 HT 3Ghz, two sticks of 512 ram at 400 and a Nvidia FX 5200 128 Mb... on a brand new thing BSOD, BSOD and BSOD for not particular reason and in different periods of time... I've tried all the suggestions found here and in other forums, set the ram from 400 to 333, 266, 133... switching banks, tried different ram sticks (even from Kingston as they say is the best) pass thru mem tests, install a different gcard (Ati radeon 9200), updated every driver, disabled any extra hardware installed, disable antivirus, checked the temperature (and I've got now 4 extra coolers built in the box)... everything and in all possible combinations... nothing worked, the d... BSOD as always Then I founded a clue... my mem stcks always gived me errors in this machine but when I tried the same tests in other computer with this same sticks all went OK so... it had to be the MB!!! I went to the Abit web and found that of course there were bios updates that (oh, surprise!!) fixed 'some' unspecified problems of compatibility between some brands of ram and the MB so I´ve just flashed the bios... ET VOILÁ!!! everything goes just PERFECT the computer has being running nonstop for two days with no problem at all with any kind of aplication or high grafic game. Hope this may work to other people just BE EXTREMELY CAREFUL WHEN FLASHING BIOS and follow every direction they give you [Reply or follow-up to this message] re: No crashes in a few days!!! Friday, April 2, 2004 at 6:07 am Posted by Johann (1 messages posted) I also have this problem. Didn't have this problem utnil I bought a new Inno3d FX5600. And I also have an AMD 1.8 and an ECS K7s5a motherboard. I get the nv4_disp.dll caused PAGE_FAULT_IN_NONPAGED_AREA BSOD. I can easily side step this error by setting my agp settings to 1x from 4x. If I set agp to 4x, my computer will boot straight to the blue screen of death. Setting agp to 1x lets me boot to windows and play games etc. without any problems. On Thursday, April 1, 2004 at 10:20 am, Kirstu wrote: >I had that same problem AND I had it many months. I tried EVERYTHING but nothing >worked. Last thing I did was underclocking... Now my 2600+ runs as 2400+ BUT IT WORKS >FINE!!!! I don't mind little loss of power when my pc works otherwise fine. > >AMD 2600+ (2400+) >ASRock K7S8X >Micro-one Radeon 9600 >Kingston 512 DDR 2700 (x2) >+ the usual [Reply or follow-up to this message] Crash Tuesday, April 6, 2004 at 4:57 pm Posted by greine12 (1 messages posted) My computer boots up like it normally should but as soon as i click on my icon to log into windows this blue screen comes up and states i have a problem with my bios. It worked perfectly fine for 3 or 4 months and I can not understand why it isn't working. On the blue screen it says that i should go into safe mode etc and at the bottom it has a few numbers including 0x0000008E. What I am assuming is that my system is to powerful and fast for windows. I am running... -512 DDR 400 OEM -120gb Seagate 7200 serial ata - Radeon 9600 pro -3.2 AMD 64 bit processor I am pretty confident that there isn't anything wrong with my hardware and that windows is just being stupid, if anyone can help that would be great! [Reply or follow-up to this message] re: Crash Wednesday, April 7, 2004 at 1:38 pm Posted by Tomz (1 messages posted) Whenever i go into a game i can play it for a while then it freezes and i cant press anything i have to restart the computer.... can anyone help?? 1.4ghz 526ram geforce4 please help :S [Reply or follow-up to this message] re: Crash Saturday, April 10, 2004 at 1:19 pm Posted by MadMan (1 messages posted) The 2 running themes through this forum are either a, win XP SP1. Have you installed it? Did your problems get worse when it was installed? or my prime suspect b, RAM. I posted earlier on "My Solution". Try running only a single chip of RAM (don't ask me why, but a few people have found using multiple RAM chips causes the problem), try using other RAM chips and the most obvious but underrated idea, try underclocking your RAM. Edge to the side of caution nd sacrifice a touch of speed for stability. And don't forget to post back if the problem gets better/worse or stays the same and say what you tried. [Reply or follow-up to this message] No Crashes for Weeks Sunday, April 11, 2004 at 3:00 am Posted by Tom Gleadall (3 messages posted) I was having regular (every few days) crashes after i installed a new stick of RAM, making 2 x 128MB. The crashes came at very random times, but never during RAM intensive games as you might expect. A few weeks ago i downloaded and installed a BIOS update for my motherboard and i havent had any of those crashes since. The BIOS update specific to my motherboard model was hard to find, but i found it eventually and it seems to have worked. My motherboard is a Soltek SL-75DRV4. Good Luck! Tom [Reply or follow-up to this message] re: No Crashes for Weeks Wednesday, April 14, 2004 at 11:32 pm Posted by BOW (1 messages posted) How to you adjust your RAM speed in the BIOS? On Sunday, April 11, 2004 at 3:00 am, Tom Gleadall wrote: >I was having regular (every few days) crashes after i installed a new stick of RAM, >making 2 x 128MB. The crashes came at very random times, but never during RAM intensive >games as you might expect. > >A few weeks ago i downloaded and installed a BIOS update for my motherboard and i >havent had any of those crashes since. The BIOS update specific to my motherboard >model was hard to find, but i found it eventually and it seems to have worked. > >My motherboard is a Soltek SL-75DRV4. > >Good Luck! > >Tom [Reply or follow-up to this message] re: No Crashes for Weeks Thursday, April 15, 2004 at 8:21 am Posted by Tony (1 messages posted) AMD 3000+ 400FSB, Gigabyte GA7N400 pro2 MotherBoard ,Nvidia FX5700ultra 128m,Inexpensive DDR Dual channel 400fsb 512, 2 Sticks of 256m.. 4 hard drives, 1 being used with Raid. Tried unistall Nforce drivers, and put original from CD... Tried aftermarket Drivers... SAME BSOD'S win32k.sys,nv4_disp.dll,page fault in Non-paged area..., I did put my old video card(Nvidia ti4200) back in and it worked like a dream. so i left it alone for a while.. then i hated looking at that 5700 ultra just sitting there going yo waist, so i went at agian... same problems.. then I found this string of messages, i had to lower my Ram FSB to 266mhz, I tried 333mhz matching my amd3000+ barton's 333mhz FSB, and it still had problems, Now being set at 266mhz its ran great for 3 days now... hope this helps someone and i hope we can all get our money's worth of product some day.... I will keep at next im going after the hotfix kb827663 from mikerowsoft............ On Sunday, April 11, 2004 at 3:00 am, Tom Gleadall wrote: >I was having regular (every few days) crashes after i installed a new stick of RAM, >making 2 x 128MB. The crashes came at very random times, but never during RAM intensive >games as you might expect. > >A few weeks ago i downloaded and installed a BIOS update for my motherboard and i >havent had any of those crashes since. The BIOS update specific to my motherboard >model was hard to find, but i found it eventually and it seems to have worked. > >My motherboard is a Soltek SL-75DRV4. > >Good Luck! > >Tom [Reply or follow-up to this message] re: BSOD, win32k.sys - Might be unfixable Thursday, April 15, 2004 at 9:50 pm Posted by Will (1 messages posted) I have read all the posts in this thread and I want to share what worked for me. I have noticed we all seem to have AMD chips and some have Nvidia vid cards. I have an ATI all in wonder in mine. I have been getting the win32k.sys BSOD at wierd times, sometimes when just idling. What worked for me was to unplug three of my hard drives to elemenate their power draw. Once I did this I found that it runs and has not crashed for 2 weeks now. I am currently ordering a 450 watt power supply so I can hook those other power robbing drives back up. When ever you start getting random reboots and you do tests and finds the memory ok look at your TRUE power requirements and unplug some to see if that is helping the problem. On Thursday, March 11, 2004 at 8:32 am, dean wrote: >I have gotten an answer that you many of you may not like. Most of the BSoD everyone >here has been getting is a combination of Athlon XP processors, Nvidia chipset and/or >a form of GeForce video card (most notably, GeForce 4 MX). There is an known issue >at Microsoft between Windows XP and combinations of the hardware above. > >First thing to do is do a thorough check of the your RAM. Obviously bad RAM is probably >the problem. Also update your motherboard BIOS and any video card BIOS (if applicable). > >If you are getting BSoD noting "0x0000008e" and "win32k.sys", you need to get in >touch with Microsoft and install hotfix KB827663 (you can also read about this at >Microsoft Knowledge Base article 827663 - http://support.microsoft.com/default.aspx?scid=kb;[LN];827663 >). That link also tells you how to contact Microsoft to get the fix. > >If that fix does not work, you have to get the file 90422_ENU_i386_zip.exe. That >file is a Micorosoft hotfix but there is no article number, and it's only referenced >as a part of SP2. The MS technician sent it to me, you'll have to be persistent >when trying to get this fix. Both these hotfixes are password protected and the >passwords have expiration dates so I can't give them to you. > >I worked with Microsoft and installed both hotfixes. My blue screen error changed >from citing "win32k.sys" to the "nv4" nvidia video driver. At that point, Microsoft >said I have to either wait until new Nvidia drivers come out, wait for Microsoft's >SP2 for WIN XP, or buy another video card. I bought a new video card and my system >runs flawlessly. > >I bought the new video card because I had to get my system up and running as soon >as possible. Some other things that I would have tried had I more time would be >to deinstall my video drivers and roll back to earlier releases from NVidia. > >Hopefully the first hotfix will work for you, and if not hopefully the second one >will work. I personally have an Athlon XP 2500+, ASUS A7N8X-VM/400 with onboard >GeForce 4MX, but now i'm using a Matrox video card. > > > > [Reply or follow-up to this message] re: BSOD, win32k.sys Sunday, April 18, 2004 at 3:06 am Posted by will (1 messages posted) ok, dont quote me on this, but page_fault_in_non_paged_area(sorry if already answered) is usually either a serious hardware problem(RAM maybe?) or a fault on your hard drive, not sure if a file or the actual thing(sorry again...) my PC is getting all these BSOD's, with a variety of error messages. I got the win32k.sys one after i clicked shut down. Athlon XP 1.66GHz, 256MB RAM, GeForce 4 MX 440 On Sunday, January 5, 2003 at 1:37 pm, Gavin wrote: >edu, > >have you managed to solve this problem?... I am getting this error too along with >the error code 0x0000008e and paged_fault_in_nonpaged_area. >(Athlon 1.4 GHZ, 512MB DDRAM, Geforce 4 4200ti...) > >Having problems trying to resolve.... everyone has the same error code but with different >file!! > >Please help if you can. > > [Reply or follow-up to this message] BSOD & multiple_irp_complete_requests Sunday, April 18, 2004 at 10:32 pm Posted by mic4559 (1 messages posted) had this f* BSOD and read this thread. I found a solution so if it can help. I have got a motorola sb4100 and it was the drivers usb 2.0 which were troubling me. So now drivers usb 2.4 and no problem anymore it is GREAT !! so try ethernet modem or stable drivers :-) [Reply or follow-up to this message] re: BSOD, win32k.sys Monday, April 26, 2004 at 4:33 am Posted by Mike (1 messages posted) I fixed the problem by lowering the speed of my ram through the bios. [Reply or follow-up to this message] re: No Crashes for Weeks Friday, April 30, 2004 at 6:31 am Posted by Tom Gleadall (3 messages posted) I posted a few weeks back saying i'd possibly fixed the problem by updating my bios. I have since had one or two crashes, but not at all as frequently as i was having them before the update. I think what i'll try next is altering the speed of my RAM in the bios if i can, since this seems to be working for some. Tom Gleadall [Reply or follow-up to this message] re: No Crashes for Weeks Friday, April 30, 2004 at 7:35 pm Posted by gibsonus (1 messages posted) I've stumbled across this forum by chance after months and months of the same problem. I run twin athlon 2000+ mp cpus on a Tyan Tiger board with a Geforce2 mx card. 2 pioneer dvd burners. 120GB Samsung hard drive. Creative sound blaster. Motorola SB4100 cable modem. After reading about changing Ram speed i had a look at my bios. Never got as far as the Ram. I changed the agp 4x override to 2x. My pc crashed during intensive video activity(encoding to mpeg2) every time. Now it is fine. It's only been about 6 hours but it seems ok. It "was" crashing after 5minutes of encding. On Friday, April 30, 2004 at 6:31 am, Tom Gleadall wrote: >I posted a few weeks back saying i'd possibly fixed the problem by updating my bios. > I have since had one or two crashes, but not at all as frequently as i was having >them before the update. > >I think what i'll try next is altering the speed of my RAM in the bios if i can, >since this seems to be working for some. > >Tom Gleadall > [Reply or follow-up to this message] re: BSOD, win32k.sys Thursday, May 13, 2004 at 9:59 am Posted by Mike (2 messages posted) i have a laptop so i have fewer options. even the bios seems very limited on just what i can do. I am getting the BSOD with the following error messages PFN list corrupt LIRQ not less or equal win32k.sys should not see me i have changed the memory and it still happens. i can't see a way to slow the system down or change the IRQ. but why would this happen? what a way to run a computer! On Sunday, April 18, 2004 at 3:06 am, will wrote: >ok, dont quote me on this, but page_fault_in_non_paged_area(sorry if already answered) >is usually either a serious hardware problem(RAM maybe?) or a fault on your hard >drive, not sure if a file or the actual thing(sorry again...) >my PC is getting all these BSOD's, with a variety of error messages. I got the win32k.sys >one after i clicked shut down. > >Athlon XP 1.66GHz, 256MB RAM, GeForce 4 MX 440 > > > [Reply or follow-up to this message] re: BSOD, win32k.sys Thursday, May 13, 2004 at 10:40 am Posted by joyce (2 messages posted) I just read through this entire thread... I've been having the same problem as everyone here, except I always get the stop when I exit AVG. I have it set up to do an automatic scan of my system at 5:00. If I stop the scan, and exit the program, the system shuts down...blue screen. If I let the scan finish, when the program shuts itself, the system shuts. I have looked at my events log, and it indicates 3 occurrences of TrueVector Services error each time it shuts down (a result, I'm sure from zone alarm). About 2 weeks ago, I installed 2 new sticks of memory in the system, have since tested them both with the memory program, and both came out fine, no errors. I am using an HP a245c pc, which is AMD athalon. I am also using a new nvidia 5700 video card, agp. Does anybody have any ideas how I can fix this problem???? On Thursday, May 13, 2004 at 9:59 am, Mike wrote: >i have a laptop so i have fewer options. even the bios seems very limited on just >what i can do. I am getting the BSOD with the following error messages >PFN list corrupt >LIRQ not less or equal >win32k.sys >should not see me > >i have changed the memory and it still happens. i can't see a way to slow the system >down or change the IRQ. but why would this happen? what a way to run a computer! > > > [Reply or follow-up to this message] re: BSOD, win32k.sys Thursday, May 13, 2004 at 10:52 pm Posted by Mike (2 messages posted) the BSOD makes a dump log. but it can not be read except with a $900 software from microsoft. so they make a bug and then charge a fortune to figure out how do fix it. On Thursday, May 13, 2004 at 10:40 am, joyce wrote: >I just read through this entire thread... >I've been having the same problem as everyone here, except I always get the stop >when I exit AVG. I have it set up to do an automatic scan of my system at 5:00. > If I stop the scan, and exit the program, the system shuts down...blue screen. >If I let the scan finish, when the program shuts itself, the system shuts. I have >looked at my events log, and it indicates 3 occurrences of TrueVector Services error >each time it shuts down (a result, I'm sure from zone alarm). > >About 2 weeks ago, I installed 2 new sticks of memory in the system, have since tested >them both with the memory program, and both came out fine, no errors. > >I am using an HP a245c pc, which is AMD athalon. I am also using a new nvidia 5700 >video card, agp. > >Does anybody have any ideas how I can fix this problem???? > > > [Reply or follow-up to this message] Confused Friday, May 14, 2004 at 3:29 pm Posted by Adri1456 (1 messages posted) After a day or so reading all of your replies, looks like I'm in the same boat as everyone else. I started receiving the BSOD a few weeks ago, and I thought that my motherboard (an Asus P4s8X-X) was shot. I then confronted some of my peers at another message board, and they gave the suggestion that my RAM stick of 512mb (from Crucial) maybe the problem. My computer runs fine today, but I get the random BSOD at the most inconvientent time. Sometimes, it maybe a few minutes after I started the computer, others, a few hours when I'm halfway through my work. I've asked my older brother on the mainland (I'm in Hawaii) to look for cheap RAM for me, so I'm on the way to replacing the potentially bad RAM. I checked it for errors, but received none. BTW, my specs are an Asus P4S8X-X motherboard, Intel P4 2.8ghz processor, ATI All-In-Wonder 9700 video card, and Crucial stick of 512mb RAM @ 2700mhz. [Reply or follow-up to this message] re: BSOD, win32k.sys Sunday, May 16, 2004 at 5:36 pm Posted by Mike (2 messages posted) I to am being bsod like a mofo every few minutes if im doing more then one thing i can hardly even use Bit torrent due to getting bsod so many times i have an ATI9100 128mb ddr so its not just for geforce its been happening VERY badly for past 1-2 weeks [Reply or follow-up to this message] re: BSOD, win32k.sys Monday, May 17, 2004 at 5:36 am Posted by joyce (2 messages posted) Just to let everyone know, I finally found out my system had a virus on it that left the file "terminator.exe" on it...i learned that this virus goes after anti-virus programs...which in fact is what happened to mine. When the AVG would try to finish a scan, the pc would shut down...stop. I had to do online virus scans to determine this. Of course, the pc then had 3 other virus's because the AVG had'nt run properly for about a week. Everything seems ok now. On Sunday, May 16, 2004 at 5:36 pm, Mike wrote: >I to am being bsod like a mofo every few minutes if im doing more then one thing >i can hardly even use Bit torrent due to getting bsod so many times > >i have an ATI9100 128mb ddr > >so its not just for geforce > >its been happening VERY badly for past 1-2 weeks > [Reply or follow-up to this message] what worked for me :) Tuesday, May 18, 2004 at 11:49 am Posted by Dead.Guy (1 messages posted) I was also getting all for these BSoDs (win32k.sys) I read though this fouram and tried the following - Taking out my 256MB stick of mem, leaving my 512MB - Putting the 256MB in and taking the 512MB out - Increasing the voltage one level to 2.6 - Decreasing the voltage back to default and changing the multiplier to 2 putting the memory at 266 from 333MHz - Put the memory back to default, all 768MB, auto multiplier, and 2.5 volts - Disabled on board LAN card - took out Sound Blaster Audigy I did all these thing and nothing worked for me… Then I… - Took out my ATI 9600 pro and put in nVidia GeForce4 5200 and now everything is fine I put everything back the way it was one by one just to be safe, ahhh I feel much better now! MY SPECS Albatron PX845PE Pro II S P4 2.4GHz 768MB of Crucial PC2700 Raid 0 Array of 2 Western Digital Raptors 10,000RPMs (sooo sweet) Now nVidia GeForce4 5200 (ATI 9600 pro 128mb was causing the problem) [Reply or follow-up to this message] Haven´t had them before... Wednesday, May 19, 2004 at 9:51 am Posted by SiN (1 messages posted) First the specs: Intel P4 2.53 Ghz, MSI MoBo, MSI GeForce 4 Ti 4400, RAM: 1x512 Mb, 1x256 Mb. I get both the win32k.sys and nv4_disp.dll error....mostly i get the PAGE_FAULT_IN_NONPAGED_AREA, and 1 or 2 times the IRQL_NOT_LESS_OR_EQUAL errors, but the strange thing about it that i´ve NEVER had these errors before! I started getting them a few weeks ago, and I thought "Well it was a very long time ago i formatted the harddrive" So i formatted my system hdd, and i still get the errors! Why? I haven´t changed a thing! No new hardware/drivers, nothing! Ive tried different Detonators, 44.03 to 56.56....worth mentioning is that i use WinXP Pro with SP1, but that hasnt been a problem before! Please, PLEASE help me! [Reply or follow-up to this message] re: Haven´t had them before... Tuesday, May 25, 2004 at 9:37 pm Posted by R3ckl3ss (1 messages posted) Dang these forums are long. I seem to be having the same problems as everyone else. I have double checked the RAM and there aren't any problems in that area. I have a Soyo KT400 Dragon Ultra Platinum Edition MB, 1GB of Kingston Ram, and a XFX GeForce Fx 5900 128mb card. I seem to notice this problem after I install DirectX9.0b. I have recently uninstalled it and have yet to have a BSOD. (2 weeks now) The problem is that most new games require 9.0 to be installed to run correctly. Anyone seem to have the same problem? On Wednesday, May 19, 2004 at 9:51 am, SiN wrote: >First the specs: >Intel P4 2.53 Ghz, >MSI MoBo, >MSI GeForce 4 Ti 4400, >RAM: 1x512 Mb, 1x256 Mb. > >I get both the win32k.sys and nv4_disp.dll error....mostly i get the PAGE_FAULT_IN_NONPAGED_AREA, >and 1 or 2 times the IRQL_NOT_LESS_OR_EQUAL errors, but the strange thing about it >that i´ve NEVER had these errors before! I started getting them a few weeks ago, >and I thought "Well it was a very long time ago i formatted the harddrive" So i formatted >my system hdd, and i still get the errors! Why? I haven´t changed a thing! No new >hardware/drivers, nothing! Ive tried different Detonators, 44.03 to 56.56....worth >mentioning is that i use WinXP Pro with SP1, but that hasnt been a problem before! >Please, PLEASE help me! [Reply or follow-up to this message] re: Haven´t had them before... Sunday, May 30, 2004 at 5:03 pm Posted by gonzie (1 messages posted) Had all the problems listed. I went into bios and changed my ram speed from 400 to 333, so far no more problems. Well that how I did it, hope it helps. On Tuesday, May 25, 2004 at 9:37 pm, R3ckl3ss wrote: >Dang these forums are long. I seem to be having the same problems as everyone else. > I have double checked the RAM and there aren't any problems in that area. I have >a Soyo KT400 Dragon Ultra Platinum Edition MB, 1GB of Kingston Ram, and a XFX GeForce >Fx 5900 128mb card. I seem to notice this problem after I install DirectX9.0b. >I have recently uninstalled it and have yet to have a BSOD. (2 weeks now) The problem >is that most new games require 9.0 to be installed to run correctly. Anyone seem >to have the same problem? > > > [Reply or follow-up to this message] re: BSOD, win32k.sys Tuesday, June 1, 2004 at 12:46 pm Posted by Rmiller (1 messages posted) On my system this was caused by a bad stick of RAM. On Friday, September 6, 2002 at 5:38 am, ed wrote: >Periodically I get BSOD's identifying the driver win32k.sys in the message... When >they appear I'm not doing anything in particular or using any particular program... >anyone know why this happens? (Athlon 1.4 GHZ, 256MB DDRAM, Geforce Mx-400...) [Reply or follow-up to this message] re: BSOD, win32k.sys Wednesday, June 2, 2004 at 4:45 pm Posted by larry (13 messages posted) very possible you have several issues. first, make sure your system is "clean" use Ad aware, spybot and hijack this. Some hijackers use sytem (note spelling) to attempt to gain entry. Secondly, if your using XP and directX9 some start up programs (some can start anytime in the day) cause BSOD. MS is supposed to have some articles on this. I am surprised if you don't also show a "device Driver" error. Larry On Tuesday, June 1, 2004 at 12:46 pm, Rmiller wrote: >On my system this was caused by a bad stick of RAM. > > > [Reply or follow-up to this message] re: BSOD, win32k.sys Sunday, June 6, 2004 at 5:23 pm Posted by Luke (1 messages posted) Okay, here is a thread update for those of you who really cannot read the many many threads above. Overview: General Windows XP BSOD (STOP screens). Highly variant, sometimes mentioning win32k.sys and other times referencing NVIDIA files. This problem seems to be specific; so far the following consistencies have been identified: * Under AMD processors * Under NVIDIA or ATI graphics * Possibly under VIA chipsets * Possibly only on systems with higher levels of RAM * People using Windows XP, all versions You cant do much with the above information, other than decide if this thread applies to you. A couple of people have posted back with solutions, listed below. These solutions are usually echoed by a couple of other people so take note: Overheating: Some people have narrowed this problem down to system overheating. You can check to see if your system is overheating by removing the case and directing a box fan straight into your system. If the problems stop then you can be pretty sure its heat related. Invest in some extra fans, internal cooling, or just leave the box fan in place! Memory: Some people have just had incompatible memory; now don’t get me wrong, not faulty memory but incompatible. This means your memory wont work with your system configuration. You can see if this is your problem by replacing the memory with a different brand. Memory configuration: Also, some people have determined that removing a stick of memory out of a two stick configuration can solve these problems. You can try this by removing one stick and running on half memory for a while. Graphics software: This problem seems to be graphics orientated, and some people have found that the errors are removed simply by installing the latest drivers. This particularly applies to NVIDIA. Graphics hardware: Another common solution is simply replacing the graphics card with another make, or if you have integrated graphics, to install a card and disable the chip in the BIOS. System voltage: Reducing the system voltage might help. In one example, setting 3.45V (Default) to 3.3V was enough to stop the problem. You can change the voltage setting through the BIOS, but be careful, and use only small increments, bad voltage settings can kill your computer. Troubleshooting help: Some of the worse problems to troubleshoot with are infrequent problems. This seems to particularly apply to this case, some people are receiving the messages very frequently and the less fortunate are getting them on a weekly basis. The problem with infrequent errors is that they can be almost impossible to diagnose, without a heck of a lot of time on your hands. Try to search for something to reproduce the problem, or run a system stress test so you can at least tell when you’ve fixed the problem. Failing that, try a number of solutions (listed above) at once. Although messy there will be a good chance you’ll hit it first time. Most importantly, don’t forget to try reinstalling Windows, 90% of the time this will remove long term errors, also check that the software you are using is bug free. Good luck and happy hunting. If you need any more advice, you can contact me through this forum! Luke [Reply or follow-up to this message] Dual Channel Memory Tuesday, June 8, 2004 at 11:37 am Posted by RdpC (1 messages posted) Intel 865PERL, P4 2.8 533Mhz Bus, 2x512MB DDR400 Markvision Value vdata RAM, MSI nVIDIA GeForce 5200 128MB AGPx8, SB Live!, 450 Watt, Windows XP SP1, A/C in the room (Around 30 ºC Processor Zone). Latest BIOS P15, Latest nVIDIA WHQL driver. All the computer is new, I just build it one day ago. I started having this problems when I was installing Windows, the setup stopped telling me some files where not able to copy, can't remember the file. Windows support said it was due possible to a faulty memory. I tried installing Windows three times. Finally when I was able to install it, my computer rebooted itself and sometimes it showed BSOD with 0x50 error, a reference to faulty memory. I put the Virtual Memory to zero to fix a possible minidump error. I then tried taking out one stick (512MB) and my computer worked perfectly. I tried the other one alone to see if it caused trouble, but the computer also worked perfectly. I discovered that it only happens when I put the RAM in Dual Channel. If I use either one stick or put both not in Dual Channel, my computer works perfectly. In Dual Channel the BSOD occurs just before the Windows Welcome screen, the computer reboots and contnues in a loop eventually showing the blue screen with reference to win32k.sys. The 865PERL, although it supports DDR400, it adjust the RAM speed at 333MHz when the processor Bus is 533MHz. I will try lowering the speed to see if Dual Channel Works. I will also try different adjustments to the AGP in BIOS to see if I can use Dual Channel. Other than that perhaps the problem is due to: Bad Quality Ram Dual Channel not supported by Windows??!! [Reply or follow-up to this message] re: BSOD, win32k.sys Tuesday, June 8, 2004 at 12:56 pm Posted by steve (1 messages posted) Well my OS is Win 2003 Server Enterprise and was having all the same problems/errors you guys were. Mine turned out to be bad memory...removed the bogus chip and all is well...i hope... steve On Friday, September 6, 2002 at 5:38 am, ed wrote: >Periodically I get BSOD's identifying the driver win32k.sys in the message... When >they appear I'm not doing anything in particular or using any particular program... >anyone know why this happens? (Athlon 1.4 GHZ, 256MB DDRAM, Geforce Mx-400...) [Reply or follow-up to this message] re: BSOD, win32k.sys Sunday, June 13, 2004 at 8:02 am Posted by peter shi (1 messages posted) well, google for "win32k winxp" brings me to this long lived post! also, the first feedback of the search: http://support.microsoft.com/default.aspx?scid=kb;en-us;834450&Product=WinXP seems there will be a new version of the .sys to address our all problems? but the file seems can not be directly downloaded, you have to contact M$... On Friday, September 6, 2002 at 5:38 am, ed wrote: >Periodically I get BSOD's identifying the driver win32k.sys in the message... When >they appear I'm not doing anything in particular or using any particular program... >anyone know why this happens? (Athlon 1.4 GHZ, 256MB DDRAM, Geforce Mx-400...) [Reply or follow-up to this message] re: BSOD, win32k.sys Wednesday, June 16, 2004 at 5:26 pm Posted by Axl Myk (2 messages posted) I seem to be having some luck with this problem.. It started when I upgraded to 1gig DDR400 (2x512).. Usually it was the win32k.sys error that everyone is getting, but a few times, nview was doing it.. I was running ver 56.72 but I back-leveled to 56.64 AFTER un-installing 56.72, deleting the nvidia directory, re-booting, running "Registry Mechanic" to clean the registry out, re-booting, then installing 56.64 .. So far, the machine has been running all day without BSOD, when normally I would get hit with it 4-10 times a day.. I suspect it was cleaning the registry that did it.. ASUS a7n8x dlx AMD 3200+ Crucial DDR400 2x512 (Infineon) Geforce 5700u [Reply or follow-up to this message] re: BSOD, win32k.sys Friday, June 25, 2004 at 7:20 am Posted by Sabyre (1 messages posted) Win32k.sys, Nv4_disp.dll Page_Fault_In_Nonpaged_Area Stop 0x00000050 Wow I see a lot of input on this issue. The thing is you are all right in your own respects. Most often it is Windows XP that makes this problem come to light. If you cant contribute this problem to an overheating video card, which is usually not the problem, a cooler video card runs more stable. This BSOD is caused by a data moving issue between apreture, RAM, and VidRAM. Asynch, Synch. It is a problem of tolerance. This data is driven by the way your OS utilizes your video driver within the constraints of your mainboard. Phew, thats a big pill to swallow. With so many variables and important ones at that it could be most anything that is causing the crash. Anything from drivers to hardware. Here is how I would go about resolving this issue for a client. 1. Check the drivers. Make sure they are up to date. Video, Mainboard (Chipset), NIC, Sound. 2. Check the BIOS. If you are overclocking DONT. "Turn down" your settings. Turn off caching, shadowing, fast writes, latency, apreture, agpx, and anything that you consider as a performance enhancement. 3. Check IRQ's. If you are still getting the error, make sure the IRQ's for your video card is dedicated. 4. Consider your RAM. I hate to get to the point when you have to consider the hardware that is used because you can usually correct hardware with software, but. If you have only one stick consider lowering the operating speed or changing it with a premium brand. When ever possible dont use ECC RAM. Count the chips, if there are an odd number that is ECC. If you have multiple sticks make sure that they are of the same brand specs and contact material. If not remove all but one and test it. 5. Mainboard. Check the manual to make sure that the devices you have installed are compatible. Check jumpers. Reseat the CPU (properly). Reseat the RAM, and Video. 6. Keep it simple. Try the program thats causing the problems with the simplest of setups ... Only what you need for hardware, disable all else. That way you can tell if its another piece hardware causing the issue. 7. If all else fails consider a diiferent OS. This problem is more common with XP than any other version of Windows. Consider Windows 2000 Pro. 8. If you have come to this point the only thing left to do is change your hardware. You can try a different video card or a different card maker. Personaly I recommend MSI for all your devices. Rock solid products. More than likely (especially you Dell folks) its your Mainboard causing the issues. Remember take your time do things right and never loose your patience. It is very frustrating for things not to work right. If you have any questions you can email me: acsmaine@hotmail.com or visit our website: www.acsmaine.com Thanks, Sabyre On Wednesday, June 16, 2004 at 5:26 pm, Axl Myk wrote: >I seem to be having some luck with this problem.. >It started when I upgraded to 1gig DDR400 (2x512).. >Usually it was the win32k.sys error that everyone is getting, but a few times, nview >was doing it.. I was running ver 56.72 but I back-leveled to 56.64 AFTER un-installing >56.72, deleting the nvidia directory, re-booting, running "Registry Mechanic" to >clean the registry out, re-booting, then installing 56.64 .. >So far, the machine has been running all day without BSOD, when normally I would >get hit with it 4-10 times a day.. I suspect it was cleaning the registry that did >it.. > > >ASUS a7n8x dlx >AMD 3200+ >Crucial DDR400 2x512 (Infineon) >Geforce 5700u > > > [Reply or follow-up to this message] re: BSOD, win32k.sys Saturday, June 26, 2004 at 6:59 pm Posted by SilverRope (3 messages posted) OK.. I had this exact same thing happen, I was fine till I plugged in 2 chips (2x512), Dual Channel DDR400 Corsair. I solved it by turning the speed down from 400 to 333 in my bios, worked perfectly for 5 months this way. This got me to thinking mine was actually a heating problem. So today I went down to Fry's electronics and bought 2 Copper "iceberg DDR memory Heatspreaders" for $7.99 each. Before at this setting, I would be lucky to last more then 1 hour in "Star Wars Galaxies" before I would receive the error. Sometimes it was win32k.sys , other times it was the nv4_disp.dll, it was totally random. Well needless to say I've been playing (SWG) for the past 9 hours without 1 incident. Not one! The only thing that has changed is the copper heatspreaders I added. Might be worth a try for someone else. I couldn't stand the idea on PC3200 running at PC2700 speeds. hehe. Anyways Good luck I hope everyone gets this worked out in the end. On Wednesday, June 16, 2004 at 5:26 pm, Axl Myk wrote: >I seem to be having some luck with this problem.. >It started when I upgraded to 1gig DDR400 (2x512).. >Usually it was the win32k.sys error that everyone is getting, but a few times, nview >was doing it.. I was running ver 56.72 but I back-leveled to 56.64 AFTER un-installing >56.72, deleting the nvidia directory, re-booting, running "Registry Mechanic" to >clean the registry out, re-booting, then installing 56.64 .. >So far, the machine has been running all day without BSOD, when normally I would >get hit with it 4-10 times a day.. I suspect it was cleaning the registry that did >it.. > > >ASUS a7n8x dlx >AMD 3200+ >Crucial DDR400 2x512 (Infineon) >Geforce 5700u > > > [Reply or follow-up to this message] re: BSOD, win32k.sys Tuesday, June 29, 2004 at 3:56 pm Posted by wim (1 messages posted) Here in Madrid we have now temperatures rising above 40ºC and the bleuscreens are popping up each 2 minutes. I had red something about RAM getting hot earlier but rejected it because after having installed 2 new ramstick everything was alright... till recently. Defenitly temperature. Even my portable went out at these temperatures till I put 2 pencils beneath it widdening the space between it and the desktop. I will look for these RAMcoolingdevices in the shop tomorrow. Let's see if it works. Does anyone nows something about grounding? We have bad or no grounding in our house. Could it be the cause? The PC is connected trough a UPS. Regards, Wim On Saturday, June 26, 2004 at 6:59 pm, SilverRope wrote: >OK.. I had this exact same thing happen, I was fine till I plugged in 2 chips (2x512), >Dual Channel DDR400 Corsair. I solved it by turning the speed down from 400 to 333 >in my bios, worked perfectly for 5 months this way. This got me to thinking mine >was actually a heating problem. > > >So today I went down to Fry's electronics and bought 2 Copper "iceberg DDR memory >Heatspreaders" for $7.99 each. Before at this setting, I would be lucky to last more >then 1 hour in "Star Wars Galaxies" before I would receive the error. Sometimes it >was win32k.sys , other times it was the nv4_disp.dll, it was totally random. > >Well needless to say I've been playing (SWG) for the past 9 hours without 1 incident. >Not one! The only thing that has changed is the copper heatspreaders I added. Might >be worth a try for someone else. > >I couldn't stand the idea on PC3200 running at PC2700 speeds. hehe. Anyways Good >luck I hope everyone gets this worked out in the end. > > > [Reply or follow-up to this message] re: BSOD, win32k.sys Wednesday, June 30, 2004 at 11:01 pm Posted by HairRazor (1 messages posted) Hey all I am new to this post, but let me get to the point, I was having a SHIT load of problems with XP and Nvidia, so I decided to set down and think really hard I tryed graphics cars left in right ( all of which are invidia ) and it Still acted the same so I add and took memory away still no go then I try one last thing I looked at all my memory stick to see somthing, and found that I was using to kinds of ram I knew they was two different ones but never though of it so I out in 726 of ram all the same brand and BAM all my probs wnet away, I was getting all the errors you guys are plus the nv4_disp.dll error I would really try looking at you ram and see if that does not help it helped me.... I was looking for answers on this for over a year and now I found one good luck to all of you. On Wednesday, June 16, 2004 at 5:26 pm, Axl Myk wrote: >I seem to be having some luck with this problem.. >It started when I upgraded to 1gig DDR400 (2x512).. >Usually it was the win32k.sys error that everyone is getting, but a few times, nview >was doing it.. I was running ver 56.72 but I back-leveled to 56.64 AFTER un-installing >56.72, deleting the nvidia directory, re-booting, running "Registry Mechanic" to >clean the registry out, re-booting, then installing 56.64 .. >So far, the machine has been running all day without BSOD, when normally I would >get hit with it 4-10 times a day.. I suspect it was cleaning the registry that did >it.. > > >ASUS a7n8x dlx >AMD 3200+ >Crucial DDR400 2x512 (Infineon) >Geforce 5700u > > > [Reply or follow-up to this message] re: BSOD, win32k.sys Thursday, July 8, 2004 at 6:27 am Posted by Axl Myk (2 messages posted) Update 7/8/04 Since running "Registry Mechanic" this machine has been singing opera.. I have gotten a few BSODs from win32k.sys, but none from the nvidia drivers since 6/16/04.. Still at ver. 56.64.. According to an article @ Blackviper.com, you don't need the nvidia helper driver (nvsvc32.exe), and can disable it.. http://www.blackviper.com/WinXP/strangeservice.htm Scroll down the page to the chart.. ASUS a7n8x dlx AMD 3200+ 1g Crucial DDR400 (2x512) (Kingston/Infineon) Geforce 5700u [Reply or follow-up to this message] re: BSOD, win32k.sys Tuesday, July 13, 2004 at 4:57 pm Posted by Van Thong (1 messages posted) I have A7N8X-VM/400 microATX. Athlon 2500+ at 333MHz FSB, using various memory modules and the system give BSOD on Xp setup. Dual channel, single channel. All crash. Problem is solved when, "Auto Precharge" in BIOS setup is "disable". Hope this info help others. On Thursday, July 8, 2004 at 6:27 am, Axl Myk wrote: >Update 7/8/04 >Since running "Registry Mechanic" this machine has been singing opera.. >I have gotten a few BSODs from win32k.sys, but none from the nvidia drivers since >6/16/04.. Still at ver. 56.64.. >According to an article @ Blackviper.com, you don't need the nvidia helper driver >(nvsvc32.exe), and can disable it.. >http://www.blackviper.com/WinXP/strangeservice.htm >Scroll down the page to the chart.. > > >ASUS a7n8x dlx >AMD 3200+ >1g Crucial DDR400 (2x512) (Kingston/Infineon) >Geforce 5700u [Reply or follow-up to this message] re: BSOD, win32k.sys Wednesday, July 14, 2004 at 2:01 pm Posted by SilverRope (3 messages posted) Just a short update, it's now been 15 days of continuous running and not 1 BSOD, Thank you Iceberg for your DDR memory Heatspreaders. [Reply or follow-up to this message] re: BSOD, win32k.sys Saturday, July 24, 2004 at 7:02 pm Posted by Tom (1 messages posted) Same thing over here. Since i started using mIRC i get that error. Running Pentium IV, 1.6Ghz, 512mb RAM with GForce4 MX 440 On Monday, January 6, 2003 at 8:55 pm, Jeff wrote: >BSOD Win32k.sys Stop 0x0000008 addr BF8B56B0 Ya its repeatable. Its software. It >happens when i'm running either a movie, or changing video modes. It's only started >recently. I just started running mIrc lately too... (AMD 1600, 512mb, SIS chipset, >GForce2 card) > > [Reply or follow-up to this message] re: BSOD, win32k.sys Wednesday, July 28, 2004 at 3:29 pm Posted by Joe (4 messages posted) I had the same problem and took a look at my bois settings come to find out the shadow bios 32 was turned of i set it to cahsed and it fixed the problem On Friday, September 6, 2002 at 5:38 am, ed wrote: >Periodically I get BSOD's identifying the driver win32k.sys in the message... When >they appear I'm not doing anything in particular or using any particular program... >anyone know why this happens? (Athlon 1.4 GHZ, 256MB DDRAM, Geforce Mx-400...) [Reply or follow-up to this message] re: BSOD, win32k.sys Sunday, August 1, 2004 at 9:57 am Posted by Rustinator (1 messages posted) I think I corrected my win32k.sys problem when I changed my power supply. From my experience, check drivers first, then do a hard drive scan for errors, then ram, then make sure the power supply is sound. My system was solid for years and then all of sudden I started having hard drive, DVD burning, "Hard Errors" and win32k.sys BSODs. I think the power supply has cured the problem. On Wednesday, July 28, 2004 at 3:29 pm, Joe wrote: >I had the same problem and took a look at my bois settings come to find out the shadow >bios 32 was turned of i set it to cahsed and it fixed the problem > > > [Reply or follow-up to this message] re: BSOD, win32k.sys Monday, August 2, 2004 at 7:03 pm Posted by jamal (1 messages posted) I have had a string of these errors, however I do not think that the primary issue is related to memory suddenly going bad. It is definatily related to issues with a hot component on the board. Sometimes casued by dust build-up, not to mention that one should remove any hardware which is suspect and re-insert it into the board to be sure it is seated properly. This issue however goes all the way back to Win NT just as most errors in WIN XP do. Generally I am forced to belive it is more caused by poor programming of Windows then anything else. When I run other NON Micro crap on my system I encounter NO!!!! crashes and errors are very few and far between. So the best option in my opinion is to say Stick it where the sun doesn't shine and invest your hard earned money into software that is designed from the ground up to serve you well. By the way you notice that nearly every post has to do with an NVidia card, probably Micro crap don't like them too much so they mess things up with Direct X to force you to buy some one elses hardware. On Sunday, August 1, 2004 at 9:57 am, Rustinator wrote: > >I think I corrected my win32k.sys problem when I changed my power supply. From my >experience, check drivers first, then do a hard drive scan for errors, then ram, >then make sure the power supply is sound. My system was solid for years and then >all of sudden I started having hard drive, DVD burning, "Hard Errors" and win32k.sys >BSODs. I think the power supply has cured the problem. > > [Reply or follow-up to this message] re: BSOD, win32k.sys Tuesday, August 3, 2004 at 9:55 am Posted by Todd (1 messages posted) i recently recieved a call (im a help desk tech) about a similar situation. upon reviewing some notes, i discovered that MS has a hot fix for this that is free of charge. reference knowledge base article 827663. just thought i would through something out there for you guys. it solved my customer's problem. [Reply or follow-up to this message] Get it from the SP2 beta Wednesday, August 11, 2004 at 2:56 pm Posted by NoGood (3 messages posted) I'm part of this club for ... more than a year and a half now? Tried about everything. Now I thougt about contacting microsoft, but I had a better, free of charge idea. Get the WinXP SP2 beta, and get the file out of it :) I installed it on another XP partition and grabbed the file after install (before install it's compressed, even when unpacked by the installer). And, I've even uploaded it for you, to save the huge download ;) http://fkserv.ugent.be/lombrosiana/win32k.sys [Reply or follow-up to this message] re: Get it from the SP2 beta Wednesday, August 11, 2004 at 8:59 pm Posted by NoGood (3 messages posted) Btw, I just tried it, and it crashes, right before the desktop. Does anyone know which files it needs to prevent it from crashing? On Wednesday, August 11, 2004 at 2:56 pm, NoGood wrote: >I'm part of this club for ... more than a year and a half now? Tried about everything. >Now I thougt about contacting microsoft, but I had a better, free of charge idea. > >Get the WinXP SP2 beta, and get the file out of it :) > >I installed it on another XP partition and grabbed the file after install (before >install it's compressed, even when unpacked by the installer). > >And, I've even uploaded it for you, to save the huge download ;) > >http://fkserv.ugent.be/lombrosiana/win32k.sys [Reply or follow-up to this message] re: Get it from the SP2 beta Sunday, August 15, 2004 at 6:03 am Posted by Dee (3 messages posted) Do you mean that it crashes after you replace the file or does it crash after the download? [Reply or follow-up to this message] re: Get it from the SP2 beta Sunday, August 15, 2004 at 8:39 am Posted by NoGood (3 messages posted) I just replaced the old win32k.sys with the new one, from another xp partition. Then i booted my normal xp partition, and it crashes on the welcom screen ... On Sunday, August 15, 2004 at 6:03 am, Dee wrote: >Do you mean that it crashes after you replace the file or does it crash after the >download? [Reply or follow-up to this message] re: Get it from the SP2 beta Sunday, August 15, 2004 at 11:31 am Posted by SilverRope (3 messages posted) Windows XP Service Pack 2 has been released for File Planet users. im downloading the 266 meg file now. :) http://www.fileplanet.com/files/140000/144129.shtml On Sunday, August 15, 2004 at 8:39 am, NoGood wrote: >I just replaced the old win32k.sys with the new one, from another xp partition. > >Then i booted my normal xp partition, and it crashes on the welcom screen ... > > > [Reply or follow-up to this message] re: BSOD, win32k.sys Tuesday, August 17, 2004 at 3:35 pm Posted by Richard (1 messages posted) Olivier or any1 I am having the same problem with my computer, i get 700 000 error when i run mem86!!!!! I want to lower my memory speed, but i dont know how! please reply All reply/help is greatly appricated!! Thanks in Advance On Monday, January 20, 2003 at 9:47 pm, Olivier Hubert wrote: > >Ok, I solved my problem, but my solution probably won't apply to all (if any) of >you guys. I have an option with my board (Asus A7N8X) for RAM timing and I only had >to change the RAM timing from "Optimal" to "Sync", which effectively lowers the RAM >speed. > >For those without this option, try lowering your memory speed (133Mhz worked for >me) or try switching RAM Dimms/Simms. There errors are usually symptoms of memory >problems. Also try to test you RAM using memtest-86 (http://www.memtest86.com/), >it found some errors while my RAM was using a higher clock speed but none with my >current 133Mhz. > >HTH > >Olivier > > [Reply or follow-up to this message] re: BSOD, win32k.sys Friday, August 20, 2004 at 2:48 pm Posted by ME? (1 messages posted) hi all, i think i have a solution well, everybody says he has 2 or more sticks of ram. my prob was that one of them, was not "exactly" the same as the other, the serial was diffrent. so i took out one stick, and now, everything went perfect. so, i think the problem is that 2 sticks of ram isnt a good idea because they "fight" with each other. my prob is gone now. ---> WARNING : TRY THIS @ HOME :D [Reply or follow-up to this message] re: BSOD, win32k.sys Friday, August 20, 2004 at 9:10 pm Posted by Jeff in New Orleans (4 messages posted) It's definitely an overheating problem. I was getting multiple BSOD's per day. Page Faults, IRQS_NOT_EQUAL, win32k.sys, STOP! 0x0000000A... I had upgraded to a new CPU but kept the old fan and didn't apply new CPU grease - and I bet the lack of grease, combined with the heat of a new second drive made overheating probs for the CPU. The BSOD's showed memory areas that a test with SANDRA Diagnostic Freeware confirmed were the same ones the CPU. They range from 00000000-0000FFFF through 000A rnage upawrd to 00FFFFF. I went out and bought two fans. One a copper based one spec'd out for my AMD Athlon XP CPU (http://64.26.27.31/products/techietoyz/cpuvgacooling.asp), and another that sits over a PCI slot, which I put next to my nVidia FX5700 256 card. I stopped getting the BSOD's and after checking the much lower temp in my BIOS under PC Health, I overclocked my CPU and it's all running faster and fine. Maybe the RAM could be overheating, but it's all about overheating as far as I was concerned. Oh, I applied the XPSP2 and all has been fine. - Jeff in New Orleans, NetComputerGuy.com On Friday, September 6, 2002 at 5:38 am, ed wrote: >Periodically I get BSOD's identifying the driver win32k.sys in the message... When >they appear I'm not doing anything in particular or using any particular program... >anyone know why this happens? (Athlon 1.4 GHZ, 256MB DDRAM, Geforce Mx-400...) [Reply or follow-up to this message] re: BSOD, win32k.sys Saturday, August 21, 2004 at 8:08 am Posted by Paul (5 messages posted) Let me add some information to this problem, since I've been experiencing it for around a year. I will vouch to say that it is not overheating unless you somehow have a LOT of heat issues to begin with. I am running a liquid-cooled system and the problem has not gone away. I have very stable and predictable temperatures. I've replaced just about every part in my computer minus the motherboard and video card (I'm switching to a non-Nvidia chipset shortly - currently I'm on a GeForce 5600) I have a Gigabyte 8KNXP mb (Intel chipset) - so I'm not even dealing with the AMD issue. I did come across some interesting information after getting a 0x000000c5 stop screen. Check out the following on Microsoft's site: http://support.microsoft.com/?kbid=291810 http://support.microsoft.com/default.aspx?scid=kb;EN-US;188831 This gives me more insight that what I knew before. Isn't this wonderful how we can learn the underlying technical aspects of Windows because of a problem? It's a great way to learn things you never wanted to... Paul On Friday, August 20, 2004 at 9:10 pm, Jeff in New Orleans wrote: >It's definitely an overheating problem. I was getting multiple BSOD's per day. Page >Faults, IRQS_NOT_EQUAL, win32k.sys, STOP! 0x0000000A... I had upgraded to a new CPU >but kept the old fan and didn't apply new CPU grease - and I bet the lack of grease, >combined with the heat of a new second drive made overheating probs for the CPU. >The BSOD's showed memory areas that a test with SANDRA Diagnostic Freeware confirmed >were the same ones the CPU. They range from 00000000-0000FFFF through 000A rnage >upawrd to 00FFFFF. > >I went out and bought two fans. One a copper based one spec'd out for my AMD Athlon >XP CPU (http://64.26.27.31/products/techietoyz/cpuvgacooling.asp), and another that >sits over a PCI slot, which I put next to my nVidia FX5700 256 card. > >I stopped getting the BSOD's and after checking the much lower temp in my BIOS under >PC Health, I overclocked my CPU and it's all running faster and fine. > >Maybe the RAM could be overheating, but it's all about overheating as far as I was >concerned. Oh, I applied the XPSP2 and all has been fine. > >- Jeff in New Orleans, >NetComputerGuy.com > > [Reply or follow-up to this message] re: BSOD, win32k.sys Saturday, August 21, 2004 at 8:21 am Posted by Paul (5 messages posted) This support article is referenced as well: http://support.microsoft.com/default.aspx?scid=kb;EN-US;244617 Paul On Saturday, August 21, 2004 at 8:08 am, Paul wrote: >Let me add some information to this problem, since I've been experiencing it for >around a year. I will vouch to say that it is not overheating unless you somehow >have a LOT of heat issues to begin with. I am running a liquid-cooled system and >the problem has not gone away. I have very stable and predictable temperatures. > I've replaced just about every part in my computer minus the motherboard and video >card (I'm switching to a non-Nvidia chipset shortly - currently I'm on a GeForce >5600) I have a Gigabyte 8KNXP mb (Intel chipset) - so I'm not even dealing with >the AMD issue. > >I did come across some interesting information after getting a 0x000000c5 stop screen. > Check out the following on Microsoft's site: > >http://support.microsoft.com/?kbid=291810 > >http://support.microsoft.com/default.aspx?scid=kb;EN-US;188831 > >This gives me more insight that what I knew before. Isn't this wonderful how we >can learn the underlying technical aspects of Windows because of a problem? It's >a great way to learn things you never wanted to... > >Paul > > > [Reply or follow-up to this message] re: BSOD, win32k.sys Saturday, August 21, 2004 at 8:52 am Posted by Jeff in New Orleans (4 messages posted) Did you try reloading the drivers supplied by your mobo mfr.? What about a complete Windows reinstall-repair? Maybe proper cooling resolves the BSOD problems for some of us who are lucky enough to not have driver probs. causing the same end-result problems. Glad mine were related to mechanical and I don't have to muck with software issues. Good luck On Saturday, August 21, 2004 at 8:21 am, Paul wrote: >This support article is referenced as well: > >http://support.microsoft.com/default.aspx?scid=kb;EN-US;244617 > >Paul > > > [Reply or follow-up to this message] re: BSOD, win32k.sys Saturday, August 21, 2004 at 9:36 am Posted by Paul (5 messages posted) 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/ On Saturday, August 21, 2004 at 8:52 am, Jeff in New Orleans wrote: >Did you try reloading the drivers supplied by your mobo mfr.? What about a complete >Windows reinstall-repair? > >Maybe proper cooling resolves the BSOD problems for some of us who are lucky enough >to not have driver probs. causing the same end-result problems. Glad mine were related >to mechanical and I don't have to muck with software issues. > >Good luck > > > [Reply or follow-up to this message] re: BSOD, win32k.sys Thursday, August 26, 2004 at 3:52 am 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/ > > > [Reply or follow-up to this message] re: BSOD, win32k.sys Monday, August 30, 2004 at 12:28 pm Posted by Robert (1 messages posted) Hello, I was checking windows annoyances for a friend who has the blue screen problem & I am suprised at so many people with this problem. We both have windows XP home he suffers the blue scren & I do not. My humble specs are; KT4 Ultra agp x8 motherboard With an AMD athlon 2200 chip Radeon 9600 PRO video card 256 DDR. 756 DDR mgs RAM My friend has an SIS motherboard with on board video with an intel p4 chip. 756 mgs SD Ram . He recently put in a Nvidia 64 meg Ti 4200 graphics card but still gets the blue screen as he did with just the onboard video. I used to own the ti 4200 but never got the blue screen. Its 0537 hrs I'm finnishing night duty soon and thats my two cents worth.. On Thursday, August 26, 2004 at 3:52 am, Paul wrote: >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 > > > > > > > > [Reply or follow-up to this message] re: BSOD, win32k.sys Tuesday, September 7, 2004 at 4:50 pm Posted by Dan (1 messages posted) Most of us, such as I, also have an Nvdia video card, I have not changed it yet, but one day after a random restart, I did get an error message saying that the video card was causing my system to be unstable. I have checked different outlets, reformatted the hard drive, changed the power supply, ran virus scans, and still the same problem. My Specs: 2.4c w/ht P4 processor 1 Gb DDR PC3200 Infineon RAM (2x512) 80 Gb Maxtor Hard Drive 420w Thermaltake PSU 64 Mb Nvida GeForce2 Video Card On Monday, August 30, 2004 at 12:28 pm, Robert wrote: >Hello, > I was checking windows annoyances for a friend who has the blue screen >problem & I am suprised at so many people with this problem. We both have windows >XP home he suffers the blue scren & I do not. >My humble specs are; >KT4 Ultra agp x8 motherboard >With an AMD athlon 2200 chip >Radeon 9600 PRO video card 256 DDR. >756 DDR mgs RAM > >My friend has an SIS motherboard with on board video >with an intel p4 chip. >756 mgs SD Ram . > >He recently put in a Nvidia 64 meg Ti 4200 graphics card but still gets the blue >screen as he did with just the onboard video. I used to own the ti 4200 but never >got the blue screen. >Its 0537 hrs I'm finnishing night duty soon and thats my two cents worth.. > > [Reply or follow-up to this message] re: BSOD, win32k.sys Sunday, September 12, 2004 at 12:07 pm Posted by Ronald (2 messages posted) I just build a new system and the problem is also with ATI cards. I just build a system with a radeon 9200, MSI K8N Neo and a Athlon 64 2800 and 512 mb ram. I could not work for 5 minutes without a BSOD. From the test's I am running it looks like a memory problem. I down graded it from 400 mhz to 100 mhz and memtest does not give errors any more. I will test the system with higher timings and see what will happen. I'll keep you posted. But many thanks for the info so far. On Tuesday, September 7, 2004 at 4:50 pm, Dan wrote: >Most of us, such as I, also have an Nvdia video card, I have not changed it yet, >but one day after a random restart, I did get an error message saying that the video >card was causing my system to be unstable. I have checked different outlets, reformatted >the hard drive, changed the power supply, ran virus scans, and still the same problem. > >My Specs: >2.4c w/ht P4 processor >1 Gb DDR PC3200 Infineon RAM (2x512) >80 Gb Maxtor Hard Drive >420w Thermaltake PSU >64 Mb Nvida GeForce2 Video Card > > > [Reply or follow-up to this message] Resolution!! Friday, September 17, 2004 at 8:29 am Posted by Paul (5 messages posted) My problems are gone. I've replaced all of my Kingston HyperX memory with OCZ Platinum (their best kind w/low timings). No blue screens, random reboots, etc - everything is looking good w/diagnostics as well. After changing everything under the sun and making my system liquid cooled - the only thing that fixed it was complete memory replacement. Kingston even swapped my memory with all new modules, but no luck. Kingston did not completely recommend their HyperX modules with my mobo (Gigabyte 8KNXP) because only cheaper memory was on their "certified" list. OCZ rigerously tested their memory on my exact board and completely certified the combo. Goes to show that not all hardware is created equally. If anyone's still experiencing this, I highly recommend verifying that the memory and motherboard are completely certified by both manufacturers. Some of the items that did NOT fix this problem: updated Nvidia drivers, updated RAID drivers, XP SP1, XP SP2 (even a proposed fix was in SP2), power supply replacement, changing memory timings, running single channel, changing cases (better cooling), liquid cooling, more fans (even lower temps), complete low-level formatting of drives, many reinstalls of Windows, pagefile modifications, service lockdowns (disabled unnecessary) and many more items. Now I'm happy I have an ultra performance, liquid-cooled system, but the headaches of this BSD and other random crashing was enough - I'm finally happy I can work on my computer without paranoia. Good luck to everyone - I hope this info helps someone! Paul (MCSE, A+, etc, etc...) On Sunday, September 12, 2004 at 12:07 pm, Ronald wrote: >I just build a new system and the problem is also with ATI cards. I just build a >system with a radeon 9200, MSI K8N Neo and a Athlon 64 2800 and 512 mb ram. >I could not work for 5 minutes without a BSOD. >From the test's I am running it looks like a memory problem. I down graded it from >400 mhz to 100 mhz and memtest does not give errors any more. I will test the system >with higher timings and see what will happen. I'll keep you posted. But many thanks >for the info so far. > > > [Reply or follow-up to this message] re: Resolution!! Monday, September 20, 2004 at 11:11 am Posted by Ronald (2 messages posted) I think you are right. It's a bad combination of memory and motherboard. The 400 mhz ram I used did it perfectly on a other system but in combination with the system I was working on it was totally sh... Changed it for an other brand and it worked perfectly. But many thanks for the solution. Ronald On Friday, September 17, 2004 at 8:29 am, Paul wrote: >My problems are gone. I've replaced all of my Kingston HyperX memory with OCZ Platinum >(their best kind w/low timings). No blue screens, random reboots, etc - everything >is looking good w/diagnostics as well. After changing everything under the sun and >making my system liquid cooled - the only thing that fixed it was complete memory >replacement. Kingston even swapped my memory with all new modules, but no luck. >Kingston did not completely recommend their HyperX modules with my mobo (Gigabyte >8KNXP) because only cheaper memory was on their "certified" list. OCZ rigerously >tested their memory on my exact board and completely certified the combo. Goes to >show that not all hardware is created equally. If anyone's still experiencing this, >I highly recommend verifying that the memory and motherboard are completely certified >by both manufacturers. > >Some of the items that did NOT fix this problem: updated Nvidia drivers, updated >RAID drivers, XP SP1, XP SP2 (even a proposed fix was in SP2), power supply replacement, >changing memory timings, running single channel, changing cases (better cooling), >liquid cooling, more fans (even lower temps), complete low-level formatting of drives, >many reinstalls of Windows, pagefile modifications, service lockdowns (disabled unnecessary) >and many more items. Now I'm happy I have an ultra performance, liquid-cooled >system, but the headaches of this BSD and other random crashing was enough - I'm >finally happy I can work on my computer without paranoia. Good luck to everyone >- I hope this info helps someone! >Paul (MCSE, A+, etc, etc...) > > > [Reply or follow-up to this message] re: Resolution!! Wednesday, October 27, 2004 at 12:54 am Posted by Myob, stupid registrations (1 messages posted) Read this & all will be magically explained - http://www.viaarena.com/default.aspx?PageID=5&ArticleID=68&P=5 .. Certainly one explanation for all the errors mentioned is on the link above (M$ has changed how 'garts' are handled) - so anything to do with a VIA chipset & agp 'at all' might be a cause .. On Monday, September 20, 2004 at 11:11 am, Ronald wrote: >I think you are right. It's a bad combination of memory and motherboard. The 400 >mhz ram I used did it perfectly on a other system but in combination with the system >I was working on it was totally sh... >Changed it for an other brand and it worked perfectly. >But many thanks for the solution. > >Ronald > > > > [Reply or follow-up to this message] re: Resolution!! Wednesday, October 27, 2004 at 1:09 pm Posted by Jack Black (6 messages posted) I had similar problems (reboots and blue screens, showing Nv4_disp.dll errors, etc.), any time Direct3D was involved; this was after clean formating a replacement HD, after the first one died (no other changes in hardware), and with no previous problems. This is what worked for me: Boot into safe mode. Re-install your video drivers (I just installed the same drivers over themselves). That's it.. I've got XP Pro and an Athlon 2600+, with an eVGA GeForceFX 5700 Ultra, using 61.76 (WHQL) drivers. [Reply or follow-up to this message] re: Resolution!! Monday, November 22, 2004 at 12:27 pm Posted by Reynaert (1 messages posted) Here is another unlucky one troubled by sudden reboots (BSOD). It seems to happen to me when a game or an application changes the video resolution. I have this problem with Mame32 games, Curse of Monkey Island, but also with a video test by the latest Sandra test utility. It might have happened since I changed my anti-virus software, so I will try disabling that. If that does not work, I will try something with the BIOS and/or the win32k.sys update. Good luck everyone... [Reply or follow-up to this message] My solution Friday, December 17, 2004 at 2:20 am Posted by Mogens (1 messages posted) Having been haunted by the same BSoD as described so many times in this thread I once again tried searching the web for a solution. And reading this thread payed off. I have tried everything imaginable. Updating Bios, drivers, WinXP-sp0,1 and 2. (SP1 seems to be much worse than the other two) etc etc The right combo of using a certain driver and sp0 actually made it posible to run for hours without BSoD so I gave it a rest even though the pc still crashed now and then. But then I had to reinstall the pc for other reasons. I tried installing the pc without my ATI 9000 all-in-wonder, just using the onboard graphics chip. I was very sure the error was caused by the graphics board because before installing it the pc ran smooth. I installed WinXP-SP2 and everything was sweet, so I made a restore point and went for it and installed the ATI card again. BSoD again! Allmost ready to give up the ATI card I tried the web again and found this thread. All this talk about RAM. I have ported my current RAM from an older machine and in that I also experiensed randon BSoD. I did all kinds of memtest then and the memory was ok and it turned out that it wasn't RAM-related. So with my current pc it didn't occur to me that RAM was the problem (still I have done some mem-testing without errors on it with this pc) since the error was related to the ATI Board. Anyway the short of it is that I tried wiping the connecters of my two RAM-sticks with a tissue with ethanol and I haven't had a single BSoD for two days now. Thanks to all for this thread and I hope my story can help someone. [Reply or follow-up to this message] re: BSOD, win32k.sys Friday, December 17, 2004 at 11:52 am Posted by M. Moulding (1 messages posted) I have a blue page pop up while using my comp. It says thier has been a error and my comp. will be shutting down this hapens 2or three times each time I use my comp. and has been going on sice I got my comp. Why??? On Friday, September 6, 2002 at 5:38 am, ed wrote: >Periodically I get BSOD's identifying the driver win32k.sys in the message... When >they appear I'm not doing anything in particular or using any particular program... >anyone know why this happens? (Athlon 1.4 GHZ, 256MB DDRAM, Geforce Mx-400...) [Reply or follow-up to this message] re: Resolution!! Wednesday, December 22, 2004 at 3:59 am Posted by Infinity (1 messages posted) I have recently built a system for a friend; ABit NF7-M (using onboard GF4MX 32Mb), 256Mb Corsair VS RAM (pc3200), Sempron 2400+. I was having terrible problems... every time i tried to install windows XP I kept recieving a BSOD identifying 'win32k.sys'. I read around alot, and found some solutions, many indicating RAM as the cause. I have tested the RAM for around 4 hours with memtest86, and no errors at all were found. I tested the CD drive, ide cables, HDD and proccessor in another machine, and all ran with no problems at all. In the end i sent the mobo back to the supplier (beliving the onboard graphics to be faulty), who sent me a replacement. I rebuilt the machine with this mobo, and STILL got the same BSODs when trying to install windows xp. I have just found the forum, and so thought I would share a solution that worked for me. First I updated the boards BIOS, this had no effect, still BSODs (so I don't know if this was neccassary). Then I tried disabling BIOS and Video RAM caching, which also had no effect. Then i saw at the bottom of the BIOS screen was an option called 'Precharge Write'. I have to admit I have no idea what this accually means, but the BIOS info told me that it would 'increase DRAM compatability' but 'drop performance by ~2%'. I disabled this and have had no problems at all since, everything runs perfectly. And 2% shouldn't be noticable :-). Good luck with all your probs, and I hope this helps. [Reply or follow-up to this message] re: Resolution!! Saturday, December 25, 2004 at 3:34 am Posted by Gareth Jones (1 messages posted) Hi guys Last week I built a computer for my little sisters for today (Christmas) and just couldn't work out why it was randomly rebooting. It was even doing it while idle in Windows, and also when booting up. Overheating was not an option as the CPU was running at 45 degrees C and it would also reboot from a first boot. I read on some other forums that some people had problems with cables, shorting etc. so I replaced all of the IDE cables and checked and reconnected all the power cables. The random reboots then stopped (so far...) but it was still rebooting when running games in DirectX mode. Super-frustrated I was about to send the mobo back to scan and ask for a replacement (or actually get an MSI which I have never had any problems with - this one is an Asus) but I read this forum just before I took the machine apart. RAM was a popular reason for the reboots. The machine has 2x 256mb Corsair XMS sticks, so I was a little doubtful of this being my particular reason. I then checked caching and shadowing settings and received the same result. BUT!!!!!.... disabling the precaching of the onboard graphics card has fixed the problem!! The board is an Asus A7N8X-VM. I hope this helps someone else out there like I was helped this morning. Cheers. [Reply or follow-up to this message] re: Resolution!! Sunday, January 23, 2005 at 12:59 pm Posted by Bleem (1 messages posted) RAM...RAM...RAM... ALL TOGETHER NOW.... RAM...RAM...RAM... Use top quality decent ram...dont skimp on the cheap stuff...and you'll find that 9/10 times this will fix the errors most have been talking about. Win xp is a ram sucker..no two ways about it... I would be interested to hear what you guys are using. ie...ram... while getting the win32k.sys errors... Non page faults in blah blah blah..lol....RAM 9/10 times... Video card errors...make sure you get a nice big cooler on your agp card RAM chips..Then store a collection of manufacturer drivers for your card and start there...Latest ones first...back tracking if problem persists.. Of course...driver issues can and are at fault for many blue screens....but dont mess around looking in other areas until youve looked at the RAM...COOLING...DRIVERS.. For the advanced users...correct bios cofiguration and a collection of manufacturers bios' - starting with the latest and working down..again if probs persist...is a must...again.. alot of problems are down to incorrect set up of bios. Flashing bios...read the manufacturers guidelines and understand before you try...or seek the help of someone you trust or in the know... Also...look at the motherboard manufacturers website for motherboard specs and ram configurations...type of ram tested and acceptble for your board, etc etc... GoodLuck... BLeeM [Reply or follow-up to this message] re: BSOD, win32k.sys Monday, January 31, 2005 at 9:18 am Posted by King Azog (1 messages posted) The problem is : You use 400Mhz Memory on a board with a FSB of 333Mhz. The auto precharge option in the BIOS will precharge (duh!) the memory at 400Mhz while the rest will go at 333Mhz. Therefore : Impossible to synchronise DDR with the rest Result : BSOD or instability problems... [Reply or follow-up to this message] re: BSOD, win32k.sys Thursday, February 10, 2005 at 2:58 am Posted by callum (2 messages posted) Firstly, this page has helped alot - maybe I can add some more... My setup: A7N8X-E Deluxe, 2x 512MB 3200 DDR Crucial RAM (certified and tested for this board), AMD XP3200 Barton and XP Professional SP1 I too was suffering all the same types of problems: - Random Reboots and BSOD often indicating win32k.sys - Pagefile errors - Errors after clean installs I tried a number of ways to solve this such as: - updated drivers, - memtest (no errors found) - flashing bios, - changing around my PCI cards - clean installs etc... After reading this page, I tried the following things that worked: - I reduced the CPU freq setting from 200 MHz to 166 MHz. (PC was then stable as a rock but performance was slower) - So then I reset my motherboard (jumpers and battery out etc) - With default settings of motherboard and freq back to 200 MHz it continued to crash. - So then I played around with the stick combinations... and came to the following conclusion: Either of my 512 sticks would work fine alone in any of the slots at default MoBo settings (400 MHz FSB), but as soon as there are 2 in there, my system becomes unstable. Does anyone have any ideas on this one? I am assuming its a slightly faulty MoBo... so I will call the supplier today... but it still seems very strange to me. [Reply or follow-up to this message] re: BSOD, win32k.sys Thursday, February 10, 2005 at 4:35 am Posted by Matthew D. Healy (1255 messages posted) Any time you have random errors, the first thing you should do is go to www.memtest.org/ and download the memtest tool. You make a bootable floppy or CD, with which you boot the computer and run a RAM test. Let it run for at least an hour, and preferably overnight. On Thursday, February 10, 2005 at 2:58 am, callum wrote: >Firstly, this page has helped alot - maybe I can add some more... My setup: A7N8X-E >Deluxe, 2x 512MB 3200 DDR Crucial RAM (certified and tested for this board), AMD >XP3200 Barton and XP Professional SP1 I too was suffering all the same types of problems: >- Random Reboots and BSOD often indicating win32k.sys - Pagefile errors - Errors >after clean installs I tried a number of ways to solve this such as: - updated drivers, >- memtest (no errors found) - flashing bios, - changing around my PCI cards - clean >installs etc... After reading this page, I tried the following things that worked: >- I reduced the CPU freq setting from 200 MHz to 166 MHz. (PC was then stable as >a rock but performance was slower) - So then I reset my motherboard (jumpers and >battery out etc) - With default settings of motherboard and freq back to 200 MHz >it continued to crash. - So then I played around with the stick combinations... and >came to the following conclusion: Either of my 512 sticks would work fine alone in >any of the slots at default MoBo settings (400 MHz FSB), but as soon as there are >2 in there, my system becomes unstable. Does anyone have any ideas on this one? I >am assuming its a slightly faulty MoBo... so I will call the supplier today... but >it still seems very strange to me. [Reply or follow-up to this message] re: BSOD, win32k.sys Wednesday, February 16, 2005 at 7:12 am Posted by Brandon (1 messages posted) I also had this mind numbing problem after upgrading my computer. My system Asus P4S800-MX motherboard, P4 3.0ghz 800 FSB 1MB L2 cache,512 MB PC 3200 RAM (Samsung); eVGA FX 5200 256 MB video card. I tried three different video cards and not using one, and still received crashes. I did a clean Windows XP install and had crashes. I talked to Microsoft, ASUS, computer specialists and none could help. Finally I found this message board and realized my bios was set to auto speed for my memory. This was causing it to try and overclock it each time. I then set it to 400 and the erros decreased. When I set it to 333 it eliminated the errors. I am goign to try a heat spreader and see what happens. [Reply or follow-up to this message] re: BSOD, win32k.sys Sunday, February 20, 2005 at 2:32 pm Posted by Donna Price (11 messages posted) I've experienced these BSODs and found that Microsoft has a hotfix that is not yet available online, but can be obtained with a call. I've put in a request for the hotfix but not yet received it; when I do, I'll post the results. On Friday, September 6, 2002 at 5:38 am, ed wrote: >Periodically I get BSOD's identifying the driver win32k.sys in the message... When >they appear I'm not doing anything in particular or using any particular program... >anyone know why this happens? (Athlon 1.4 GHZ, 256MB DDRAM, Geforce Mx-400...) [Reply or follow-up to this message] re: BSOD, win32k.sys Thursday, February 24, 2005 at 11:37 am Posted by fktrIbx (1 messages posted) Same issues- I replaced the motherboard and all problems vanished. Ram timing? One of the BIOS updates for the board included a fix for "Samsung 256MB K4H560838D-TCB3 DDR 333 memory compatibility issue". I Suspect they have more issues than they know. Mobo: KT4AV-L Ram: Kingston 512mb pc3200 Cpu: Athlon XP 2600+ I work at a tech shop and we've found the above board often has problems going above 100mhz FSB. [Reply or follow-up to this message] re: BSOD, win32k.sys Thursday, March 3, 2005 at 3:11 pm Posted by Tyrian (5 messages posted) I can say in my case it isn't cooling. I'm experimenting with memory speeds (nTune Allows me to adjust my HyperTransport and thereby my memory speed) After enough tweaking, if it doesn't stabilize, i will call Kingston and have them replace the sticks. But before that i will call them and have them tell me recommended timings. I'm just happy i got widows xp on this monster. Rig: AMD 64bit 3500+ (939 Socket) 1024 Kingston ram DDR 3200 Aspire case (7 fans -casetemp 95 F / 34 C) ATI Radeon x800Xt PE (AGP) 3xhdd totaling 550gb. (Win XP on SATA) 2 DVD Drives (one +-RW) [Reply or follow-up to this message] BSOD only after overclocking Monday, March 7, 2005 at 11:57 am Posted by everica (1 messages posted) Hi, any help would be greatly appreciated. I just built a computer for my sister and everything ran just fine when the cpu was at normal speed or underclocked ,but as soon as I overclock it ANY the computer will not boot up. I get the BSOD with irql_not_less_or_equal. I've seen posts where people fix these problems several different ways but I don't understand why mine only does it AFTER overclocking. Could anyone please help. Specs: Athalon XP 2500+ ECS KT600-A Motherboard Kingston 512k pc3200 radeon 9200 (le) windows xp [Reply or follow-up to this message] re: BSOD only after overclocking Monday, March 7, 2005 at 12:47 pm Posted by Tyrian (5 messages posted) first suggestion.. read through your motherboard manual and check if it has certain positions for dual and single side memory modules... if not, make sure the memory is in slot order (in other words, don't fill 3, and 4 before one and two.) No sireee, windows doesn't like that one bit. Also make sure that there is no dust whatsoever, and that your motherboard settings for timing and such match those recommended by the manufacturer, before you start up the slope. Also, try increasing voltage to help stability. On Monday, March 7, 2005 at 11:57 am, everica wrote: >Hi, any help would be greatly appreciated. I just built a computer for my sister >and everything ran just fine when the cpu was at normal speed or underclocked ,but >as soon as I overclock it ANY the computer will not boot up. I get the BSOD with >irql_not_less_or_equal. I've seen posts where people fix these problems several >different ways but I don't understand why mine only does it AFTER overclocking. >Could anyone please help. > >Specs: >Athalon XP 2500+ >ECS KT600-A Motherboard >Kingston 512k pc3200 >radeon 9200 (le) >windows xp [Reply or follow-up to this message] re: BSOD and Memory on Athlons Friday, March 11, 2005 at 2:03 pm Posted by Jack Gulley (5917 messages posted) Just to add a little more fuel to the fire on Athlon and memory related problems. I have an Athlon PC3200 system, standard setting (no overclocking) MSI board, that after several months of running Windows XP without problems, started throwing many of the above BSOD's and could find nothing wrong. Latest versions of MemTest86_v3.2 ran OK over night. Gave up and started running Windows ME on the system so I could use it. But then things started going wrong there also and after switching back to XP, it was having more frequent errors than before. Was talking to a neighbor with several machines and he was having the same problem with them. So I took three of his, mine and another of mine that had not had any problems and set them up and started testing and swapping parts around. Found that some combinations of different memory modules would not work in one machine, but run OK in others. Some would only work when paired with specific other modules. Others would work only when ran alone. Some only in specific combinations on a specific machine (not just a specific model of board). (All PC3200) Then discovered that putting in PC2700 (old good quality and well tested and used), worked on all the machines? Just a little slower at a lower bus speed. What got me, was that one 512MB PC3200 module would work just fine by itself, yet when combined with any other module on two of the systems, would only show up as a 256MB module??? Yet it worked just fine on two other systems. In one case, this was the same exact system board and BIOS level, yet it worked OK in one and failed in the other. Also noticed that these memory parts all worked just fine in any combination on a Giga-Byte P4 system board (unless there was also a memory error detected by MemTest86). Did some creative swapping around of parts, weeded out one memory module that was suspect, and one that was going bad, took notes and got all the systems working error free. And had one module replaced by the vendor who sold it to me, but a different replacement "brand". First point is, that there is some memory bus compatibility problems with the Athlon processors and/or the system boards they are used on. It could be a simple thing such as the quality of the manufacturing process of each individual system board and the thickness of the layers between signal paths that allow cross talk or signal quality problems between the processor and the memory sockets. This is something system board makers should check closely and frequently, but seldom do in volume production because of the expense of destroying boards to do the testing. Then a week later, my machine with a single 512MB replacement module in it started throwing errors again. Ran MemTest86 and it would pickup a single address and bit error about once every eight to ten hours. Same bit every time. It also did the same thing in other machines. This was a "cheap replacement" Vdata Markvision Value 512MB DDR PC3200 CL=2.5 module, with a "Life Time Warranty". Over the next few days, the error rate became more frequent to the point that it is now almost useless. Having to run with a PC2700 module right now. The second point is, that a single bit error like this can cause a very hard to diagnose problem. Changing drivers or other programs just change the chances of the failing bit causing a problem and the nature of the problem. It is a well known fact that when such an error starts to occur, it it often temperature sensitive at first and only gets worse over time until the part has a complete failure of the bit. Started taking a close look at the memory modules and the others that were known to cause problems in specific systems. They all had one noticeable thing in common. The tops of the chips all had a rough or course texture, like they had been ground off, instead of the normal smooth gloss texture from normal molding of the chips! This is a sign that these parts may have been "re-branded or remarked", as they all have the same low quality of stamping of the chip information on the refurbished surface. Just try to find out any information about Vdata or MarkVision parts and their "Life Time Warranty". No address or contact point. Much the same for the other "suspect" parts. And they are usually sold by vendors who have a no return policy after x number of days, and who do NOT handle Warranty returns of these parts for you. Taking it a step farther, I downloaded the latest copy of CPU-Z (and found a bug in it which the author quickly fixed for us over night) and ran it on all of these modules to look at the SPD information on their supported speed specifications, and Manufacturer's name information. Again, all of the different modules with problems and re-branded chips had a Manufacturer's ID in the SPD chip of 0000000000000000 or blanks! Clearly a violation of the SPD memory identification standards and an obvious attempt to evade Warranty responsibility, if not an attempt to defraud. Third point is, there appears to be a lot of low quality memory in the market. While I don't think this is the cause of most of these problems, it sure points out that there is a lot of "suspect" memory floating around in the market place and that it can cause problems. And that some vendors may have quality problems with their system board manufacturing process. [Reply or follow-up to this message] re: BSOD and Memory on Athlons Friday, March 11, 2005 at 5:32 pm Posted by Tyrian (5 messages posted) sounds suspicious.. good dectective work. I use kingston (EQII gives 43% discount) so, i haven't had too many problems since i rearranged my memory set up. Good Luck On Friday, March 11, 2005 at 2:03 pm, Jack Gulley wrote: > Just to add a little more fuel to the fire on Athlon and memory related problems. >I have an Athlon PC3200 system, standard setting (no overclocking) MSI board, that >after several months of running Windows XP without problems, started throwing many >of the above BSOD's and could find nothing wrong. Latest versions of >target="_blank"> MemTest86_v3.2 ran OK over night. > Gave up and started running Windows ME on the system so I could use it. But then >things started going wrong there also and after switching back to XP, it was having >more frequent errors than before. > Was talking to a neighbor with several machines and he was having the same problem >with them. So I took three of his, mine and another of mine that had not had any >problems and set them up and started testing and swapping parts around. Found that > some combinations of different memory modules would not work in one machine, but >run OK in others. Some would only work when paired with specific other modules. Others >would work only when ran alone. Some only in specific combinations on a specific >machine (not just a specific model of board). (All PC3200) Then discovered that putting >in PC2700 (old good quality and well tested and used), worked on all the machines? >Just a little slower at a lower bus speed. > What got me, was that one 512MB PC3200 module would work just fine by itself, >yet when combined with any other module on two of the systems, would only show up >as a 256MB module??? Yet it worked just fine on two other systems. In one case, this >was the same exact system board and BIOS level, yet it worked OK in one and failed >in the other. > Also noticed that these memory parts all worked just fine in any combination on >a Giga-Byte P4 system board (unless there was also a memory error detected by MemTest86). > Did some creative swapping around of parts, weeded out one memory module that >was suspect, and one that was going bad, took notes and got all the systems working >error free. And had one module replaced by the vendor who sold it to me, but a different >replacement "brand". > First point is, that there is some memory bus compatibility problems with the >Athlon processors and/or the system boards they are used on. It could be a simple >thing such as the quality of the manufacturing process of each individual system >board and the thickness of the layers between signal paths that allow cross talk >or >signal quality problems between the processor and the memory sockets. This is something >system board makers should check closely and frequently, but seldom do in volume >production because of the expense of destroying boards to do the testing. > Then a week later, my machine with a single 512MB replacement module in it started >throwing errors again. Ran MemTest86 and it would pickup a single address and bit >error about once every eight to ten hours. Same bit every time. It also did the same >thing in other machines. This was a "cheap replacement" Vdata Markvision Value 512MB >DDR PC3200 CL=2.5 module, with a "Life Time Warranty". Over the next few days, the >error rate became more frequent to the point that it is now almost useless. Having >to run with a PC2700 module right now. > The second point is, that a single bit error like this can cause a very hard to >diagnose problem. Changing drivers or other programs just change the chances of the >failing bit causing a problem and the nature of the problem. It is a well known fact >that when such an error starts to occur, it it often temperature sensitive at first >and only gets worse over time until the part has a complete failure of the bit. > Started taking a close look at the memory modules and the others that were known >to cause problems in specific systems. They all had one noticeable thing in common. >The tops of the chips all had a rough or course texture, like they had been ground >off, instead of the normal smooth gloss texture from normal molding of the chips! >This is a sign that these parts may have been "re-branded or remarked", as they all >have the same low quality of stamping of the chip information on the refurbished >surface. > Just try to find out any information about Vdata or MarkVision parts and their >"Life Time Warranty". No address or contact point. Much the same for the other "suspect" >parts. And they are usually sold by vendors who have a no return policy after x number >of days, and who do NOT handle Warranty returns of these parts for you. > Taking it a step farther, I downloaded the latest copy of CPU-Z >(and found a bug in it which the author quickly fixed for us over night) and ran >it on all of these modules to look at the SPD information on their supported speed >specifications, and Manufacturer's name information. Again, all of the different >modules with problems and re-branded chips had a Manufacturer's ID in the SPD chip >of 0000000000000000 or blanks! Clearly a violation of the SPD memory >identification standards and an obvious attempt to evade Warranty responsibility, >if not an attempt to defraud. > Third point is, there appears to be a lot of low quality memory in the market. > While I don't think this is the cause of most of these problems, it sure points >out that there is a lot of "suspect" memory floating around in the market place and >that it can cause problems. And that some vendors may have quality problems with >their system board manufacturing process. [Reply or follow-up to this message] re: BSOD and Memory on Athlons Sunday, March 20, 2005 at 7:37 pm Posted by Phu (1 messages posted) Hi i've been having a similar problem with those BSODs too. i have AMD Athlon XP 2800+, 1.5gig Hynix DDR-400, 200gig HDD. i swapped the PCI cards over e.g. TV tuner used to be in PCI Slot 1, but now in Slot3 etc and the problem went away. Happy it worked for me. Good luck guys [Reply or follow-up to this message] re: still need help Monday, April 18, 2005 at 8:53 pm Posted by Jux (1 messages posted) While reading the other posts, I realized what my problem probobly is.. havn't tried yet though. I started getting blue-screened shortly after "upgrading" my memory. Tried just the new stick (512mb Kingston Value @ 333) as well as both (other is 128mb No-Name @ 266). The error occurs w/ both sticks installed, (effectively slowing the 333 to 266) so it seems to me that some cheaper ram just cant handle certain speeds, even if they may supposedly be able to. (Intel D845GBF, 512mb Kinston pc2100, 128mb ATI Radeon 9200) On Tuesday, May 27, 2003 at 12:36 pm, Gary wrote: >I'm having a similar problem, but I still need a little help in resolving it. (It >has been lots of fun just trying to complete this message before my system crashes >again.) My Intel D845 GRG board doesn’t seem to offer the option of changing the >RAM timing from "Optimal" to "Sync" as someone suggested. At least I couldn’t find >it in the BIOS settings. Someone suggested lowering the memory speed. I assume >that means buying lower speed RAM. (I am already using the lowest speed available >for my board.) I have onboard video, so some of those solutions won't help. It >looks like the solution is new RAM, so I'm open to suggestions of what to look for >(or avoid). My board will only take DDR. Right now I have 256 MB 266 MHz PC 2100. >(Windows XP / 1.8 Celeron) >Thanks. [Reply or follow-up to this message] re: still need help Tuesday, April 19, 2005 at 5:58 am Posted by Tyrian (5 messages posted) one thing is for sure, the Kingston ram is almost guarenteed (well it is guaranteed... but thats another story) not to be your problem . Stay away from no name cheap ram. You get what you buy when you purchase ram... unless you find a nice deal from a big company, a stick of cheap ram is exactly that; a stick of cheap ram... On Monday, April 18, 2005 at 8:53 pm, Jux wrote: >While reading the other posts, I realized what my problem probobly is.. havn't tried >yet though. I started getting blue-screened shortly after "upgrading" my memory. > Tried just the new stick (512mb Kingston Value @ 333) as well as both (other is >128mb No-Name @ 266). The error occurs w/ both sticks installed, (effectively slowing >the 333 to 266) so it seems to me that some cheaper ram just cant handle certain >speeds, even if they may supposedly be able to. (Intel D845GBF, 512mb Kinston pc2100, >128mb ATI Radeon 9200) > > > [Reply or follow-up to this message] win32k.sys but different Friday, April 22, 2005 at 7:28 am Posted by zerovich (2 messages posted) hello guys, I am having almost the same problem, an error page shows up, but the weird thing is that it shuts down the computer and I can't even swith it on, I mean it is dead like for good. I have to wait for like 5 min to be able to switch it on and for it to load the Windows. Then I get this error rarely, sometimes the computer would block and I can't do anything but restart, it happens during antivirus scans. I tried the online antivirus of kaspersky and Panda, every time they are about to complete the scan it shuts down or blocks. My comp is Pentium IV, 3.0Gh, Nvidia GEForce FX 5200, 512 DDR, and the platform is MWindows XP Home edition. It is weird that I can use my computer for a very long time without that message shwoing up, but when i try to perform a scan it shuts down. I'd be very glad if anyone could help. [Reply or follow-up to this message] re: win32k.sys but different Friday, April 22, 2005 at 1:42 pm Posted by Tyrian (5 messages posted) Try a virus scanner that works on boot (as in a boot disk) that will keep the virus from activating. On Friday, April 22, 2005 at 7:28 am, zerovich wrote: >hello guys, I am having almost the same problem, an error page shows up, but the >weird thing is that it shuts down the computer and I can't even swith it on, I mean >it is dead like for good. I have to wait for like 5 min to be able to switch it on >and for it to load the Windows. Then I get this error rarely, sometimes the computer >would block and I can't do anything but restart, it happens during antivirus scans. >I tried the online antivirus of kaspersky and Panda, every time they are about to >complete the scan it shuts down or blocks. My comp is Pentium IV, 3.0Gh, Nvidia GEForce >FX 5200, 512 DDR, and the platform is MWindows XP Home edition. It is weird that >I can use my computer for a very long time without that message shwoing up, but when >i try to perform a scan it shuts down. I'd be very glad if anyone could help. [Reply or follow-up to this message] re: win32k.sys but different Saturday, April 23, 2005 at 5:13 am Posted by zerovich (2 messages posted) thank you Tyrian for the advice, bt I don't think it has to do with the antivirus. Like now, when I switch it on, it blocks itself even if I don't do anything special, I am just browsing the net or sometimes when i don't even touch it. I tried yesterday to see if it would blok when playing a game, so I tried to play in NFSU II + the winamp, it didn't switch off. I installed CPUCool in order too see if it is an overheating problem but the tepmerature never raises more than 53/55 C. Besides the error, blue msg doesn't show anymore, it's just the system that blocks itself and I have to restart(but then once again, if I restart immediatly it won't loead windows, just dead so I have to wait like 5min to be able to switch it on normally, so it would loead the windows). This is very weird coz at the beginning, once, the coolers started to work like plane engines, very powerfully all of a sudden so I thought it might be a heat problem, but now I am sure it's not. I can't undersatnd what's the problem, maybe it is a soft conflict, but once again, nothing special was installed on.. [Reply or follow-up to this message] re: BSOD, win32k.sys Saturday, May 14, 2005 at 5:34 pm Posted by keith blake (1 messages posted) Oliver, if you were here in Sydney Australia I would come over and KISS you ! I have been having win32k.sys errors for months and even getting segmentation faults with ANY linux distro except Mandrake and now after adjusting my ram timing ALL GONE ! Thank You Thank You Thank You Thank You and yes I am happy ! On Monday, January 20, 2003 at 9:47 pm, Olivier Hubert wrote: > >Ok, I solved my problem, but my solution probably won't apply to all (if any) of >you guys. I have an option with my board (Asus A7N8X) for RAM timing and I only had >to change the RAM timing from "Optimal" to "Sync", which effectively lowers the RAM >speed. > >For those without this option, try lowering your memory speed (133Mhz worked for >me) or try switching RAM Dimms/Simms. There errors are usually symptoms of memory >problems. Also try to test you RAM using memtest-86 (http://www.memtest86.com/), >it found some errors while my RAM was using a higher clock speed but none with my >current 133Mhz. > >HTH > >Olivier > > [Reply or follow-up to this message] re: BSOD, win32k.sys Monday, May 16, 2005 at 5:06 pm Posted by me (5 messages posted) disable spread spectrum in your bios as a firest option to solve this problem. i had a perfectly working fx5600 until a mobo update and bios update this is the setting i found to correct the problem On Saturday, May 14, 2005 at 5:34 pm, keith blake wrote: >Oliver, if you were here in Sydney Australia I would come over and KISS you ! >I have been having win32k.sys errors for months and even getting segmentation faults >with ANY linux distro except Mandrake and now after adjusting my ram timing ALL GONE >! >Thank You Thank You Thank You Thank You >and yes I am happy ! > > > > [Reply or follow-up to this message] re: Resolution!! Wednesday, May 18, 2005 at 6:59 am Posted by Prasanna Balasubramanian (2 messages posted) Yo ! i am very to happy to see this page ,i got my problem resolved by changing the memory bus speed in the bios first i thought it was to do with faulty motherboard but it ultimately the RAM settings that has to be changed Thanks a Lot for all you Guys for giving me a clue to fix my problem Thanks a ton !!!!! [Reply or follow-up to this message] re: BSOD, win32k.sys Sunday, May 22, 2005 at 8:52 pm Posted by Bret (23 messages posted) For me the solution was better cooling... heat can do strange things! On Friday, September 6, 2002 at 5:38 am, ed wrote: >Periodically I get BSOD's identifying the driver win32k.sys in the message... When >they appear I'm not doing anything in particular or using any particular program... >anyone know why this happens? (Athlon 1.4 GHZ, 256MB DDRAM, Geforce Mx-400...) [Reply or follow-up to this message] re: BSOD, win32k.sys Sunday, May 29, 2005 at 9:26 pm Posted by Jerry Erbesfield (1 messages posted) win32k.sys error fixed, on my computer! It was my power supply. At first, for 2-3 weeks, I was getting the win32k.sys error intermittantly, then the computer completely stopped booting. Discovered that the power supply was completely dead. I suppose the fan in the power supply had stopped, creating excessive heat, causing the win32k.sys error and eventually the power supply to blow. Incedently, I have an Intel P4 chipset, Asus MB, 512 Rambus RAM and NVIDA RIVA TNT2 video card. My system is NOT an AMD Athelon like so many others. Happens to the best of them I guess. Anyhow mine's fixed! Jerry Erbesfield [Reply or follow-up to this message] re: BSOD - many different ones Wednesday, June 1, 2005 at 11:32 pm Posted by Kevin (1 messages posted) I found a solution which worked for me. I was getting several different blue screen errors fairly regularly. My solution was to do a thorough cleaning of my computer's insides with a lot of compressed air, making sure that i also used it up close to clean off the dust that was on the heatsinks as well as all the dust on the fans, HDs, etc. Hope this helps someone. I would suggest doing a thorough clean of your computer with compressed air first. Then, I would check to see if your cpu's are overheating, then check your BIOS for memory options and use memtest to test out your memory, and if there is a fault, replace it. Although my cpus were not overheating, the heatsink was 100% covered in dust before i cleaned my computer's insides Please note: Cleaning my computer thoroughly solved my problem but when i ran linux i didn't have a problem with my system being very dusty. Good Luck to you all. > [Reply or follow-up to this message] BSOD - for no apperent reason Tuesday, June 7, 2005 at 2:04 pm Posted by Alex (1 messages posted) I have a ECS (elite group) KN extreme, an AMD 64 3200+ and a gig of ram..... I found that my computer was crashing every 17 hours and I was getting BSOD messages sayin that either a driver or memory was bad, I updated every posible driver and checked my memory with memtest 86, to my dismay nothing was conclusive, IT was also annoying that every time I tryed to open UT2003 or UT2004 or most other video games my computer locked up and the only solution was to reset it, then I red that my memory (2 512 sticks of corsair value ram) worked better if the voltage was slightly raised...... then I also read about ram timings, this error was caused by ram timings, while that ram was still good apperntly when I had messed around with settings earlyer, by switching ram related stuff to manuel it changed the timmings with out me knowing about it, so I changed the voltage from defult to 1.71 (the closest i could get to 1.7) volts and then changed the ram timings to auto (I mean like the precash timing and other stuff like it, here is an example of ram timing "3-3-3-8" and as if magicly my pc worked perfect, never had a random crash sence, now UT and other games work, I would sugesst finding your correct ram timing or use auto if you have it and if you have corsair memory raising the voltage to 1.7, I hope this helps, this thread helped me solve my problem and their was no specific info for my situation, so I figured I would make some........:) [Reply or follow-up to this message] re: BSOD, win32k.sys Saturday, July 2, 2005 at 3:20 pm Posted by Eli Tabs (1 messages posted) Everytime I "cold boot", I get a BOSD with a win32k.sys and a x0000008a or a x 00000019 error code message. Why? I have a P4 1.7GH with 256MB... Please help me... This happens only upon first boot. after which I can leave the box on for days with no problem. I have run memtest86 and several other dignostic tests including Hot CPU Tester and a CPU/Mobo Stabibility test which my box passed.... [Reply or follow-up to this message] re: BSOD, win32k.sys Tuesday, July 5, 2005 at 10:44 am Posted by Geof Gibson (9 messages posted) I too, have developed this problem. I solved it by going into my BIOS and dropping my FSB from 200 (its max) to 166. I then ran the nTune app. which drives the nForce 2, and it bumped the FSB up to 192 MHz with stability. I have noticed some trends whilst searching the net about this problem. 1) The vast majority of sufferers are running AMD Althlons 2) Most people who list their chipsets seem to list nForce 2 3) Almost all solutions seem to require adding cooling or dropping bus speeds 4) Many people have found memory errors while troubleshooting (is this the cuase or cuased by ??) In my case, Chaintech 7NJL6 board with nForce 2 chips. AMD Athlon 3200 CPU. 1GB of Viking RAM DDR 400. Diamond Viper 9600XT AGP card w/256 MB RAM. Hope this helps. [Reply or follow-up to this message] re: BSOD, win32k.sys Friday, July 8, 2005 at 6:54 am Posted by annoyed at windows (2 messages posted) I was getting BSOD's identifying the driver win32k.sys in the message. I solved this problem by uninstalling the codec pack - all in one I'd just installed from free-codecs.com. On Tuesday, July 5, 2005 at 10:44 am, Geof Gibson wrote: >I too, have developed this problem. >I solved it by going into my BIOS and dropping my FSB from 200 (its max) to 166. > I then ran the nTune app. which drives the nForce 2, and it bumped the FSB up to >192 MHz with stability. > >I have noticed some trends whilst searching the net about this problem. >1) The vast majority of sufferers are running AMD Althlons >2) Most people who list their chipsets seem to list nForce 2 >3) Almost all solutions seem to require adding cooling or dropping bus speeds >4) Many people have found memory errors while troubleshooting (is this the cuase >or cuased by ??) > >In my case, Chaintech 7NJL6 board with nForce 2 chips. AMD Athlon 3200 CPU. 1GB >of Viking RAM DDR 400. Diamond Viper 9600XT AGP card w/256 MB RAM. > >Hope this helps. > > [Reply or follow-up to this message] re: BSOD, win32k.sys Thursday, July 14, 2005 at 2:38 pm Posted by Kev (2 messages posted) Thought I might just add a bit on my problem. It's sort of the same as everyone else's. I built my machine following a guide I used in a PC mag. The PC then worked perfectly well from December up to May, where it then decided to just go insane and create random reboots. After the 12th random restart I reformatted and reinstalled XP Pro which worked fine for 2 months till 1 week ago whilst I was playing San Andreas where it just went BSOD again. My primary BSOD is the 0x0000008e and Microsoft describes it as a Device conflict. Due to the insane amount of times I restart the PC it has led to some very rare other error messages including 0x00000050 blaming AVG for a Page Fault. I personally believe it is the error set out by microsoft to do with XP Pro (As I always get the win32k.sys error) and a device error. Since the BSOD everything is unstable! MSN crashes, AVG crashes, ABIT EQ crashes even MS word and when I enter My Documents (not to a BSOD but to the ....has executed an illegal process and will be terminated screen). Memtest ran fine with not a single error and my CPU runs at between 40-47 degrees. The GFX card is fine as well (A Radeon 9800Pro). I'm currently in the process of degrading to Home as Microsoft has told me that the 0x0000008e error I'm experiencing is to do with XP Pro conflicting with a driver, most likely the ATI catalyst drivers. Oh yeah a bit further back I saw some people mentioning CPU-Z giving the manufacuterer of RAM a 0000000000, I found this is primarily due to Generic/OEM RAM like mine. For those of you experiencing BSOD STOP errors like 0x0000008e I suggest booting up into MS DOS or using Linux to see if it is your Current OS which is the problem as if you still experience crashes in other OS's it is most probably a Hardware issue. Lucky for me nothing crashes at ALL whilst in Linux :D [Reply or follow-up to this message] re: BSOD, win32k.sys Thursday, July 14, 2005 at 2:58 pm Posted by Falcon (13489 messages posted) "Lucky for me nothing crashes at ALL whilst in Linux" Yeah, Linux just tends to be that way, y'know? Must be why it's in nearly 70% of all web servers... :-D My Malware Removal Instructions Perform the following: Disable System Restore * Perform an online virus scan * * * * . Download, update, and run these tools: Spybot Search & Destroy * Lavasoft Adaware * CWShredder * Repeat as necessary until clean. If you still experience problems after doing these steps, download HijackThis * and post a log to this forum. To protect against reinfection, download and use these: If at all possible, I recommend that you use alternative software, particularly web browsers and email clients: Web Browsers * * * Email Clients * * If this is not a viable option, or for additional protection, use these: Javacool's SpywareBlaster * Javacool's SpywareGuard * Malware-blocking HOSTS file * IE-SPYAD * , Internet Explorer only Optionally Reenable System Restore * . Better alternatives to System Restore. If you encounter any broken links, please inform me of them. Also note that these links direct through my web server to allow me to keep them up-to-date or post additional info. If you are unable to use the links above, click the stars instead, which are a direct link to the page in question. [Reply or follow-up to this message] re: BSOD, win32k.sys Tuesday, July 26, 2005 at 7:17 am Posted by Paul Cooper (2 messages posted) After reading practically the whole forum except for the last 1/18th ish because it was all too repetitive , it just confirmed my suspicions of the same problem i was having. Generally you will find its the ram causing the problem, ram timing is a fickle business, and each stick of ram is uniquely capable of maintaining certain timing/frequency settings. With ram generally if ur lower the frequency you can lower (increase performance of) the timings , as if you raise the frequency timings must be sacrificed for stability. In the manufacturing process no one stick comes out the same (basically) and then quality of components is a factor also. Mixing and matching different brands of ram means that your more at risk of instability at higher frequencys as timing conflicts can occur, one stick my be able to sustain those timing settings at that frequency whereas the other(s) may not , thus causing instability, and if one stick of ram becomes unstable from timing settings all will fail as they are linked together, that is how some ppl found lowering the frequency or isolating it to one ram stick fixed the problem as at the lower frequency all could run stabily at the set timing and by isolating there was only the one stick as a variable , so long as that was stable at those settings all good. Good quality ram is usually the go because it runs through stricter testing and uses higher quality components. Usually Corsair/OCZ/Kingstom etc quality sticks are actually stress tested past the reccomended settings to ensure maximum stability and matched sets are tested together aggressively to ensure their maximum stability whilst working in a dual configuration. Another thing to look out for is more modern motherboards with advanced memory architectures can be very picky about what ram can be used and in what configuration , i have a new Asus SLI motherboard for instance that will work with certain brands of ram in 1 stick configuration but not 2 or 4 , whereas some will work in 1 stick or 4 sticks but not dual [Reply or follow-up to this message] re: BSOD, win32k.sys Saturday, July 30, 2005 at 8:09 pm Posted by Ryan Tucker (1 messages posted) SOLUTION: If you are having many problems with you comp after a fresh re-install of xp, such as win32k.sys or stop errors for multiple drivers. (THIS WORKS) turn off you computer and pull one of your Ram Sticks. Also clean your heat sink with some compressed air cleaner. If your comp still has issues try taking out the other stick of ram till you find the damaged one. [Reply or follow-up to this message] re: BSOD, win32k.sys Wednesday, August 10, 2005 at 11:32 am Posted by Tom McLaughlin (13 messages posted) Funny for me, I'm getting 0x7a error with INPAGE location, as opposed to your NonPage. My system WAS working with Windows 2000 Pro, but I didn't stress (believed I mentioned it though) was I already tried a fresh install of both WinXP and Win2003 Server and both dead end at the same spot, loading driver error. So I loaded Win2K Pro and it works. Also swapped the Kingston 512 PC3200 RAM with my other XP unit and it works fine, actually I'm typing with it installed on this machine. SO it isn't the RAM. Did an update to Samsung HD next will flash the BIOS. But will try to find an old XP (none SP) and install that. On Tuesday, January 14, 2003 at 8:50 pm, Olivier Hubert wrote: > >Ok I'm relieved now, I thought I was the only one going mad with this. I have had >BSOD's for a week now and don't know why. The only thing our computers have in common >(that I see at first glance) is the GeForce4 card... > >My BSOD's show STOP 0x00000050 or 0x0000008E with PAGE_FAULT_IN_NONPAGED_AREA. Sometimes >nv4_disp.dll is faulty and sometimes win32k.sys and even wmaud.sys once (I think). > >Athlon 2400+ >Asus A7N8X (nForce2 chipset) >512 MB DDR 2700 >Asus GeForce4 Ti4600 > > [Reply or follow-up to this message] re: BSOD, win32k.sys Wednesday, August 10, 2005 at 2:43 pm Posted by Kev (2 messages posted) Hmmm...Just got a notice reminder about this thread and thought I'd bring in a bit of feedback since my errors. So my PC was going haywire with 0xc0000005 and 0x1000008 errors, general instability etc. So I did a mass reformat, wiped everything off. Before reinstalling XP Hoem I flashed BIOS, then after installing OS I installed all the latest drivers for all my hardware (and mobo). Errors came up when I installed Zone Alarm but dissapeared after uninstalling. Then I kept getting 0xc0000005 errors (exceptions not BSOD's) whilst playing certain games (the PC would reboot from bugchecks after that as well). I solved this by degrading ATI catalyst drivers from 5.7 to 5.5. Now all games run great, a few instabilities still in the higher end ones (Farcry/Half Life 2) but thats probs cause I play them on MAX graphics :P On Wednesday, August 10, 2005 at 11:32 am, Tom McLaughlin wrote: > >Funny for me, I'm getting 0x7a error with INPAGE location, as opposed to your NonPage. > >My system WAS working with Windows 2000 Pro, but I didn't stress (believed I mentioned >it though) was I already tried a fresh install of both WinXP and Win2003 Server and >both dead end at the same spot, loading driver error. > >So I loaded Win2K Pro and it works. Also swapped the Kingston 512 PC3200 RAM with >my other XP unit and it works fine, actually I'm typing with it installed on this >machine. SO it isn't the RAM. > >Did an update to Samsung HD next will flash the BIOS. But will try to find an old >XP (none SP) and install that. > > > [Reply or follow-up to this message] re: BSOD, win32k.sys Thursday, August 11, 2005 at 10:13 pm Posted by Tom McLaughlin (13 messages posted) Well figured out what it was...the Iomega Zip drive. I had that as Master and the CD-ROM as slave. XP isnt' smart enough to differentiate and kept looking at the ZIP drive for the files to install. I unplugged the ZIP, made the CD master and presto it works. Stupid stupid stupid Microsoft. I installed Windows 2000 Pro with no problem, but XP or 2003 seem to be stund bunnies. On Wednesday, August 10, 2005 at 2:43 pm, Kev wrote: >Hmmm...Just got a notice reminder about this thread and thought I'd bring in a bit >of feedback since my errors. > >So my PC was going haywire with 0xc0000005 and 0x1000008 errors, general instability >etc. So I did a mass reformat, wiped everything off. Before reinstalling XP Hoem >I flashed BIOS, then after installing OS I installed all the latest drivers for all >my hardware (and mobo). Errors came up when I installed Zone Alarm but dissapeared >after uninstalling. Then I kept getting 0xc0000005 errors (exceptions not BSOD's) >whilst playing certain games (the PC would reboot from bugchecks after that as well). >I solved this by degrading ATI catalyst drivers from 5.7 to 5.5. Now all games run >great, a few instabilities still in the higher end ones (Farcry/Half Life 2) but >thats probs cause I play them on MAX graphics :P > > > [Reply or follow-up to this message] re: BSOD, win32k.sys Sunday, August 14, 2005 at 6:59 pm Posted by greggg (6 messages posted) I got this problem with nv4_disp some months ago after buying a geforce FX5500 to meet requisites for a game i recently got. After updating my operating system (xp sp2), it miraculously fixed the problem, probably cuz it fixed the faulty DirectX that I think I had previously (since DX is uninstallable...). Then coupla weeks back, I had to download this newer patch for my game, which i think resulted in a BSOD. I responded by updating to the latest nvidia driver, which fixed it for about the next two times i logged on. Then it got bad again, with win32k.sys BSOD and such, so i had to log in Safe mode and revert to an older video driver, which made some difference, but still interrupted with BSOD sometimes because I just clicked on the desktop. Last time I got into windows for more than 20 secs was when I opened Realplayer to watch House of Flying Daggers that I never finished. Then the problem deteriorated from instant rebooting because the blue screen cuts in to windows with many STOP errors,PAGED_FAULT_IN_NONPAGED_AREA; DRIVER_IRQL_NOT_LESS_OR_EQUAL; nv4_disp.dll; win32k.sys; win32k.sys etc before I get the time even to open the control panel until the point where it couldn't load windows because a certain winnt\system32\config\system file was corrupt (so it told me). Then I decided to install a whole new OS, but it crashed halfway thru installation. So i flipped thru some troubleshoots and, after testing several times, finally found that disabling L1 and L2 Cache in the Setup menu before Windows is loaded. This, while not crashing, reduced proccessing to a tedious rate so that installing that bloody operating system took about literally half a day (plus some 10+hrs because i got impatient and turned my comp off before it completed OS installation setup, resulting in my starting over again). It didn't get any better with that new Operating system. Still that BSOD but now consistently with PAGED_FAULT_IN_NONPAGED_AREA and STOP 0x050 plus problem with this darn acpi.sys I'm typing this with my old Compaq comp that I dug out of my attic somewhere, and it only has 200mhz cpu (as opposed to 900mhz of my broken comp) with 100mb RAM (1G DDRAM) and 1mb graphic memory (128mb). Really now, if I don't solve this cursed problem, i'm gonna burst. I do wanna get back to my Warcraft game...I am almost adamant in the belief that this was due to my recent installation of nvidia drivers, which wasn't what i was supposed to download, mind you, because my video card was actually PNY Verto made, so i actually shoulda downloaded from pny.com--any of you think that could be the cause? In any case, I can't fix it now, since everytime i start windows, BSOD cuts in and my comp automatically restarts in a continuous cycle, and I am only able to log on to my second OS in safe mode with L1 and L2 cache disabled, which makes it extremely slow...also could be overheating, cpu's about 160F last time I checked. Anyways, gonna test the whole nine yards next week, overheat, clean, memory, the works. [Reply or follow-up to this message] re: BSOD, win32k.sys Tuesday, August 16, 2005 at 2:55 pm Posted by greggg (6 messages posted) So I cleaned out the entire comp as best as I could with a combination of cotton swabs, paper towel, towel, and breath. Then I went ahead and removed Sound Card, some other card or modem, unplugged CD writtable, and reseated the video card and one of the RAM sticks. So I powered the bloody thing, and it actually turned on pretty quick, as opposed to not outputting anything at all. It showed some wrong reading of my CPU (like 630, when the right one should be 950) and RAM (some 756MB instead of 1G), but actually LET me into the blasted desktop with astounding speed. Showed a lotta Found New Hardware crap, but I canceled all that. Ran a DX Diag, CPU was wrong still, but fixed RAM reading. THEN I BLOODY HEELLLLLLLL LET SHUT IT DOWN BECAUZE I WAS WORRIED ABOUT THE *%&#% CPU READING!!!!!!!!!!!!!!!!!!!!!!!! AND IT NEVER LET ME INTO THE DESKTOP AGAIN AGAIN AGAIN AGAIN AGAIn AGain again! Only way it could get to the bloody desktop was by turning L Caches off and logging into Safe Mode, which was back to the same acursed problem I had before. Did a lotta RAM switching and it just wasn't right, every time I had to clear CMOS after crashing for it to boot again. Anyways, I installed some basic video/sound drivers and could boot into NOrmal windows, but it was so tediously slow that I concluded it must be my CPU that's faulty. How the heck am I supposed to play Warcraft ever agian...I was hoping to do some nice PvP action on it... [Reply or follow-up to this message] re: BSOD, win32k.sys Tuesday, August 23, 2005 at 8:59 am Posted by Baron French (1 messages posted) I have a Nvidia card and XP SP2. I have done masses of research on the problem with BSOD and Nvidia and SP2. Simply put, SP2 is extremely strict when it comes to drivers and will not let anything untoward happen to your system. Nvidia, unfortunately, have some of the sloppiest written drivers out there. Quite simply, Nvidia drivers don't work under SP2. The most common solution I found was people uninstalled SP2, or if like me you need SP2 for certain apps, you buy a non-Nvidia based card. I'm off to buy an ATI All-In-Wonder 9600 card after work. I searched the web and it seems to work well under XP SP2. On Tuesday, August 16, 2005 at 2:55 pm, greg madon wrote: >So I cleaned out the entire comp as best as I could with a combination > >of cotton swabs, paper towel, towel, and breath. Then I went ahead and > >removed Sound Card, some other card or modem, unplugged CD writtable, > >and reseated the video card and one of the RAM sticks. > >So I powered the bloody thing, and it actually turned on pretty quick, > >as opposed to not outputting anything at all. It showed some wrong > >reading of my CPU (like 630, when the right one should be 950) and RAM > >(some 756MB instead of 1G), but actually LET me into the blasted desktop > >with astounding speed. Showed a lotta Found New Hardware crap, but I > >canceled all that. Ran a DX Diag, CPU was wrong still, but fixed RAM > >reading. > >THEN I BLOODY HEELLLLLLLL LET SHUT IT DOWN BECAUZE I WAS WORRIED ABOUT > >THE *%&#% CPU READING!!!!!!!!!!!!!!!!!!!!!!!! AND IT NEVER LET ME INTO > >THE DESKTOP AGAIN AGAIN AGAIN AGAIN AGAIn AGain again! Only way it > >could get to the bloody desktop was by turning L Caches off and logging > >into Safe Mode, which was back to the same acursed problem I had before. > >Did a lotta RAM switching and it just wasn't right, every time I had to > >clear CMOS after crashing for it to boot again. Anyways, I installed > >some basic video/sound drivers and could boot into NOrmal windows, but > >it was so tediously slow that I concluded it must be my CPU that's > >faulty. How the heck am I supposed to play Warcraft ever agian...I was > >hoping to do some nice PvP action on it... [Reply or follow-up to this message] re: BSOD, win32k.sys Thursday, September 22, 2005 at 10:57 am Posted by georgemason (93 messages posted) This is greg, I couldn't sign in cuz forgot my password :| Yes, your opinion agrees with what has happened with me. I recall that the first time I had the BSOD was when I first plugged in my GF card. I shouldn't have installed the driver first though, that was callow of me...or it coulda been some unicode programs i installed but most likely it would be nvidia card or driver. I need to convince my family to use win2k... Anyways, I assembled a brand=new comp. It is thrice as fast inside a black case. Looks awesome and yet this week i have had some random restarts... without the video driver but with an older Geforce card that was a bit worn out as I plugged it out and in a lot when I tried to fix the damaged comp. thx for reply On Tuesday, August 23, 2005 at 8:59 am, Baron French wrote: >I have a Nvidia card and XP SP2. I have done masses of research on the problem with >BSOD and Nvidia and SP2. Simply put, SP2 is extremely strict when it comes to drivers >and will not let anything untoward happen to your system. Nvidia, unfortunately, >have some of the sloppiest written drivers out there. Quite simply, Nvidia drivers >don't work under SP2. The most common solution I found was people uninstalled SP2, >or if like me you need SP2 for certain apps, you buy a non-Nvidia based card. I'm >off to buy an ATI All-In-Wonder 9600 card after work. I searched the web and it >seems to work well under XP SP2. > > [Reply or follow-up to this message] re: BSOD, win32k.sys Wednesday, October 26, 2005 at 6:13 pm Posted by yasser (1 messages posted) On Friday, September 6, 2005 at 10:38 am, ed wrote: >Periodically I get BSOD's identifying the driver win32k.sys in the message... When >they appear I'm not doing anything in particular or using any particular program... >anyone know why this happens? (celeron 2.5 GHZ, 256MB DDRAM, asrock built in ...) [Reply or follow-up to this message] re: BSOD, win32k.sys Wednesday, October 26, 2005 at 6:41 pm Posted by Jim Fromageons (1 messages posted) I had the same problem and finaly fix it, it was not the ram nor the video card, it was the hard drive. One of the was cable select and the other one was primary master, so i set the second one primary slave and the problem is now fix... so guys just check your hdd connexion and jumper and thanx for your help... it was realy usefull On Friday, September 6, 2002 at 5:38 am, ed wrote: >Periodically I get BSOD's identifying the driver win32k.sys in the message... When >they appear I'm not doing anything in particular or using any particular program... >anyone know why this happens? (Athlon 1.4 GHZ, 256MB DDRAM, Geforce Mx-400...) [Reply or follow-up to this message] re: BSOD, win32k.sys Wednesday, November 2, 2005 at 10:20 pm Posted by codemyyster (4 messages posted) alright so i had this problem for many weeks, i had 3-4 different BSOD, mini_nv4.dll, win32k.sys, kmixer.sys...all that good shit, just a pointer... if you have your CPU overclocked, before you do ANY trouble shooting...take the CPU speed back down to the manufacturers setting. that was the problem with mine, after i spent weeks updating drivers, diagnosing my computer, testing ram, cleaning ram, removing and replacing everything, bios updates, modifications, pretty much everything you can think of. once you get the cpu speed back to manufacturer's setting [check online..anywhere], then you're good to go, but if the problem still persists-- have fun troubleshooting. [Reply or follow-up to this message] re: BSOD, win32k.sys Thursday, November 3, 2005 at 4:53 am Posted by Gary W (1 messages posted) I have been dealing with this for about a year. XP Pro, SP2, GEforce, DDR400, Albatron MB. I have noticed that before it bluescreens the processor utilization goes to 100% for a minute or two. I am not convinced this is a driver problem. I would like to know if anyone running big name vendor hardware (intel, HP, Dell mainboard) has seen this? On Wednesday, November 2, 2005 at 10:20 pm, codemyyster wrote: >alright so i had this problem for many weeks, i had 3-4 different BSOD, mini_nv4.dll, >win32k.sys, kmixer.sys...all that good shit, just a pointer... if you have your CPU >overclocked, before you do ANY trouble shooting...take the CPU speed back down to >the manufacturers setting. that was the problem with mine, after i spent weeks updating >drivers, diagnosing my computer, testing ram, cleaning ram, removing and replacing >everything, bios updates, modifications, pretty much everything you can think of. > once you get the cpu speed back to manufacturer's setting [check online..anywhere], >then you're good to go, but if the problem still persists-- have fun troubleshooting. [Reply or follow-up to this message] re: BSOD, win32k.sys Saturday, November 12, 2005 at 3:15 pm Posted by Claudio (1 messages posted) I had the same problem. I have an Athlon XP 2200+. 512Mb RAM, Geforce2 Mx100. I have tried almost everything. (Changed ram, video card, hard disk...) I finally checked CPU temperature with a nice program ("everest home" http://www.lavalys.com/ ) My PC went to BSOD after some CPU going to 100% because temperature went up to 68-70° C Now I have underclocked the PC (CPU bus from 166 to 133) and never got the problem again. CPU temp stays between 55-60°C also when going at 100% CPU. I will try to clean, check and eventually change the cooler. Hope this will help, since this problems seems to be going on from years :) Bye, Claudio. On Thursday, November 3, 2005 at 4:53 am, Gary W wrote: >I have been dealing with this for about a year. XP Pro, SP2, GEforce, DDR400, Albatron >MB. I have noticed that before it bluescreens the processor utilization goes to 100% >for a minute or two. I am not convinced this is a driver problem. I would like >to know if anyone running big name vendor hardware (intel, HP, Dell mainboard) has >seen this? > > [Reply or follow-up to this message] re: BSOD, win32k.sys Thursday, November 17, 2005 at 9:14 am Posted by Steve O (3 messages posted) I have had most of the BSOD's above and have read most of these messages. I came across a document written by a programmer (must have been). A lot of it i didn't understand, but this is what I got out of it ---- there is a very close relationship between drivers and allocated memory spaces. That is why some people have cured their problems swapping memory or updating drivers. I still don't understand the overheating problems, I'll have to think about that one. Anyway ----- I cured a lot of my problems by re-installing Windows and updating my drivers. Just a note >>>> some motherboard manufacturers don't update their pages for the newest drivers. Go directly to the source ----- VIA, ATI, NVidia, etc. Oh, Oh Blue screen Bye [Reply or follow-up to this message] re: BSOD, win32k.sys Thursday, November 17, 2005 at 9:30 am Posted by Steve O (3 messages posted) I'm sorry i left out the link to the document. I guess it was written for Page_Fault_In_Nonpaged_area http://www.osronline.com/article.cfm?article=335 [Reply or follow-up to this message] re: BSOD, win32k.sys Sunday, November 20, 2005 at 12:56 pm Posted by Jeffrey K (1 messages posted) Out of curiosity, does this have any similiarity to CAS latency? if so, I am assuming I "lower" it and not increase it right? If that's not similar, what is for a chaintech 7KJD motherboard? On Monday, January 20, 2003 at 9:47 pm, Olivier Hubert wrote: > >Ok, I solved my problem, but my solution probably won't apply to all (if any) of >you guys. I have an option with my board (Asus A7N8X) for RAM timing and I only had >to change the RAM timing from "Optimal" to "Sync", which effectively lowers the RAM >speed. > >For those without this option, try lowering your memory speed (133Mhz worked for >me) or try switching RAM Dimms/Simms. There errors are usually symptoms of memory >problems. Also try to test you RAM using memtest-86 (http://www.memtest86.com/), >it found some errors while my RAM was using a higher clock speed but none with my >current 133Mhz. > >HTH > >Olivier > > [Reply or follow-up to this message] re: I think this is a northbridge overheating problem Wednesday, November 23, 2005 at 5:48 pm Posted by Kevin Torvalds (1 messages posted) Well, to solve your cooling problem, go to Fry's Electronics, Best Buy, Circuit City, Etc. and ask for a laptop cooling pad (with fans). They will know what you mean. The USB powered ones are ideal. Now about the other problem with win32k, I hoped it wouldn't come to it, but my problem is with bad RAM. You see, I have a bad problem with cooling in my hp pavillion ze4400, and so the ram has been damaged. So I went out to Fry's and got the cooling pad, hoping this would fix it, but it turns out I was too late. So I must now go out and buy new RAM :( Oh well! I'll just crazy upgrade to a bunch more ram than I have, and it will be fresh, new and undamaged. On Wednesday, June 4, 2003 at 6:41 am, jetface wrote: > >Sorry, manus, I am not too familiar with cooling down a laptop chipset. You might >be able to find some information on the internet, though. That's one of the drawbacks >of laptops, unfortunately, not enough space to get in there and mess around. You >might try setting it on a wire shelf or something so the bottom can exchange heat >with the surroundings. A few years ago, when my TNT2 wasn't keeping up and overheating, >I put a floor fan next to my computer to improve circulation around the whole box. > It actually worked and might work for you. It is important to have good circulation >around any computer. But, like I said, I haven't had any experience cooling laptops, >but I'm sure someone out there has. Good luck! > [Reply or follow-up to this message] No more bluescreens Saturday, December 3, 2005 at 5:12 pm Posted by Harry Stottle (3 messages posted) Thanks to everyone here my problems are over. My conclusions are: If you can install or reinstall Windows, CPU overheating is unlikely the cause. If you run memcheck (or such) and get errors, swap out the RAM. If you get zero errors. still swap out RAM, don't trust the result. Set all motherboard variables to default and have a stable system before trying over/underclocking as a cure. A lot of bluescreens can easily corrupt files, so a clean install of everything will help. System at fault is just a cheap word processor with an ASRock all in one, Semperon 2300+ and 512 MB RAM. It failed as soon as the video drivers were installed, but this was not the cause. Problem was a stick of 512 RAM that tested fine with memcheck and memdiag but just didn't like the motherboard. [Reply or follow-up to this message] re: No more bluescreens Friday, February 10, 2006 at 6:36 am Posted by Jim (1 messages posted) I too had BSDs in all shapes and sizes. Also, I could not get on the Internet except in Safe Mode with Networking as Administrator - it still failed as my user account. I reduced the graphics card Hardware Accelleration to nothing, moved the RAM to another slot and blew out all the "dust bunnies". I have now got back on the Internet first time, upgraded to SP2, and no BSDs. That after being up until 2 in the morning last night fighting with, what I thought was a virus. We live and learn!! [Reply or follow-up to this message] BSOD, win32k.sys, clogged fan and bad memory Saturday, February 11, 2006 at 8:27 am Posted by Ed (1 messages posted) Thanks to everyone on this board for your posts about BSOD and memory failures. My problem started yesterday with a BSOD and a “STOP 0x000000EA THREAD_STUCK_IN_DEVICE_DRIVER” error. I changed the settings for the display and reduced the hardware acceleration to zero and disabled the write combing as instructed by the error message. I though I was losing a hard drive or my video card. I had noticed my fan running at high speed the last two to three weeks and didn’t think anything of it. It turns out my fan was mostly blocked due to dust and dirt. I cleaned the dust out of the fan and blew some of the dust out of the box. The fan speed slowed down but I was still getting BSOD errors and win32k.sys errors with the BSOD. I ran hard drive diagnostics on both my 160 and 200G drives with no errors. The system ran chkdsk after rebooting on three occasions. I was also receiving “page_fault_in_non_page_area” errors with the win32k.sys errors. My system would run for 5 to 8 minutes and then crash. I download the memory test from memtest86.com and burned it to DVD and booted from the DVD to test the memory. I was getting all kinds of errors from the start of the mem test and I thought that was normal. I removed on of the 512mb sticks and was still getting all of the errors on the memory test. I swapped the 512mb stick and what do you know, no errors on the test. It turns out one of my 512mb sticks was bad. I picked up a new 512 stick last night and let the system run with just one memory stick last night and there were no errors or BSODs. I installed the new stick this morning and everything seems to be ok. I guess the moral of the story is, keep your machine cool and clean the dust out of the fan. My system is a dell 4700 3.4ghz P4 with 1g ram. [Reply or follow-up to this message] re: BSOD, win32k.sys Tuesday, February 21, 2006 at 4:23 am Posted by Louis Klampfer (8 messages posted) I get the same on my laptop toshiba satilite a65 i think ... the blue screen of death... On Monday, January 20, 2003 at 5:36 pm, Jim wrote: >Same Problem here too. I have an ATI Radeon 7000 video card, 850mhz AMD Duron. >Any help would be appreciated. > > [Reply or follow-up to this message] re: BSOD, win32k.sys Wednesday, April 5, 2006 at 7:08 am Posted by Vlad (1 messages posted) I have the same problem. It usually happen when I play a game, although the game doesn't demand much resources. I read that many people solved their problem by adjusting the speed of RAM. I am quite useless in computer. Can someone explain how do I do it? [Reply or follow-up to this message] re: BSOD, win32k.sys Monday, April 17, 2006 at 5:40 am Posted by jtomlin (1 messages posted) PC-CHIPS mobo BSODing win32k.sys after memory upgrade*(corsair 512MB DDR)*. Flashed bios and everything is now well. - Although this problem seemed staggered, didn't show up until about a week after the memory upgrade. This problem definatly seems to be linked to system HARDWARD instability issues. Most of everyone's problems have been solved by either modifying CMOS settings or by upgrading/remove RAM modules. I recommend a step by step approach until the error is resolved. Removing any recently installed hardware / software Install driver updates for any newly installed hardware Loading "optimal settings" in BIOS Checking for BIOS updates from your motherboard manufacturer's website, or your PC manufacturer's website. Remember, most likely hardware, not software issue. Feel free to call MOBO manufacturers too. They usually have quarky fixes to strange problems. On Wednesday, April 5, 2006 at 7:08 am, Vlad wrote: > >I have the same problem. It usually happen when I play a game, although the game >doesn't demand much resources. > >I read that many people solved their problem by adjusting the speed of RAM. I am >quite useless in computer. Can someone explain how do I do it? [Reply or follow-up to this message] re: BSOD, win32k.sys Saturday, April 22, 2006 at 3:42 pm Posted by yiren (1 messages posted) I was using winodws xp and encountered this win32k.sys blue screen problem recently. I have reinstalled the whole system serval times and still can not resolve the problem. Until last week, I replaced the RAM and it worked fine since then. So, if you are sure it is not software problem, try to replace RAM. :) On Monday, April 17, 2006 at 5:40 am, jtomlin wrote: >PC-CHIPS mobo BSODing win32k.sys after memory upgrade*(corsair 512MB >DDR)*. Flashed bios and everything is now well. >- Although this problem seemed staggered, didn't show up until about a week after >the memory upgrade. > > >This problem definatly seems to be linked to system HARDWARD instability issues. > Most of everyone's problems have been solved by either modifying CMOS settings or >by upgrading/remove RAM modules. > >I recommend a step by step approach until the error is resolved. > > > Removing any recently installed hardware / software > Install driver updates for any newly installed hardware > Loading "optimal settings" in BIOS > Checking for BIOS updates from your motherboard manufacturer's website, or your >PC manufacturer's website. > >Remember, most likely hardware, not software issue. Feel free to call MOBO manufacturers >too. They usually have quarky fixes to strange problems. > > > [Reply or follow-up to this message] re: BSOD, win32k.sys Sunday, April 23, 2006 at 9:19 pm Posted by Dave (1 messages posted) Hi I have been having the blue screen of death problem. It started when I put in an extra gig of RAM so now running 1.5G DDR. I thought it was the RAM at first so had it replaced however I still get the same message. a stop message followed by win32k.sys address BF8166C3 base at BF800000 datestamp 43446a58. If anyone knows what the problem is caused by could they let me know its driving me insane. On Saturday, April 22, 2006 at 3:42 pm, yiren wrote: >I was using winodws xp and encountered this win32k.sys blue screen problem recently. >I have reinstalled the whole system serval times and still can not resolve the problem. >Until last week, I replaced the RAM and it worked fine since then. So, if you are >sure it is not software problem, try to replace RAM. :) > > > [Reply or follow-up to this message] re: BSOD, win32k.sys Thursday, May 25, 2006 at 7:59 am Posted by ironic_8b49 (1 messages posted) I got this same error before and found that making sure I'm using the recommended memory for my motherboard fix the error. On Friday, September 6, 2002 at 5:38 am, ed wrote: >Periodically I get BSOD's identifying the driver win32k.sys in the message... When >they appear I'm not doing anything in particular or using any particular program... >anyone know why this happens? (Athlon 1.4 GHZ, 256MB DDRAM, Geforce Mx-400...) [Reply or follow-up to this message] re: BSOD, win32k.sys Sunday, May 28, 2006 at 6:03 am Posted by kresnack (1 messages posted) Had this error interspersed with NV4_disp.dll bsod more and more frequently. MS finally responded with turning off hardware acceleration. I just lowered it from full to ~80% and no dumps since. Desktop-right click-Properties-Settings-Advanced-Troubleshoot-move slider to right. BSOD down from dozen+ times yesterday to zero since. g'luck, k On Thursday, May 25, 2006 at 7:59 am, ironic_8b49 wrote: >I got this same error before and found that making sure I'm using the recommended >memory for my motherboard fix the error. > > > [Reply or follow-up to this message] re: BSOD, win32k.sys Tuesday, May 30, 2006 at 5:21 am Posted by Cerberus (1 messages posted) I have also been having this error, i get BAD_POOL, nv4disp.dll and win32k.sys and PAGE_FAULT_IN_NON_PAGED AREA. I also have an nvidia graphics card, my system : AMD athlon 3200+ (754), 512mb of kingston RAM (was 1 gb but half doesn't work now since errors) and leadtek 6600GT. I will try the hardware accelearyion fix and see what that does. I think the page fault error has something to do with the RAM. On Sunday, May 28, 2006 at 6:03 am, kresnack wrote: >Had this error interspersed with NV4_disp.dll bsod more and more frequently. MS finally >responded with turning off hardware acceleration. I just lowered it from full to >~80% and no dumps since. Desktop-right click-Properties-Settings-Advanced-Troubleshoot-move >slider to right. BSOD down from dozen+ times yesterday to zero since. g'luck, k > > > [Reply or follow-up to this message] re: BSOD, win32k.sys Friday, June 23, 2006 at 9:16 am Posted by koyak (2 messages posted) Had the same problem as above.. Solved it by disabling DEP, by amending /NoExecute=OptIn to /NoExecute=ALWAYSOFF ============ Problem ============ BSOD,0x0000008e right before the login page on half of the bootups, and during execution of a few directx programs ============ System specs ============ Mainboard : Intel Corporation D845BG Chipset : Intel i845D Processor : Intel Pentium 4 @ 2000 MHz Physical Memory : 768 MB Video Card : AGP Nvidia Corp GeForce2 MX/MX 400 [NV11] Sound : SB Audigy LS with KXDrivers Hard Disk : Maxtor (123 GB) DVD-Rom Drive : BENQ DVD DD DW1620 Operating System : Microsoft Windows XP Professionnal 5.01.2600 Service Pack 2 DirectX : Version 9.0c (March 2006) ============ Solution ============ Tried most of the solutions above.. 1. Changing ram 2. Cooling 3. Disabling various software such as antivirs and certain services, startup programs 4. Driver upgrades/downgrades/WHQL Certified alternatives for various hardware 5. Disabling various hardware.. 6. Dusting out the mobo n cards!!! 7. Changing power supply 8. etc None of them worked for me (though it might for you.. all systems are set up differently) However, disabling DEP worked perfectly.. no more BSODs :) (till date. If anything goes wrong again I will post again) Good luck! [Reply or follow-up to this message] re: BSOD, win32k.sys Friday, June 23, 2006 at 9:50 am Posted by koyak (2 messages posted) Just a note... the DEP settings are found in boot.ini in your root folder. You have to show hidden files to see it :P [Reply or follow-up to this message] The key to a BSOD! This is what you have been looking for. Thursday, June 29, 2006 at 10:02 pm Posted by Josh (2 messages posted) --------------------------------------------------------------- If the following information is unavailable to you in the event viewer (described below), you will need to confirm that logging is turned on for system failures. You can confirm this by right-clicking "My Computer" and selecting Properties. Navigate to the "Advanced" tab and click "Settings" in the Startup and Recovery box. "Write an event to the system log" MUST be checked in order for a record of the crash to show up in event viewer. --------------------------------------------------------------- The filenames that the BSOD give you are the filenames that the problem is with. If you fail to get the filename it shows, you can right-click on "My Computer" and select Manage. From there you will expand the Event Viewer (on the left) and look into the System section. In the right pane, a list of events will be there. Most of them will be "Information." Your going to look for an Information event that has "Save Dump" next to it. You can narrow your search by looking at the date and time. It should appear around the date and time the crash occured. Double click on the Save Dump and read the Description. Once you learn the location and name of the Dump file (.dmp) you will need something to open this special type of file with. You can use WinDBG, which is included in the Microsoft Debugging Tools kit (http://www.microsoft.com/whdc/devtools/debugging/default.mspx). Once you install the tools, you will need to run WinDBG from the start menu (Start> All Programs> Debugging Tools for Windows> WinDBG). Select File, Open Crash Dump. Navigate to the location of the dump file you found earlier in Event Viewer and open it (Usually C:\WINDOWS\Minidump\dumpname.dmp). Now you have the information from the dump file. You should copy the name of the file that produced the BSOD and google it to get more information. You need to know what the file is used for... what it belongs to. Once you have this new information, you can begin fixing your problem. Usually the filename will end up belonging to a specific device or goes in cooperation with a specific device. This is the device you should be troubleshooting. You may need to reinstall the drivers for this device, or reinstall the device completely. If it is a driver problem, your driver may be incompatable with your operating system or may be having problems with new updates to your operating system (such as a new service pack update). If you continue to have problems after troubleshooting the device, you may want to try reversing a service pack update. Be forewarned, when reversing service pack updates you may risk corrupting your operating system even further. The installation or uninstallation of ANY service pack or update to your OS should go completely uninterrupted and without fault. I hope this has helped to solve all of your BSOD problems, these are some of the steps a computer technician will use to solve this type of problem. Godbless and Goodluck to all of you. [Reply or follow-up to this message] The key to a BSOD! This is what you have been looking for. Friday, June 30, 2006 at 1:14 am Posted by Josh (2 messages posted) As a side note to my previous post: In order to view the FULL dump and not just the filename in it (filename located near bottom of dump), you may have to install the symbols for your current Service Pack and set the Symbol File Path in WinDBG (File> Symbol File Path). If desired, you can obtain the pack of symbols at the same link I posted earlier. [Reply or follow-up to this message] re: The key to a BSOD! XP is Def, SB16 not to blame Saturday, July 15, 2006 at 3:20 am Posted by Cal (1 messages posted) everyboby check and see if you all have sound blaster sound cards! my com gets the BSOD with the typical "page fault..." win32k.sys" garb, but only when i use sounds ie. games, winamp, videos ect. ive checked it out if i throw out the SB it works fine but when i use my SB it crashes, now i know what ya thinking, listen to this, i have 3 diffrent SBs, a SBlive, an SBpci128, and a classic SB16 isa. the SB16 is the stablest but it still crashes. they all use diffrent drivers. so its got to be a windows software problem to do with useing sounds not the SBs themselfs. thats what i got, also swichted out ram and did hardware checks, scan disk, defrag, changed video cards ect. so the plot thickens. some one find the missing link how do i fix this problem! btw newst winamp seems to work well aslong as i dont do anything else at the same time. On Friday, June 30, 2006 at 1:14 am, Josh wrote: >As a side note to my previous post: > >In order to view the FULL dump and not just the filename in it (filename located >near bottom of dump), you may have to install the symbols for your current Service >Pack and set the Symbol File Path in WinDBG (File> Symbol File Path). > >If desired, you can obtain the pack of symbols at the same link I posted earlier. [Reply or follow-up to this message] re: The key to a BSOD! XP is Def, SB16 not to blame Monday, July 17, 2006 at 6:42 pm Posted by Kyle (1 messages posted) WOW U ARE A HUGE HELP MAN, if i posted my errors would you help me find the culprit? [Reply or follow-up to this message] Core Problem WIN32K.SYS Cause Effect and Repair MyEppliance Sunday, October 8, 2006 at 8:27 am Posted by myeppliance (1 messages posted) Three main reasons are a Formatting the drive from win32 to NT using the quick option = Reformat with out quick Corrupt Office 2000 files = Reinstall Office Replacement Memory at Different Clock Speeds = Match Speeds USB 2.0 Device v Power In USB 1.0 Port = Update Bios and or OS Multi-User Win32 Driver Win32k Entry PointsKernel Service Table •Gensrv.exegenerates Systable.asm •Builds three tables in win32k.sys–W32pServiceTable (function & Return value) –W32pArgument–TableProvidedto NT kernel via KeAddSystemServiceTableon initialization •nt¥base¥ntos¥ke¥i386¥trap.asm [Reply or follow-up to this message] re: Core Problem WIN32K.SYS Cause Effect and Repair MyEppliance Wednesday, November 8, 2006 at 3:58 pm Posted by chris (1 messages posted) So... I had one of my clients computers with this problem... and it turned out that this guy had hundreds of viruses/spyware on his machine. I ended up reformating and it works fine now. HTH [Reply or follow-up to this message] re: Core Problem WIN32K.SYS Tuesday, December 12, 2006 at 8:06 am Posted by MaJiX04 (1 messages posted) The win32k.sys problem aflicts hundreds of users throughout the year on a daily basis with there being no apparent reason for this, sometimes it's down to faulty drivers, bad memory, overheating even the odd bad stack caller. But in my experience of dealing with problem and I've dealt with this on a number of occasions via different pc's and through instances not of my own making. But the results and answers in getting the systems running again or valid fixes. Most of the time you will be told to check your memory first with memtest86, worth doing..anyway..! Then open your case and check to see how dirty the lil bugger is, see if all the fans are still turn'nin. CLEAN INSIDE. (nb) Common one this, for creating problems. Now reseat your memory with your pc switched off at the wall, and do the same with everthing else, also it's a good idea to remount your cpu with some new artic silver grease, remember make a very thin contact surface. Most common reason for the non-page-error associated with bsod that accompanies this problem is... wait for it... My computer-properties-advanced-performance-settings-advanced-virtual memory-change Depending on how much Ram you have installed and the os installation your virtual ram settings should be ajusted for the requirments of the system, don't let the pc do it. Ajust it yourself. If you have selected no paging then your problem is here and you need to select custom settings. for say 512mb set 800mb min and max 1gig 1200min and max on every bootable part of the drive ie: xp installation drive c: after which your problems should disapear. [Reply or follow-up to this message] re: Core Problem WIN32K.SYS Monday, December 25, 2006 at 4:28 pm Posted by Bee Welbourne (1 messages posted) Please could someone help a bit of a novice please... I have been having blue screen win32k.sys problems for a few months now on my laptop and reading on here, it seems my best first option is to reduce my cpu speed a bit. Can anyone tell me how to do this please... Oh and i had a brand new pc today and i was on it for 4 hours then got dreaded blue screen. The only common factor between both pc's(well one is a laptop the other a pc) is my blueyonder installation.... may i ask, what provider is everyone using? Please please take pity on a novice..... [Reply or follow-up to this message] re: Core Problem WIN32K.SYS Tuesday, January 16, 2007 at 9:32 am Posted by cloudsBro (1 messages posted) I also get the win32k.sys error. It happens when I attempted to install my Printer and also it happens randomly for no apparent reason. Also if I try to play a game, it will quit to the desktop... any help?? I use 512 RAM windwos XP SP1 [Reply or follow-up to this message] re: Core Problem WIN32K.SYS Thursday, February 1, 2007 at 4:16 pm Posted by sal (1 messages posted) Ok here is what helped me. I had 758memory 2 sticks one of the memory sticks was after market. the after market was 256 i removed it and that solved my problem. right now im running with only 512 memory. So there is your easy fix do that should help alot of you out there. I read that 80% of these win 32k. sys problems are memory realted and i will tend to agree with that now :). hope this helped posted this because i know it will help alot of you out there. now im looking to buy another 512 of memory :). On Tuesday, January 16, 2007 at 9:32 am, cloudsBro wrote: >I also get the win32k.sys error. It happens when I attempted to install my Printer >and also it happens randomly for no apparent reason. Also if I try to play a game, >it will quit to the desktop... any help?? >I use 512 RAM windwos XP SP1 [Reply or follow-up to this message] re: Core Problem WIN32K.SYS Tuesday, May 1, 2007 at 12:17 am Posted by SomeGuy (1 messages posted) Hi, I've been having blue screens of all sorts & flavours for the past 2 weeks, finally I decided to try to fix it. After over 20 hours of effort, guess what the fix actually was? Simply cleaning the dust from inside my PC! And I didn't even have that much dust... I mean I've seen some pretty dusty systems, mine was just a little bit dusty. I did take my P4 CPU heatsink off & cleaned in there. I also cleaned my fans & video card (without taking it off), and I did not really touch my RAM. My CPU was NOT overheating beforehand (I tested that), my RAM was NOT faulty (I tested that too), my fan speeds were fine, my voltages were fine, my RAM clock speeds & CPU clock speed were fine... I actually initially thought I had installed something that had corrupted parts of Windows, I actually spent the bulk of my time trying to Repair XP PRO SP2... where I ran into all sorts of other issues including a very common 34 minute install hang / loop problem (*ucking MS) that was resolved by breaking my RAID mirror... anyway, it all came down to just dust! How do I know, because the quickest way for me to BSOD was to play a couple of videos simultaneously. I.e. load up 2 or 3 simultaneous Youtube videos and Poof! sometimes I would do nothing... the system would sit idle and 3 hours later.. BSOD! After I cleaned the dust, I rebooted & ran (no exageration) 10 simultaneous videos from .AVI, MPG & .WMV files of my HD + 7 Youtube videos, MSN messenger, Yahoo messenger, Mcafee antivirus, Ms Outlook & a few internet explorer & Firefox web sessions... no crash, just the CPU pinned at 100% for about 15 minutes. The system I have: Gigabyte motherboard GA-8IEXP 1 GB RAM (2x 512MB) ATI All in Wonder 2006 w/ 256MB RAM DVD read/write 2x Maxtors Ultra ATA 16, 300 GB in RAID 1 (mirror) 1x Western Digital 80 GB HD Onboard Intel 10/100 PRO NIC XP Pro SP2 with all the latest updates (as of April 2007) Good luck with your problem! someguy [Reply or follow-up to this message] re: The key to a BSOD! This is what you have been looking for. Tuesday, August 14, 2007 at 8:58 am Posted by Mr.T (1 messages posted) Well well well .... WINAMP IS THE SUSPECT !!! ANYBODY HAVE A TIP WHAT TO DO ? Could not read faulting driver name *** WARNING: Unable to verify timestamp for win32k.sys Probably caused by : win32k.sys ( win32k!NtUserfnIMECONTROL+2b4 ) Followup: MachineOwner --------- PAGE_FAULT_IN_NONPAGED_AREA (50) Invalid system memory was referenced. This cannot be protected by try-except, it must be protected by a Probe. Typically the address is just plain bad or it is pointing at freed memory. Arguments: Arg1: fffffa80047dc000, memory referenced. Arg2: 0000000000000000, value 0 = read operation, 1 = write operation. Arg3: fffff97fff17efd4, If non-zero, the instruction address which referenced the bad memory address. Arg4: 0000000000000000, (reserved) Debugging Details: ------------------ Could not read faulting driver name READ_ADDRESS: fffffa80047dc000 FAULTING_IP: win32k!NtUserfnIMECONTROL+2b4 fffff97f`ff17efd4 8b4630 mov eax,dword ptr [rsi+30h] MM_INTERNAL_CODE: 0 CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: DRIVER_FAULT BUGCHECK_STR: 0x50 PROCESS_NAME: winamp.exe CURRENT_IRQL: 1 LAST_CONTROL_TRANSFER: from fffff800010a58f2 to fffff8000102e950 STACK_COMMAND: kb FOLLOWUP_IP: win32k!NtUserfnIMECONTROL+2b4 fffff97f`ff17efd4 8b4630 mov eax,dword ptr [rsi+30h] SYMBOL_STACK_INDEX: 49 SYMBOL_NAME: win32k!NtUserfnIMECONTROL+2b4 FOLLOWUP_NAME: MachineOwner MODULE_NAME: win32k IMAGE_NAME: win32k.sys DEBUG_FLR_IMAGE_TIMESTAMP: 45e6f310 FAILURE_BUCKET_ID: X64_0x50_win32k!NtUserfnIMECONTROL+2b4 BUCKET_ID: X64_0x50_win32k!NtUserfnIMECONTROL+2b4 Followup: MachineOwner --------- 1: kd> lmvm win32k start end module name fffff97f`ff000000 fffff97f`ff460000 win32k M (pdb symbols) C:\WINDOWS\Symbols\sys\win32k.pdb Loaded symbol image file: win32k.sys Image path: win32k.sys Image name: win32k.sys Timestamp: Thu Mar 01 16:36:48 2007 (45E6F310) CheckSum: 00459B42 ImageSize: 00460000 Translations: 0000.04b0 0000.04e0 0409.04b0 0409.04e0 [/quote] [Reply or follow-up to this message] re: BSOD, win32k.sys Friday, November 2, 2007 at 4:05 pm Posted by Brian (2 messages posted) I have a Sony VAIO PCV-RX540 that has the BSOD problem too! My system is: -1.2 Ghz Celeron -512 Mb System RAM -ATI Radeon 7500 Graphics /w DVI, S-VIDEO in/out and Cable TV in and 64 Mb DDR2 video memory -20 Gb Hard Drive -Windows XP Home Service Pack 1 -17" CRT Monitor -Pioneer DVD-ROM -HP DVD Writer 740b -Floppy Disk Drive ---------------------------------- The BSOD involves win32k.sys and says at the top: KERNEL_DATA_INPAGE_ERROR ------------------------------------- When I come out of standby mode I get this BSOD! Please help! [Reply or follow-up to this message] re: BSOD, win32k.sys Saturday, November 3, 2007 at 9:58 pm Posted by Vtornik (1 messages posted) I get this too. It started with SP2. I think it is the DEP which is causing the problem. Turn it off. [Reply or follow-up to this message] re: BSOD, win32k.sys Tuesday, November 13, 2007 at 1:53 pm Posted by Davey Nelson (1 messages posted) I recently (3 wks) started getting this BSOD with win32k.sys sporadically after a Windows update. The first 10~20 times I was able to reboot, skip disk scan and get back in Windows. Now, I can't even boot into safe mode. I did notice every time I recover from a previous crash my SB24bit system icon would be disabled. I saw someone above saying SB was a problem. I updated the drivers and still got BSOD. Also notice that BSOD happens right before XP shows the Welcome screen. Someone also had the same problem and suggested disabling DEP. I need to try this. Otherwise I've tried everything mentioned aboved. One time it was a ipinet.sys(?) error on the BSOD. Wasn't able to update video driver cuz I couldn't even get in safe mode anymore. XP Pro, SP2 Acer Open, Nvidia2 MB AMD XP 2500+ (not overclocked) 512mb Cosair DDR 3200 (CAS3) ChainTech FX5500 256mb SB Live! 24 bit. On Saturday, November 3, 2007 at 8:58 pm, Vtornik wrote: >I get this too. It started with SP2. I think it is the DEP which is causing the problem. >Turn it off. [Reply or follow-up to this message] re: BSOD, win32k.sys Tuesday, December 18, 2007 at 10:30 am Posted by tommmy (1 messages posted) Go to C:\WINDOWS\System32 and rename the Win32k.sys file to Win32k.old and then close the window. Now go back to the system32 folder and you will have a new and non-corrupt Win32k.sys file. Try that, good luck [Reply or follow-up to this message] re: BSOD, win32k.sys Sunday, December 30, 2007 at 4:17 pm Posted by faeriedragon (1 messages posted) I've been having similiar problems as a lot of you have described here for the past month AT LEAST. I cannot, for the life of me, figure out what is going on. I've had the same set up for the past 5 plus years, with a few upgrades here and there. I use a Dell 4400 with Intel P4, Nvidia graphics card, and I've updated the latest drivers. I've even reinstalled XP from scratch around the same time the BSOD's started. Sometimes the computer just hangs and there is no response from the mouse and keyboard, which are both USB. I read up on this and found out it could be a PS/2 issue, although I don't use PS/2 for the mouse and keyboard. I even tried a new'ish mouse and still have this issue. I've read that you can turn off the PS/2 to stop this from happening (but I haven't tried this yet.....) HOWEVER, I also get the BSOD. Today, I started to keep track. So far, it has happened three times. Once with the win32.sys error; once with an afd.sys error and once with no direct file error. I'm wondering if the BSOD errors are due to XP..... So my challenge for you all out there is: Has anyone tried installing Linux to see if MAYBE it's a Win incompatibility issue and not just simply a hardware or software issue? I'm seriously considering loading Linux just out of curiosity of this hypothesis. But if anyone else has tried this with success and you no longer have these BSOD issues, please please post here and let us know! On Tuesday, December 18, 2007 at 10:30 am, tommmy wrote: > >Go to C:\WINDOWS\System32 and rename the Win32k.sys file to Win32k.old and then >close the window. Now go back to the system32 folder and you will have a >new and non-corrupt Win32k.sys file. Try that, good luck [Reply or follow-up to this message] re: BSOD, win32k.sys Thursday, January 24, 2008 at 3:22 pm Posted by Cynthia (1 messages posted) I started getting the win32k.sys problem too, about two weeks ago, actually. It seems to have accerlerated. I found it happens if you have too many tabs up on the internet or running video (like someone else posted before). I was able to contact the Dell people-- my computer may be out of warranty, but a nice person helped out anyway-- and they suggested to restart the whole Windows XP...I lost everything, all my downloads, and the win32k.sys is still attacking my computer! Someone please solve this problem! On Thursday, January 16, 2003 at 5:47 pm, sac wrote: >I am also getting the win32k.sys fault. I also have a geforce video card. As far >as I understand from reading about it online, a lot of people are getting this fault >and I haven't found the cure for it yet. if anyone knows how to fix it please let >me know > > [Reply or follow-up to this message] re: BSOD, win32k.sys Saturday, February 9, 2008 at 2:41 pm Posted by Joe (2 messages posted) I really don't think this is a software issue - I have been troubleshooting this issue for almost a month and I build computers for a living - have an Asrock 760gx chipset, 2x512mb ram and I believe I have finally come up with a solution - I get random blue screen (BSOD) errors constantly (including win32k.sys, ntfs.sys, and many others) at random and have re-done the cpu heatsink and fan, used Sandra burn-in test to check the system and during the burn-in it crashes randomly - have narrowed it down to a temperature issue. If I put a small but powerful fan blowing on the motherboard it will run fine with no crashes. So I am thinking memory is overheating because when I run MS mem test it has memory errors without the fan. So it is either memory or the motherboard chipset that is getting too hot and causing errors. So anyone with random errors such as this I suggest trying this - I was about to throw out the motherboard until I tested this theory of overheating memory. I will narrow it down - the chipset cooler is a heatsink with no fan, so maybe replacing that with an active cooling fan may help, or adding ram heatsinks, one or the other or both should solve this once and for all. Note: before adding the fan, when running Sandra environment monitor all the temps are within normal range while doing the burn-in. Hopefully this can help others who have been pulling hair out!!! :-) So, first step, backup your important files, check for viruses & spyware, clean out your fans and dust - then check memory, power supply and system temperatures (my mainboard temp averages 26-32 deg c and cpu 28-63 c, (I do recommend the Sandra tools to do a burn-in test to quickly check because that will stress your computer and if it's going to crash it will when running this) then do this fan trick and see if that stops the crashes. [Reply or follow-up to this message] BSOD, win32k.sys Thursday, June 12, 2008 at 3:58 pm Posted by Dan (3 messages posted) I am also having this problem, but it only happens when I am running a new game I just bought, Mass Effect. I know it isn't because I don't meet the system requirements, because I am well within the recommended range. I have also had other BSOD errors. Sometimes with the win32k.sys I get a 0x0000008E errors and other times I get a Bad_pool_header error with 0x00000019. Does anyone have any ideas what is causing this? [Reply or follow-up to this message] re: BSOD, win32k.sys Wednesday, July 30, 2008 at 3:47 am Posted by samreay (4 messages posted) Yes, there is another one out there with the accursed BSOD 0x8E(0x5) error, with a reference to the horrible WIN32K.SYS file... Basically the computer system is BRAND NEW but there have been some issues with microsoft xp and the motherboard optical drivers, which have been resolved and may have nothing to do with the problem. Basically, as a student, I have downloaded Revit2009 form the Autodesk site (now 4 times)... and each time I run it, and make a new project, it BSOD's me. This, is starting to...frustrate...me. I KNOW it is not a RAM issue (Memtest twice, Miscrosoft Memory Diagnostic, switching modules), nor a Hard Drive issue (done the tests as well)... and as the system is less then a month old I dont see you it owuld really be anything hardware nor heating (I mean Ive got a ton of fans seriously, and the Q9300 processor is one of the cooler ones on the market). Ive done the chkdsk cmd thing, renamed win32k.sys to win32k.old, disabled the opitcal drivers that had previously stuffed everything up, updated my nvidia drivers, checked the event viewer (which showed no errors remarkably)... and Im at my wits end. Any ideas on what could be causing the problem would be greatly appreciated. [Reply or follow-up to this message] re: BSOD, win32k.sys Wednesday, July 30, 2008 at 7:41 pm Posted by Dan (3 messages posted) I gave up on trying to fix this because the solutions everyone else was giving me were doing nothing. I just went for the reformat of the hard drive, which I wouldn't recommend unless u are desperate, but it worked. If you decide to reformat just make sure you have all the documents you want to keep saved on another computer or flashdrive, cd, etc. Also make sure you have the cd for your operation system because if you format and find you dont have it you have a very big paper weight untill u purchase a new operating system. You also may want to make sure you have the cds for your programs too if you dont want to go out and buy another copy. On Wednesday, July 30, 2008 at 3:47 am, samreay wrote: >Yes, there is another one out there with the accursed BSOD 0x8E(0x5) error, with >a reference to the horrible WIN32K.SYS file... > >Basically the computer system is BRAND NEW but there have been some issues with microsoft >xp and the motherboard optical drivers, which have been resolved and may have nothing >to do with the problem. Basically, as a student, I have downloaded Revit2009 form >the Autodesk site (now 4 times)... and each time I run it, and make a new project, >it BSOD's me. > >This, is starting to...frustrate...me. > >I KNOW it is not a RAM issue (Memtest twice, Miscrosoft Memory Diagnostic, switching >modules), nor a Hard Drive issue (done the tests as well)... and as the system is >less then a month old I dont see you it owuld really be anything hardware nor heating >(I mean Ive got a ton of fans seriously, and the Q9300 processor is one of the cooler >ones on the market). Ive done the chkdsk cmd thing, renamed win32k.sys to win32k.old, >disabled the opitcal drivers that had previously stuffed everything up, updated my >nvidia drivers, checked the event viewer (which showed no errors remarkably)... and >Im at my wits end. > >Any ideas on what could be causing the problem would be greatly appreciated. > [Reply or follow-up to this message] re: BSOD, win32k.sys Monday, August 18, 2008 at 7:40 am Posted by Dave (1 messages posted) Hi Ryan: I was just curious if you ever solved the problem below you had back in 2003??? I am having the same problem now and I can't for the life of me figure it out I've reinstalled windows changed RAM with no success, Can you help me? Dave On Sunday, January 19, 2003 at 11:58 am, ryan wrote: >I'm getting this error too, however i DON'T have a geforce video card....my system >is a 1.4 GHz Athlon 512 MB ram and an old old old old video card of which i don't >even know the name. win32k.sys is usually (but not always) named along with the PAGE_FAULT_IN_NON_PAGED_AREA >error. I also get these other errors: > >DRIVER_IRQL_NOT_LESS_OR_EQUAL_TO > >IRQL_NOT_LESS_OR_EQUAL_TO > >BAD_POOL_CALLER > >These errors have each implicated different .sys and .dll files at different times. >I'd recommend searching through the post on this forum which deals with the IRQL >errors. Some posters on there have had success with switching cards to different >PCI slots and replacing their ram. I don't know if any of these problems are related >(in fact I doubt it), but I hope we get to the bottom of this soon. > >Check Here http://www.annoyances.org/exec/forum/winxp/n1022109789 [Reply or follow-up to this message] re: BSOD, win32k.sys Friday, August 29, 2008 at 1:10 am Posted by Xeno1 (3 messages posted) Just thought I'd let everyone know that I had this same problem for about the last week or so and I managed to solve it, at least on my machine anyway. It turned out to be a problem between Winamp and my CMI8738 sound card drivers. What was weird is that after that my sound card drivers refused to uninstall so I could reinstall new drivers, even after multiple reboots and in safe mode. In the end, I had to pull the sound card. Hope maybe this helps someone else having this same problem. [Reply or follow-up to this message] re: BSOD, win32k.sys, at the end of my chain Sunday, August 31, 2008 at 11:23 pm Posted by Yourmicrowhat (4 messages posted) I've read this thread from top to bottom and nothing worked. Dell Inspiron 4700 Windows XP Pro SP2 Intel 2.8 GHz 512MB PC3200 (Dell brand) I can't get the machine into regular mode, I can't get the machine into safe mode, it's a SATA hard drive which doesn't show up in emergency DOS mode and the error is always the same. STOP: 0x0000008E (0xc0000005, 0xbf803eb6, 0xf86b47c4, 0x00000000) win32k.sys - address bf803eb6 base at bf800000, datestamp 47e0e106 Moving memory hasn't worked, using different memory didn't work, Dell are idiots and locked the clock speed of the memory, and I can't do anything file related because I can't get the machine to boot into anything that let's me access the hard drive. The fixboot and fixmbr commands in the recovery console didn't work either. I even tried taking another drive from a second machine that had a working installation of windows XP on it to try to get the machine to boot and I still get the same behavior. The last thing I can think to do is just get another mother board after that I'm out of ideas. [Reply or follow-up to this message] re: BSOD, win32k.sys, at the end of my chain Monday, September 1, 2008 at 11:49 am Posted by Xeno1 (3 messages posted) Try this, go to http://support.microsoft.com/kb/307545 and follow the directions on that page. What you're going to be doing is manually restoring your registry to an earlier point through the windows recovery console. I would definitely print out a copy of this because it's not a short, or easy process by any means but I've done this myself a few times and it's worked every time. I would suggest that you print out a copy of the instructions because they're pretty lengthy and involved. Good luck. [Reply or follow-up to this message] re: BSOD, win32k.sys, at the end of my chain Tuesday, September 2, 2008 at 8:00 pm Posted by Yourmicrowhat (4 messages posted) Well I had hope but got as far as "Do not use this method on an OEM installation of Windows". Since this is an installation that came with the computer when it was bought I can't use that method. Thanks for the effort though. [Reply or follow-up to this message] re: BSOD, win32k.sys, at the end of my chain Tuesday, September 2, 2008 at 8:29 pm Posted by Xeno1 (3 messages posted) By any chance did you install Winamp recently? It seems to be the biggest cause of this problem. Actually it's the Sonic Burning engine that it installs with it that causes the problem. If so, try booting in to the windows repair console and then change the directory to system32 -(cd\system32) and delete the following files: px.dll pxcpya64.exe pxcpyi64.exe pxdrv.dll pxhpinst.exe pxinsa64.exe pxinsi64.exe pxmas.dll pxsfs.dll pxwave.dll pxwma.dll vxblock.dll I'm not sure how experienced you are at doing this kind of stuff, but all you have to do is type in del then a space and then each of the above files, one at a time. Then change the directory to drivers -(cd\drivers) and delete PxHelp20.sys Otherwise, it looks to me that you may be in for a windows reinstall. [Reply or follow-up to this message] re: BSOD, win32k.sys, at the end of my chain Wednesday, September 3, 2008 at 11:15 am Posted by Yourmicrowhat (4 messages posted) Unfortunately no dice on that try either. I'm thinking it might be something more serious than a simple corrupt file. I swapped in the hard drive from another computer that had a working copy of windows XP on it and it won't boot in this machine either yet when I swap it back to its original machine it boots fine. I can't be 100% certain because the original drive from the non-booting machine is a SATA interface and all my other machines are EIDE and don't have any SATA ports. So I can't swap the original drive from the non-booting machine to one of my other machines that does work. I'm going to try a fresh Windows install in the non-booting machine on an empty drive I have before I go for a reinstal on the original drive in hopes I can save the files on it, that or get a SATA to EIDE adapter and try to save them that way. Thanks for trying. [Reply or follow-up to this message] re: BSOD, win32k.sys, at the end of my chain Thursday, September 4, 2008 at 1:14 pm Posted by Yourmicrowhat (4 messages posted) Ok a friend that was having the same problem, and who's laptop was also a dell and still under waranty, called up Dell. They told him to hold down ctrl and F11 durring boot up and it would take him to the restore default installation option. This would return the BIOS and Windows back to the state the machine was shipped to the store. It took about 10 minutes and all of the settings had to be redone in Windows, and any other programs that had been installed by the user were lost. The drivers for all the hardware were kept though so atleast that's one headache I don't have to go through. Thanks for the replies. [Reply or follow-up to this message] re: BSOD, win32k.sys, at the end of my chain Sunday, September 7, 2008 at 10:50 am Posted by Jill Heayn (2 messages posted) I have the exact same error message, and I too, cannot boot my pc. Please let me know if you find a fix. Thanks. I had a similar error message on my laptop, but was able to catch the problem before losing the opsys. On Sunday, August 31, 2008 at 11:23 pm, Yourmicrowhat wrote: >I've read this thread from top to bottom and nothing worked. > >Dell Inspiron 4700 >Windows XP Pro SP2 >Intel 2.8 GHz >512MB PC3200 (Dell brand) > >I can't get the machine into regular mode, I can't get the machine into safe mode, >it's a SATA hard drive which doesn't show up in emergency DOS mode and the error >is always the same. > >STOP: 0x0000008E (0xc0000005, 0xbf803eb6, 0xf86b47c4, 0x00000000) > >win32k.sys - address bf803eb6 base at bf800000, datestamp 47e0e106 > >Moving memory hasn't worked, using different memory didn't work, Dell are idiots >and locked the clock speed of the memory, and I can't do anything file related because >I can't get the machine to boot into anything that let's me access the hard drive. > >The fixboot and fixmbr commands in the recovery console didn't work either. I even >tried taking another drive from a second machine that had a working installation >of windows XP on it to try to get the machine to boot and I still get the same behavior. >The last thing I can think to do is just get another mother board after that I'm >out of ideas. > > [Reply or follow-up to this message] BSOD win32k.sys among others Tuesday, September 9, 2008 at 7:03 am Posted by Paul (1 messages posted) Okay you say you can download the new ... but I can not boot up in safe mode or any other unfortunately I did not get a system operating disk when I bought this package deal on TV can chkdsk / f fix this if I put this harddrive on another pc as a slave? On Monday, May 19, 2003 at 2:33 pm, Prince_Saiyan wrote: > >you guys can help eliminate this problem by downloading the new 44.03 Detonator Driver >for your nVidia Cards (like GeForce). A friend of mine had EXACTLY those problems >with PAGE_FAULT_IN_NONPAGED_AREA and win32k.sys. but NEVER again after he updated >the Detonator drivers. Try it... > [Reply or follow-up to this message] re: BSOD win32k.sys among others Monday, November 24, 2008 at 10:22 am Posted by Chris Robertson (10 messages posted) Always skip to the bottom and see how the story ends... Here is what you do. There is a little memory test utility (memtest, an HCI design). Run this (or another memory testing program) in safe mode, eliminating the video drivers This tells you if it is memory or driver error.. It is a combination of both or either really. Some memory has problem at the higher end and when you load it up because of video games it tends to crash, plus poor, old etc. memory will failover or die. If possible, get memory that is rated faster then your factory. This will ensure, to a degree, that it can handle the speed, and intensitity. If you find your memory is good, go back and run the test in regular mode and see if it crashes. If it does, it may be the driver/card combo. I really doubt it. Might even try to increase the memory. Sometimes you system allocates some of the memory, and your video driver doesn't know this. Then your video driver attempts to over right memory reserved for the system. Oh there are several things that can cause this. Just eliminate one at a time. On Tuesday, September 9, 2008 at 7:03 am, Paul wrote: >Okay you say you can download the new ... but I can not boot up in safe mode or any >other unfortunately I did not get a system operating disk when I bought this package >deal on TV can chkdsk / f fix this if I put this harddrive on another pc as a >slave? > > > [Reply or follow-up to this message] re: BSOD, win32k.sys Friday, January 2, 2009 at 3:55 pm Posted by john (1 messages posted) irql is software irq is hardware On Monday, January 20, 2003 at 5:36 pm, Jim wrote: >Same Problem here too. I have an ATI Radeon 7000 video card, 850mhz AMD Duron. >Any help would be appreciated. > > [Reply or follow-up to this message] re: BSOD, win32k.sys Sunday, January 4, 2009 at 7:07 am Posted by kdog (1 messages posted) hi i got most of these BSOD erros and i also get applictations closeing randomly.... i dont think it is my video card because if it was my vidseo card monitering software would have told me that something is wrong. and so far it hasn't i can't overclock my computer because it doesn't let me even with aftermarket overclocking software... so i can't change any clocking on my computer from what it was when it came off the gateway assembaly line.. i also get BSODs with drivers like: FSDFW.sys and i get the DRIVER_IRQL_LESS_OR_NOT_EQUAL what could be my problem.. im hoping it doesn't cost me any money. On Tuesday, July 1, 2003 at 7:36 pm, David R wrote: > >Success! I can echo the experiences of everyone here. The actual circumstance was >never consistent, and rarely repeatable, but included application hangs and spontaneous >reboots with references to win32k.sys, various explorer files, various dll files, >invalid page faults, PAGE_FAULT_IN_NONPAGED_AREA, DRIVER_IRQL_NOT_LESS_OR_EQUAL ... >the list goes on and on. > >This has been going on since I built this machine in November 2002. I feel like >I've followed every suggestion feasible with no success. However, when people continued >to bring up overheating, I wrongly assumed they were talking about the well known >Athlon overheating issue. I installed a fan in front, one in back, the built in >fan in the power supply and a Thermaltake Volcano 7 on the processor. By the way, >my setup is: MSI KT3 Ultra-ARU, Athlon 1800+, ABIT Siluro GEForce3 Ti200, Soundblaster >Audigy, 512MB PC2700 RAM, 300w Power Supply > >So, it turns out that it wasn't my processor that was overheating, it was my video >card. The card has its own cooling fan built in, so I figured it could take care >of itself. However, my sound card was in the next slot below the video card, leaving >just a few mm clearance between the two. Furthermore, I noticed the ribbon cables >were further blocking airflow over the video card. When I think back, the only common >thing about my problems was that they all happened while the video card was painting >a window. > >To test if this is your problem also, take the side off your PC and use a box fan >to make sure there's plenty of circulation around your video card. My PC has been >up and running for almost a week now, and I've been beating up on it with everything >I can think of (this PC has never run for this long before). To fix it, I didn't >do anything except move my sound card down one slot. Excuse me my long-windedness, >but I feel like shouting it from the rooftops. I can't believe I finally fixed this, >the most exasperating problem of my PC-based life. [Reply or follow-up to this message] re: BSOD, win32k.sys Thursday, March 12, 2009 at 9:48 pm Posted by Jim (3 messages posted) Am having a similar problem with the blue screen of death, though it only happens rarely I know everytime I try and do a video call in windows live messenger it happens all the time below is the info from my last 2 crashes: On Thu 12/03/2009 9:29:06 PM your computer crashed This was likely caused by the following module: win32k.sys Bugcheck code: 0x1000008E (0xC000001D, 0xE4013BB0, 0xB5B32A2C, 0x0) Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M file path: C:\WINDOWS\system32\win32k.sys product: Microsoft® Windows® Operating System company: Microsoft Corporation description: Multi-User Win32 Driver The crash took place in a standard Microsoft module. Likely the culprit is another driver on your system which cannot be identified. On Fri 20/02/2009 10:02:15 PM your computer crashed This was likely caused by the following module: win32k.sys Bugcheck code: 0x1000008E (0xC000001D, 0xE2B9A3A0, 0xB5BE12BC, 0x0) Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M file path: C:\WINDOWS\system32\win32k.sys product: Microsoft® Windows® Operating System company: Microsoft Corporation description: Multi-User Win32 Driver The crash took place in a standard Microsoft module. Likely the culprit is another driver on your system which cannot be identified. Am running XP home on a intel dual core prccesor, 2gigs of ran, using the onboard sound card realtek highdefinition audio and a Nvidia Gforce 512mb video card. I have a feeling in maybe my video card but have no proof of that just from other posts Ive read from others they all tend to have a Gforce also. Anyhow if anyone can help me I'd appreciate it alot. Cheers, Jim [Reply or follow-up to this message] re: BSOD, win32k.sys Sunday, March 22, 2009 at 9:25 am Posted by jaakske (1 messages posted) after reading all this submissions, lowering the ram frequency seams to have worked for me, thanks to all the people that make this reply's, thank u from belgium [Reply or follow-up to this message] re: BSOD, win32k.sys Friday, May 1, 2009 at 2:38 pm Posted by gibby (1 messages posted) If you are getting the blue death screen crash periodically, follow the instructions here to repair any corrupt system kernel files, it's simple and works wonders!!! Reboot normally, click start, run, type cmd, click ok. At the command prompt type cd\ and hit enter. At the c:\ prompt (should look like this c:\>) type sfc scannow, hit enter. Let the system perform it's scan. If any of your system kernel files are damaged or corrupt, a window will pop up asking you to insert your windows cd. This means one or more programs on your system is causing the blue screen and has damaged or corrupted a system kernel file. Insert your windows cd and let the scan finish doing its thing, everything will be fixed automatically, takes 15 min or so. When done, type exit at the command prompt and reboot your computer, remove the windows cd after booting up. Your blue screen problems should be resolved. Your system kernel files have been repaired, actually they have been replaced by the original & correct files from your windows cd.... Hope this helps everyone dealing with the damned blue death screen! [Reply or follow-up to this message] re: BSOD, win32k.sys Monday, September 28, 2009 at 1:27 am Posted by blazewing (1 messages posted) i get the same bsod only mine says driver_ircl_not_less_or_equal_to. i'm running a custom built machine based on the compaq presario's athalon motherboard and windows xp home edition. i get this error anytime....the thing is i didn't add any new software. it just pops up. i found a temporary fix, using the system restore,but that lasts about a week and than the bsod all over again. is there a permanent fix? On Tuesday, January 14, 2003 at 8:50 pm, Olivier Hubert wrote: > >Ok I'm relieved now, I thought I was the only one going mad with this. I have had >BSOD's for a week now and don't know why. The only thing our computers have in common >(that I see at first glance) is the GeForce4 card... > >My BSOD's show STOP 0x00000050 or 0x0000008E with PAGE_FAULT_IN_NONPAGED_AREA. Sometimes >nv4_disp.dll is faulty and sometimes win32k.sys and even wmaud.sys once (I think). > >Athlon 2400+ >Asus A7N8X (nForce2 chipset) >512 MB DDR 2700 >Asus GeForce4 Ti4600 > > [Reply or follow-up to this message] Tip: Use one of the [Reply or follow-up to this message] links above to add a message to this thread Search this forum Start a new thread on a different subject Report abuse of the forum Return to the Windows XP Discussion Forum