BlueScreen

Please help me locate the problem.

I have been getting bluescreen previously and did a test using MEMTEST86+ and found error. So I sent my Laptop to HP Center and they checked the RAM and found that there is no problem with the RAM and Harddisk. So they replaced the motherboard, after that I reformatted my laptop and reinstalled Vista Ultimate x64 SP1 with all latest updates and I checked using MEMTEST86+ again (boot version) and no error found.

Its the third day reinstalled my OS with latest driver and bios, now I am still getting bluescreen. Even the technician at the HP center blamed my Windows previously but I already reformatted my laptop. Why am I still getting bluescreen?

Here I attached all my minidump! It contains 3 minidump. Please help me, I am working everyday and I do not have time to send it over to HP center for checking. I am only free at night where HP center is closed already. I know I can trust the help from this forum.

God Bless!

chicaman said:

Please help me locate the problem.

I have been getting bluescreen previously and did a test using MEMTEST86+ and found error. So I sent my Laptop to HP Center and they checked the RAM and found that there is no problem with the RAM and Harddisk. So they replaced the motherboard, after that I reformatted my laptop and reinstalled Vista Ultimate x64 SP1 with all latest updates and I checked using MEMTEST86+ again (boot version) and no error found.

Its the third day reinstalled my OS with latest driver and bios, now I am still getting bluescreen. Even the technician at the HP center blamed my Windows previously but I already reformatted my laptop. Why am I still getting bluescreen?

Here I attached all my minidump! It contains 3 minidump. Please help me, I am working everyday and I do not have time to send it over to HP center for checking. I am only free at night where HP center is closed already. I know I can trust the help from this forum.

God Bless!

Click to expand...

Hi and welcome to vista forums

well the three dumps ahve different causes. (memory corruption,firefox, and win32.sys) You do however have lots of old drivers so I suspect that you dont have sp2 installed (maybe not even sp1) because the dates are from as far back as 2006.

could you tell us about what version is installed? and what build of vista are you runnning?

thanks
ken

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


