All of my Dvd burners not working ona fresh win7 install

It says no disc when I put a fresh disk in the Sony dual layer dvd external burner. I try other 16x blank dvds and even though my computer (Win7) sees the Dvd drive, it refuses to acknowledge blank discs. Also....when I try to burn anything with my other built in burner, it is now burning and coming up with weird errors. "Session Fixation Error" and after trying both Astroburn and CDBurnerXp....all I get is coasters.

Someone mentions "forcing"

http://forum.digital-digest.com/arch...p/t-64167.html

Would that do any good?

No burners work on my freshly installed Win7 setup. I did all updates as well.

Thanks if anyone has some ideas. Please...don't say 'media' or other weak-sauce stuff....I have tried 5 different brands of 16x speed and slower. It is not that, and I find it weird that both burners (which worked before) now both won't burn after a new Win7 install.

Did you take a look in Event Viewer...looking for errors which might provide clues?

Louis

Look in Device Manager. Any errors?

Have you tried doing a Windows Update to see if any of the hardware has any updates that could accompany them?

-- Ryan
Windows Outreach Team

Have you tried doing a Windows Update to see if any of the hardware has any updates that could accompany them?

-- Ryan
Windows Outreach Team

Optical drives do not require any drivers or Windows Updates in order to work or be recognized by Windows.

I do all updates with Win7 upon install...and Device Manager shows no problems. I was using the same program to burn with before my computer crashed from a trojan and I wiped the drive and did a fresh install of win7. I installed Astroburn and it stops with an error and no matter what I burn...it ends up a cup coaster. I tried installing BurnerXP an same thing. I even tried using the Win7 native built in system burning (dragging and dropping the files into the dvd file window and creating a cue of things to burn, and once it starts...it says "burn failed")

How should I check the error log and is there any other ideas?

EDIT = the error at that time says "The device, \Device\CdRom0, is not ready for access yet."

there is also an Atapi error : "The driver detected a controller error on \Device\Ide\IdePort2."

Edited by etherdose, 22 February 2011 - 08:33 PM.

VEW might be able to tel us what the problem is.

Download VEW by Vino Rosso http://images.malwareremoval.com/vino/VEW.exe
and save it to your desktop

Running Windows Vista or Windows 7 you will need to right click the file and select Run as administrator and click Continue or Allow at the User Account Control Prompt.

Click the check boxes next to Application and System located under Select log to query on the upper left

Under Select type to list on the right click the boxes next to Error and Warning Note: If running Windows Vista or Windows 7 also click the box next to Critical (not XP).

Under Number or date of events select Number of events and type 20 in the box next to 1 to 20 and click Run

Once it finishes it will display a log file in notepad

Please copy and paste its entire contents into your next reply

Vino's Event Viewer v01c run on Windows 2008 in English
Report run at 25/02/2011 2:31:46 PM

Note: All dates below are in the format dd/mm/yyyy

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
'Application' Log - Critical Type
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
'Application' Log - Error Type
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Log: 'Application' Date/Time: 25/02/2011 5:23:44 AM
Type: Error Category: 0
Event: 1013 Source: MsiInstaller
Product: NVIDIA PhysX -- Installation terminated

Log: 'Application' Date/Time: 25/02/2011 5:22:46 AM
Type: Error Category: 0
Event: 8194 Source: VSS
Volume Shadow Copy Service error: Unexpected error querying for the IVssWriterCallback interface. hr = 0x80070005, Access is denied. . This is often caused by incorrect security settings in either the writer or requestor process.

Operation:
Gathering Writer Data

Context:
Writer Class Id: {e8132975-6f93-4464-a53e-1050253ae220}
Writer Name: System Writer
Writer Instance ID: {27c1f29d-ee17-4209-98c1-81ea3692914c}

Log: 'Application' Date/Time: 24/02/2011 2:05:35 AM
Type: Error Category: 3
Event: 215 Source: ESENT
WinMail (1052) WindowsMail0: The backup has been stopped because it was halted by the client or the connection with the client failed.

