Anybody plz help me!!!!

[lak121727]

Hic, have to say that I've just bought my lappy from ebay. It's came out unexpected with a flawless appearance but the core. OMG I have been frustrating with this iron mass since it's always turn out to be BSOD for A LOT OF TIME even I've tried to re-install the OS several times. I was thought it was caused by the driver of some thing deep inside it but ....hmmmmh have to say that I have no idea about computer before so Im pleading on u guys, please help dragging me out of this bad T.T
Mine is HP G60 series with 4GB RAM, chip Intel core 2 duo T6600 @ 2.2GHZ each, and the OS is Win 7 ultimate x86. T.T
Here come along the minidump file
Thks alot.

 

[Jonathan_King]

Please enable driver verifier: http://www.sevenforums.com/crash-lo...-driver-verifier-identify-issues-drivers.html

Also test RAM. Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder or another ISO burning program. Boot from the CD, and leave it running for at least 5 or 6 passes.


...Summary of the Dumps:

[font=lucida console]
Built by: 7600.16385.x86fre.win7_rtm.090713-1255
Debug session time: Fri Jul 23 09:08:42.283 2010 (UTC - 4:00)
System Uptime: 0 days 0:02:51.142
BugCheck A, {147a0a69, 2, 0, 8267dc4f}
Probably caused by : memory_corruption
BUGCHECK_STR:  0xA
PROCESS_NAME:  csrss.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨[/font]

 

[lak121727]

Firstly thanks, Hmh rite now I dont think have to install those driver (grapic,and touchpad) so all I need to do is just have the soft above run booting like u said and the problem will be solved then?
I wonder if my rams have severe problems so any things further I can do then?
Actually, from the last crash I saw it something related to file win32k.sys, is it the common thing for BOSD?

 

[zigzag3143]

Firstly thanks, Hmh rite now I dont think have to install those driver (grapic,and touchpad) so all I need to do is just have the soft above run booting like u said and the problem will be solved then?
I wonder if my rams have severe problems so any things further I can do then?
Actually, from the last crash I saw it something related to file win32k.sys, is it the common thing for BOSD?

In whatever app you are using to see win32k.sys, it is rarely the problem, just the applications way of blaming something. Happens all the time. win 7 OS files are almost never the cause.

 

[Jonathan_King]

If you enable driver verifier, it should point to a bad driver if it finds one. It will actually make the problem worse, until we fix it.

Yes, win32k.sys is a default file blamed.

To test your RAM, download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder or another ISO burning program. Boot from the CD, and leave it running for at least 5 or 6 passes.

 

[lak121727]

Hi guys!
I just let the system running thru the night and it make till 8 passes but there's no errors were marked.
But still, my lappy was BOSD again and again even worse than that. It restart without the blue screen

 

[Jonathan_King]

Out of the 4 dumps provided, none had signs of Verifier running. Please enable it: http://www.sevenforums.com/crash-lo...-driver-verifier-identify-issues-drivers.html

Three pointed to the NT Kernel as the cause, which means that either hardware is the cause, or control was passed to the kernel before it bluescreened.

One pointed to your Intel graphics drivers. They are dated pre-Windows 7 RTM, which means they are technically not compatible with Windows 7. You should be able to find an update, which will hopefully take care of the problem.

igdkmd32.sys Wed May 06 14:13:40 2009

In summary, enable verifier and update your Intel graphics drivers.

...Summary of the Dumps:

