Jump to content


 


Register a free account to unlock additional features at BleepingComputer.com
Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.


Click here to Register a free account now! or read our Welcome Guide to learn how to use this site.

Photo

Blue screen of death, is it a virus?


  • Please log in to reply
10 replies to this topic

#1 vorsybl

vorsybl

  • Members
  • 34 posts
  • OFFLINE
  •  
  • Local time:11:22 PM

Posted 28 May 2012 - 05:48 AM

I've had my computer for about a year now. I assembled the parts myself. It is quite fast. I bought it to play the latest games at high graphics.

For some reason the computer started operating very slowly, it would take literally 10 minutes for windows to load, then another 5 minutes to log into a user account. I use windows 7 home edition. I decided that it had been a year and it would be for the greater good to reinstall windows with a fresh start, reformat the harddrive. Now though when I try and install a game mid way the blue screen of death comes in crashing the entire computer forcing me to hard reboot. I've run AVG scan, tds killer scan, and no threats are found. Including malware bytes. What could be the problem? Thanks for any help

Edited by hamluis, 29 May 2012 - 04:19 PM.
Moved from Am I Infected to Win 7 - Hamluis.


BC AdBot (Login to Remove)

 


#2 AustrAlien

AustrAlien

    Inquisitor


  • BC Advisor
  • 6,772 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Cowra NSW Australia
  • Local time:02:22 PM

Posted 28 May 2012 - 07:09 AM

It seems very unlikely that it might be a malware problem. It is much more likely to be a hard drive problem.

Let's collect some more information: I'll have a look at it and help you try to resolve the problem.

:step1: Please follow the instructions: BSOD Posting Instructions: Windows 7 - Vista

(Note: When you run BSOD_Windows7_Vista_v2.64_jcgriff2_.exe, it will also run autoruns.exe ... and both need to be in the same location!)
... with one exception in the following line:
  • "4. Zip up the entire output folder + PERFMON and attach the zip file to your next post."
The BC forums will allow a total attachment size of only 512 kb (and what you need to attach will exceed this limit). Please upload the zip file to a file sharing website of your choice and and post a link to it in this thread so that we can access your uploaded zip file. I will have a look at the contained information and see if I can shed some light on your BSOD issue.

See the suggestions in the following links for recommendations on file sharing websites:
  • http://lifehacker.com/388284/best-online-file-sharing-services
  • http://www.hongkiat.com/blog/15-great-free-online-file-sharing-alternatives/
  • http://www.smashingapps.com/2008/08/28/5-best-free-file-hosting-services-to-store-your-files.html

:step2: Please Publish a Snapshot using Speccy, and post a link to it in this thread.
  • It is a convenient and accurate way of providing us with details of your computer specifications.

:step3: Please download MiniToolBox, save it to your desktop and run it.
  • Checkmark the following checkboxes:
    • List Installed Programs
  • Click Go.
    When the scan is finished, a text file will open in a Notepad window.
  • Copy the entire contents of the Notepad window, and paste in your reply.
    (Result.txt will be saved in the same directory the tool is run.)
====================================
When you have completed the above, test the hard drive. It is best to use the hard drive manufacturer's own diagnostic utility, but Seagate's tool will work OK on most brands. The diagnostic tool is run from a bootable CD (Windows does not need to be working. The first two steps are done on a working computer, while the third step is to boot the ailing computer with the CD that you create in the first two steps.)

:step1: Please download SeaTools for DOS (CD) from Seagate's SeaTools for DOS web page

or use the following direct download link to download the latest version of SeaTools for DOS:
Download SeaTools for DOS ISO Image

The downloaded file name is SeaToolsDOS223ALL.ISO
[/list]
:step2: Burn the downloaded .ISO image to a CD using the appropriate burning software.
  • If you do not already have a suitable burning program for writing .ISO images to disc ...
    • Download and install ImgBurn.
      Ensure that you UN-check the box agreeing to install the Ask toolbar during the installation.
    • Place a new (blank) CD disc in the drive tray.
    • Choose Write image file to disc.
    • Under Source, click on the Browse button: Navigate to and select the .ISO file that you wish to burn.
    • Place a check-mark in the box beside Verify.
  • Click Posted Image

    When the CD has been burned and verified as successful, it will be bootable.