Log: 'Application' Date/Time: 22/02/2011 6:30:51 AM
Type: Error Category: 100
Event: 1000 Source: Application Error
Faulting application name: oblivion.exe, version: 1.2.0.416, time stamp: 0x462392c7 Faulting module name: oblivion.exe, version: 1.2.0.416, time stamp: 0x462392c7 Exception code: 0xc0000005 Fault offset: 0x0018b262 Faulting process id: 0x90c Faulting application start time: 0x01cbd25815768c21 Faulting application path: E:\Games\Oblivion\Nehrim\oblivion.exe Faulting module path: E:\Games\Oblivion\Nehrim\oblivion.exe Report Id: 4aa360e2-3e4d-11e0-99de-0025117494de

Log: 'Application' Date/Time: 21/02/2011 8:21:44 AM
Type: Error Category: 101
Event: 1002 Source: Application Hang
The program oblivion.exe version 1.2.0.416 stopped interacting with Windows and was closed. To see if more information about the problem is available, check the problem history in the Action Center control panel. Process ID: 3e8 Start Time: 01cbd19ddb111dfb Termination Time: 569 Application Path: E:\Games\Oblivion\Nehrim\oblivion.exe Report Id:

Log: 'Application' Date/Time: 21/02/2011 8:03:39 AM
Type: Error Category: 101
Event: 1002 Source: Application Hang
The program oblivion.exe version 1.2.0.416 stopped interacting with Windows and was closed. To see if more information about the problem is available, check the problem history in the Action Center control panel. Process ID: bb4 Start Time: 01cbd19b424eee85 Termination Time: 156 Application Path: E:\Games\Oblivion\Nehrim\oblivion.exe Report Id:

Log: 'Application' Date/Time: 17/02/2011 5:51:54 AM
Type: Error Category: 100
Event: 1000 Source: Application Error
Faulting application name: MassEffectConfig.exe, version: 1.2.0.13, time stamp: 0x481b677e Faulting module name: MassEffectConfig.exe, version: 1.2.0.13, time stamp: 0x481b677e Exception code: 0xc000000d Fault offset: 0x000ad694 Faulting process id: 0x7fc Faulting application start time: 0x01cbce66c78bf172 Faulting application path: E:\Games\Mass Effect\Binaries\MassEffectConfig.exe Faulting module path: E:\Games\Mass Effect\Binaries\MassEffectConfig.exe Report Id: 0585c2bc-3a5a-11e0-b6a2-0025117494de

Log: 'Application' Date/Time: 17/02/2011 5:47:35 AM
Type: Error Category: 100
Event: 1000 Source: Application Error
Faulting application name: MassEffectConfig.exe, version: 1.2.0.13, time stamp: 0x481b677e Faulting module name: MassEffectConfig.exe, version: 1.2.0.13, time stamp: 0x481b677e Exception code: 0xc000000d Fault offset: 0x000ad694 Faulting process id: 0x3f4 Faulting application start time: 0x01cbce662d65fff1 Faulting application path: E:\Games\Mass Effect\Binaries\MassEffectConfig.exe Faulting module path: E:\Games\Mass Effect\Binaries\MassEffectConfig.exe Report Id: 6b425dbd-3a59-11e0-b6a2-0025117494de

Log: 'Application' Date/Time: 17/02/2011 5:47:19 AM
Type: Error Category: 100
Event: 1000 Source: Application Error
Faulting application name: MassEffectConfig.exe, version: 1.2.0.13, time stamp: 0x481b677e Faulting module name: MassEffectConfig.exe, version: 1.2.0.13, time stamp: 0x481b677e Exception code: 0xc000000d Fault offset: 0x000ad694 Faulting process id: 0x474 Faulting application start time: 0x01cbce6624046f27 Faulting application path: E:\Games\Mass Effect\Binaries\MassEffectConfig.exe Faulting module path: E:\Games\Mass Effect\Binaries\MassEffectConfig.exe Report Id: 61e19046-3a59-11e0-b6a2-0025117494de

