Anybody plz help me!!!!

lak121727 · 23 Jul 2010

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 · 23 Jul 2010

Please enable driver verifier: Using Driver Verifier to identify issues with Drivers

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:

Code:


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

lak121727 · 23 Jul 2010

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 · 23 Jul 2010

lak121727 said:

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 · 23 Jul 2010

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 · 25 Jul 2010

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 · 25 Jul 2010

Out of the 4 dumps provided, none had signs of Verifier running. Please enable it: Using Driver Verifier to identify issues with Drivers

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.

Code:

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

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

...Summary of the Dumps:

Code:


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

lak121727 · 25 Jul 2010

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 · 25 Jul 2010

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

lak121727 · 25 Jul 2010

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