- Thread Author
- #1
Well, I've got strange problem with my pc. When I put any cd or dvd, my pc stops responding. I cannot do anything. It worked only just after installing RC1, but when I turned pc off and later turned on, it became like this. So what can I do with this? I tried searching, but couldn't find anything. I downloaded beta from Microsoft.com
I have build 7100, 32 bit
OS Name Microsoft Windows 7 Ultimate
Version 6.1.7100 Build 7100
Other OS Description Not Available
OS Manufacturer Microsoft Corporation
System Name DOMPC
System Manufacturer Unknow
System Model Unknow
System Type X86-based PC
Processor AMD Athlon(tm) 64 X2 Dual Core Processor 5200+, 2700 Mhz, 2 Core(s), 2 Logical Processor(s)
BIOS Version/Date Phoenix Technologies, LTD 6.00 PG, 2007-12-03
Installed Physical Memory (RAM) 2,00 GB
I have build 7100, 32 bit
OS Name Microsoft Windows 7 Ultimate
Version 6.1.7100 Build 7100
Other OS Description Not Available
OS Manufacturer Microsoft Corporation
System Name DOMPC
System Manufacturer Unknow
System Model Unknow
System Type X86-based PC
Processor AMD Athlon(tm) 64 X2 Dual Core Processor 5200+, 2700 Mhz, 2 Core(s), 2 Logical Processor(s)
BIOS Version/Date Phoenix Technologies, LTD 6.00 PG, 2007-12-03
Installed Physical Memory (RAM) 2,00 GB
Does this occour also when using imagefiles in emulated drives? And does it happen with all types of media - blank cd's, DVDs, disks only containing data (no autorun etc). To emulate a drive you can use Deamon Tools. Try checking your system logfile to see if it reports any error right before it freezes.
- Thread Author
- #3
Try emulating a drive, and see if it also is a problem.. You can access the log by rightclicking on My Computer, click manage, and find "Logbook" or similair in the left side of the window. You then open "Windows-Logger" and the "System" log. That log file should hold something usefull (if there is anything usefull). To make it easier to use, you should delete the log (rightclick on it in the left side and choose remove/clear). When deleted, you can provoke the problem again, and then look in the log file... ![Smile :) :)](https://cdn.jsdelivr.net/joypixels/assets/8.0/png/unicode/64/1f642.png)
![Smile :) :)](https://cdn.jsdelivr.net/joypixels/assets/8.0/png/unicode/64/1f642.png)
- Thread Author
- #5
Similar threads
- Replies
- 4
- Views
- 2K
- Replies
- 0
- Views
- 739
- Replies
- 3
- Views
- 3K
- Question
- Replies
- 8
- Views
- 3K