New
#51
I thought you had Installed the Chipset Driver
I did earlier. Then i did a fresh install of Win 7
The drive tests mate I only suggested as an elimination thing to do as I like to eliminate what may even sound completely out of whack.
Ummm, if I may "chip" in i'd like to check a couple other things
1. List any Problem devices
- Make sure devices are connected and powered on
- Click Start->Run, enter: msinfo32. Click the + sign next to Components to expand it
- Click Problem Devices. Anything appear?
- If yes, click on it, Ctrl-A to select all, Ctrl-C to copy it, Ctrl-V to paste into next post
- On the other hand, if no devices are listed, tell me so
2. Create a Device Manager Report
- Run the 32 or 64 bit version of DevManView as appropriate for your OS
- Click Ctl-A to select all devices. Then Ctl-S to save
- IMPORTANT: Change Save As type to Tab Delimited Text then save the report and upload to your next post
Not Available ACPI\ENE0100\3&21436425&0 The drivers for this device are not installed.
TSSTcorp CDDVDW TS-L633L ATA Device IDE\CDROMTSSTCORP_CDDVDW_TSL633L________________0400____\5&FBDE2CC&0&1.0.0 Failure using the VxD loader.
Hi there .. That Device refers to ProtectSmart Hard Drive Protection ... Can be Downloaded from the HP Website ..
Have you sorted the Fonts problem yet ?
I'm coming up with needing "ENE CIR Receiver Driver" (i'm gussing it's for an IR receiver on your laptop) Download driver HERE
Now my 2 cents again I see three problem devices listed there - am I right? because I am not very familiar with this sort of stuff.
Now for the TSST it's an optical device - so far so good and the other a receiver driver .
Now I Googled the ACPI and came across this Unknow device acpi/hpq004/3&21436425&0 - HP Support Forum - 121884
which I see is the drive stuff.
Now going back to my earlier suggestions would not it be an idea to test that drive?
There are 2 line items in the report (corresponding to 2 Problem Devices). There are 3 parts to each line item in the report
1. Device Name
2. Device ID
3. Driver Error string (this is the Driver Status Code translated to its string value)
From my observation, the Problem Device report doesn't report every device with driver error BUT (again, just from observation) it does seem to always include devices missing their driver (this is where device status code =28 which equals string "The drivers for this device are not installed."
Device ID
The Device ID is delimited by the character "\". So you'll see there are 3 parts to the first device.
ACPI\ENE0100\3&21436425&0The first part (in Green) of an ID is called the "enumerator". The enumerator for the device missing its driver for this case is ACPI. The remainder of the string helps define the actual device (fyi.. ACPI\ devices are not-plug and play). In this case you need to match the whole string ACPI\ENE0100\3&21436425&0 which defines the device as the receiver i noted in my post.
The OP's error message was unknown device with no driver. The ACPI device in the problem report is the cause of the error message