Log: 'Application' Date/Time: 17/02/2011 5:46:42 AM
Type: Error Category: 100
Event: 1000 Source: Application Error
Faulting application name: MassEffectConfig.exe, version: 1.2.0.13, time stamp: 0x481b677e Faulting module name: MassEffectConfig.exe, version: 1.2.0.13, time stamp: 0x481b677e Exception code: 0xc000000d Fault offset: 0x000ad694 Faulting process id: 0x984 Faulting application start time: 0x01cbce660d6600bd Faulting application path: E:\Games\Mass Effect\Binaries\MassEffectConfig.exe Faulting module path: E:\Games\Mass Effect\Binaries\MassEffectConfig.exe Report Id: 4b47b5ce-3a59-11e0-b6a2-0025117494de

Log: 'Application' Date/Time: 17/02/2011 5:46:12 AM
Type: Error Category: 100
Event: 1000 Source: Application Error
Faulting application name: MassEffectConfig.exe, version: 1.2.0.13, time stamp: 0x481b677e Faulting module name: MassEffectConfig.exe, version: 1.2.0.13, time stamp: 0x481b677e Exception code: 0xc000000d Fault offset: 0x000ad694 Faulting process id: 0xf14 Faulting application start time: 0x01cbce65fb89c01b Faulting application path: E:\Games\Mass Effect\Binaries\MassEffectConfig.exe Faulting module path: E:\Games\Mass Effect\Binaries\MassEffectConfig.exe Report Id: 396b4e1a-3a59-11e0-b6a2-0025117494de

Log: 'Application' Date/Time: 17/02/2011 5:45:59 AM
Type: Error Category: 100
Event: 1000 Source: Application Error
Faulting application name: MassEffectConfig.exe, version: 1.2.0.13, time stamp: 0x481b677e Faulting module name: MassEffectConfig.exe, version: 1.2.0.13, time stamp: 0x481b677e Exception code: 0xc000000d Fault offset: 0x000ad694 Faulting process id: 0xf24 Faulting application start time: 0x01cbce65f45550a9 Faulting application path: E:\Games\Mass Effect\Binaries\MassEffectConfig.exe Faulting module path: E:\Games\Mass Effect\Binaries\MassEffectConfig.exe Report Id: 322cf373-3a59-11e0-b6a2-0025117494de

Log: 'Application' Date/Time: 17/02/2011 5:45:44 AM
Type: Error Category: 100
Event: 1000 Source: Application Error
Faulting application name: MassEffectConfig.exe, version: 1.2.0.13, time stamp: 0x481b677e Faulting module name: MassEffectConfig.exe, version: 1.2.0.13, time stamp: 0x481b677e Exception code: 0xc000000d Fault offset: 0x000ad694 Faulting process id: 0xc8 Faulting application start time: 0x01cbce65eae45655 Faulting application path: E:\Games\Mass Effect\Binaries\MassEffectConfig.exe Faulting module path: E:\Games\Mass Effect\Binaries\MassEffectConfig.exe Report Id: 28c7920b-3a59-11e0-b6a2-0025117494de

Log: 'Application' Date/Time: 17/02/2011 5:45:26 AM
Type: Error Category: 100
Event: 1000 Source: Application Error
Faulting application name: MassEffectConfig.exe, version: 1.2.0.13, time stamp: 0x481b677e Faulting module name: MassEffectConfig.exe, version: 1.2.0.13, time stamp: 0x481b677e Exception code: 0xc000000d Fault offset: 0x000ad694 Faulting process id: 0xd9c Faulting application start time: 0x01cbce65e05823db Faulting application path: E:\Games\Mass Effect\Binaries\MassEffectConfig.exe Faulting module path: E:\Games\Mass Effect\Binaries\MassEffectConfig.exe Report Id: 1e398aca-3a59-11e0-b6a2-0025117494de