:step3: Boot from the CD.
  • (You may need to access the BIOS Setup Menu or the Boot Menu and change the boot order to enable booting from CD before hard drive.)
  • From Basic tests on the Main Menu, run the Short test and then the Long test.

    (The long test will take some considerable time to complete.)
    The results will be shown as either a PASS or FAIL.
    There is a chance that during the Long test, you may be offered the opportunity to attempt repairs on the hard drive:
  • If so, go ahead and attempt to do so, but ONLY after backing up all important personal files.
[/list]Note: You may wish to view the following ...
Please let us know the results of the tests.

When you can, include the make and model number of the problematic hard drive. If you do choose to use SeaTools, you will see the model number (and maybe the make) when SeaTools first detects the hard drive.

Edited by AustrAlien, 28 May 2012 - 07:11 AM.

AustrAlien
Google is my friend. Make Google your friend too.

Posted Image

#3 vorsybl

vorsybl
  • Topic Starter

  • Members
  • 34 posts
  • OFFLINE
  •  
  • Local time:11:22 PM

Posted 28 May 2012 - 11:50 AM

Hey man thanks for being willing to help. It might take me some time to complete all the steps but I'll start now. In the case that we can't fix it, worst case scenario, I would need to buy a new HDD?



This is the link to the computer system health information: http://www.mediafire.com/?3lu5oca1wb6m1b5

As far as the other steps, maybe you can take a look at this information first because those steps require the purchase of blank cds are more complicated. Thanks again. Oh yeah and HDD is the western digital WD10EARS 1TB drive

Speccy screenshot: http://speccy.piriform.com/results/Yxls2yMDdeLbxyDGZI2lRHF

Edited by vorsybl, 28 May 2012 - 06:09 PM.


#4 AustrAlien

AustrAlien

    Inquisitor


  • BC Advisor
  • 6,772 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Cowra NSW Australia
  • Local time:02:22 PM

Posted 28 May 2012 - 10:44 PM

9 minidumps are available. One crash occurred when running aswMBR, and is attributed to that.
The remaining 8 crashes were all:
KERNEL_DATA_INPAGE_ERROR (7a)
DISK_HARDWARE_ERROR: There was error with disk hardware
the disk subsystem has experienced a failure

7 of those 8 crashes reported:
ERROR_CODE: (NTSTATUS) 0xc000000e - A device which does not exist was specified.

while the eighth reported:
ERROR_CODE: (NTSTATUS) 0xc0000185 - The I/O device reported an I/O error.

Looking at the SYSTEM event log provides the clue as to where the problem lies, as the following entry is logged over and over again:

Log Name: System
Source: atapi
Event ID: 11
Task: N/A
Level: Error
Opcode: N/A
Keyword: Classic
User: N/A
User Name: N/A
Computer: vorsybl-PC
Description:
The driver detected a controller error on \Device\Ide\IdePort2.


What devices do you have connected to IDE ports?
From the Speccy report:
Optiarc DVD RW AD-7261S ATA Device
Any other? (maybe an old CD-ROM device that no longer works ???)

Firstly, remove any media (disk) that you may have in the optical drive (Speccy shows something present in the optical drive).
  • Test the system.

The problem could lie with with the media in the optical drive, the device itself, or with the cable(s) and/or connection(s).
  • Check the connections of the cables (both ends of the data cable).
  • Be very suspicious if the power connection is less than a good, tight, firm fit.
  • You may need to replace a data cable, or the device.
In order to prove/disprove the diagnosis, disconnect all IDE-connected devices and test the system.

Lastly, the good news: I don't think the problem lies with the 1TB HDD on which you have the Windows system installed.