[font=lucida console]
Built by: 7600.16539.x86fre.win7_gdr.100226-1909
Debug session time: Sat Jul 24 14:44:21.885 2010 (UTC - 4:00)
System Uptime: 0 days 0:05:14.602
BugCheck D1, {822c8480, ff, 8, 822c8480}
Probably caused by : ntkrpamp.exe ( nt!KiTrap0E+2cf )
BUGCHECK_STR:  0xD1
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.x86fre.win7_gdr.100226-1909
Debug session time: Sat Jul 24 14:36:43.141 2010 (UTC - 4:00)
System Uptime: 0 days 0:00:18.858
PROCESS_NAME:  System
BUGCHECK_STR:  0x24
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.x86fre.win7_gdr.100226-1909
Debug session time: Sat Jul 24 00:58:35.365 2010 (UTC - 4:00)
System Uptime: 0 days 1:36:23.098
*** WARNING: Unable to verify timestamp for igdkmd32.sys
*** ERROR: Module load completed but symbols could not be loaded for igdkmd32.sys
BugCheck 1000008E, {c000001d, 90065601, 829769dc, 0}
*** WARNING: Unable to verify timestamp for dxgkrnl.sys
*** ERROR: Module load completed but symbols could not be loaded for dxgkrnl.sys
Probably caused by : igdkmd32.sys ( igdkmd32+41601 )
BUGCHECK_STR:  0x8E
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16385.x86fre.win7_rtm.090713-1255
Debug session time: Fri Jul 23 09:08:42.283 2010 (UTC - 4:00)
System Uptime: 0 days 0:02:51.142
BugCheck A, {147a0a69, 2, 0, 8267dc4f}
Probably caused by : memory_corruption
BUGCHECK_STR:  0xA
PROCESS_NAME:  csrss.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
[/font]

 

[lak121727]

Ok thanks for your times
I just update the lastest driver of the graphic from hp page
and Im going to enable the Driver Verifier as u said
but I dont quite get this thing


"Reboot the system and wait for it to crash to the Blue Screen. Continue to use your system normally, and if you know what causes the crash, do that repeatedly".
So I have to restart it repeatedly until when?

 

[Jonathan_King]

No, reboot once to start Verifier. From then on use your computer normally.

 

[lak121727]

Oh! I just did it and didnt see any crash after reboot ~~
Is it ok like that?

 

[ttran]

Yes it's ok like that. Just use your system normally and wait for it to crash, then upload the new minidump after it crash

 

[lak121727]

Thanks then.

 

[lak121727]

Here we go
This is the file the newest crash

 

[ttran]

Netio.sys is probably not the cause, however, NETw5s32.sys appear in the crash dump. It is your intel wifi driver, I would download and install fresh copy of it.

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