Log: 'Application' Date/Time: 17/02/2011 5:44:42 AM
Type: Error Category: 100
Event: 1000 Source: Application Error
Faulting application name: MassEffectConfig.exe, version: 1.2.0.13, time stamp: 0x481b677e Faulting module name: MassEffectConfig.exe, version: 1.2.0.13, time stamp: 0x481b677e Exception code: 0xc000000d Fault offset: 0x000ad694 Faulting process id: 0x81c Faulting application start time: 0x01cbce65c60c571a Faulting application path: E:\Games\Mass Effect\Binaries\MassEffectConfig.exe Faulting module path: E:\Games\Mass Effect\Binaries\MassEffectConfig.exe Report Id: 03e8dbf6-3a59-11e0-b6a2-0025117494de

Log: 'Application' Date/Time: 17/02/2011 5:43:58 AM
Type: Error Category: 100
Event: 1000 Source: Application Error
Faulting application name: MassEffectConfig.exe, version: 1.2.0.13, time stamp: 0x481b677e Faulting module name: MassEffectConfig.exe, version: 1.2.0.13, time stamp: 0x481b677e Exception code: 0xc000000d Fault offset: 0x000ad694 Faulting process id: 0xd0 Faulting application start time: 0x01cbce65aafaed83 Faulting application path: E:\Games\Mass Effect\Binaries\MassEffectConfig.exe Faulting module path: E:\Games\Mass Effect\Binaries\MassEffectConfig.exe Report Id: e9d9caf8-3a58-11e0-b6a2-0025117494de

Log: 'Application' Date/Time: 17/02/2011 5:40:46 AM
Type: Error Category: 100
Event: 1000 Source: Application Error
Faulting application name: MassEffectConfig.exe, version: 1.2.0.13, time stamp: 0x481b677e Faulting module name: MassEffectConfig.exe, version: 1.2.0.13, time stamp: 0x481b677e Exception code: 0xc000000d Fault offset: 0x000ad694 Faulting process id: 0x9a8 Faulting application start time: 0x01cbce65389dae13 Faulting application path: E:\Games\Mass Effect\Binaries\MassEffectConfig.exe Faulting module path: E:\Games\Mass Effect\Binaries\MassEffectConfig.exe Report Id: 77625815-3a58-11e0-b6a2-0025117494de

Log: 'Application' Date/Time: 17/02/2011 4:48:49 AM
Type: Error Category: 100
Event: 1000 Source: Application Error
Faulting application name: MassEffectConfig.exe, version: 1.2.0.13, time stamp: 0x481b677e Faulting module name: MassEffectConfig.exe, version: 1.2.0.13, time stamp: 0x481b677e Exception code: 0xc000000d Fault offset: 0x000ad694 Faulting process id: 0xb4c Faulting application start time: 0x01cbce5df7886390 Faulting application path: E:\Games\Mass Effect\Binaries\MassEffectConfig.exe Faulting module path: E:\Games\Mass Effect\Binaries\MassEffectConfig.exe Report Id: 355b2b9a-3a51-11e0-b6a2-0025117494de

Log: 'Application' Date/Time: 17/02/2011 4:48:36 AM
Type: Error Category: 100
Event: 1000 Source: Application Error
Faulting application name: MassEffectConfig.exe, version: 1.2.0.13, time stamp: 0x481b677e Faulting module name: MassEffectConfig.exe, version: 1.2.0.13, time stamp: 0x481b677e Exception code: 0xc000000d Fault offset: 0x000ad694 Faulting process id: 0x8f4 Faulting application start time: 0x01cbce5defc6478a Faulting application path: E:\Games\Mass Effect\Binaries\MassEffectConfig.exe Faulting module path: E:\Games\Mass Effect\Binaries\MassEffectConfig.exe Report Id: 2dce67e7-3a51-11e0-b6a2-0025117494de

