Service Request Ticket - # 46563

Service Request Information

CONTACT Name Friberg, Susie   View open tasks   View tasks from last 30 days   Schedule Change Contact Date Mar 02, 2012 01:03 PM
Department Disability Access Services Phone 88250
Location Email fribergs@wou.edu Request for more information Send 'Keeping in touch' email Send 'I'm thinking of you' email
SR INFO Type WOU #
Priority Equipment Type
Status Flagged
Description
Laptop Edit WOU # 20110358[Edit Inv] (opens in a new window) Bldg/Room OFF PDR
Service Tag Description Dell Latitude E6320 Intel Core i5-2520M 2.5GHz 3MB
Serial No. 7NZ16R1 Location PDR

CPU Intel Core i5-2520M(2.50GHz,3MB cache)


OS Unknown Software bundled with Cyberlink PowerDVD9.5 and Roxio Creator Stater Ed, MS Office Pro Plus 2010 from P0082337 installed as Office Pro Plus 2007

Wired NIC D4:BE:D9:02:CD:0C


Wireless NIC 08:11:96:AC:A4:5C


Bluetooth NIC D0:DF:9A:B6:24:9C

TECHS Submitted by Teresa Hutchinson Contact hutchinsont@wou.edu 88010
Primary Technician Contact lvoth11@wou.edu 88925

Tracking

Entered by Date Memo
Laven Voth
Email

Public
Entered by Date Memo
Laven Voth Mar 06, 2012 02:50 PM 
Status changed from (1) Pending to (5) Completed
 Add Attachment
Laven Voth Mar 06, 2012 02:50 PM 
Ran ccleaner, it was acting perfect for me.  So I
think it should be good to go, there were a lot of
reg errors, so maybe something was acting up.
 Add Attachment
Teresa Hutchinson Mar 06, 2012 08:39 AM 
****This is an outgoing email****
Hi Susie,

We were just emailing you regarding a service
request that we have for you. (#46563)

Have a new laptop that keeps getting a black screen.

Thanks for your patience and we will help with
this as soon as possible.

Thanks,
Teresa
Add Attachment
Public
Teresa Hutchinson Mar 02, 2012 02:49 PM 
Task reassigned to Laven Voth.
 Add Attachment
Teresa Hutchinson Mar 02, 2012 01:03 PM 
****This is an email****

Lastly, we got 2 new laptops recently.  Computer
#: 20110358[Edit Inv] is periodically giving us the black
screen of death.  It did today again and a forced
restart couldn't revive it.  It eventually came
back to life. Is there a way Computing Services
can document that so that if issues continue to
arise that we can show the manufacturer that
something is amiss?  What are your thoughts? 
Document on my end?

Thanks,
susie
 Add Attachment