========================
BSOD BUGCHECK SUMMARY
................................................................
Loading Dump File [C:\CactusIsland\vorsybl_BC\Windows7_Vista_jcgriff2\052812-37580-01.dmp]
Built by: 7601.17803.amd64fre.win7sp1_gdr.120330-1504
Debug session time: Mon May 28 18:35:09.278 2012 (UTC + 10:00)
System Uptime: 0 days 4:17:31.121
Probably caused by : memory_corruption
KERNEL_DATA_INPAGE_ERROR (7a)
The requested page of kernel data could not be read in. Typically caused by
a bad block in the paging file or disk controller error. Also see
KERNEL_STACK_INPAGE_ERROR.
If the error status is 0xC000000E, 0xC000009C, 0xC000009D or 0xC0000185,
it means the disk subsystem has experienced a failure.
Arguments:
Arg1: fffff6fc40009a28, lock type that was held (value 1,2,3, or PTE address)
Arg2: ffffffffc000000e, error status (normally i/o status code)
Arg3: 00000000a3aab860, current process (virtual address for lock type 3, or PTE)
Arg4: fffff88001345c08, virtual address that could not be in-paged (or PTE contents if arg1 is a PTE address)
ERROR_CODE: (NTSTATUS) 0xc000000e - A device which does not exist was specified.
DISK_HARDWARE_ERROR: There was error with disk hardware
BUGCHECK_STR: 0x7a_c000000e
DEFAULT_BUCKET_ID: CODE_CORRUPTION
PROCESS_NAME: Fallout3.exe
FAILURE_BUCKET_ID: X64_MEMORY_CORRUPTION_LARGE_4096
Bugcheck code 0000007A
Arguments fffff6fc`40009a28 ffffffff`c000000e 00000000`a3aab860 fffff880`01345c08
BiosVersion = BLH6710H.86A.0076.2010.1115.1959
BiosReleaseDate = 11/15/2010
BaseBoardManufacturer = Intel Corporation
BaseBoardProduct = DH67CL
BaseBoardVersion = AAG10212-205
CPUID: "Intel® Core™ i7-2600K CPU @ 3.40GHz"
MaxSpeed: 3400
CurrentSpeed: 3392
................................................................
Loading Dump File [C:\CactusIsland\vorsybl_BC\Windows7_Vista_jcgriff2\052812-25443-01.dmp]
Built by: 7601.17803.amd64fre.win7sp1_gdr.120330-1504
Debug session time: Tue May 29 00:39:11.894 2012 (UTC + 10:00)
System Uptime: 0 days 3:00:10.737
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+3717a )
KERNEL_DATA_INPAGE_ERROR (7a)
ERROR_CODE: (NTSTATUS) 0xc0000185 - The I/O device reported an I/O error.
DISK_HARDWARE_ERROR: There was error with disk hardware
BUGCHECK_STR: 0x7a_c0000185
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
PROCESS_NAME: rundll32.exe
FAILURE_BUCKET_ID: X64_0x7a_c0000185_nt!_??_::FNODOBFM::_string_+3717a
Bugcheck code 0000007A
Arguments fffff6fc`5002ed58 ffffffff`c0000185 00000000`bf023820 fffff8a0`05dabba4
................................................................
Loading Dump File [C:\CactusIsland\vorsybl_BC\Windows7_Vista_jcgriff2\052812-24897-01.dmp]
Built by: 7601.17803.amd64fre.win7sp1_gdr.120330-1504
Debug session time: Mon May 28 19:30:57.644 2012 (UTC + 10:00)
System Uptime: 0 days 0:36:33.487
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+3717a )
KERNEL_DATA_INPAGE_ERROR (7a)
ERROR_CODE: (NTSTATUS) 0xc0000185 - The I/O device reported an I/O error.
DISK_HARDWARE_ERROR: There was error with disk hardware
BUGCHECK_STR: 0x7a_c0000185
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
PROCESS_NAME: wmpnetwk.exe
FAILURE_BUCKET_ID: X64_0x7a_c0000185_nt!_??_::FNODOBFM::_string_+3717a
Bugcheck code 0000007A
Arguments fffff6fc`5001ae90 ffffffff`c0000185 00000001`162fe880 fffff8a0`035d2850
................................................................
Loading Dump File [C:\CactusIsland\vorsybl_BC\Windows7_Vista_jcgriff2\052812-23509-01.dmp]
Built by: 7601.17803.amd64fre.win7sp1_gdr.120330-1504
Debug session time: Mon May 28 21:18:42.445 2012 (UTC + 10:00)
System Uptime: 0 days 0:45:14.304
Unable to load image \??\C:\Users\vorsybl\AppData\Local\Temp\aswMBR.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for aswMBR.sys
*** ERROR: Module load completed but symbols could not be loaded for aswMBR.sys
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : aswMBR.sys ( aswMBR+6beb )
IRQL_NOT_LESS_OR_EQUAL (a)
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0xA
PROCESS_NAME: System
FAILURE_BUCKET_ID: X64_0xA_aswMBR+6beb
Bugcheck code 0000000A
Arguments 00000000`00000000 00000000`00000002 00000000`00000000 fffff800`02ee9925
................................................................
Loading Dump File [C:\CactusIsland\vorsybl_BC\Windows7_Vista_jcgriff2\052812-23181-01.dmp]
Built by: 7601.17803.amd64fre.win7sp1_gdr.120330-1504
Debug session time: Mon May 28 20:28:24.248 2012 (UTC + 10:00)
System Uptime: 0 days 0:56:33.091
Unable to load image \SystemRoot\system32\drivers\peauth.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for peauth.sys
*** ERROR: Module load completed but symbols could not be loaded for peauth.sys
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : peauth.sys ( peauth+1776 )
KERNEL_DATA_INPAGE_ERROR (7a)
ERROR_CODE: (NTSTATUS) 0xc000000e - A device which does not exist was specified.
DISK_HARDWARE_ERROR: There was error with disk hardware
BUGCHECK_STR: 0x7a_c000000e
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
PROCESS_NAME: audiodg.exe
FAILURE_BUCKET_ID: X64_0x7a_c000000e_peauth+1776
Bugcheck code 0000007A
Arguments fffff6fc`4002cd60 ffffffff`c000000e 00000000`2e143880 fffff880`059ac000
................................................................
Loading Dump File [C:\CactusIsland\vorsybl_BC\Windows7_Vista_jcgriff2\052712-38875-01.dmp]
Built by: 7601.17803.amd64fre.win7sp1_gdr.120330-1504
Debug session time: Mon May 28 02:18:59.758 2012 (UTC + 10:00)
System Uptime: 0 days 4:32:47.601
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
GetPointerFromAddress: unable to read from fffff800030ae278
Probably caused by : memory_corruption
KERNEL_DATA_INPAGE_ERROR (7a)
ERROR_CODE: (NTSTATUS) 0xc000000e - A device which does not exist was specified.
DISK_HARDWARE_ERROR: There was error with disk hardware
BUGCHECK_STR: 0x7a_c000000e
DEFAULT_BUCKET_ID: CODE_CORRUPTION
PROCESS_NAME: System
FAILURE_BUCKET_ID: X64_MEMORY_CORRUPTION_LARGE_4096
Bugcheck code 0000007A
Arguments fffff6fc`40009788 ffffffff`c000000e 00000000`238b5860 fffff880`012f1944
................................................................
Loading Dump File [C:\CactusIsland\vorsybl_BC\Windows7_Vista_jcgriff2\052712-37393-01.dmp]
Built by: 7601.17803.amd64fre.win7sp1_gdr.120330-1504
Debug session time: Sun May 27 21:41:44.559 2012 (UTC + 10:00)
System Uptime: 0 days 7:07:00.402
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+3717a )
KERNEL_DATA_INPAGE_ERROR (7a)
ERROR_CODE: (NTSTATUS) 0xc000000e - A device which does not exist was specified.
DISK_HARDWARE_ERROR: There was error with disk hardware
BUGCHECK_STR: 0x7a_c000000e
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
PROCESS_NAME: System
FAILURE_BUCKET_ID: X64_0x7a_c000000e_nt!_??_::FNODOBFM::_string_+3717a
Bugcheck code 0000007A
Arguments fffff6fc`400159c0 ffffffff`c000000e 00000000`47f89be0 fffff880`02b38000
................................................................
Loading Dump File [C:\CactusIsland\vorsybl_BC\Windows7_Vista_jcgriff2\052712-34429-01.dmp]
Built by: 7601.17803.amd64fre.win7sp1_gdr.120330-1504
Debug session time: Mon May 28 03:05:03.604 2012 (UTC + 10:00)
System Uptime: 0 days 0:30:50.447
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
GetPointerFromAddress: unable to read from fffff800030fe278
Probably caused by : memory_corruption
KERNEL_DATA_INPAGE_ERROR (7a)
ERROR_CODE: (NTSTATUS) 0xc000000e - A device which does not exist was specified.
DISK_HARDWARE_ERROR: There was error with disk hardware
BUGCHECK_STR: 0x7a_c000000e
DEFAULT_BUCKET_ID: CODE_CORRUPTION
PROCESS_NAME: svchost.exe
FAILURE_BUCKET_ID: X64_MEMORY_CORRUPTION_LARGE_4096
Bugcheck code 0000007A
Arguments fffff6fc`400098b0 ffffffff`c000000e 00000000`aa23b860 fffff880`01316648
................................................................
Loading Dump File [C:\CactusIsland\vorsybl_BC\Windows7_Vista_jcgriff2\052712-30981-01.dmp]
Built by: 7601.17803.amd64fre.win7sp1_gdr.120330-1504
Debug session time: Mon May 28 10:06:24.968 2012 (UTC + 10:00)
System Uptime: 0 days 0:16:14.812
GetPointerFromAddress: unable to read from fffff800030f8278
Probably caused by : memory_corruption
KERNEL_DATA_INPAGE_ERROR (7a)
ERROR_CODE: (NTSTATUS) 0xc000000e - A device which does not exist was specified.
DISK_HARDWARE_ERROR: There was error with disk hardware
BUGCHECK_STR: 0x7a_c000000e
DEFAULT_BUCKET_ID: CODE_CORRUPTION
PROCESS_NAME: left4dead2.exe
FAILURE_BUCKET_ID: X64_MEMORY_CORRUPTION_LARGE
Bugcheck code 0000007A
Arguments fffff6fc`40009910 ffffffff`c000000e 00000000`9f05b860 fffff880`01322944
................................................................