Log: 'Application' Date/Time: 13/02/2011 2:49:02 PM
Type: Error Category: 0
Event: 4373 Source: Windows Installer 3.1
The event description cannot be found.

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
'Application' Log - Warning Type
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Log: 'Application' Date/Time: 15/02/2011 3:50:38 PM
Type: Warning Category: 1
Event: 1020 Source: ASP.NET 4.0.30319.0
Updates to the IIS metabase were aborted because IIS is either not installed or is disabled on this machine. To configure ASP.NET to run in IIS, please install or enable IIS and re-register ASP.NET using aspnet_regiis.exe /i.

Log: 'Application' Date/Time: 15/02/2011 4:54:56 AM
Type: Warning Category: 0
Event: 1530 Source: Microsoft-Windows-User Profiles Service
Windows detected your registry file is still in use by other applications or services. The file will be unloaded now. The applications or services that hold your registry file may not function properly afterwards. DETAIL - 1 user registry handles leaked from \Registry\User\S-1-5-21-1175919193-271066947-1081189780-1000_Classes:
Process 2200 (\Device\HarddiskVolume1\Windows\System32\rundll32.exe) has opened key \REGISTRY\USER\S-1-5-21-1175919193-271066947-1081189780-1000_CLASSES


Log: 'Application' Date/Time: 15/02/2011 4:54:55 AM
Type: Warning Category: 0
Event: 1530 Source: Microsoft-Windows-User Profiles Service
Windows detected your registry file is still in use by other applications or services. The file will be unloaded now. The applications or services that hold your registry file may not function properly afterwards. DETAIL - 1 user registry handles leaked from \Registry\User\S-1-5-21-1175919193-271066947-1081189780-1000:
Process 2200 (\Device\HarddiskVolume1\Windows\System32\rundll32.exe) has opened key \REGISTRY\USER\S-1-5-21-1175919193-271066947-1081189780-1000


Log: 'Application' Date/Time: 14/02/2011 4:19:12 AM
Type: Warning Category: 1
Event: 1020 Source: ASP.NET 4.0.30319.0
Updates to the IIS metabase were aborted because IIS is either not installed or is disabled on this machine. To configure ASP.NET to run in IIS, please install or enable IIS and re-register ASP.NET using aspnet_regiis.exe /i.

Log: 'Application' Date/Time: 09/02/2011 6:59:30 PM
Type: Warning Category: 0
Event: 1530 Source: Microsoft-Windows-User Profiles Service
Windows detected your registry file is still in use by other applications or services. The file will be unloaded now. The applications or services that hold your registry file may not function properly afterwards. DETAIL - 4 user registry handles leaked from \Registry\User\S-1-5-21-1175919193-271066947-1081189780-1000:
Process 1116 (\Device\HarddiskVolume1\Windows\System32\svchost.exe) has opened key \REGISTRY\USER\S-1-5-21-1175919193-271066947-1081189780-1000\Software
Process 1116 (\Device\HarddiskVolume1\Windows\System32\svchost.exe) has opened key \REGISTRY\USER\S-1-5-21-1175919193-271066947-1081189780-1000\Software\Policies\Microsoft\Windows\CurrentVersion\Internet Settings
Process 1116 (\Device\HarddiskVolume1\Windows\System32\svchost.exe) has opened key \REGISTRY\USER\S-1-5-21-1175919193-271066947-1081189780-1000\Software\Policies
Process 1116 (\Device\HarddiskVolume1\Windows\System32\svchost.exe) has opened key \REGISTRY\USER\S-1-5-21-1175919193-271066947-1081189780-1000\Software\Microsoft\Windows\CurrentVersion\Internet Settings


Log: 'Application' Date/Time: 07/02/2011 4:15:08 AM
Type: Warning Category: 3
Event: 3036 Source: Microsoft-Windows-Search
The content source <csc://{S-1-5-21-1175919193-271066947-1081189780-1000}/> cannot be accessed.

Context: Application, SystemIndex Catalog

Details:
(HRESULT : 0x80004005) (0x80004005)


