- Community Home
- >
- Servers and Operating Systems
- >
- HPE ProLiant
- >
- ProLiant Servers (ML,DL,SL)
- >
- Re: HPCISSS.SYS causing Win 2008 blue screen?
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-24-2008 12:45 PM
тАО07-24-2008 12:45 PM
Windows 2008 Enterprise X64 with Service for NFS running.
Symptom:
Whenever I use NFS client to get large files from the server, it crashes with blue screen. If I use SMB client (Windows client) to copy file, it works just fine.
Troubleshooting done:
I opened case with Microsoft.
Microsoft said the problem was caused by hpcisss.sys driver. Suggest me update this driver.
=========
Module: hpcisss
Base Address: fffffa6000800000
Image Name: hpcisss.sys
Machine Type: 34404 (X64)
Time Stamp: 45f1c0e9 Fri Mar 09 15:17:45 2007
=========
However,
#1
From Device Manager, I saw that the P400 controller was actually using a different driver hpcisss2.sys.
I have no idea why hpcisss.sys was loaded, and who loaded it.
#2
The trouble maker (hpcisss.sys) seems to be from Microsoft (comes with Windows 2008 DVD). How do I update it?
Microsoft is still "investigating" (for couple days). Would like to get some idea from HP.
Thanks!
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-24-2008 12:52 PM
тАО07-24-2008 12:52 PM
Re: HPCISSS.SYS causing Win 2008 blue screen?
I already review this article (http://h20000.www2.hp.com/bizsupport/TechSupport/Document.jsp?objectID=c01068337&dimid)
Didn't seem to apply to Win2008.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-25-2008 11:58 AM
тАО07-25-2008 11:58 AM
Re: HPCISSS.SYS causing Win 2008 blue screen?
yes that driver is for smart array controller p400 that's why you get when you have an smart controller and HP as far as I know Windows has a generic one...
do you know if you have the latest driver for P400 controller?
http://h20000.www2.hp.com/bizsupport/TechSupport/SoftwareDescription.jsp?lang=en&cc=us&prodTypeId=15351&prodSeriesId=1121516&prodNameId=3288134&swEnvOID=4024&swLang=8&mode=2&taskId=135&swItem=MTX-6a5dcf1cd5414b7f8d3089bda6
regards
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-25-2008 01:02 PM
тАО07-25-2008 01:02 PM
Re: HPCISSS.SYS causing Win 2008 blue screen?
Thanks for your reponse.
#1 I already have the latest driver for the P400 controller (see screenshot attached to first post).
#2 Per Windows Device Manager, P400 was NOT using hpcisss.sys. P400 was using hpcisss2.sys. What's the difference between these two files? (see screenshot attached to 2nd post).
Thanks!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-25-2008 01:24 PM
тАО07-25-2008 01:24 PM
Re: HPCISSS.SYS causing Win 2008 blue screen?
oh sorry I saw that know
I was checking document and found this
hpcisss.sys is for old controller like 5i, 6x family
and hpcisss2.sys is for newer controllers like e200 - p400 - ...
http://h20000.www2.hp.com/bc/docs/support/SupportManual/c01479108/c01479108.pdf
and according to your research hpcisss.sys is causing the issue
so my ideas:
1. why if you remove/delete hpcisss.sys or at least rename to .old since you don't have any 5x - 6x Controller
2. if that can not be done what if you try updating it
http://h20000.www2.hp.com/bizsupport/TechSupport/SoftwareDescription.jsp?lang=en&cc=us&prodTypeId=15351&prodSeriesId=397634&prodNameId=3288132&swEnvOID=4024&swLang=8&mode=2&taskId=135&swItem=MTX-c0d3a81b502b4bf1993352c00d
if you extract it there is a hpcisss.sys so override it or try the the .exe
regards
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-25-2008 01:26 PM
тАО07-25-2008 01:26 PM
Re: HPCISSS.SYS causing Win 2008 blue screen?
HpCISSs2.sys
---------------------------------
Blue screen appears intermittently after upgrading
After upgrading an HP BL460C server to Windows Server 2008, the server may intermittently display a blue screen.
Verify the following:
├в ┬в
You have the latest version of the HpCISSs2.sys driver installed on the server. Earlier versions of this driver may cause issues when running on Windows Server 2008. The driver is available in the HP Support Pack, which is available from the Hewlett-Packard Web site.
├в ┬в
The antivirus software on the server is the most current version. Older versions may not be compatible with Windows Server 2008.
If the blue screen continues to appear after you upgrade the driver and antivirus software on the server, consider the following:
├в ┬в
Enable a special pool. For more information, see article 188831, "How to use the special pool feature to isolate pool damage," in the Microsoft Knowledge Base (http://go.microsoft.com/fwlink/?LinkId=111004).
├в ┬в
Obtain a new memory dump.
http://technet2.microsoft.com/windowsserver2008/en/library/8f639d7b-fe03-42f0-8cb9-3a5bbb0ca47c1033.mspx?mfr=true
----------------------
regards
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-26-2008 05:21 AM
тАО07-26-2008 05:21 AM
Re: HPCISSS.SYS causing Win 2008 blue screen?
I updated the hpcisss.sys, rebooted the server, still have the same problem.
Questions:
#1 Why was the hpcisss.sys loaded (when there's no actual hardware requires that driver)?
#2 Is there anyway to prevent hpcisss.sys from being loaded?
Thanks!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-26-2008 08:02 PM
тАО07-26-2008 08:02 PM
Re: HPCISSS.SYS causing Win 2008 blue screen?
#1 Why was the hpcisss.sys loaded (when there's no actual hardware requires that driver)?
--- you did some screens and appeared that W2008 loaded it... I don't why what people from MS say?
#2 Is there anyway to prevent hpcisss.sys from being loaded?
--- I wish I could. Don't you have any component that needs that file??
regards
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-27-2008 10:06 AM
тАО07-27-2008 10:06 AM
Solutioncheck this utility
AutoRuns for Windows v9.32
http://technet.microsoft.com/en-us/sysinternals/bb963902.aspx
maybe in drivers Tab you can some info about hpcisss.sys I could test it in a server since I am not in front of one (at least today ;-))
regards
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-27-2008 12:50 PM
тАО07-27-2008 12:50 PM
Re: HPCISSS.SYS causing Win 2008 blue screen?
On a DL380 G5 system with P400 controller, hpcisss.sys shouldn't be loaded. Microsoft didn't (or couldn't) explain why it was loaded in the memory. :)