Page 2 of 3 First 123 Last
  1. #21

    Re: computer crash when using blank recordable cd

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

    Quote Originally Posted by one_unique_guy View Post
    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


    • Ad Bot

      advertising
      Beep.

        
       

  2. #22

    Re: computer crash when using blank recordable cd

    sorry but problem back even with new drive, any other ideas?
    Quote Originally Posted by jcgriff2 View Post
    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

    `

  3. #23
    jcgriff2's Avatar
    Join Date
    Feb 2012
    Location
    New Jersey Shore
    Posts
    16,312
    • specs System Specs
      • Manufacturer:
        HP
      • Model Number:
        HP ENVY TouchSmart 17-j130us Notebook - E8A04UA
      • Motherboard:
        HP Insyde 720265-501 6050A2549501-MB-A02
      • CPU:
        Intel Core i7-4700MQ Processor with Turbo Boost up to 3.4GHz.
      • Memory:
        12GB DDR3L SDRAM (2 DIMM)
      • Graphics:
        Intel HD graphics 4600 with up to 1792MB total graphics memory
      • Sound Card:
        Beats Audio quad speakers and two subwoofers
      • Hard Drives:
        1TB 5400RPM hard drive with HP ProtectSmart Hard Drive Protection
      • Disk Drives:
        Hitachi 500 GB SSD; 7 TB USB External
      • Power Supply:
        90w
      • Case:
        Laptop
      • Display:
        17.3-inch diagonal HD+ BrightView LED-backlit touchscreen display (1600 x 900)
      • Operating System:
        Windows 8.1

    Re: computer crash when using blank recordable cd

    What media did it crash with?
    - CD
    - DVD
    - blank
    -non-blank

    BSOD Posting Instructions - Windows 10, 8.1, 8, 7 & Vista ` ` `Carrona Driver Reference Table (DRT)
    https://www.sysnative.com/
    Sysnative Hex-Decimal-UNIX Date Conversion

    Has Sysnative Forums helped you?
    Please consider donating to help support the forum.
    Thank You!

    Microsoft MVP 2009-2015
    Windows Insider MVP 2018 - Present

  4. #24

    Join Date
    Feb 2012
    Posts
    2,086
    Blog Entries
    7

    Re: computer crash when using blank recordable cd

    Please zip up and upload the crash dumps.

  5. #25

    Join Date
    Feb 2012
    Posts
    2,086
    Blog Entries
    7

    Re: computer crash when using blank recordable cd

    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?

  6. #26

    Re: computer crash when using blank recordable cd

    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

  7. #27

    Re: computer crash when using blank recordable cd

    here is reports I think it is all of them
    Last edited by jcgriff2; 07-16-2017 at 04:39 PM.

  8. #28
    jcgriff2's Avatar
    Join Date
    Feb 2012
    Location
    New Jersey Shore
    Posts
    16,312
    • specs System Specs
      • Manufacturer:
        HP
      • Model Number:
        HP ENVY TouchSmart 17-j130us Notebook - E8A04UA
      • Motherboard:
        HP Insyde 720265-501 6050A2549501-MB-A02
      • CPU:
        Intel Core i7-4700MQ Processor with Turbo Boost up to 3.4GHz.
      • Memory:
        12GB DDR3L SDRAM (2 DIMM)
      • Graphics:
        Intel HD graphics 4600 with up to 1792MB total graphics memory
      • Sound Card:
        Beats Audio quad speakers and two subwoofers
      • Hard Drives:
        1TB 5400RPM hard drive with HP ProtectSmart Hard Drive Protection
      • Disk Drives:
        Hitachi 500 GB SSD; 7 TB USB External
      • Power Supply:
        90w
      • Case:
        Laptop
      • Display:
        17.3-inch diagonal HD+ BrightView LED-backlit touchscreen display (1600 x 900)
      • Operating System:
        Windows 8.1

    Re: computer crash when using blank recordable cd

    Hi -

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

    After that, chkdsk ran -
    Code:
     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.
    Correcting errors in the master file table's (MFT) BITMAP attribute.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.
    MFT corrected by chkdsk -
    Code:
     Correcting errors in the master file table's (MFT) BITMAP attribute.


    246 Windows Updates failures since January -
    Code:
     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.
    
    You do have 73 hotfixes installed.



    Microsoft Antimalware on the attack -
    Code:
     Event[542]:
      Log Name: System
      Source: Microsoft Antimalware
      Date: 2012-05-07T15:57:10.000
      Description: 
    Microsoft Antimalware has removed history of malware and other potentially unwanted software.
     	Time: ?4/?22/?2012 3:57:10 PM
     	User: NT AUTHORITY\SYSTEM
    Code:
     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:Win32/ModifiedBootRecord
     	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
    
    
    http://www.microsoft.com/security/po...tid=4294967289

    Code:
     
    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
    Code:
     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
    Code:
     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
    
    I'm wondering if infection is present.

    Any other strange occurrences?

    Regards. . .

    jcgriff2

    `

    BSOD Posting Instructions - Windows 10, 8.1, 8, 7 & Vista ` ` `Carrona Driver Reference Table (DRT)
    https://www.sysnative.com/
    Sysnative Hex-Decimal-UNIX Date Conversion

    Has Sysnative Forums helped you?
    Please consider donating to help support the forum.
    Thank You!

    Microsoft MVP 2009-2015
    Windows Insider MVP 2018 - Present

  9. #29
    jcgriff2's Avatar
    Join Date
    Feb 2012
    Location
    New Jersey Shore
    Posts
    16,312
    • specs System Specs
      • Manufacturer:
        HP
      • Model Number:
        HP ENVY TouchSmart 17-j130us Notebook - E8A04UA
      • Motherboard:
        HP Insyde 720265-501 6050A2549501-MB-A02
      • CPU:
        Intel Core i7-4700MQ Processor with Turbo Boost up to 3.4GHz.
      • Memory:
        12GB DDR3L SDRAM (2 DIMM)
      • Graphics:
        Intel HD graphics 4600 with up to 1792MB total graphics memory
      • Sound Card:
        Beats Audio quad speakers and two subwoofers
      • Hard Drives:
        1TB 5400RPM hard drive with HP ProtectSmart Hard Drive Protection
      • Disk Drives:
        Hitachi 500 GB SSD; 7 TB USB External
      • Power Supply:
        90w
      • Case:
        Laptop
      • Display:
        17.3-inch diagonal HD+ BrightView LED-backlit touchscreen display (1600 x 900)
      • Operating System:
        Windows 8.1

    Re: computer crash when using blank recordable cd


    BSOD Posting Instructions - Windows 10, 8.1, 8, 7 & Vista ` ` `Carrona Driver Reference Table (DRT)
    https://www.sysnative.com/
    Sysnative Hex-Decimal-UNIX Date Conversion

    Has Sysnative Forums helped you?
    Please consider donating to help support the forum.
    Thank You!

    Microsoft MVP 2009-2015
    Windows Insider MVP 2018 - Present

  10. #30

    Re: computer crash when using blank recordable cd

    It is possible, I am using MS security essentials, so I should not have problems, but it is always possible

  11. #31
    jcgriff2's Avatar
    Join Date
    Feb 2012
    Location
    New Jersey Shore
    Posts
    16,312
    • specs System Specs
      • Manufacturer:
        HP
      • Model Number:
        HP ENVY TouchSmart 17-j130us Notebook - E8A04UA
      • Motherboard:
        HP Insyde 720265-501 6050A2549501-MB-A02
      • CPU:
        Intel Core i7-4700MQ Processor with Turbo Boost up to 3.4GHz.
      • Memory:
        12GB DDR3L SDRAM (2 DIMM)
      • Graphics:
        Intel HD graphics 4600 with up to 1792MB total graphics memory
      • Sound Card:
        Beats Audio quad speakers and two subwoofers
      • Hard Drives:
        1TB 5400RPM hard drive with HP ProtectSmart Hard Drive Protection
      • Disk Drives:
        Hitachi 500 GB SSD; 7 TB USB External
      • Power Supply:
        90w
      • Case:
        Laptop
      • Display:
        17.3-inch diagonal HD+ BrightView LED-backlit touchscreen display (1600 x 900)
      • Operating System:
        Windows 8.1

    Re: computer crash when using blank recordable cd

    Did you run chkdsk or did the system do it on its own?

    BSOD Posting Instructions - Windows 10, 8.1, 8, 7 & Vista ` ` `Carrona Driver Reference Table (DRT)
    https://www.sysnative.com/
    Sysnative Hex-Decimal-UNIX Date Conversion

    Has Sysnative Forums helped you?
    Please consider donating to help support the forum.
    Thank You!

    Microsoft MVP 2009-2015
    Windows Insider MVP 2018 - Present

  12. #32

    Re: computer crash when using blank recordable cd

    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

  13. #33

    Join Date
    Feb 2012
    Posts
    2,086
    Blog Entries
    7

    Re: computer crash when using blank recordable cd

    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.

  14. #34
    James7679's Avatar
    Join Date
    May 2012
    Location
    Central Florida
    Age
    39
    Posts
    290
    • specs System Specs
      • Manufacturer:
        Me
      • Model Number:
        James5000
      • Motherboard:
        Gigabyte GA-Z68A-D3-B3
      • CPU:
        i5 2500K @ ~4500 w/1.32 volts @21idle-68full load
      • Memory:
        2x4 Patriot Viper 2 Extreme @1600
      • Graphics:
        EVGA 580 3gb reference
      • Sound Card:
        Nvidia HD Audio to 7.1 receiver
      • Hard Drives:
        64GB Patriot Torqx2 (OS and BF3), 250GB 'cuda for files and dox and 1tb 'cuda for imaging and backup
      • Disk Drives:
        1xLG CD/DVD Burner 1xLG BluRay
      • Power Supply:
        Corsair 550vx
      • Case:
        Thermaltake V3
      • Cooling:
        Noctua NH-C14
      • Display:
        32&quot; 1080p Hdtv
      • Operating System:
        Win7 x64 Home Prem.

    Re: computer crash when using blank recordable cd

    have you managed to resolve this issue?

  15. #35

    Re: computer crash when using blank recordable cd

    Quote Originally Posted by usasma View Post
    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.
    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

  16. #36

    Re: computer crash when using blank recordable cd

    Quote Originally Posted by James7679 View Post
    have you managed to resolve this issue?
    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.

  17. #37
    James7679's Avatar
    Join Date
    May 2012
    Location
    Central Florida
    Age
    39
    Posts
    290
    • specs System Specs
      • Manufacturer:
        Me
      • Model Number:
        James5000
      • Motherboard:
        Gigabyte GA-Z68A-D3-B3
      • CPU:
        i5 2500K @ ~4500 w/1.32 volts @21idle-68full load
      • Memory:
        2x4 Patriot Viper 2 Extreme @1600
      • Graphics:
        EVGA 580 3gb reference
      • Sound Card:
        Nvidia HD Audio to 7.1 receiver
      • Hard Drives:
        64GB Patriot Torqx2 (OS and BF3), 250GB 'cuda for files and dox and 1tb 'cuda for imaging and backup
      • Disk Drives:
        1xLG CD/DVD Burner 1xLG BluRay
      • Power Supply:
        Corsair 550vx
      • Case:
        Thermaltake V3
      • Cooling:
        Noctua NH-C14
      • Display:
        32&quot; 1080p Hdtv
      • Operating System:
        Win7 x64 Home Prem.

    Re: computer crash when using blank recordable cd

    what kind of Motherboard do you have?

  18. #38

    Join Date
    Feb 2012
    Posts
    2,086
    Blog Entries
    7

    Re: computer crash when using blank recordable cd

    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?

  19. #39

    Re: computer crash when using blank recordable cd

    Quote Originally Posted by usasma View Post
    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?
    thx, already did, someone sugested power or data cords might be problem, just changed power cord will check soon. thanks for all the help

  20. #40

    Re: computer crash when using blank recordable cd

    Quote Originally Posted by James7679 View Post
    what kind of Motherboard do you have?
    using new build w/ gigabyte mb, sorry forgot the model number 8 gig mem/maybe 6 forget wich, intel I5 chip&cooler

Page 2 of 3 First 123 Last

Similar Threads

  1. BSOD and MMC not working, cannot update, 4 blank icons in control panel
    By dshakra in forum BSOD, Crashes, Kernel Debugging
    Replies: 49
    Last Post: 07-18-2013, 04:07 PM
  2. HP DV6324us Blank Screen
    By Syracuseball in forum Hardware
    Replies: 6
    Last Post: 03-18-2013, 08:38 AM

Log in

Log in