Log: 'Application' Date/Time: 07/02/2011 1:58:42 AM
Type: Warning Category: 0
Event: 1530 Source: Microsoft-Windows-User Profiles Service
Windows detected your registry file is still in use by other applications or services. The file will be unloaded now. The applications or services that hold your registry file may not function properly afterwards. DETAIL - 1 user registry handles leaked from \Registry\User\S-1-5-21-1175919193-271066947-1081189780-1000:
Process 428 (\Device\HarddiskVolume1\Windows\System32\winlogon.exe) has opened key \REGISTRY\USER\S-1-5-21-1175919193-271066947-1081189780-1000


Log: 'Application' Date/Time: 07/02/2011 1:19:32 AM
Type: Warning Category: 0
Event: 11 Source: Microsoft-Windows-RPC-Events
Possible Memory Leak. Application (C:\Windows\System32\svchost.exe -k LocalServiceNetworkRestricted) (PID: 764) has passed a non-NULL pointer to RPC for an [out] parameter marked [allocate(all_nodes)]. [allocate(all_nodes)] parameters are always reallocated; if the original pointer contained the address of valid memory, that memory will be leaked. The call originated on the interface with UUID ({3F31C91E-2545-4B7B-9311-9529E8BFFEF6}), Method number (10). User Action: Contact your application vendor for an updated version of the application.

Log: 'Application' Date/Time: 07/02/2011 12:57:32 AM
Type: Warning Category: 0
Event: 1530 Source: Microsoft-Windows-User Profiles Service
Windows detected your registry file is still in use by other applications or services. The file will be unloaded now. The applications or services that hold your registry file may not function properly afterwards. DETAIL - 1 user registry handles leaked from \Registry\User\S-1-5-21-1175919193-271066947-1081189780-1000:
Process 424 (\Device\HarddiskVolume1\Windows\System32\winlogon.exe) has opened key \REGISTRY\USER\S-1-5-21-1175919193-271066947-1081189780-1000


Log: 'Application' Date/Time: 07/02/2011 12:13:13 AM
Type: Warning Category: 1
Event: 1008 Source: Microsoft-Windows-Search
The Windows Search Service is starting up and attempting to remove the old search index {Reason: Full Index Reset}.


~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
'System' Log - Critical Type
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Log: 'System' Date/Time: 25/02/2011 10:05:19 PM
Type: Critical Category: 63
Event: 41 Source: Microsoft-Windows-Kernel-Power
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.

Log: 'System' Date/Time: 20/02/2011 3:18:12 AM
Type: Critical Category: 63
Event: 41 Source: Microsoft-Windows-Kernel-Power
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.

Log: 'System' Date/Time: 12/02/2011 6:35:37 PM
Type: Critical Category: 63
Event: 41 Source: Microsoft-Windows-Kernel-Power
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.

Log: 'System' Date/Time: 07/02/2011 4:10:49 AM
Type: Critical Category: 63
Event: 41 Source: Microsoft-Windows-Kernel-Power
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
'System' Log - Error Type
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Log: 'System' Date/Time: 25/02/2011 10:05:28 PM
Type: Error Category: 0
Event: 6008 Source: EventLog
The previous system shutdown at 9:37:48 AM on ?2/?25/?2011 was unexpected.

Log: 'System' Date/Time: 18/02/2011 5:43:06 PM
Type: Error Category: 0
Event: 15 Source: cdrom
The device, \Device\CdRom0, is not ready for access yet.

Log: 'System' Date/Time: 18/02/2011 9:25:40 AM
Type: Error Category: 0
Event: 15 Source: cdrom
The device, \Device\CdRom0, is not ready for access yet.

Log: 'System' Date/Time: 18/02/2011 9:15:25 AM
Type: Error Category: 0
Event: 15 Source: cdrom
The device, \Device\CdRom0, is not ready for access yet.

Log: 'System' Date/Time: 17/02/2011 8:26:35 PM
Type: Error Category: 0
Event: 1 Source: VDS Basic Provider
Unexpected failure. Error code: 490@01010004

Log: 'System' Date/Time: 15/02/2011 4:58:28 AM
Type: Error Category: 0
Event: 15 Source: Disk
The device, \Device\Harddisk0\DR0, is not ready for access yet.

