re: BSOD, win32k.sys
Friday, October 3, 2003 at 5:24 am
Windows XP Annoyances Discussion Forum
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!
>
- Written in response to:
- re: BSOD, win32k.sys (Steven Z: Tuesday, September 30, 2003 at 2:32 pm)
Responses to this message:
|
|
All messages in this thread [show all]
 |  | | | | |  | Confused (Adri1456: Fri, May 14, 2004, 3:29 pm) |
| | | | | |  | re: BSOD, win32k.sys (Ryan Ruckel: Fri, Oct 3, 2003, 5:24 am) |
| | | | | | | Crash (greine12: Tue, Apr 6, 2004, 4:57 pm) |
| | | | | | | | | re: Crash (MadMan: Sat, Apr 10, 2004, 1:19 pm) |
| |
| |
| |
Return to the Windows XP Discussion Forum
|
|
