BSOD

**Omgporn** · 16th June 2009

Hiya, I've scored a new mothboard and processor 2 weeks ago. Using my same hard drive, disk drive etc. I've got a E8400 installed on a ASUS P5Q PRo

Been getting a few BSOD problems (mainly during closing links, changing songs on my media player)

I've got a few DMP files (which I've uploaded if you can help)

Message is :
0x0000008e (0xc00000005,0xbf83b9cL) and a few more, but didn't catch them

Then theres something talking about Win32k.sys

Any help would be amazing.

**Omgporn** · 16th June 2009

Note

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

Symbol search path is: SRVc:\symbols
Executable search path is:
Unable to load image ntoskrnl.exe, Win32 error 0n2
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 3) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Machine Name:
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055d720
Debug session time: Tue Jun 16 17:50:02.156 2009 (GMT+1)
System Uptime: 1 days 5:52:16.864
Unable to load image ntoskrnl.exe, Win32 error 0n2
* 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
..............
Unable to load image win32k.sys, Win32 error 0n2
* WARNING: Unable to verify timestamp for win32k.sys
* ERROR: Module load completed but symbols could not be loaded for win32k.sys
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*****************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000008E, {c0000005, bf83b9c1, a98e5600, 0}

* 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 *
* *
*
*
* *
* *
* 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 *
* *
*
*
* *
* *
* 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 *
* *
*
*
* *
* *
* 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 *
* *
*
*
* *
* *
* 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 *
* *
*
*
* *
* *
* 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 *
* *
*
*
* *
* *
* 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 *
* *
*
Probably caused by : win32k.sys ( win32k+3b9c1 )

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

0: kd> !analyze -v
*********
* *
* Bugcheck Analysis *
* *
*****************************************************************************

KERNEL_MODE_EXCEPTION_NOT_HANDLED_M (1000008e)
This is a very common bugcheck. Usually the exception address pinpoints
the driver/function that caused the problem. Always note this address
as well as the link date of the driver/image that contains this address.
Some common problems are exception code 0x80000003. This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG. This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG. This will let us see why this breakpoint is
happening.
Arguments:
Arg1: c0000005, The exception code that was not handled
Arg2: bf83b9c1, The address that the exception occurred at
Arg3: a98e5600, Trap Frame
Arg4: 00000000

Debugging Details:
------------------

* 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 *
* *
*
*
* *
* *
* 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 *
* *
*
*
* *
* *
* 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 *
* *
*
*
* *
* *
* 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 *
* *
*
*
* *
* *
* 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 *
* *
*
*
* *
* *
* 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 *
* *
*
*
* *
* *
* 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 *
* *
***********************************************************************

ADDITIONAL_DEBUG_TEXT:
Use '!findthebuild' command to search for the target build information.
If the build information is available, run '!findthebuild -s ; .reload' to set symbol path and load symbols.

MODULE_NAME: win32k

FAULTING_MODULE: 804d7000 nt

DEBUG_FLR_IMAGE_TIMESTAMP: 48025f2a

EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at "0x%08lx" referenced memory at "0x%08lx". The memory could not be "%s".

FAULTING_IP:
win32k+3b9c1
bf83b9c1 0000 add byte ptr [eax],al

TRAP_FRAME: a98e5600 -- (.trap 0xffffffffa98e5600)
ErrCode = 00000002
eax=00000001 ebx=00000000 ecx=00000000 edx=e23e2610 esi=e2c62ce8 edi=e123d7f0
eip=bf83b9c1 esp=a98e5674 ebp=a98e584c iopl=0 nv up ei pl zr na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010246
win32k+0x3b9c1:
bf83b9c1 0000 add byte ptr [eax],al ds:0023:00000001=??
Resetting default scope

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: DRIVER_FAULT

BUGCHECK_STR: 0x8E

LAST_CONTROL_TRANSFER: from 8054161c to bf83b9c1

