[SOLVED] computer crash when using blank recordable cd

crap 10 minutes later and same crash problem, now what???

one_unique_guy said:
Sorry not home often, but trying to get solved. I tried a dvd+r dl blank disk seems fine, just the cd-r disks affect the system possibly cd+r but don't have one to check with. will try SONY DVD drive and let you know soon.


wierd it was the drive I am guessing, cuz it works fine with SONY dvd rw drive now, I am hoping it stays this way. thank you for your help
Click to expand...
 
sorry but problem back even with new drive, any other ideas?
jcgriff2 said:
Hi -

Thank you for posting back - much appreciated. I thought it was fixed because i had a blank cd in the drive for 30 minutes usually takes about 1 minute to shutdown with old drive

Good luck with the new DVD drive.

Regards. . .

jcgriff2

`
Click to expand...
 
Doh! I forgot about the crash dump problem.
Please submit a new set of jcgriff2 reports.
Does the problem occur with just CD's still?
 
only seems to be blank cd-r disks only because i have no cd+r disks and only when blank, dvd works fine i think, havent burrned any dvd stuff latley.
will send info soon jcgriff reports
 
Hi -

Was the DVD drive the only piece of hardware that was replaced?
Code: 
 [FONT=Lucida Console]
Event[302]:
  Log Name: Application
  Source: Microsoft-Windows-Security-SPP
  Date: 2012-05-07T16:38:53.000
  Description: 
[COLOR="#FF0000"]Hardware has changed from previous boot.[/COLOR]
 AppId=55c92734-d682-4d71-983e-d6ec3f16059f, SkuId=586bc076-c93d-429a-afe5-a69fbc644e88.[/FONT]


After that, chkdsk ran -
Code: 
 [FONT=Lucida Console]Event[278]:
  Log Name: Application
  Source: Microsoft-Windows-Wininit
  Date: 2012-05-07T17:17:26.000
  Description: 


Checking file system on C:
The type of the file system is NTFS.


One of your disks needs to be checked for consistency. You
may cancel the disk check, but it is strongly recommended
that you continue.
Windows will now check the disk.                         

CHKDSK is verifying files (stage 1 of 3)...
The attribute of type 0x80 and instance tag 0x0 in file 0x3d5a
has allocated length of 0xfbd3000 instead of 0xfc23000.
Deleted corrupt attribute list entry
with type code 128 in file 15706.
Unable to locate attribute with instance tag 0x0 and segment
reference 0x160000000004d9.  The expected attribute type is 0x80.
Deleting corrupt attribute record (128, "")
from file record segment 1241.
Unable to locate attribute with instance tag 0x0 and segment
reference 0xcd000000000625.  The expected attribute type is 0x80.
Deleting corrupt attribute record (128, "")
from file record segment 1573.
Unable to locate attribute with instance tag 0x0 and segment
reference 0x300000000ad32.  The expected attribute type is 0x80.
Deleting corrupt attribute record (128, "")
from file record segment 44338.
Unable to locate attribute with instance tag 0x0 and segment
reference 0x300000000ad70.  The expected attribute type is 0x80.
Deleting corrupt attribute record (128, "")
from file record segment 44400.
Unable to locate attribute with instance tag 0x0 and segment
reference 0x2000000010d50.  The expected attribute type is 0x80.
Deleting corrupt attribute record (128, "")
from file record segment 68944.
Unable to locate attribute with instance tag 0x0 and segment
reference 0x1000000019e0d.  The expected attribute type is 0x80.
Deleting corrupt attribute record (128, "")
from file record segment 105997.
Unable to locate attribute with instance tag 0x0 and segment
reference 0x200000001b2ea.  The expected attribute type is 0x80.
Deleting corrupt attribute record (128, "")
from file record segment 111338.
Unable to locate attribute with instance tag 0x0 and segment
reference 0x3000000034ed8.  The expected attribute type is 0x80.
Deleting corrupt attribute record (128, "")
from file record segment 216792.
Unable to locate attribute with instance tag 0x0 and segment
reference 0x7000000035040.  The expected attribute type is 0x80.
Deleting corrupt attribute record (128, "")
from file record segment 217152.
Unable to locate attribute with instance tag 0x0 and segment
reference 0xc00000003537f.  The expected attribute type is 0x80.
Deleting corrupt attribute record (128, "")
from file record segment 217983.
Unable to locate attribute with instance tag 0x0 and segment
reference 0x20000000357e1.  The expected attribute type is 0x80.
Deleting corrupt attribute record (128, "")
from file record segment 219105.
Unable to locate attribute with instance tag 0x0 and segment
reference 0x20000000035bd5.  The expected attribute type is 0x80.
Deleting corrupt attribute record (128, "")
from file record segment 220117.
Attribute record of type 0x80 and instance tag 0x0 is cross linked
starting at 0x1b522 for possibly 0x6 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x0
in file 0x2708b is already in use.
The attribute of type 0x80 and instance tag 0x0 in file 0x2708b
has allocated length of 0x26b0000 instead of 0x1b68000.
Deleted corrupt attribute list entry
with type code 128 in file 159883.
Unable to locate attribute with instance tag 0x0 and segment
reference 0x600000002708d.  The expected attribute type is 0x80.
Deleting corrupt attribute record (128, "")
from file record segment 159885.
Unable to locate attribute with instance tag 0x0 and segment
reference 0x600000002708e.  The expected attribute type is 0x80.
Deleting corrupt attribute record (128, "")
from file record segment 159886.
  227072 file records processed.                                         

File verification completed.
Deleting orphan file record segment 1241.
Deleting orphan file record segment 1573.
  108 large file records processed.                                   

  0 bad file records processed.                                     

  0 EA records processed.                                           

  61 reparse records processed.                                      

CHKDSK is verifying indexes (stage 2 of 3)...
The file reference 0xd00000002a22c of index entry sql8A95.tmp of index $I30
with parent 0x1a9 is not the same as 0xf00000002a22c.
Deleting index entry sql8A95.tmp in index $I30 of file 425.
Index entry ~DF11ECA95CCB4FFF21.TMP of index $I30 in file 0x203 points to unused file 0x2a13d.
Deleting index entry ~DF11ECA95CCB4FFF21.TMP in index $I30 of file 515.
Index entry ~DF11E~1.TMP of index $I30 in file 0x203 points to unused file 0x2a13d.
Deleting index entry ~DF11E~1.TMP in index $I30 of file 515.
The file reference 0xb00000002a13f of index entry ~DFD3234A49AC146377.TMP of index $I30
with parent 0x203 is not the same as 0xc00000002a13f.
Deleting index entry ~DFD3234A49AC146377.TMP in index $I30 of file 515.
The file reference 0xb00000002a13f of index entry ~DFD32~1.TMP of index $I30
with parent 0x203 is not the same as 0xc00000002a13f.
Deleting index entry ~DFD32~1.TMP in index $I30 of file 515.
The file reference 0xe00000002a11f of index entry 7XGJNYU3.txt of index $I30
with parent 0x24b is not the same as 0xf00000002a11f.
Deleting index entry 7XGJNYU3.txt in index $I30 of file 587.
Unable to locate the file name attribute of index entry MSS.log
of index $I30 with parent 0x62d in file 0x290c0.
Deleting index entry MSS.log in index $I30 of file 1581.
Unable to locate the file name attribute of index entry MSS00D16.log
of index $I30 with parent 0x62d in file 0x2a219.
Deleting index entry MSS00D16.log in index $I30 of file 1581.
Index entry 28c8b86deab549a1.customDestinations-ms of index $I30 in file 0x552a points to unused file 0x2a20b.
Deleting index entry 28c8b86deab549a1.customDestinations-ms in index $I30 of file 21802.
Index entry 28C8B8~1.CUS of index $I30 in file 0x552a points to unused file 0x2a20b.
Deleting index entry 28C8B8~1.CUS in index $I30 of file 21802.
Index entry RecoveryStore.{44CE7380-988E-11E1-9088-50E549C6BE72}.dat of index $I30 in file 0xebfd points to unused file 0x2a135.
Deleting index entry RecoveryStore.{44CE7380-988E-11E1-9088-50E549C6BE72}.dat in index $I30 of file 60413.
Index entry RECOVE~1.DAT of index $I30 in file 0xebfd points to unused file 0x2a135.
Deleting index entry RECOVE~1.DAT in index $I30 of file 60413.
Index entry {44CE7381-988E-11E1-9088-50E549C6BE72}.dat of index $I30 in file 0xebfd points to unused file 0x2a13e.
Deleting index entry {44CE7381-988E-11E1-9088-50E549C6BE72}.dat in index $I30 of file 60413.
Index entry {44CE7~1.DAT of index $I30 in file 0xebfd points to unused file 0x2a13e.
Deleting index entry {44CE7~1.DAT in index $I30 of file 60413.
  286180 index entries processed.                                        

Index verification completed.
CHKDSK is scanning unindexed files for reconnect to their original directory.
Recovering orphaned file 6qf5421.tmp (167440) into directory file 159882.
Recovering orphaned file 59g5B05.tmp (167446) into directory file 159882.
Recovering orphaned file MSS00D18.log (168128) into directory file 1581.
Recovering orphaned file 9II7WY5B.txt (172319) into directory file 587.
Recovering orphaned file 28C8B8~1.CUS (172351) into directory file 21802.
Recovering orphaned file 28c8b86deab549a1.customDestinations-ms (172351) into directory file 21802.
Recovering orphaned file login[1].htm (172588) into directory file 60431.
Recovering orphaned file LOGIN_~1.HTM (172588) into directory file 60431.
Recovering orphaned file 0j92CC7.tmp (216203) into directory file 159882.
Recovering orphaned file o1a337C.tmp (216350) into directory file 159882.
Recovering orphaned file ccd3DD9.tmp (218565) into directory file 159882.
  11 unindexed files scanned.                                        

Recovering orphaned file k4f45E6.tmp (218664) into directory file 159882.
CHKDSK is recovering remaining unindexed files.
  1 unindexed files recovered.                                      

CHKDSK is verifying security descriptors (stage 3 of 3)...
  227072 file SDs/SIDs processed.                                        

Cleaning up 327 unused index entries from index $SII of file 0x9.
Cleaning up 327 unused index entries from index $SDH of file 0x9.
Cleaning up 327 unused security descriptors.
Security descriptor verification completed.
Inserting data attribute into file 15706.
Inserting data attribute into file 159883.
  29557 data files processed.                                           

CHKDSK is verifying Usn Journal...
The USN Journal length 0x2c37ceea8 in file 0xe5a7 is less the
largest USN encountered, 0x2c37f81e8, plus eight in file 0x28e16.
Repairing Usn Journal $J data stream.
Usn Journal verification completed.
[COLOR="#FF0000"]Correcting errors in the master file table's (MFT) BITMAP attribute.[/COLOR]Correcting errors in the Volume Bitmap.
Windows has made corrections to the file system.

 976657407 KB total disk space.
 531856124 KB in 190324 files.
    118500 KB in 29557 indexes.
         0 KB in bad sectors.
    323167 KB in use by the system.
     65536 KB occupied by the log file.
 444359616 KB available on disk.

      4096 bytes in each allocation unit.
 244164351 total allocation units on disk.
 111089904 allocation units available on disk.

Internal Info:
00 77 03 00 f4 5a 03 00 76 51 06 00 00 00 00 00  .w...Z..vQ......
c1 8e 00 00 3d 00 00 00 00 00 00 00 00 00 00 00  ....=...........
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................

Windows has finished checking your disk.
Please wait while your computer restarts.[/FONT]

MFT corrected by chkdsk -
Code: 
 [FONT=Lucida Console][color=red]Correcting errors in the master file table's (MFT) BITMAP attribute.[/COLOR][/FONT]


246 Windows Updates failures since January -
Code: 
 [FONT=Lucida Console]Failed extract of third-party root list from auto update cab at:
 <http://www.download.windowsupdate.com/msdownload/update/v3/static/trustedr/en/authrootstl.cab> 
with error: 
A required certificate is not within its validity period when verifying 
against the current system clock or the timestamp in the signed file.
[/FONT]
You do have 73 hotfixes installed.



Microsoft Antimalware on the attack -
Code: 
 [FONT=Lucida Console]Event[542]:
  Log Name: System
  Source: Microsoft Antimalware
  Date: 2012-05-07T15:57:10.000
  Description: 
[COLOR="#FF0000"]Microsoft Antimalware has removed history of malware and other potentially unwanted software.[/COLOR]
 	Time: ?4/?22/?2012 3:57:10 PM
 	User: NT AUTHORITY\SYSTEM[/FONT]

Code: 
 [FONT=Lucida Console]Event[1454]:
  Log Name: System
  Source: Microsoft Antimalware
  Date: 2012-05-01T15:40:44.000
  Description: 
Microsoft Antimalware has detected a suspicious behavior.
 For more information please see the following:
http://go.microsoft.com/fwlink/?linkid=158117&threatid=4294967289
 	Name: Behavior:[COLOR="#FF0000"]Win32/ModifiedBootRecord[/COLOR]
 	ID: 2323894493
 	Severity: Low
 	Category: Suspicious Behavior
 	Path: file:_C:\Users\Paul\AppData\Local\Temp\un984.exe;process:_6192
 	Detection Origin: Local machine
 	Detection Type: Suspicious
 	Detection Source: Real-Time Protection
 	Status: Executing
 	User: Main\Paul
 	Process Name: C:\Users\Paul\AppData\Local\Temp\un984.exe
 	Signature ID: 23858570787236
 	Signature Version: AV: 1.125.839.0, AS: 1.125.839.0
 	Engine Version: 1.1.8304.0
 	Fidelity Label:  Medium
 	Target File Name:  \Device\Harddisk3\DR4

[/FONT]

http://www.microsoft.com/security/p...ram:Win32/GenericBehavior&threatid=4294967289

Code: 
 [FONT=Lucida Console]
Event[1525]:
  Log Name: System
  Source: Microsoft Antimalware
  Date: 2012-05-01T03:10:46.000
  Description: 
Microsoft Antimalware Configuration has changed. If this is an unexpected event you should review the settings as this may be the result of malware.
 	Old value: Default\Signature Updates\UpdatedWithinGracePeriod = 0x2
 	New value: HKLM\SOFTWARE\Microsoft\Microsoft Antimalware\Signature Updates\UpdatedWithinGracePeriod = 0x0[/FONT]

Code: 
 [FONT=Lucida Console]Event[1526]:
  Log Name: System
  Source: Microsoft Antimalware
  Date: 2012-05-01T03:10:46.000
  Description: 
Microsoft Antimalware Configuration has changed. If this is an unexpected event you should review the settings as this may be the result of malware.
 	Old value: Default\OneTimeSqmDataSent = 0x0
 	New value: HKLM\SOFTWARE\Microsoft\Microsoft Antimalware\OneTimeSqmDataSent = 0x1[/FONT]

Code: 
 [FONT=Lucida Console]Event[1527]:
  Log Name: System
  Source: Microsoft Antimalware
  Date: 2012-05-01T03:10:45.000
   Description: 
Microsoft Antimalware has removed history of malware and other potentially unwanted software.
 	Time: ?4/?16/?2012 3:10:45 AM
 	User: NT AUTHORITY\SYSTEM
[/FONT]

I'm wondering if infection is present.

Any other strange occurrences?

Regards. . .

jcgriff2

`
 
