Ticket #102 (closed defect: fixed)

Opened 11 years ago

Last modified 11 years ago

STOP D1 blue screen on Todd's machine

Reported by: joshuadf Owned by: k1@…
Priority: major Milestone:
Component: systems Version:
Keywords: Cc: det@…,k1@…

Description

Todd's machine has a blue screen with a different error than Onard's had.

STOP 0x000000D1 DRIVER_IRQL_NOT_LESS_OR_EQUAL

The driver listed is mvstdi5x.sys... please make sure we're using the latest from https://www.washington.edu/uware/uwick/ (it's 8.5i for Summer 2007) and look if McAfee has any separate patches available.

Change History

comment:1 Changed 11 years ago by k1@…

  • Status changed from new to assigned

I downloaded the latest version of VirusScan? from the UW computing site (says version 8.5 or 8.6 depending where you look) and pushed it via the domain installer as an upgrade. So that will update on the next reboot for each machine. If the problem persists I'll upgrade the drivers on Todd's machine or he feels inclined do so to he can do it himself.

comment:2 Changed 11 years ago by joshuadf

JE, Todd's machine still says 8.0. Did you actually test this on any machine? I see that 8.0 is also still listed alongside 8.6 in your Group Policy. Where did you get the 8.6 MSI file? I usually download from: https://www.washington.edu/uware/virusscan/ which only lists 8.5i.

Also, don't forget to send a summary of your progress on other projects, I'm particularly interested in hardware inventory and wpkg.

comment:3 Changed 11 years ago by k1@…

I was experimenting with the group policy settings with certain packages set to upgrade other packages, it looks like it didn't work so I've set it to the other way where I remove the old package with the new one.

It says 8.6, but that MSI file was extracted from installer from the the UW computing site which is listed as 8.5i. This was the same method I used to obtain the 8.0 installer MSI.

comment:4 Changed 11 years ago by k1@…

  • Status changed from assigned to closed
  • Resolution set to fixed

I haven't heard about any more problems related to this so I'll just close it.

Note: See TracTickets for help on using tickets.