Random Blue screen error:Event ID 41,kernel Power

[Arvind]

Greetings

I purchased a new HP Pavillion dv4 laptop a week ago,loaded with Windows 7 Home Premium.
I have been experiencing random Blue screen errors since the day i purchaed.

The error in the event viewer is as below.

Event ID :41
Source:Kernel Power
Log name :System
Details:
System has rebooted without cleanly shuttinh down first.This error could be caused if the system stopped responding,crashed or lost power unexpectedly

I recieved this error at various instances.
1.While exploring the machine
2.Playing games
3.when it is idle

Also there is another event recorded at the same time
Event id 1001
Source:Bug Check

Please advise as to what is causing this issue.
I appreaciate all your help and time!!

Look forward for a response as soon as possible.

Thank You
Arvind

 

[Capt.Jack Sparrow]

Hi Arvind, Welcome to SF,

Could you post us the Dump file so we can analysis and find the problem. This tutorial should help you http://www.sevenforums.com/crash-lockup-debug-how/34900-1-novice-how-ask-help-bsod-problem.html

Hope this helps,
Captain

 

[Arvind]

Hi Captian!!!

Thank You!
I will try to get these files for you!!!

Have a good evening
Take care
Arvind

 

[zigzag3143]

Greetings

I purchased a new HP Pavillion dv4 laptop a week ago,loaded with Windows 7 Home Premium.
I have been experiencing random Blue screen errors since the day i purchaed.

The error in the event viewer is as below.

Event ID :41
Source:Kernel Power
Log name :System
Details:
System has rebooted without cleanly shuttinh down first.This error could be caused if the system stopped responding,crashed or lost power unexpectedly

I recieved this error at various instances.
1.While exploring the machine
2.Playing games
3.when it is idle

Also there is another event recorded at the same time
Event id 1001
Source:Bug Check

Please advise as to what is causing this issue.
I appreaciate all your help and time!!

Look forward for a response as soon as possible.

Thank You
Arvind

Hi Arvind and welcome'

the event ID 41 just states the system was shutdown abnormally. we really do need the actual dmp file Use these to find and upload it

Ken J+

 

[Arvind]

Hi Ken!!

Thank You

I should be able to get you guys the dump file tomorrow by 1 PM EST.

Take Care
Arvind

 

[Arvind]

Hi Guys

Please find the attached .dmo files.
I have copied the contents from the c:\Windows\Minidump folder.
Please let me know if you need anything else.


Also kindly let me know your findings!!

Thank You
Arvind

 

[usasma]

For starters, I suspect your Norton/Symantec protection might be corrupted.
Please do this:

Anti-Virus Removal:
Please do the following:
- download a free antivirus for testing purposes: Free AntiVirus
- uninstall the Norton from your system
- remove any remnants of Norton using this free tool: Download and run the Norton Removal Tool
- IMMEDIATELY install and update the free antivirus
- check to see if this fixes the BSOD's

One of the dump files points to your USB. What do you have connected to the USB? Please disconnect all USB devices while we're testing. Also, Please provide this file to see what may be connected internally to your USB (webcam, fingerprint reader, audio are some possibilities):

MSINFO32:
Please go to Start and type in "msinfo32.exe" (without the quotes) and press Enter
Save the report as an .nfo file, then zip up the .nfo file and upload/attach the .zip file with your next post.

If you're having difficulties with the format, please open an elevated (Run as administrator) Command Prompt and type "msinfo32 /nfo C:\Users\Public\Desktop\TEST.NFO" (without the quotes) and press Enter. Then navigate to the C:\Users\Public\Desktop directory to retrieve the TEST.NFO file. If you have difficulties with making this work, please post back.

Then I'd suggest some free hardware diagnostics due to the mention of hardware/memory in the dump files:

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)

Also, 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. Please note that the oldest drivers are listed first:

iirsp.sys    Tue Dec 13 16:48:01 2005 - Intel Raid StorPort Driver
djsvs.sys    Tue Apr 11 20:20:11 2006 - Adaptec Ultra SCSI miniport
nfrd960.sys  Tue Jun 06 17:12:15 2006 - IBM ServeRAID Controller Driver
adpu320.sys  Tue Feb 27 19:03:08 2007 - [FONT=Verdana][SIZE=2]Adaptec .NET Ultra320 Driver[/SIZE][/FONT]
adpahci.sys  Tue May 01 13:29:26 2007 - Adaptec Windows SATA Storport Driver                                                              
arc.sys      Thu May 24 17:31:06 2007 - Adaptec RAID Storport Driver
SiSRaid2.sys Wed Sep 24 14:19:45 2008 - SiS RAID Stor Miniport Driver
sisraid4.sys Wed Oct 01 17:52:22 2008 - SiS AHCI Stor-Miniport Driver
adp94xx.sys  Fri Dec 05 18:59:55 2008 - Adaptec HostRAID SAS Driver
lsi_fc.sys   Tue Dec 09 17:28:47 2008 - LSI Logic Fusion-MPT FC Driver (StorPort)

