BSOD related to power config on Compaq V2415LA

[GatoSoft]

Hi! ^_^

It's sad that my first thread in this forums is related to a crash, but I'm certainly stuck right now. :shock:

Well... the story begins like this: it's an old notebook from a client. Since she changed some time ago 1 GB. of RAM in replace of the original 256 MB. module the notebook have originally (that was damaged some time ago) and since she's not having money issues I decided to recommended her to buy Windows 7. So, she bought Windows 7 Ultimate (she wanted that, I've actually recommended just Home Premium) and I've happily installed it without apparent problems for a good couple of hours. Then, I've continued fixing some other PC's I've here for repair and that took me a while... like an hour. When I went back to the laptop, it had an BSOD with error 0x0000008E.
Anyway, I continued installing things and setting up everything keeping in mind the error and... nothing. So, a client called me at phone for about 45 minutes, leaving the laptop in idle... just the desktop and some wallpapers doing slideshow. When I came back, there was the BSOD again... other BSOD, acussing error 0x0000007F.
So, I suspected for power configuration and noticed that the coolers were off but the rest of the laptop doesn't.
My next move was pressing Windows+X for the Mobility Center and everytime I want to change the power policy, I got a BSOD with a random error.

The full system specs are:
CPU: AMD Sempron LV 3000+ (1.8 GHz.)
RAM: 1 GB. DDR-333, Kingston
Chipset: ATI Radeon Xpress 200M (RS480M/SB450)
GPU: ATI Radeon Xpress 200M
HDD: Toshiba MK4025GAS (40 GB., IDE, 4200 RPM)
ODD: TSSTcorp Combo (DVD-ROM/CD-RW 8x24x24x24)
Other:
- Texas Instruments UltraMedia Card Reader PCI xx21/xx11
- Broadcom 802.11g Wireless LAN
OS: Windows 7 Ultimate (32 bits, obviously )

Drivers installed normally, except for HP Quick Launch Buttons who needed to download the Vista driver and installed using compatibility with Vista.
Also, I've noticed that there in the hidden drivers is a Unknokn "Keyboard_Filter_01" and in the BIOS Setup, in "Advanced" section is a configuration for "Battery Setting optimization" that can be configured for "Battery life" or "Performance".
Memory and HDD went perfect.
I'm in a hurry right now and must to leave... NOW.
Every help is well received. I'm desperated!

Regards from Argentina!

 

[zigzag3143]

Hi! ^_^

It's sad that my first thread in this forums is related to a crash, but I'm certainly stuck right now. :shock:

Well... the story begins like this: it's an old notebook from a client. Since she changed some time ago 1 GB. of RAM in replace of the original 256 MB. module the notebook have originally (that was damaged some time ago) and since she's not having money issues I decided to recommended her to buy Windows 7. So, she bought Windows 7 Ultimate (she wanted that, I've actually recommended just Home Premium) and I've happily installed it without apparent problems for a good couple of hours. Then, I've continued fixing some other PC's I've here for repair and that took me a while... like an hour. When I went back to the laptop, it had an BSOD with error 0x0000008E.
Anyway, I continued installing things and setting up everything keeping in mind the error and... nothing. So, a client called me at phone for about 45 minutes, leaving the laptop in idle... just the desktop and some wallpapers doing slideshow. When I came back, there was the BSOD again... other BSOD, acussing error 0x0000007F.
So, I suspected for power configuration and noticed that the coolers were off but the rest of the laptop doesn't.
My next move was pressing Windows+X for the Mobility Center and everytime I want to change the power policy, I got a BSOD with a random error.

The full system specs are:
CPU: AMD Sempron LV 3000+ (1.8 GHz.)
RAM: 1 GB. DDR-333, Kingston
Chipset: ATI Radeon Xpress 200M (RS480M/SB450)
GPU: ATI Radeon Xpress 200M
HDD: Toshiba MK4025GAS (40 GB., IDE, 4200 RPM)
ODD: TSSTcorp Combo (DVD-ROM/CD-RW 8x24x24x24)
Other:
- Texas Instruments UltraMedia Card Reader PCI xx21/xx11
- Broadcom 802.11g Wireless LAN
OS: Windows 7 Ultimate (32 bits, obviously )

Drivers installed normally, except for HP Quick Launch Buttons who needed to download the Vista driver and installed using compatibility with Vista.
Also, I've noticed that there in the hidden drivers is a Unknokn "Keyboard_Filter_01" and in the BIOS Setup, in "Advanced" section is a configuration for "Battery Setting optimization" that can be configured for "Battery life" or "Performance".
Memory and HDD went perfect.
I'm in a hurry right now and must to leave... NOW.
Every help is well received. I'm desperated!

Regards from Argentina!

Hi and welcome

We could be more helpful if you could get the dmp file created when the computer crashed. use these to find and upload it to us, http://www.sevenforums.com/crash-lockup-debug-how/34900-1-novice-how-ask-help-bsod-problem.html

Thanks

Kenn J+

 

[GatoSoft]

Ok... here we have some dumps of the different BSODs that laptop is showing. I thought it would be of no use to upload lots of dumps since there are constantly different errors showing up. But now that I'm thinking, it's still good idea, just to compare and find similarities between them.

Thanks and sorry for not posting this before.
I'll be waiting here...

 

[usasma]

STOP 0x8E: BSOD Index
STOP 0x7F: BSOD Index

The more BSOD's the better (for our purposes). We can see patterns in a bunch that we can't see in just one.

The symbols aren't correct for this copy of Windows, please describe the source of the copy that you installed (what kind of disk, did it have the Microsoft hologram on it, etc).

Due to the wide spread of possible errors, it's most likely that this is a Windows corruption or a hardware failure. Let's start with this:

H/W Diagnostics:
Please start by running these bootable hardware diagnostics:
Memory Diagnostics (read the details at the link)
HD Diagnostic (read the details at the link)

Also, please run one of these free, independent online malware scans to ensure that your current protection hasn't been compromised: Malware (read the details at the link)

Please update or remove these older drivers that were loaded at the time of the crash. Don't use Windows Update or the Update drivers function of Device Manager. Please use the following instructions to locate the most current drivers:

How To Find Updated Drivers:
- search Google for the name of the driver
- compare the Google results with what's installed on your system to figure out which device/program it belongs to
- visit the web site of the manufacturer of the hardware/program to get the latest drivers (DON'T use Windows Update or the Update driver function of Device Manager).
- if there are difficulties in locating them, post back with questions and someone will try and help you locate the appropriate program.

- some driver links are on this page: http://www.carrona.org/drvrdown.html

Here's the older drivers:

atikmdag.sys Mon Dec 01 16:01:46 2008 - ATI Video drivers
camc6aud.sys Wed Apr 20 20:46:31 2005 - [B][URL="http://www.google.com/search?q=%22Conexant%20WDM%20AC97%20Audio%20Driver%22"]Conexant WDM AC97 Audio Driver[/URL][/B]
camc6hal.sys Wed Apr 20 20:47:25 2005 - [B][URL="http://www.google.com/search?q=%22Conexant%20AmcHal%20Driver%22"]Conexant AmcHal Driver[/URL][/B]
ElbyCDIO.sys Tue Aug 07 15:48:32 2007 - [B][URL="http://www.google.com/search?q=%22CDRTools%22"]CDRTools[/URL] or [URL="http://www.google.com/search?q=%22ElbyCDIO%20Driver%22"]ElbyCDIO Driver[/URL] or [URL="http://www.google.com/search?q=%22DVD%20Region%20Killer%22"]DVD Region Killer[/URL] or [URL="http://www.google.com/search?q=%22VirtualCloneDrive%22"]VirtualCloneDrive[/URL][/B] by [B][URL="http://www.elby.ch/"]Elaborate Bytes AG[/URL][/B] ([url=http://www.elby.ch]elby CloneDVD™ 2[/url]).
ElbyDelay.sys Wed Dec 13 14:14:57 2006 - [B][URL="http://www.google.com/search?q=%22CDRTools%22"]CDRTools[/URL] or [URL="http://www.google.com/search?q=%22ElbyCDIO%20Driver%22"]ElbyCDIO Driver[/URL] or [URL="http://www.google.com/search?q=%22DVD%20Region%20Killer%22"]DVD Region Killer[/URL] or [URL="http://www.google.com/search?q=%22VirtualCloneDrive%22"]VirtualCloneDrive[/URL][/B] by [B][URL="http://www.elby.ch/"]Elaborate Bytes AG[/URL][/B] ([url=http://www.elby.ch]elby CloneDVD™ 2[/url]).
HpqKbFiltr.sys Mon Jun 18 18:12:03 2007 - HpqKbFiltr Keyboard Filter Driver                              - HP Quick Launch Buttons                               
SynTP.sys    Fri Sep 14 22:10:35 2007 - Synaptics Touchpad driver
VSTATI3.SYS  Tue Jun 20 13:39:32 2006 - Conexant Modem HSFHWATI WDM driver
VSTCNXT3.SYS Wed Oct 15 20:29:13 2008 - Conexant HSF_CNXT driver
VSTDPV3.SYS  Wed Oct 15 20:32:04 2008 - Conexant  HSF_DP driver

Summary of the BSOD's:

*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Debug session time: Thu Jan 14 15:40:06.283 2010 (GMT-5)
System Uptime: 0 days 0:02:54.205
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
BugCheck 1000000A, {0, 2, 1, 82abb2af}
Probably caused by : win32k.sys ( win32k+c0d75 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Debug session time: Thu Jan 14 15:57:34.149 2010 (GMT-5)
System Uptime: 0 days 0:02:09.071
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
*** WARNING: Unable to verify timestamp for atikmdag.sys
*** ERROR: Module load completed but symbols could not be loaded for atikmdag.sys
BugCheck 100000D1, {ba9a8c0a, 9, 0, 8c0b5091}
Probably caused by : tunnel.sys ( tunnel!TwKernelOffloadV4FlowParams+1c11 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Debug session time: Thu Jan 14 16:00:07.344 2010 (GMT-5)
System Uptime: 0 days 0:02:02.266
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
BugCheck 1000007F, {8, 801dc000, 0, 0}
Probably caused by : ntoskrnl.exe
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Debug session time: Thu Jan 14 16:04:05.453 2010 (GMT-5)
System Uptime: 0 days 0:03:31.375
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
*** WARNING: Unable to verify timestamp for SynTP.sys
*** ERROR: Module load completed but symbols could not be loaded for SynTP.sys
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Debug session time: Thu Jan 14 16:07:11.993 2010 (GMT-5)
System Uptime: 0 days 0:02:34.915
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Debug session time: Thu Jan 14 16:14:01.256 2010 (GMT-5)
System Uptime: 0 days 0:02:58.178
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Debug session time: Thu Jan 14 16:18:12.703 2010 (GMT-5)
System Uptime: 0 days 0:03:11.625
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Debug session time: Thu Jan 14 16:21:37.915 2010 (GMT-5)
System Uptime: 0 days 0:03:01.836
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
BugCheck 1000008E, {c0000005, 82ac1396, 94fcd84c, 0}
Probably caused by : ntoskrnl.exe ( nt+bd396 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Debug session time: Thu Jan 14 16:27:28.140 2010 (GMT-5)
System Uptime: 0 days 0:04:10.062
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
*** WARNING: Unable to verify timestamp for atikmdag.sys
*** ERROR: Module load completed but symbols could not be loaded for atikmdag.sys
BugCheck 100000D1, {8000000d, 9, 0, 8e45627d}
Probably caused by : atikmdag.sys ( atikmdag+4827d )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Debug session time: Thu Jan 14 16:31:08.959 2010 (GMT-5)
System Uptime: 0 days 0:03:10.881
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
BugCheck 1000007F, {d, 0, 0, 0}
Probably caused by : ntoskrnl.exe ( nt+271e6e )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

 

[GatoSoft]

Thanks for the fast answer again! ^_^

Well... I noted that yesterday, in the hurry, I've said "Memory and HDD went perfect", but I intended to say "Memory and HDD tests went perfect".
What I meant to say is that I've used MemTest86+ v2.11 and after 11 complete passes, nothing went wrong. Also, I've tested HDD surface using MHDD, HDD Regenerator (both, latest versions) and ChkDsk (usinf /F suffix and after no errors been found, used /R) and everything returning no errors at all. I sed those programs since I've lurking in Toshiba's home page and couldn't find software for disk diagnostic.
Anyway, I think I would try reinstalling again (making a disk image before, just if everything goes wrong :huh and then try to change the power configuration. If BSOD appears, then I'll try to update drivers (not using "Windows Outdate" ).
I'll be back as soon as possible with some results. If you have some interim suggestion and want to help me, it's welcome.


EDIT: I think I'm not having good luck. Even with a clean install without any program more than Windows itself and without any driver at all I'm getting the same errors whenever I try to change the power configuration or go into sleep mode or something related. Help me!

 

[usasma]

If you do a clean install and you still have problems - then it's most likely to be a hardware problem (as long as you've checked Device Manager to be sure there's no issues there).

 

[GatoSoft]

Sorry for answering so late but after lost of discussions with the ignorant client that pretend to know more than the person who's healing his machine he "released" that the notebook have been working bad since a few months ago. I know, everything was telling me that was a hardware problem but... well, I trusted what my client said.
It happened just after they upgraded their RAM to an (apparently) incompatible generic RAM.
The client now got his notebook semi-working (they don't want to change their RAM) but working at it's max.
Thanks for the support guys! I really appreciate it.

Greetings from Argentina!