AustrAlien
Google is my friend. Make Google your friend too.

Posted Image

#5 AustrAlien

AustrAlien

    Inquisitor


  • BC Advisor
  • 6,772 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Cowra NSW Australia
  • Local time:02:22 PM

Posted 28 May 2012 - 11:07 PM

After posting, it suddenly struck me that the optical drive may in fact be a SERIAL ATA device (considering the age of the hardware), and sure enough, googling results indicate a SATA connection rather than IDE connection on this model device.

Now, that sort of excites me .... weird eh?
I am very suspicious of the SATA data cable connections. Unless they have locking clips and are a good tight fit, the connections can be quite tenuous sometimes. I have come across this problem before. Check the connections carefully (both ends of the cable). Are they loose at all?
AustrAlien
Google is my friend. Make Google your friend too.

Posted Image

#6 vorsybl

vorsybl
  • Topic Starter

  • Members
  • 34 posts
  • OFFLINE
  •  
  • Local time:11:22 PM

Posted 29 May 2012 - 03:00 AM

Lol allen ur funny.

Yeah I was reading through your last post, and I don't have any IDE hardware, if by IDE you mean those ribbon cables. Aren't those outdated now? These parts are a year old, pretty recent if you ask me. The HDD and CD rom drive are connected by SATA cable.

