BSOD (win32k.sys)

[Under Zero]

Hi everybody
I have bought new computer and I have some Blue screens
I want to know if this error is not from the hardware.

OS: Windows XP SP2
CPU: Core2duo 2.33 GHz
Graphic Card: Geforece 8600 GTS (256MB)
Ram: 4GB
Motherboard: Gigabyte GA-P35-DS3L

here is the dump:

Microsoft (R) Windows Debugger Version 6.6.0003.5
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\WINDOWS\Minidump\Mini112507-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: *** Invalid ***
****************************************************************************
* Symbol loading may be unreliable without a symbol search path. *
* Use .symfix to have the debugger choose a symbol path. *
* After setting your symbol path, use .reload to refresh symbol locations. *
****************************************************************************
Executable search path is:
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
Unable to load image ntoskrnl.exe, Win32 error 2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Windows XP Kernel Version 2600 (Service Pack 2) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055c700
Debug session time: Sun Nov 25 20:10:36.218 2007 (GMT+2)
System Uptime: 0 days 1:12:20.940
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
Unable to load image ntoskrnl.exe, Win32 error 2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Loading Kernel Symbols
.............................................................................................................................
Loading User Symbols
Loading unloaded module list
..............
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1A, {41284, 3897001, cd4, c0883000}

***** Kernel symbols are WRONG. Please fix symbols to do analysis.

*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : win32k.sys ( win32k+b8a0 )

Followup: MachineOwner
---------

 

[Tmagic650]

Your debugger dump info is invalid... You have not set the proper symbol path in the debugger

 

[Under Zero]

Thank you for reply
is it important to install symbol ?

 

[Tmagic650]

Of course it is important! You need the symbols to properly decode the error results. How did you get this far posting the dump files without understanding that you need to have the symbol files downloaded and installed on your C drive? Then you have to put the symbol file path in the debug tool

 

[Under Zero]

Thank you
OK I'll do that

 

[Under Zero]

Hi, I'm sorry I was busy so I couldn't post the Dump file.
here is the dump file:

Microsoft (R) Windows Debugger Version 6.6.0003.5
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\WINDOWS\Minidump\Mini120507-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: C:\WINDOWS\Symbols
Executable search path is:
Unable to load image ntoskrnl.exe, Win32 error 2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
Windows XP Kernel Version 2600 (Service Pack 2) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055c700
Debug session time: Wed Dec 5 08:38:23.500 2007 (GMT+2)
System Uptime: 0 days 11:35:03.242
Unable to load image ntoskrnl.exe, Win32 error 2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
Loading Kernel Symbols
.............................................................................................................................
Loading User Symbols
Loading unloaded module list
...........
Unable to load image win32k.sys, Win32 error 2
*** WARNING: Unable to verify timestamp for win32k.sys
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000008E, {c0000005, bf804976, b4bd7c1c, 0}

Probably caused by : win32k.sys ( win32k!HmgShareCheckLock+55 )

Followup: MachineOwner
---------

Also I want to say that I tested the RAM with MemTest and Goldmemory and they found 4 Errors.

 

[Tmagic650]

You still have trouble with the debugger. Post the minidump file only and let me decode it

 

[Under Zero]

OK here it is in the attachments

 

[Tmagic650]

"One cause may be that the virtual memory of Windows XP is corrupted. Disable and then enable the Virtual Memory to see whether it solved the problem"...

To disable Virtual memory:

1. Right click My Computer and choose properties
2. Click the Advanced tab
3. Under Performance click settings.
4. Click the Advanced tab.
5. Under Virtual memory click change
6. Click no paging file
7. Click OK
8. Restart the computer

To enable Virtual memory:

1. Right click My Computer and choose properties
2. Click the Advanced tab
3. Under Performance click settings.
4. Click the Advanced tab.
5. Under Virtual memory click change
6. Click System Managed Size
7. Click OK
8. Restart the computer

 

[Under Zero]

don't you think the problem is from the RAM ?
because I reinstalled the windows and the problem is not solved yet.
Also as I said I tested the RAM and I found 4 Errors.

I'll do what you said and I hope it solves the problem

I want to know how can I make the blue screen appear because I want to know if the problem is solved or not

and thank you for your helping.

 

[Tmagic650]

"Also as I said I tested the RAM and I found 4 Errors"...

Any RAM ERRORS are not GOOD! Replace the RAM too

 

[Under Zero]

Thank you. I'll go to the man who sold me the PC and make him replace the RAM.
would you mind posting the dump file so as to take it to the man who sold me the PC ?