Loading Dump File [C:\Users\TUANTR~1\AppData\Local\Temp\Rar$DI00.021\072510-10483-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*e:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16539.x86fre.win7_gdr.100226-1909
Machine Name:
Kernel base = 0x82844000 PsLoadedModuleList = 0x8298c810
Debug session time: Mon Jul 26 11:20:17.587 2010 (UTC + 7:00)
System Uptime: 0 days 0:34:11.319
Loading Kernel Symbols
...............................................................
................................................................
................
Loading User Symbols
Loading unloaded module list
......
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck A, {300002, 2, 0, 82b838b5}

Unable to load image \SystemRoot\system32\DRIVERS\NETw5s32.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for NETw5s32.sys
*** ERROR: Module load completed but symbols could not be loaded for NETw5s32.sys
Probably caused by : NETIO.SYS ( NETIO!NetioAllocateAndReferenceNetBufferListNetBufferMdlAndData+14 )

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

 

[lak121727]

Thanks for answering
The thing is Hp provides me a lot of driver for network and I dont know the right one.
Can you take a look and tell me from the list below:

Software & Driver Downloads HP G60-551CA Notebook PC - HP Customer Care (United States - English)

Cam on XD

 

[ttran]

You can just go to intel website and download the intel wireless adapter driver there

if based on the website you provide me, it is in the network category with the name is Intel PRO/Wireless Drivers for Microsoft Windows 7

 

[lak121727]

Thanks a lot
Let's see if everything's ok!

 

[lak121727]

Hic! I turn on my computer this morning and there's a new problem with it. Whenever i plug the charger in, it suddenly restart when reach the log on screen. as long as i use the battery, it's ok, rite now everything seems to be alrite but i think due to its crashing alot of time like this, system cause the sudden death like that.
And this is the new file of crash i saw this morning, after install the wifi driver last night
Do I have to turn off the verifier now?

 

[CarlTR6]

This stop error is D1 and points hardware as the cause. It does not point to a specific driver.

STOP 0x000000D1: DRIVER_IRQL_NOT_LESS_OR_EQUAL

Usual causes: Device driver

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


Loading Dump File [C:\Users\Owner\Downloads\072610-11980-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\symbols*[URL="http://msdl.microsoft.com/download/symbols"]Symbol information[/URL]
Executable search path is: 
Windows 7 Kernel Version 7600 MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16539.x86fre.win7_gdr.100226-1909
Machine Name:
Kernel base = 0x8283d000 PsLoadedModuleList = 0x82985810
Debug session time: Mon Jul 26 12:35:51.543 2010 (GMT-4)
System Uptime: 0 days 0:00:17.260
Loading Kernel Symbols
...............................................................
................................................................
................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck D1, {830ca114, ff, 8, 830ca114}

Probably caused by : hardware

Followup: MachineOwner
---------
 *** Possible invalid call from 82812a4e ( hal!HalpScaleQueryPerformanceCounter+0x50 )
 *** Expected target 8281a114 ( hal!_allmul+0x0 )

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

DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high.  This is usually
caused by drivers using improper addresses.
If kernel debugger is available get stack backtrace.
Arguments:
Arg1: 830ca114, memory referenced
Arg2: 000000ff, IRQL
Arg3: 00000008, value 0 = read operation, 1 = write operation
Arg4: 830ca114, address which referenced memory

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


READ_ADDRESS: GetPointerFromAddress: unable to read from 829a5718
Unable to read MiSystemVaType memory at 82985160
 830ca114 

CURRENT_IRQL:  2

FAULTING_IP: 
+5cb1952f018fddd4
830ca114 ??              ???

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP

BUGCHECK_STR:  0xD1

PROCESS_NAME:  System

TRAP_FRAME:  807e0bbc -- (.trap 0xffffffff807e0bbc)
ErrCode = 00000010
eax=0e8220a4 ebx=00da7a64 ecx=00da7a64 edx=00000000 esi=00853140 edi=00000000
eip=830ca114 esp=807e0c30 ebp=807e0c50 iopl=0         nv up di pl zr na pe nc
cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010046
830ca114 ??              ???
Resetting default scope

LAST_CONTROL_TRANSFER:  from 82812a53 to 830ca114

FAILED_INSTRUCTION_ADDRESS: 
+5cb1952f018fddd4
830ca114 ??              ???

POSSIBLE_INVALID_CONTROL_TRANSFER:  from 82812a4e to 8281a114

STACK_TEXT:  
WARNING: Frame IP not in any known module. Following frames may be wrong.
807e0c2c 82812a53 00853140 00000000 00000000 0x830ca114
807e0c50 82812b11 00000011 00000000 00da7a64 hal!HalpScaleQueryPerformanceCounter+0x55
807e0c80 828c27ce 00000000 807c74d8 00000000 hal!KeQueryPerformanceCounter+0x89
807e0c98 828c273e 8d69aae8 807c9800 807c4000 nt!PpmQueryTime+0x16
807e0d20 828a500d 00000000 0000000e 00000000 nt!PoIdle+0x5c1
807e0d24 00000000 0000000e 00000000 00000000 nt!KiIdleLoop+0xd


STACK_COMMAND:  .trap 0xffffffff807e0bbc ; kb

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: hardware

IMAGE_NAME:  hardware

DEBUG_FLR_IMAGE_TIMESTAMP:  0

BUCKET_ID:  CPU_CALL_ERROR

Followup: MachineOwner
---------
 *** Possible invalid call from 82812a4e ( hal!HalpScaleQueryPerformanceCounter+0x50 )
 *** Expected target 8281a114 ( hal!_allmul+0x0 )

How long have you had Driver Verifier running? I suggest that you let it run for at least 36 hours before you turn it off.

 

[lak121727]

So do you think that I have problem with those hardware inside?
I just turn the Verifier off. Now have to turn it on again. After 36hrs will turn off again?