As this is an HP system, it's likely that you're not using all of these drivers - but it will depend on the storage chipset of your system to determine which one's are needed.

To provide that info, someone will have to let us know about a hardware identification program that lists that/those hardware devices (storage controllers). Then we can tell which one's are important.

Summary of the BSOD's:

Built by: 7600.16385.x86fre.win7_rtm.090713-1255
Debug session time: Sat Jan  9 18:19:21.364 2010 (GMT-5)
System Uptime: 0 days 0:01:27.018
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  WinSAT.exe
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.x86fre.win7_rtm.090713-1255
Debug session time: Sat Jan  9 19:30:01.906 2010 (GMT-5)
System Uptime: 0 days 0:00:30.685
BugCheck D1, {107, 2, 1, 8b650003}
Probably caused by : WinUSB.sys ( WinUSB!WinUSB_WritePipeCompletion+2e7 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.x86fre.win7_rtm.090713-1255
Debug session time: Sun Jan 10 05:07:06.082 2010 (GMT-5)
System Uptime: 0 days 0:07:29.876
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  liong2.exe
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.x86fre.win7_rtm.090713-1255
Debug session time: Tue Jan 12 09:04:53.039 2010 (GMT-5)
System Uptime: 0 days 0:03:24.833
BugCheck D1, {b8ac040, ff, 1, 82c20791}
Probably caused by : hardware ( nt!KiTrap0E+2cf )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.x86fre.win7_rtm.090713-1255
Debug session time: Tue Jan 19 22:59:58.414 2010 (GMT-5)
System Uptime: 0 days 0:21:28.209
BugCheck A, {0, 2, 1, 82ca01b9}
Probably caused by : memory_corruption
DEFAULT_BUCKET_ID:  CODE_CORRUPTION
PROCESS_NAME:  System
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.x86fre.win7_rtm.090713-1255
Debug session time: Wed Jan 20 06:52:29.985 2010 (GMT-5)
System Uptime: 0 days 0:06:17.780
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  svchost.exe

 

[Arvind]

Hi Usasma

Thank you for the email.
Please find the attached systeminfo zip file and let me know if there is anything you find in it.
There is not connected to the USB. I havent got a chance to use the USB yet.I did not plug anything when the crash occured.

I appreciate all your help and time!!
I look forward to hear from you.

Thanks Again
Arvind

 

[usasma]

I can't spot anything attached to your USB.
Have you gotten any further BSOD's?

 

[Arvind]

Hi Usasma

Thanks for the update.

I havent recieved any BSOD's.I havent tried the suggestions yet. I am having problems locating few files.

1.I have a Norton 16.0 installed and I am unable to locate the appropriate Norton Removal tool for this version.

2.I seacrhed for the drivers specified below however was unable to locate them.
iirsp.sys
djsvs.sys
nfrd960.sys
adpu320.sys
adpahci.sys
arc.sys
SiSRaid2.sys
sisraid4.sys
adp94xx.sys
lsi_fc.sys


Please advise.
Thank You
Arvind

 

[lconnie]

I had been running Win XP Home dual booted with Windows 7 RC. All was fine. I clean installed Windows 7 Home Premium on the XP partition and then the fun began. I was having intermittent BSOD and other hardware-looking warnings, some reflected USB, some Norton drivers, none of it made any sense. Memory diagnostics passed, everything else tested out okay. Reloaded Windows 7 Home Premium. Moved the Windows.old files to an external drive. Formatted the partition that had Windows 7 RC. Unloaded all the USB drivers and reinstalled. Still random BSODs. I have an ATI Diamond Radeon graphics card installed and have my monitor connected to it. Drivers were up to date. Had read somewhere that going from XP to 7 can occasionally do some weird things to those settings, so I went into the BIOS and changed from PCI to AGP on-board while still cabled to the card. I don't pretend to understand all of this, but I have not had a problem since. Maybe too early to tell, but I think there was a disconnect between the BIOS and Windows. What remains puzzling is that it all worked fine in Windows 7 RC. Can anyone shed any light on what this is about?

 

[razvanl]

Hi,
Same problem here restart and then restart and so on....
I will do a zip with the latest dumps and upload it, hope something will come out of it.
The machine is a sony vaio laptop model vpccw1s1e all details here

 

[Davidkm]

Had this problem on 2 different systems. I was able to solve it by turning off Intel speedstep in the bios. I also noticed others had found this solution also on intels forum.