Log: 'System' Date/Time: 15/02/2011 4:58:28 AM
Type: Error Category: 0
Event: 11 Source: atapi
The driver detected a controller error on \Device\Ide\IdePort2.

Log: 'System' Date/Time: 15/02/2011 4:58:27 AM
Type: Error Category: 0
Event: 15 Source: Disk
The device, \Device\Harddisk0\DR0, is not ready for access yet.

Log: 'System' Date/Time: 15/02/2011 4:58:27 AM
Type: Error Category: 0
Event: 15 Source: Disk
The device, \Device\Harddisk0\DR0, is not ready for access yet.

Log: 'System' Date/Time: 15/02/2011 4:58:27 AM
Type: Error Category: 0
Event: 15 Source: Disk
The device, \Device\Harddisk0\DR0, is not ready for access yet.

Log: 'System' Date/Time: 15/02/2011 4:58:27 AM
Type: Error Category: 0
Event: 15 Source: Disk
The device, \Device\Harddisk0\DR0, is not ready for access yet.

Log: 'System' Date/Time: 15/02/2011 4:58:27 AM
Type: Error Category: 0
Event: 15 Source: Disk
The device, \Device\Harddisk0\DR0, is not ready for access yet.

Log: 'System' Date/Time: 15/02/2011 4:58:09 AM
Type: Error Category: 0
Event: 15 Source: Disk
The device, \Device\Harddisk0\DR0, is not ready for access yet.

Log: 'System' Date/Time: 15/02/2011 4:58:09 AM
Type: Error Category: 0
Event: 15 Source: Disk
The device, \Device\Harddisk0\DR0, is not ready for access yet.

Log: 'System' Date/Time: 15/02/2011 4:58:09 AM
Type: Error Category: 0
Event: 15 Source: Disk
The device, \Device\Harddisk0\DR0, is not ready for access yet.

Log: 'System' Date/Time: 12/02/2011 7:22:55 PM
Type: Error Category: 0
Event: 7000 Source: Service Control Manager
The TuneUp Theme Extension service failed to start due to the following error: The executable program that this service is configured to run in does not implement the service.

Log: 'System' Date/Time: 12/02/2011 7:18:29 PM
Type: Error Category: 0
Event: 7000 Source: Service Control Manager
The TuneUp Theme Extension service failed to start due to the following error: The executable program that this service is configured to run in does not implement the service.

Log: 'System' Date/Time: 10/02/2011 6:08:29 PM
Type: Error Category: 0
Event: 1 Source: VDS Basic Provider
Unexpected failure. Error code: 490@01010004

Log: 'System' Date/Time: 09/02/2011 1:56:04 AM
Type: Error Category: 0
Event: 11 Source: Disk
The driver detected a controller error on \Device\Harddisk3\DR7.

Log: 'System' Date/Time: 09/02/2011 1:56:03 AM
Type: Error Category: 0
Event: 11 Source: Disk
The driver detected a controller error on \Device\Harddisk3\DR7.

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
'System' Log - Warning Type
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Log: 'System' Date/Time: 25/02/2011 10:16:59 PM
Type: Warning Category: 0
Event: 51 Source: Disk
An error was detected on device \Device\Harddisk4\DR4 during a paging operation.

Log: 'System' Date/Time: 25/02/2011 10:16:59 PM
Type: Warning Category: 0
Event: 51 Source: Disk
An error was detected on device \Device\Harddisk4\DR4 during a paging operation.

Log: 'System' Date/Time: 25/02/2011 10:16:59 PM
Type: Warning Category: 0
Event: 51 Source: Disk
An error was detected on device \Device\Harddisk4\DR4 during a paging operation.

Log: 'System' Date/Time: 25/02/2011 10:16:59 PM
Type: Warning Category: 0
Event: 51 Source: Disk
An error was detected on device \Device\Harddisk4\DR4 during a paging operation.