Only the DVD changed, then Windows updated driver then in restart auto scan hard drive/ repaired. just new video changed now cant see menu bar/start button and left most part of screen, I unlocked bar and expanded up so "quick start is showing but not start button or clock on right side, adjusting screen size does not fix
 
usasma said:
If it's not malware, then I have to suspect bad hardware.
Check the hard drives (ALL of them) with this free procedure: http://www.carrona.org/hddiag.html
Check memory with this free procedure: http://www.carrona.org/memdiag.html

If able to run stuff in Windows, try the rest of these free diagnostics: http://www.carrona.org/addldiag.html

Try checking the connections for your video card - and try another monitor (and cable) to see if that helps with the screen problem.
Click to expand...

everything is good untill I use the DVD burner, All scans return "good" nothing not working right.
got monitor fixed by re setting to hdmi again, seems the monitor forgot what is was using for information. lol
 
James7679 said:
have you managed to resolve this issue?
Click to expand...

am attempting to re-install windows, it worked fine for 3 months then this error occured, cant figure it out, nothing at all on BSOD!!!
Having problems with re-installing win 7. cant even wipe drive to start fresh. getting help in win 7 threads.
 
Eventually you're going to have to try a new CD/DVD drive.
Maybe you can purchase one from a store that will allow returns if its not needed?
 
usasma said:
Eventually you're going to have to try a new CD/DVD drive.
Maybe you can purchase one from a store that will allow returns if its not needed?
Click to expand...

thx, already did, someone sugested power or data cords might be problem, just changed power cord will check soon. thanks for all the help
 

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top