Thing is, when I first got my computer a year ago, I'm not sure what the problem was but for some reason I was forced to open the computer and mess around with the sata cables connecting the drives. Since I was unfamiliar with the sata cable and used to IDE cables with my previous rig, I yanked the cable out without pressing the latch destroying the cable. This was the cable for the HDD to mother board, so, to use my computer I disconnected the one used by the DVD drive and the computer worked since the HDD was able to communicate with the rest of the computer.

Because my computer crashed while playing GTAIV a few days ago and started running ridiculously slowly, for example taking ten minutes just to pass the windows loading screen, I thought a windows reinstall would bring the hardware back to its full potential. To do so, I had to get a new sata cable to make the drive work so I could reinstall windows as there would be no other way to carry out the task.

So, according to your conclusions, it might be possible that the cables are connected improperly, and may even be in the wrong sata slots on the motherboard. What do you think? Yeah fallout 3 is in the cd drive.

Btw, thanks again for sifting through all that info and drawing conclusions from it, appreciate it as theres really no compensation inovlved other than the challenge of figuring the problem out.

But yeah, as far as I know, my computer doesn't use any IDE connections at all. It's all sata cables

Weird thing is, why is it reading as IDE when the drives use SATA cables?

Another thing I Should probably mention is that, when I was reinstalling windows, booting from CD, at first it couldn't detect the 1TB HDD, which made me nervous. I restarted several times hoping it would show up, went into BIOS only to see that the drive was not listed as it was before. I opened my computer again and, not sure why but moved the jumper thing on those three pins, I'm guessing it's the bIOS or? I'm not sure but I did that and when I restarted the drive was detected again. I really hope I haven't caused any permanent damage to my hardware lol.

Edited by vorsybl, 29 May 2012 - 03:11 AM.


#7 AustrAlien

AustrAlien

    Inquisitor


  • BC Advisor
  • 6,772 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Cowra NSW Australia
  • Local time:02:22 PM

Posted 29 May 2012 - 04:25 AM