Loading Dump File [C:\Users\K\Desktop\Mini100709-02.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*d:\symbols*Symbol information
Executable search path is:
Windows Server 2008/Windows Vista Kernel Version 6001 (Service Pack 1) MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 6001.22258.amd64fre.vistasp1_ldr.080904-1629
Machine Name:
Kernel base = 0xfffff800`01c50000 PsLoadedModuleList = 0xfffff800`01e15db0
Debug session time: Wed Oct 7 09:18:17.870 2009 (GMT-4)
System Uptime: 0 days 0:57:48.730
Loading Kernel Symbols
...............................................................
................................................................
.......................
Loading User Symbols
Loading unloaded module list
......
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 50, {fffff95ffff37e20, 8, fffff95ffff37e20, 5}


Could not read faulting driver name
Probably caused by : win32k.sys ( win32k!fnHkINLPMSG+1cb )

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

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

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: fffff95ffff37e20, memory referenced.
Arg2: 0000000000000008, value 0 = read operation, 1 = write operation.
Arg3: fffff95ffff37e20, If non-zero, the instruction address which referenced the bad memory
address.
Arg4: 0000000000000005, (reserved)

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


Could not read faulting driver name

WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff80001e79080
fffff95ffff37e20

FAULTING_IP:
+60f1952f0367d964
fffff95f`fff37e20 ?? ???

MM_INTERNAL_CODE: 5

CUSTOMER_CRASH_COUNT: 2

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

BUGCHECK_STR: 0x50

PROCESS_NAME: firefox.exe

CURRENT_IRQL: 0

TRAP_FRAME: fffffa60180256f0 -- (.trap 0xfffffa60180256f0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=00000000001be320 rbx=0000000000000000 rcx=fffffa60180258d8
rdx=0000059fe8198850 rsi=0000000000000000 rdi=0000000000000000
rip=fffff95ffff37e20 rsp=fffffa6018025888 rbp=0000000000030000
r8=000000000000c1f3 r9=0000000000030000 r10=0000000000000000
r11=fffffa6018025b68 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei ng nz na po cy
fffff95f`fff37e20 ?? ???
Resetting default scope

LAST_CONTROL_TRANSFER: from fffff80001cb11e2 to fffff80001ca30d0

STACK_TEXT:
fffffa60`180255f8 fffff800`01cb11e2 : 00000000`00000050 fffff95f`fff37e20 00000000`00000008 fffffa60`180256f0 : nt!KeBugCheckEx
fffffa60`18025600 fffff800`01ca1c59 : 00000000`00000008 fffffa60`18025db0 00610068`002b0000 00000000`003af9b4 : nt!MmAccessFault+0x4f2
fffffa60`180256f0 fffff95f`fff37e20 : fffff960`000af02b fffffa60`0000002f 00000000`00000000 fffffa60`18025b68 : nt!KiPageFault+0x119
fffffa60`18025888 fffff960`000af02b : fffffa60`0000002f 00000000`00000000 fffffa60`18025b68 00000000`00000000 : 0xfffff95f`fff37e20
fffffa60`18025890 fffff960`0009cf19 : 00000000`00000000 00000000`00000000 fffff900`c084c8a0 00000000`00000000 : win32k!fnHkINLPMSG+0x1cb
fffffa60`18025970 fffff960`000db260 : fffff900`00000000 fffff900`c084c8a0 fffffa60`18025ca0 fffff800`00000000 : win32k!xxxCallCtfHook+0x1b5
fffffa60`18025a00 fffff960`000db735 : 00000000`00000000 fffff800`000025ff 00000000`00000000 fffffa60`ffffffff : win32k!xxxRealInternalGetMessage+0x508
fffffa60`18025ae0 fffff960`000df547 : fffff900`00000000 00000000`00000000 00000000`00000001 fffff800`01cc0400 : win32k!xxxInternalGetMessage+0x35
fffffa60`18025b20 fffff800`01ca2b73 : fffffa80`05382bb0 00000000`001be418 fffffa60`18025bc8 fffffa60`18025ca0 : win32k!NtUserPeekMessage+0x77
fffffa60`18025bb0 00000000`75139f8a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`001be3f8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x75139f8a


STACK_COMMAND: kb

FOLLOWUP_IP:
win32k!fnHkINLPMSG+1cb
fffff960`000af02b 38498b cmp byte ptr [rcx-75h],cl

SYMBOL_STACK_INDEX: 4

SYMBOL_NAME: win32k!fnHkINLPMSG+1cb

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: win32k

IMAGE_NAME: win32k.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 47919441

FAILURE_BUCKET_ID: X64_0x50_win32k!fnHkINLPMSG+1cb

BUCKET_ID: X64_0x50_win32k!fnHkINLPMSG+1cb

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

Hi,

This is my build (found it in HKEY_LOCAL_MACHINE\Software\Microsoft\Windows NT\CurrentVersion )

6001.22389.amd64fre.vistasp1_ldr.090302-1506


I am using Intel Processor though P7350 with 4GB RAM

chicaman said:

Hi,

This is my build (found it in HKEY_LOCAL_MACHINE\Software\Microsoft\Windows NT\CurrentVersion )

6001.22389.amd64fre.vistasp1_ldr.090302-1506


I am using Intel Processor though P7350 with 4GB RAM

Click to expand...

Great. SP1, have you upgraded the bios?

One thing we can do is to run a system file check. it verifies the sytem files and tries to fix any broken ones. to run it goto search>type cmd>right click and run as admin> type sfc /scannow.

let us know the results

Ken

Microsoft Windows [Version 6.0.6001]
Copyright (c) 2006 Microsoft Corporation. All rights reserved.

C:\Windows\system32>sfc /scannow

Beginning system scan. This process will take some time.

Beginning verification phase of system scan.
Verification 100% complete.

Windows Resource Protection found corrupt files and successfully repaired
them. Details are included in the CBS.Log windir\Logs\CBS\CBS.log. For
example C:\Windows\Logs\CBS\CBS.log

C:\Windows\system32>

Click to expand...

Yes, I have updated my BIOS to the latest version.

chicaman

great

sfc fixed the system files. You should also upgrade to sercive pack 2. There was a link posted today. just google vista service pack 2 and get it from microsoft

let me know if I can help


Ken

Okie, I appreciated the help Ken. Btw, my name is Ken too :P I will repost my problem here if I have any problem and hope you dont mind if I send you a PM regarding my post here just in case you didnt see it. I gotta sleep now its 12.30am at my place now, tml gotta work, will install SP2 tomorrow night after my works! Thanks again!

CM

Nice name very distinctive<g> let us know if you need help


Ken

Here this morning I got another bluescreen

This is the minidump

Which hardware is possibly causing the problem? Should I change to 32bit instead? can 32bit fully support 4gb ram?

Ken

This one does ident the faulting file.

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


Loading Dump File [C:\Users\K\Desktop\Mini100909-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*d:\symbols*Symbol information
Executable search path is:
Windows Server 2008/Windows Vista Kernel Version 6001 (Service Pack 1) MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 6001.22389.amd64fre.vistasp1_ldr.090302-1506
Machine Name:
Kernel base = 0xfffff800`01e48000 PsLoadedModuleList = 0xfffff800`0200ddb0
Debug session time: Thu Oct 8 19:05:50.365 2009 (GMT-4)
System Uptime: 0 days 9:53:01.394
Loading Kernel Symbols
...............................................................
................................................................
......................
Loading User Symbols
Loading unloaded module list
......
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 3B, {c000001d, fffff96000142458, fffffa6005d83010, 0}

Probably caused by : win32k.sys ( win32k!SpeedHitTest+58 )

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

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

SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c000001d, Exception code that caused the bugcheck
Arg2: fffff96000142458, Address of the exception record for the exception that caused the bugcheck
Arg3: fffffa6005d83010, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.

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


EXCEPTION_CODE: (NTSTATUS) 0xc000001d - {EXCEPTION} Illegal Instruction An attempt was made to execute an illegal instruction.

FAULTING_IP:
win32k!SpeedHitTest+58
fffff960`00142458 4885c9 test rcx,rcx

CONTEXT: fffffa6005d83010 -- (.cxr 0xfffffa6005d83010)
rax=fffffa6005d838a8 rbx=000000c900000119 rcx=0000000000000000
rdx=000000c900000119 rsi=00000000000000c9 rdi=fffff900c0a7b160
rip=fffff96000142458 rsp=fffffa6005d83870 rbp=fffff900c0a7b870
r8=fffffa6005d83a80 r9=4000000000000004 r10=0000000000000000
r11=fffffa6005d83a78 r12=0000000000000000 r13=fffffa6005d83a88
r14=fffffa6005d83a80 r15=0000000000000000
iopl=0 nv up ei ng nz na pe cy
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010283
win32k!SpeedHitTest+0x58:
fffff960`00142458 4885c9 test rcx,rcx
Resetting default scope

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

BUGCHECK_STR: 0x3B

PROCESS_NAME: csrss.exe

CURRENT_IRQL: 0

LAST_CONTROL_TRANSFER: from fffff960001d6a25 to fffff96000142458

STACK_TEXT:
fffffa60`05d83870 fffff960`001d6a25 : 000000c9`00000119 000000c9`00000119 fffff900`c0a00b60 00000000`000000c9 : win32k!SpeedHitTest+0x58
fffffa60`05d838b0 fffff960`0013e1dd : 000000c9`00000119 000000c9`00000119 fffff960`0033df30 00000000`00000000 : win32k!DCESpeedHitTest+0x1d9
fffffa60`05d83920 fffff960`001a6ffb : 00000000`00000000 000000c9`00000119 00000000`021eed84 00000000`00000001 : win32k!zzzSetFMouseMoved+0x4d
fffffa60`05d83a80 fffff960`001829c0 : 00000000`00000000 00000000`00000000 00000000`00000001 00000000`0000000d : win32k!ProcessQueuedMouseEvents+0x2b5
fffffa60`05d83b00 fffff960`0010cb27 : fffffa80`0000000f 00000000`00000003 ffffffff`80000368 fffffa80`05c377c0 : win32k!RawInputThread+0x928
fffffa60`05d83bc0 fffff960`00184e46 : fffffa80`00000002 fffffa60`18012fa0 00000000`00000000 00000000`00000000 : win32k!xxxCreateSystemThreads+0x67
fffffa60`05d83bf0 fffff800`01e98a33 : fffffa80`05c38060 00000000`00000004 000007fe`fdd78b60 00000000`00000000 : win32k!NtUserCallNoParam+0x36
fffffa60`05d83c20 000007fe`fdccbbda : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`0094fc48 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7fe`fdccbbda


FOLLOWUP_IP:
win32k!SpeedHitTest+58
fffff960`00142458 4885c9 test rcx,rcx

SYMBOL_STACK_INDEX: 0

SYMBOL_NAME: win32k!SpeedHitTest+58

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: win32k

IMAGE_NAME: win32k.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 49edba8a

STACK_COMMAND: .cxr 0xfffffa6005d83010 ; kb

FAILURE_BUCKET_ID: X64_0x3B_win32k!SpeedHitTest+58

BUCKET_ID: X64_0x3B_win32k!SpeedHitTest+58

Followup: MachineOwn
---------

Since these BSOD's are so random I have to think there is some piece of hardware that is at the root of them. I assume you aren't overclocking, running a RAID, or anything else unusual?

was vista pre-installed, or did you upgrade from XP?

I cant help thinking there is something really simple that im not asking you that will be an aha moment.
Besides the core computer (cpu, ram, mobo,monitor,keyboard,mouse) is there anything else? external HD, card reader? etc?

ken

edit:
Ken after re-reading all the previous dumps i found that win32.sys is in many if not most of them.

I did a clean installation of Vista. I updated my system specs. Yes I did use mouse and keyboard. External HDD and Card Reader and I got a BSOD even if I did not connect them.

Now I took out a stick of RAM and gonna test them one by one. So far so good *touchwood* as I am testing the original RAM. If no problem till tomorrow morning, I gonna change another stick and test them out again to check which is the cause. Suspecting hardware problem but dont know which hardware as Memtest86+ told me RAM passed the test. If both RAM is good, then the cause is MOBO.


I will update back soon.

It's possible that hardware could be causing this - but it's more likely that there is an issue with a System Service that's causing your problems.

Win32k.sys most likely isn't the issue. It's most likely that the faulty system service interacts improperly with win32k.sys and causes it to crash. If win32k.sys was a problem then you'd likely be seeing many other issues on the system.

Please zip up the entire contents of the C:\Windows\Minidump directory and attach it to your next post.

Also, please generate the following reports then zip them up and attach the .zip file to your next post also.

Start...Run...type "perfmon /report" (without the quotes) and press Enter.
Save the report as an .html file

Start...Run...type "msinfo32" (without the quotes) and press Enter.
Save the report as an .nfo file