STACK_TEXT:
WARNING: Stack unwind information not available. Following frames may be wrong.
a98e584c 8054161c 0701147f 00000000 e2dfc718 win32k+0x3b9c1
a98e5884 7c90e4f4 badb0d00 0012b118 045e0000 nt+0x6a61c
a98e5888 badb0d00 0012b118 045e0000 606c18ab 0x7c90e4f4
a98e588c 0012b118 045e0000 606c18ab bbe6be18 0xbadb0d00
a98e5890 045e0000 606c18ab bbe6be18 89a526b8 0x12b118
a98e5894 606c18ab bbe6be18 89a526b8 bbe6be18 0x45e0000
a98e5898 bbe6be18 89a526b8 bbe6be18 00001fab 0x606c18ab
a98e589c 89a526b8 bbe6be18 00001fab a98e5b48 0xbbe6be18
a98e58a0 bbe6be18 00001fab a98e5b48 00000000 0x89a526b8
a98e58a4 00000000 a98e5b48 00000000 3b040000 0xbbe6be18

STACK_COMMAND: kb

FOLLOWUP_IP:
win32k+3b9c1
bf83b9c1 0000 add byte ptr [eax],al

SYMBOL_STACK_INDEX: 0

SYMBOL_NAME: win32k+3b9c1

FOLLOWUP_NAME: MachineOwner

IMAGE_NAME: win32k.sys

BUCKET_ID: WRONG_SYMBOLS

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

**Omgporn** · 16th June 2009

I've got another dump that talks about my ATI drivers. Will try messing about with them.

**Soulassassin** · 16th June 2009

A bit obvious but did you format as all the drivers for the motherboard will be different.

**Omgporn** · 16th June 2009

Yes, had to format the drive many times now. Same problem. Installing windows using that computer too.

**TotallyRandom** · 16th June 2009

Right so you fitted new board,
Installed Windows Windows XP Kernel Version (Service Pack 3) New disk /Downloaded ?

Did you install Driver any any order?
Did you install the latest ones from the web site?
Chipset (mobo) first
Video second
Audio Third
network

Do you have any other Devices connected/installed
What are else are you installing after drivers?
as this *** WARNING: Unable to verify timestamp for ntoskrnl.exe
Normally means a third part app has change the ntoskrnl file

Download the correct Symbols Pack for your OS and Service pack from here then
http://www.microsoft.com/whdc/DevToo...symbolpkg.mspx
Open the Tool File > Symbol Path > Downloaded Folder then reopen your file will give us better results than above

**danthescan** · 17th June 2009

Originally Posted by Omgporn

Yes, had to format the drive many times now. Same problem. Installing windows using that computer too.

Clarify that,do you mean you have had the same trouble on 2 different machines with that hard drive.
Sounds obvious if you look at it that way.

**Omgporn** · 17th June 2009

Nope, only been getting BSOD's on this new pc.

I ran Seatools on it and I think the hard drive's screwed. Failed every test within seconds haha

**Fearless** · 17th June 2009

could always do a full system check/benchmark with sisoft sandra? although your drive is screwed it would pick up anything else

**Omgporn** · 21st June 2009

Jesus, its all gone to hell. I basically had 5 days without them and I've got 6 today!

All seem to be related with win32ksys and my graphics card. Had a few talking about TCPIP.

Tried Memtest (windows version) and it kept failing and eventually it bsod'd from that (ATI error)

Think when I get paid next, I'll buy a new HDD, ram and graphics card.

**Omgporn** · 25th June 2009

Tomorrow I may buy a new HDD, 4gb 1ghz ram by OCZ (microdirect) and a ATI 4870 from someone I know

Bit extreme buying all these things, but its getting so annoying. Keep getting errors related 'to hardware' , 'nfts.sys' and others. I've changed the nfts file yesterday and still get it randomly. I'll try and report back tomorrow with my results!