Log: 'System' Date/Time: 25/02/2011 10:16:59 PM
Type: Warning Category: 0
Event: 51 Source: Disk
An error was detected on device \Device\Harddisk4\DR4 during a paging operation.

Log: 'System' Date/Time: 25/02/2011 10:16:59 PM
Type: Warning Category: 0
Event: 51 Source: Disk
An error was detected on device \Device\Harddisk4\DR4 during a paging operation.

Log: 'System' Date/Time: 25/02/2011 10:16:59 PM
Type: Warning Category: 2
Event: 57 Source: Ntfs
The system failed to flush data to the transaction log. Corruption may occur.

Log: 'System' Date/Time: 25/02/2011 10:16:59 PM
Type: Warning Category: 0
Event: 51 Source: Disk
An error was detected on device \Device\Harddisk4\DR4 during a paging operation.

Log: 'System' Date/Time: 25/02/2011 10:16:59 PM
Type: Warning Category: 0
Event: 51 Source: Disk
An error was detected on device \Device\Harddisk4\DR4 during a paging operation.

Log: 'System' Date/Time: 25/02/2011 10:16:59 PM
Type: Warning Category: 0
Event: 51 Source: Disk
An error was detected on device \Device\Harddisk4\DR4 during a paging operation.

Log: 'System' Date/Time: 25/02/2011 10:16:59 PM
Type: Warning Category: 0
Event: 51 Source: Disk
An error was detected on device \Device\Harddisk4\DR4 during a paging operation.

Log: 'System' Date/Time: 25/02/2011 10:16:59 PM
Type: Warning Category: 0
Event: 51 Source: Disk
An error was detected on device \Device\Harddisk4\DR4 during a paging operation.

Log: 'System' Date/Time: 25/02/2011 10:16:59 PM
Type: Warning Category: 0
Event: 51 Source: Disk
An error was detected on device \Device\Harddisk4\DR4 during a paging operation.

Log: 'System' Date/Time: 25/02/2011 10:16:59 PM
Type: Warning Category: 0
Event: 51 Source: Disk
An error was detected on device \Device\Harddisk4\DR4 during a paging operation.

Log: 'System' Date/Time: 25/02/2011 10:16:59 PM
Type: Warning Category: 0
Event: 51 Source: Disk
An error was detected on device \Device\Harddisk4\DR4 during a paging operation.

Log: 'System' Date/Time: 25/02/2011 10:16:59 PM
Type: Warning Category: 0
Event: 51 Source: Disk
An error was detected on device \Device\Harddisk4\DR4 during a paging operation.

Log: 'System' Date/Time: 25/02/2011 10:16:59 PM
Type: Warning Category: 0
Event: 51 Source: Disk
An error was detected on device \Device\Harddisk4\DR4 during a paging operation.

Log: 'System' Date/Time: 25/02/2011 10:16:59 PM
Type: Warning Category: 0
Event: 51 Source: Disk
An error was detected on device \Device\Harddisk4\DR4 during a paging operation.

Log: 'System' Date/Time: 25/02/2011 10:16:59 PM
Type: Warning Category: 0
Event: 51 Source: Disk
An error was detected on device \Device\Harddisk4\DR4 during a paging operation.

Log: 'System' Date/Time: 25/02/2011 10:16:59 PM
Type: Warning Category: 0
Event: 51 Source: Disk
An error was detected on device \Device\Harddisk4\DR4 during a paging operation.

See this http://support.microsoft.com/kb/244780

Also, this is old, but there might be an answer in there http://www.eventid.net/display.asp?eventid=51&eventno=793&source=Disk&phase=1 scroll down to 'anonymous'

Look in Device Manager. Any errors?

Yeah...under Device Manager...no errors.

Also...I clicked the links that were posted just above this one and it is a long list of what the errors mean, but I don't see how to resolve it. I run Win7 and so although there are many errors referring to cd roms, I still don't know what to do to resolve this.

Edited by etherdose, 27 February 2011 - 03:29 PM.

*bump*