It does make things a little difficult when incorrect terminology &/or description is provided by the tools we rely on ... since we aren't there looking at things ourselves.

I am with you now on the SATA devices in your system! Thank you for confirming.

You mentioned the SATA data cables, but you did not mention the power cables/connectors that connect to the two devices.
  • Do they also have locking clips on them and are the connections firmly in place?
    They are equally important as the data cables/connectors.
The new data cable that you bought:
  • Does it have locking clips and are the connections/connectors firmly in place?
We might have to do this the hard way, by a process of elimination. Try this:
  • Disconnect the optical drive and test the system?
  • Does it still crash, and do "The driver detected a controller error on \Device\Ide\IdePort2." entries still appear in the System event log?
Note: The reason that I focus on the optical drive, is that if it were the hard drive (with Windows on it) creating those errors, the system would crash very promptly at the first sign of trouble, and not leave a trail of logged errors in the event logs for us to see. At this stage, my prime suspects remain the optical drive/cables/connectors.

Edited by AustrAlien, 29 May 2012 - 04:40 AM.

AustrAlien
Google is my friend. Make Google your friend too.

Posted Image

#8 vorsybl

vorsybl
  • Topic Starter

  • Members
  • 34 posts
  • OFFLINE
  •  
  • Local time:11:22 PM

Posted 29 May 2012 - 07:10 AM

I took the media out of the cd drive, and so far the system hasn't crashed yet. I've played some battlefield just fine, and now I'm trying to download starcraft II, so far it hasn't caused any problems like before. Such a simple fix if the problem really is the cd drive. If it does crash again though I"ll open up the computer and make sure the cables are connected firmly, but the placement in the sockets should be right right? I mean, the computer wouldn't be working at all if the cables were going into the wrong ports on the motherboard?

Also one last thing, I have AVG and malware bytes installed. Are these programs sufficient in protecting my system from garbage in real time, or are there some other programs out there that I should have to keep it protected?

Thanks again

#9 AustrAlien

AustrAlien

    Inquisitor


  • BC Advisor
  • 6,772 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Cowra NSW Australia
  • Local time:02:22 PM

Posted 29 May 2012 - 02:56 PM

Such a simple fix ...

Unbelievably so! It will be very interesting to see if that really does fix the problem.

When you have used the system for a day or two, and given it a good workout, please run the jcgriff2 application again and upload the resulting info so that I can have a look at the event logs again. Likewise, if the system crashes again, upload the jcgriff2 info.

You wrote: "the placement in the sockets should be right right? I mean, the computer wouldn't be working at all if the cables were going into the wrong ports on the motherboard?"
Right! The cable connection is pretty much foolproof.

You wrote: "I have AVG and malware bytes installed. Are these programs sufficient in protecting my system from garbage in real time ..."
AVG and MBAM are as good as you will get, and just those two applications are sufficient in most cases: However, in no way do they compare with or replace the importance of user caution in preventing infection.
AustrAlien
Google is my friend. Make Google your friend too.

Posted Image

#10 vorsybl

vorsybl
  • Topic Starter

  • Members
  • 34 posts
  • OFFLINE
  •  
  • Local time:11:22 PM

Posted 29 May 2012 - 08:43 PM

Hey dude, so so far everything seems to be fine. Before when the drive was on downloading big files would cause a crash mid way, no such problems now. Starcraft has been downloading just fine with no crashes. Thing is though the dvd drive isn't on. It's connected but for some reason isn't on, like it won't open. I don't really need to use it at the moment but, in the future I may. Any ideas what the issue is with the dvd drive? Maybe it needs replacing? Otherwise, everything seems to be fine so far, thanks again for the help.

#11 AustrAlien

AustrAlien

    Inquisitor


  • BC Advisor
  • 6,772 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Cowra NSW Australia
  • Local time:02:22 PM

Posted 29 May 2012 - 10:33 PM

So far, so good.

You wrote: "the dvd drive isn't on. It's connected but for some reason isn't on, like it won't open."
It's not getting power by the sound of it. Check the connection made by the power cable with the optical drive. The power cable plug/socket connection is the weakest link in the chain, and most likely the problem. Otherwise, it may be a problem inside the optical drive itself.

Edited by AustrAlien, 29 May 2012 - 10:34 PM.

AustrAlien
Google is my friend. Make Google your friend too.

Posted Image




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users