I tried posting this in BSODs and crash debugging, but I just got ignored. I became annoyed, since this is a SERIOUS problem that's been persisting for more than a month. I've provided as many possible details about the machine as I can, and I've listed all of my tests and diagnostics. Please read the whole post.
Specs:
Mobo: Asus M4A89TD Pro USB3
RAM: G. Skill Ripjaws x2 2GB
CPU: AMD Phenom II Black x4
PSU: Corsair HX 650W
HDD: Western Digital Caviar Blue 500gb SATA 6.0 x2
GPU: Sapphire Radeon ATI HD 5770 PCIe
Case: Cooler Master CM690II Advanced
I've built two computers in the recent past, one for myself and one for my boyfriend. I've noticed that when shutting down my boyfriend's machine, and powering it back on, Windows will crash to a BSOD or get stuck on a black screen. The suspicious thing is, this will ONLY happen when shutting down and powering back on. If the system is simply restarted, Windows will start up every single time without a crash. Restarts don't cause problems, only powering on.
Strangely, his computer will not record the BSODs that occur when they happen at the startup logo. This means that I cannot post the analyzed BSODs here with BlueScreenView or any other program, so PLEASE DON'T ASK ME TO. They do not show up on any BSOD reader. The crashes DO NOT appear in the minidump folder. Please DO NOT ask me to supply the minidump folder.
I have run a Memtest on each individual stick, each with 6 passes with zero errors.
I wrote down the most recent errors that popped up when his computer crashed on starting up, since I can't look at his blue screens otherwise. The first said SYSTEM_SERVICE_EXCEPTION, BCC was 3B.
The second crash didn't give an error name/message, it just gave a STOP error ending in 7F and the related file was ahcix64.sys, which I have seen multiple times on various BSODs on his system, as well as my own.
Another recent one was DRIVER_IRQL_NOT_LESS_OR_EQUAL with Stop error D1.
ntoskrnl is also a file I see frequently during BSODs.
Each time the system is reset after powering it on, it gets farther and farther in the startup process until eventually it will give in and start up without a crash. Once Windows is up, it is, strangely, stable. Games will run perfectly without errors. Programs will function normally. Performance is exceptional, and the computer is very fast. It will run perfectly for weeks without a single crash, hangup, or problem.
I have not done a startup repair yet. The main reason for that is, his hard drives are set up in RAID 0. I'm afraid that it may damage the array somehow. If I get reassurance that it won't, I might try to fix it.
All of his drivers are up to date. All of his programs are up to date. His Directx is fully functioning with no errors. His Windows 7 is fully updated. Everything else seems to be A-Okay, except for the startup problem.
I also scanned his PC for viruses and he doesn't have a single one.
This problem was happening long before I had installed anti-virus software on his machine. Anti-virus software is not the culprit.
I've also cleared his CMOS.
I've already done a SFC Scan and no corrupt files were found. I can't run a chkdsk because he has RAID 0.
I have cleared all of his temporary files.
I have defragmented his disks.
Knowing I've taken all of these measures... please don't ask me to repeat them. I've done everything I can. I've downloaded every tool I could to help. I have no answers.
A most recent development has me thinking it could be a hardware problem. When touching the front/top USB ports on the case, the display crashes to a black screen. The rear USB ports don't cause this to happen, only the top/front ones. The USB ports are directly next to the power and reset switches.
I can provide System Info and Event Logs as needed, if some of you want to actually help, or even can help if your knowledge is applicable.
I know this is a lot of information, but people on forums like these tend to get annoyed when not enough information is given. Ironically, when posting long messages like these, I rarely get a response despite how detailed and informative they are. I realize not being able to use BlueScreenView or WhoCrashed to solve a problem makes it harder to troubleshoot, but I know it's not impossible. If you CAN help, I beseech your guidance.
Specs:
Mobo: Asus M4A89TD Pro USB3
RAM: G. Skill Ripjaws x2 2GB
CPU: AMD Phenom II Black x4
PSU: Corsair HX 650W
HDD: Western Digital Caviar Blue 500gb SATA 6.0 x2
GPU: Sapphire Radeon ATI HD 5770 PCIe
Case: Cooler Master CM690II Advanced
I've built two computers in the recent past, one for myself and one for my boyfriend. I've noticed that when shutting down my boyfriend's machine, and powering it back on, Windows will crash to a BSOD or get stuck on a black screen. The suspicious thing is, this will ONLY happen when shutting down and powering back on. If the system is simply restarted, Windows will start up every single time without a crash. Restarts don't cause problems, only powering on.
Strangely, his computer will not record the BSODs that occur when they happen at the startup logo. This means that I cannot post the analyzed BSODs here with BlueScreenView or any other program, so PLEASE DON'T ASK ME TO. They do not show up on any BSOD reader. The crashes DO NOT appear in the minidump folder. Please DO NOT ask me to supply the minidump folder.
I have run a Memtest on each individual stick, each with 6 passes with zero errors.
I wrote down the most recent errors that popped up when his computer crashed on starting up, since I can't look at his blue screens otherwise. The first said SYSTEM_SERVICE_EXCEPTION, BCC was 3B.
The second crash didn't give an error name/message, it just gave a STOP error ending in 7F and the related file was ahcix64.sys, which I have seen multiple times on various BSODs on his system, as well as my own.
Another recent one was DRIVER_IRQL_NOT_LESS_OR_EQUAL with Stop error D1.
ntoskrnl is also a file I see frequently during BSODs.
Each time the system is reset after powering it on, it gets farther and farther in the startup process until eventually it will give in and start up without a crash. Once Windows is up, it is, strangely, stable. Games will run perfectly without errors. Programs will function normally. Performance is exceptional, and the computer is very fast. It will run perfectly for weeks without a single crash, hangup, or problem.
I have not done a startup repair yet. The main reason for that is, his hard drives are set up in RAID 0. I'm afraid that it may damage the array somehow. If I get reassurance that it won't, I might try to fix it.
All of his drivers are up to date. All of his programs are up to date. His Directx is fully functioning with no errors. His Windows 7 is fully updated. Everything else seems to be A-Okay, except for the startup problem.
I also scanned his PC for viruses and he doesn't have a single one.
This problem was happening long before I had installed anti-virus software on his machine. Anti-virus software is not the culprit.
I've also cleared his CMOS.
I've already done a SFC Scan and no corrupt files were found. I can't run a chkdsk because he has RAID 0.
I have cleared all of his temporary files.
I have defragmented his disks.
Knowing I've taken all of these measures... please don't ask me to repeat them. I've done everything I can. I've downloaded every tool I could to help. I have no answers.
A most recent development has me thinking it could be a hardware problem. When touching the front/top USB ports on the case, the display crashes to a black screen. The rear USB ports don't cause this to happen, only the top/front ones. The USB ports are directly next to the power and reset switches.
I can provide System Info and Event Logs as needed, if some of you want to actually help, or even can help if your knowledge is applicable.
I know this is a lot of information, but people on forums like these tend to get annoyed when not enough information is given. Ironically, when posting long messages like these, I rarely get a response despite how detailed and informative they are. I realize not being able to use BlueScreenView or WhoCrashed to solve a problem makes it harder to troubleshoot, but I know it's not impossible. If you CAN help, I beseech your guidance.
First check to see if logging is enabled in usercp
To ensure minidumps are enabled:
Go to Start, in the Search Box type: sysdm.cpl, press Enter.
Under the Advanced tab, click on the Startup and Recovery Settings... button.
Ensure that Automatically restart is unchecked.
Under the Write Debugging Information header select Small memory dump (256 kB) in the dropdown box (the 256kb varies).
Ensure that the Small Dump Directory is listed as %systemroot%\Minidump.
OK your way out.
Reboot if changes have been made.
Second the file (ahcix64.sys) is his RAID controller driver. It should be updated as a first step.
How To Find Drivers: - - The most common drivers are listed on this page: Driver Reference http://www.carrona.org/dvrref.html
- - Driver manufacturer links are on this page: http://www.carrona.org/drvrdown.html
If it is generating BucChecks' you can force a log but update the driver first.
To ensure minidumps are enabled:
Go to Start, in the Search Box type: sysdm.cpl, press Enter.
Under the Advanced tab, click on the Startup and Recovery Settings... button.
Ensure that Automatically restart is unchecked.
Under the Write Debugging Information header select Small memory dump (256 kB) in the dropdown box (the 256kb varies).
Ensure that the Small Dump Directory is listed as %systemroot%\Minidump.
OK your way out.
Reboot if changes have been made.
Second the file (ahcix64.sys) is his RAID controller driver. It should be updated as a first step.
How To Find Drivers:
Quote:
- search Google for the name of the driver
- compare the Google results with what's installed on your system to figure out which device/program it belongs to
- visit the web site of the manufacturer of the hardware/program to get the latest drivers (DON'T use Windows Update or the Update driver function of Device Manager).
- if there are difficulties in locating them, post back with questions and someone will try and help you locate the appropriate program.
- compare the Google results with what's installed on your system to figure out which device/program it belongs to
- visit the web site of the manufacturer of the hardware/program to get the latest drivers (DON'T use Windows Update or the Update driver function of Device Manager).
- if there are difficulties in locating them, post back with questions and someone will try and help you locate the appropriate program.
- - Driver manufacturer links are on this page: http://www.carrona.org/drvrdown.html
If it is generating BucChecks' you can force a log but update the driver first.
Also as far as the front ports shorting out, if the case is a Cooler Master it is a common problem caused by static electricity. According to reports, CM is not real responsive, but will replace the front pannel if still in warranty, if "they have the parts in stock".
�� Quote: Originally Posted by zigzag3143 
First check to see if logging is enabled in usercp
To ensure minidumps are enabled:
Go to Start, in the Search Box type: sysdm.cpl, press Enter.
Under the Advanced tab, click on the Startup and Recovery Settings... button.
Ensure that Automatically restart is unchecked.
Under the Write Debugging Information header select Small memory dump (256 kB) in the dropdown box (the 256kb varies).
Ensure that the Small Dump Directory is listed as %systemroot%\Minidump.
OK your way out.
Reboot if changes have been made.
Quote:
Second the file (ahcix64.sys) is his RAID controller driver. It should be updated as a first step.
Quote:
How To Find Drivers:
Quote:
- search Google for the name of the driver
- compare the Google results with what's installed on your system to figure out which device/program it belongs to
- visit the web site of the manufacturer of the hardware/program to get the latest drivers (DON'T use Windows Update or the Update driver function of Device Manager).
- if there are difficulties in locating them, post back with questions and someone will try and help you locate the appropriate program.
- compare the Google results with what's installed on your system to figure out which device/program it belongs to
- visit the web site of the manufacturer of the hardware/program to get the latest drivers (DON'T use Windows Update or the Update driver function of Device Manager).
- if there are difficulties in locating them, post back with questions and someone will try and help you locate the appropriate program.
- - Driver manufacturer links are on this page: Drivers and Downloads
If it is generating BucChecks' you can force a log but update the driver first.
�� Quote: Originally Posted by essenbe Also as far as the front ports shorting out, if the case is a Cooler Master it is a common problem caused by static electricity. According to reports, CM is not real responsive, but will replace the front pannel if still in warranty, if "they have the parts in stock".
As far as I am aware, moving the computer will not help. Some people have claimed success in different ways. Try for a new front panel from CM first. Some have solved the problem by disconnecting the restart button. A consensus seem to think the problem is the location of front panel wires and a CD/DVD player in the first(top) bay. Some claim by moving the CD/DVD to the second bay resolves the problem. Try touching the rear panel before touching the front panel, see if that helps. The only serious issue is that if caused by static electricity, other components and motherboard could be damaged.
EDIT: I don't own one and have never had the issue. I have wanted a HAF X case so rave read numerous reviews on them and other CM cases. It seems to affect only a few people, but is a known issue for CM front panel connections. Consensus seems to be that with a CD/DVD player in the top slot, the front panel wires short out by touching it. Others have blamed it on adding a second top fan which comes in very close proximity to the front panel wires on some models.
EDIT: I don't own one and have never had the issue. I have wanted a HAF X case so rave read numerous reviews on them and other CM cases. It seems to affect only a few people, but is a known issue for CM front panel connections. Consensus seems to be that with a CD/DVD player in the top slot, the front panel wires short out by touching it. Others have blamed it on adding a second top fan which comes in very close proximity to the front panel wires on some models.
The DVD-rom is in the top slot, as well. We don't have additional top fans in the cases, only the ones included, so that shouldn't be an issue. I may have to go into his machine later and make all kinds of adjustments. There could be something seriously wrong that I'm doing or that I've done to it. I'll have to double check the wiring and such as well. I'm thinking that maybe all of these problems are linked.
This is from someone on another forum checking my event viewer:
That doesn't look good at all.
If I can't seem to understand what I might have done wrong, I may try to take some pictures of my connections and wiring to maybe get some help and advice with that in case I connected something incorrectly.
My own motherboard recently shorted out and I have to RMA it back. I'm wondering if the same thing happened to my case and board with the USB ports. My DVD drive was in the first slot as well and I had everything connected identically. I do remember on a few occasions the screen going black when plugging in a device in the top/front of the case, like headphones and USB drives.
This is from someone on another forum checking my event viewer:
Quote:
Here are some farly recent events in the Event logs:
Kernel-PnP -The driver \Driver\amdkmdap failed to load for the device PCI\VEN_1002&DEV_68B8&SUBSYS_1482174B&REV_00\4&30701afe&0&0010.
Kernel-Power - BugcheckCode 59 (converts to 3B - SYSTEM_SERVICE_EXCEPTION)
Display - Display driver amdkmdap stopped responding and has successfully recovered.
These events may indicate a problem with the display adapter driver(s), display adapter, or other hardware issue.
Are you able to swap out the present display adapter to rule out a problem with the adapter itself?
There also appears to be a problem with USB such as the following error from msinfo32:
Fault bucket X64_0x1e_0_usbohci!OHCI_CheckController+1a
This may also indicate a hardware problem, possibly a motherboard issue.
Kernel-PnP -The driver \Driver\amdkmdap failed to load for the device PCI\VEN_1002&DEV_68B8&SUBSYS_1482174B&REV_00\4&30701afe&0&0010.
Kernel-Power - BugcheckCode 59 (converts to 3B - SYSTEM_SERVICE_EXCEPTION)
Display - Display driver amdkmdap stopped responding and has successfully recovered.
These events may indicate a problem with the display adapter driver(s), display adapter, or other hardware issue.
Are you able to swap out the present display adapter to rule out a problem with the adapter itself?
There also appears to be a problem with USB such as the following error from msinfo32:
Fault bucket X64_0x1e_0_usbohci!OHCI_CheckController+1a
This may also indicate a hardware problem, possibly a motherboard issue.
If I can't seem to understand what I might have done wrong, I may try to take some pictures of my connections and wiring to maybe get some help and advice with that in case I connected something incorrectly.
My own motherboard recently shorted out and I have to RMA it back. I'm wondering if the same thing happened to my case and board with the USB ports. My DVD drive was in the first slot as well and I had everything connected identically. I do remember on a few occasions the screen going black when plugging in a device in the top/front of the case, like headphones and USB drives.
The problem reported by the other site seems to be the display adaptor. I don't know what card or display you are running. I suggest going to the site and installing the display driver directly from there. AMD or Nvidia usually have more up to date drivers than the manuf. site. The USB problem may be the front panel issue and not the MB. Before RMA try disconnecting the restart switch from the front panel and moving the CD/DVD. That's much easier than an RMA and may solve the problem. If the problem is in fact the front panel, a MB rma won't help.
All right, I'll try to find time to re-install everything today and see if I can fix the problem in the case first. If the problem persists I guess I may still have to RMA but I will still keep the changes I made to the case when I get a new Mobo.
Good Idea
Unfortunately, the changes didn't affect my motherboard, it's still completely unresponsive. My case speaker won't even make any noise. I'll still have to RMA my board, but I'll try to make the same changes to my boyfriend's machine and hopefully that will prevent his motherboard from suffering the identical fate.
Sorry to hear that. I guess you have run tests to check all of the other omponents.
I've tested all of the rest of the hardware in my own machine, if that's what you mean. All of them work fine in his machine, so I know it's the board.
Yes, that's what I meant. I've RMA'd boards before and it is quite a pain. I just didn't want you to go that route if it wasn't necessary. But, I'm sure you already know that.
Yeah, haha, I know. it is quite a pain, indeed.
Thanks for the help and concern
I'll let you know if the changes to my boyfriend's machine helps his problems with it and if I find out anything else.
Thanks for the help and concern
I'll let you know if the changes to my boyfriend's machine helps his problems with it and if I find out anything else.
I found the RAID/AHCI drivers. I have a question.
Do I need to install both? Or just AHCI? I don't want to break the computer even more by having a driver I'm not supposed to have. When checking his device manager, I see that he definitely has an out-of-date AHCI/RAID driver from Microsoft.
I don't know why it says it's from Microsoft. I installed a RAID driver on his computer from Asus when I first built these. I think that after I updated the BIOS, his RAID driver got switched to the Microsoft version. WTF?
So, I figured before I did anything, I'd ask if I needed to install both AHCI and RAID, because I guess they're separate. Or maybe they aren't and I'm an idiot.
If you need more information, here is the downloads section of our motherboards which contains the ACHI/RAID drivers underneath "Utilities."
Windows 7 is 64-bit.
http://support.asus.com/Download.asp...fUSB3&p=1&s=24
I'm thinking this may be a major cause for why his computer is having trouble booting. The RAID driver is apparently a Windows-issued one. On top of that, the Windows-issued driver is apparently SCSI and not AHCI, like it's supposed to say. That's what it used to say before I flashed the BIOS. Now that I think about it, these crashes on startup began happening after updating his BIOS, so these might be connected. While updating the BIOS caused many other crashes to stop, it caused this new one to begin.
Also, what is the safest way of updating these drivers so I don't cause damage to the array?
Do I need to install both? Or just AHCI? I don't want to break the computer even more by having a driver I'm not supposed to have. When checking his device manager, I see that he definitely has an out-of-date AHCI/RAID driver from Microsoft.
I don't know why it says it's from Microsoft. I installed a RAID driver on his computer from Asus when I first built these. I think that after I updated the BIOS, his RAID driver got switched to the Microsoft version. WTF?
So, I figured before I did anything, I'd ask if I needed to install both AHCI and RAID, because I guess they're separate. Or maybe they aren't and I'm an idiot.
If you need more information, here is the downloads section of our motherboards which contains the ACHI/RAID drivers underneath "Utilities."
Windows 7 is 64-bit.
http://support.asus.com/Download.asp...fUSB3&p=1&s=24
I'm thinking this may be a major cause for why his computer is having trouble booting. The RAID driver is apparently a Windows-issued one. On top of that, the Windows-issued driver is apparently SCSI and not AHCI, like it's supposed to say. That's what it used to say before I flashed the BIOS. Now that I think about it, these crashes on startup began happening after updating his BIOS, so these might be connected. While updating the BIOS caused many other crashes to stop, it caused this new one to begin.
Also, what is the safest way of updating these drivers so I don't cause damage to the array?
So I was going to update his RAID drivers because it looks like his system is using that Microsoft one instead of the Asus one, but whenever I try to get it to update with the Asus RAID driver I downloaded, the update screen gets pissy at me and says, basically, "cut it out, that driver is already updated," even though the file I'm trying to give it is completely different.
When looking at the "volumes" tab under the driver information, it's all blank.
Apparently the RAID is using two driver files I've never heard of involved in a RAID. disk.sys and partmgr.sys.
I realize the drivers for Asus are from last year. But I don't think I care how recent the Microsoft one is. I have a bad feeling that the computer is trying to run the wrong driver or even two at the same time for the RAID. Since it won't allow me to update the ahcix64s.sys file, which is the old version from April off of the Asus disk, I can't even determine if the update can fix the problem.
When looking at the "volumes" tab under the driver information, it's all blank.
Apparently the RAID is using two driver files I've never heard of involved in a RAID. disk.sys and partmgr.sys.
I realize the drivers for Asus are from last year. But I don't think I care how recent the Microsoft one is. I have a bad feeling that the computer is trying to run the wrong driver or even two at the same time for the RAID. Since it won't allow me to update the ahcix64s.sys file, which is the old version from April off of the Asus disk, I can't even determine if the update can fix the problem.
Someone else is going to have to help on that. I've never used raid. But bios has to be set as raid and on some AMD systems under raid you have to select either IDE or ahci mode. I really can't tell you whether the Microsoft raid driver is as good or better than the AMD raid driver.
BIOS is in RAID for the drives.
Hello
I do not have a lot of time this evening but if you reply to this post I will receive an email to remind me to look at it again tomorrow.
I have read through the posts but it has been a quick read so bear with me if I cover ground that is already covered
You mentioned early on in the post problem may be caused by the front USB ports, I recommend disconnecting these ports for the time being to take them out of the equation.
It is also a good time to check that the front USB is connected to the right header marked in yellow and not the wrong one marked in red which may cause the MB to be damaged.
Attachment 165230
Secondly I recommend backing up your RAID drive. Windows backup should be sufficient to make an image on a USB drive, this will take away the worry of damaging your install when we try to repair the problem.
Reference the RAID If windows has installed its own driver you should have the option to roll back to the last driver.
Attachment 165231
You will find the newest RAID driver here; ASUSTeK Computer Inc. -Support- Drivers and Download M4A89TD PRO/USB3
You only need the RAID driver having the AHCI driver installed as well should not cause a problem.
If you need to install the new driver try uninstalling the old RAID driver. You should get the option to delete the old driver whilst uninstalling it. Be aware that you may need to new start the PC if you cannot install the new driver before the restart you may have to use start up repair to start the PC and you will need the new driver handy in a location where you can find it to enable you to install it as a part of the start up repair!!! I recommend here that you try the roll back feature first and only attempt to uninstall the old driver after you have made a backup image
I hope this helps for the moment
PS posting a snip of you MB and connections is a good idea and may well help diagnosing the problem
I do not have a lot of time this evening but if you reply to this post I will receive an email to remind me to look at it again tomorrow.
I have read through the posts but it has been a quick read so bear with me if I cover ground that is already covered
You mentioned early on in the post problem may be caused by the front USB ports, I recommend disconnecting these ports for the time being to take them out of the equation.
It is also a good time to check that the front USB is connected to the right header marked in yellow and not the wrong one marked in red which may cause the MB to be damaged.
Attachment 165230
Secondly I recommend backing up your RAID drive. Windows backup should be sufficient to make an image on a USB drive, this will take away the worry of damaging your install when we try to repair the problem.
Reference the RAID If windows has installed its own driver you should have the option to roll back to the last driver.
Attachment 165231
You will find the newest RAID driver here; ASUSTeK Computer Inc. -Support- Drivers and Download M4A89TD PRO/USB3
You only need the RAID driver having the AHCI driver installed as well should not cause a problem.
If you need to install the new driver try uninstalling the old RAID driver. You should get the option to delete the old driver whilst uninstalling it. Be aware that you may need to new start the PC if you cannot install the new driver before the restart you may have to use start up repair to start the PC and you will need the new driver handy in a location where you can find it to enable you to install it as a part of the start up repair!!! I recommend here that you try the roll back feature first and only attempt to uninstall the old driver after you have made a backup image
I hope this helps for the moment
PS posting a snip of you MB and connections is a good idea and may well help diagnosing the problem
Roll Back is greyed out. I can't use that option.
The USB is plugged into the correct port in the motherboard.
How do I backup his RAID drives/create a backup image?
The USB is plugged into the correct port in the motherboard.
How do I backup his RAID drives/create a backup image?
To backup the computer you can use windows system image. Control pannel- backup computer. In the lest side click create system image. Be sure to have an external hard drive connected or plenty of DVDs.
A very highly rated free imagng program is Macrium. It is probably the most flexable and easiest.
I notice you list Western Digital drives in your specs. Western digital offers a free imaging program, a scaled down version of Acronis.
I would recommend using at least 2 imaging programs to make sure. Whichever ones you choose, make sure to burn and test their recovery disks.
EDIT: To try to update the drivers, If you have installed the raid drivers, in device manager click on update driver, choose select from a list of drivers on my computer, select let me choose, navigate to C/Windows/System32/drivers it will pick available drivers for you. you just choose which one you want.
A very highly rated free imagng program is Macrium. It is probably the most flexable and easiest.
I notice you list Western Digital drives in your specs. Western digital offers a free imaging program, a scaled down version of Acronis.
I would recommend using at least 2 imaging programs to make sure. Whichever ones you choose, make sure to burn and test their recovery disks.
EDIT: To try to update the drivers, If you have installed the raid drivers, in device manager click on update driver, choose select from a list of drivers on my computer, select let me choose, navigate to C/Windows/System32/drivers it will pick available drivers for you. you just choose which one you want.
Is ahcix64s the file to choose for the driver? Or would the RAID driver be named anything else that I don't know of?
I'll have to let pooch answer that. But, I think that is the AMD ahci driver, which may also be the raid driver but I don't know.
Click on the link I gave you and navigate to the yellow arrow.
Attachment 165300
When you have downloaded the driver unpack it and navigate through the folders; RAID, JM361, Install, Driver, amd64. Inside this last folder are the drivers you are looking for
Attachment 165301
Do as Essenbe suggested only navigate here instead
Attachment 165300
When you have downloaded the driver unpack it and navigate through the folders; RAID, JM361, Install, Driver, amd64. Inside this last folder are the drivers you are looking for
Attachment 165301
Do as Essenbe suggested only navigate here instead
Did you disconnect the front USB as I suggested to see if the blue screens stiil happen?
I would recommend updating all your MB drivers http://support.asus.com/download.asp...IjRELzxMxkH2UQ, Also your Graphic card drivers link here; AMD Catalyst 11.6 Win 7 | Vista 64-bit download from Guru3D.com
Which BIOS do you have installed? The latest is version 2001 and looking at the list there have 3 fixes for system stability.
Which SATA ports are the HDD'S connected to?
To update the BIOS please refer to the MB manual if you need to you can also download a copy here; http://support.asus.com/download.asp...IjRELzxMxkH2UQ
I would recommend updating all your MB drivers http://support.asus.com/download.asp...IjRELzxMxkH2UQ, Also your Graphic card drivers link here; AMD Catalyst 11.6 Win 7 | Vista 64-bit download from Guru3D.com
Which BIOS do you have installed? The latest is version 2001 and looking at the list there have 3 fixes for system stability.
Which SATA ports are the HDD'S connected to?
To update the BIOS please refer to the MB manual if you need to you can also download a copy here; http://support.asus.com/download.asp...IjRELzxMxkH2UQ
I didn't disconnect them yet, but I'm going to fix that today if I get a chance, I'm in the middle of moving into a new apartment so neither he nor I have much time on our hands this weekend, but in between all of the business I'm trying to fix his computer.
His BIOS is updated.
His graphics driver is the most current.
HDDs are in 1 and 2 and it IS set to RAID. Optical drive is in port 6 and set to IDE. The strange thing is, in his BIOS, ports 1-4 are not shown. It only shows 5-6.
I had already downloaded the new RAID driver from Asus and was attempting to update with it, but I guess I was trying to update it with the wrong folder or something. I'll try it out on his computer when I get a chance.
NOTE: It says the RAID driver is incompatible with the device when I try to update with the file you specified. It's telling me to make sure it's for 64-bit Windows.
I checked his controller configuration in the ROM utility, and it says Controller IRQ: 10, AHCI HBA MMIO Base Address FE5FE000, in case that's useful information.
Should I instead be trying RAID>AMD>DRIVER>DISK>RAID>WIN7>X64 ? I've never heard of the JMicron RAID driver before in my life, and I don't know the first thing about using it.
His BIOS is updated.
His graphics driver is the most current.
HDDs are in 1 and 2 and it IS set to RAID. Optical drive is in port 6 and set to IDE. The strange thing is, in his BIOS, ports 1-4 are not shown. It only shows 5-6.
I had already downloaded the new RAID driver from Asus and was attempting to update with it, but I guess I was trying to update it with the wrong folder or something. I'll try it out on his computer when I get a chance.
NOTE: It says the RAID driver is incompatible with the device when I try to update with the file you specified. It's telling me to make sure it's for 64-bit Windows.
I checked his controller configuration in the ROM utility, and it says Controller IRQ: 10, AHCI HBA MMIO Base Address FE5FE000, in case that's useful information.
Should I instead be trying RAID>AMD>DRIVER>DISK>RAID>WIN7>X64 ? I've never heard of the JMicron RAID driver before in my life, and I don't know the first thing about using it.
Another question, how do I update the chipset drivers?
�� Quote: Originally Posted by MelancholyRose I didn't disconnect them yet, but I'm going to fix that today if I get a chance, I'm in the middle of moving into a new apartment so neither he nor I have much time on our hands this weekend, but in between all of the business I'm trying to fix his computer.
�� Quote: Originally Posted by MelancholyRose �� Quote: Originally Posted by MelancholyRose HDDs are in 1 and 2 and it IS set to RAID. Optical drive is in port 6 and set to IDE. The strange thing is, in his BIOS, ports 1-4 are not shown. It only shows 5-6.
�� Quote: Originally Posted by MelancholyRose I had already downloaded the new RAID driver from Asus and was attempting to update with it, but I guess I was trying to update it with the wrong folder or something. I'll try it out on his computer when I get a chance.
NOTE: It says the RAID driver is incompatible with the device when I try to update with the file you specified. It's telling me to make sure it's for 64-bit Windows.
I checked his controller configuration in the ROM utility, and it says Controller IRQ: 10, AHCI HBA MMIO Base Address FE5FE000, in case that's useful information.
Should I instead be trying RAID>AMD>DRIVER>DISK>RAID>WIN7>X64 ? I've never heard of the JMicron RAID driver before in my life, and I don't know the first thing about using it.
NOTE: It says the RAID driver is incompatible with the device when I try to update with the file you specified. It's telling me to make sure it's for 64-bit Windows.
I checked his controller configuration in the ROM utility, and it says Controller IRQ: 10, AHCI HBA MMIO Base Address FE5FE000, in case that's useful information.
Should I instead be trying RAID>AMD>DRIVER>DISK>RAID>WIN7>X64 ? I've never heard of the JMicron RAID driver before in my life, and I don't know the first thing about using it.
�� Quote: Originally Posted by MelancholyRose Another question, how do I update the chipset drivers?
Attachment 165392
Unzip and use the Asus SetUp.exe
No matter what I do, it keeps saying the folder I specified doesn't contain a compatible software driver for my device, and says to make sure it is designed to work with x64. I picked x64... what am I doing wrong here?
I am not sure what is going wrong, but I don't think you are at fault. In the driver folder is a msi installer try right clicking on this and selecting run as administrator.
Actually I might be at fault, because I was trying to update the driver for the "disk drives" but not the "storage controller" and they are two separate and different things on my device manager.
But it does still say that the AHCI compatible RAID controller is up-to-date even though I don't think it is.
Never mind, I got it to respond and update the driver. I don't know if that worked or not to stop the BSODs, but I'll have to check soon.
When looking at the "driver version" under the details, it does in fact say it's the latest version.
But it does still say that the AHCI compatible RAID controller is up-to-date even though I don't think it is.
Never mind, I got it to respond and update the driver. I don't know if that worked or not to stop the BSODs, but I'll have to check soon.
When looking at the "driver version" under the details, it does in fact say it's the latest version.
Got my fingers crossed
I just did a power on after a shut down. Windows successfully booted without a hang or crash.
With the knowledge I received about the case having shorting issues with the optical drive being in the top slot on a Cooler Master, I moved it down a slot into the second one, from the advice of Essenbe. It worked. I'm touching the USB ports on the top now and they aren't shorting. I also blew some massive amounts of dust out of the front of the case, 'cause.... damn.
I'm thinking that the updated RAID driver and moving the optical drive combined may have helped. I won't say this is 100 percent solved just yet. I may run a few tests just to see, and I'll keep everyone informed.
As for the help I got here, thank you to everyone, and I'll rep you accordingly
Note: his PC is now incredibly bizarrely silent compared to before. Whatever I did, it must have helped in other areas, too.
With the knowledge I received about the case having shorting issues with the optical drive being in the top slot on a Cooler Master, I moved it down a slot into the second one, from the advice of Essenbe. It worked. I'm touching the USB ports on the top now and they aren't shorting. I also blew some massive amounts of dust out of the front of the case, 'cause.... damn.
I'm thinking that the updated RAID driver and moving the optical drive combined may have helped. I won't say this is 100 percent solved just yet. I may run a few tests just to see, and I'll keep everyone informed.
As for the help I got here, thank you to everyone, and I'll rep you accordingly
Note: his PC is now incredibly bizarrely silent compared to before. Whatever I did, it must have helped in other areas, too.
I am pleased that it is working and I hope that it stays that way. Damn that dust!! I think we are all afflicted, that and in my case cat hairs. lol I wish you well in your testing.
Pooch
Damn that dust!! I think we are all afflicted, that and in my case cat hairs. lol I wish you well in your testing.Pooch
Oh yeah, there is cat hair abundant. XD
Woops, I forgot to put the SATA plug back into the Optical drive lol. Guess I have to do that, now. I hope the optical drive wasn't the reason for the BSODs.
Okay, well, I plugged the optical drive back in, and I got a BSOD while Windows was starting up.
STOP 1E
fltmgr.sys
STOP 1E
fltmgr.sys
�� Quote: Originally Posted by MelancholyRose Woops, I forgot to put the SATA plug back into the Optical drive lol. Guess I have to do that, now. I hope the optical drive wasn't the reason for the BSODs.
�� Quote: Originally Posted by MelancholyRose Okay, well, I plugged the optical drive back in, and I got a BSOD while Windows was starting up.
STOP 1E
fltmgr.sys
STOP 1E
fltmgr.sys
Yup, they sure are.
Luckily, I enabled Kernel dump recently instead of small memory, and it caught the BSOD info so that I can post it here now.
==================================================
Dump File : 071611-25396-01.dmp
Crash Time : 16/07/2011 4:56:06 PM
Bug Check String : KMODE_EXCEPTION_NOT_HANDLED
Bug Check Code : 0x0000001e
Parameter 1 : ffffffff`c0000005
Parameter 2 : fffff880`0105e99b
Parameter 3 : 00000000`00000000
Parameter 4 : 00000000`05d98018
Caused By Driver : fltmgr.sys
Caused By Address : fltmgr.sys+499b
File Description :
Product Name :
Company :
File Version :
Processor : x64
Computer Name :
Full Path : C:\Windows\Minidump\071611-25396-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7601
Dump File Size : 269,848
==================================================
On Sat 16/07/2011 8:53:16 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\071611-25396-01.dmp
This was probably caused by the following module: fltmgr.sys (fltmgr+0x499B)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF8800105E99B, 0x0, 0x5D98018)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32\drivers\fltmgr.sys
product: Microsoft� Windows� Operating System
company: Microsoft Corporation
description: Microsoft Filesystem Filter Manager
Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system which cannot be identified at this time.
On Sat 16/07/2011 8:53:16 PM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: fltmgr.sys (fltmgr!FltIsCallbackDataDirty+0x20AB)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF8800105E99B, 0x0, 0x5D98018)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32\drivers\fltmgr.sys
product: Microsoft� Windows� Operating System
company: Microsoft Corporation
description: Microsoft Filesystem Filter Manager
Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system which cannot be identified at this time.
I can also provide event logs if needed.
This is what I read about the file:
FltMgr.sys is a �system� file used by Windows to help control various aspects of your hard drives & files. Its official name is the �Microsoft Filesystem Filter Manager� and its main duty in the operating system is make sure that the data written to the hard drive is correct and not corrupted. The fltmgr.sys error is caused when Windows cannot read or process files that are on the hard drive, usually because the File System Manager is damaged or unreadable. If this is the case, it can cause hard drives to stop working and the blue screen to appear.
Some places are saying that old drivers can cause this to happen, but I don't know what drivers he has that are outdated, they're all up-to-date as far as I know. Will Driver Verifier determine that?
Luckily, I enabled Kernel dump recently instead of small memory, and it caught the BSOD info so that I can post it here now.
==================================================
Dump File : 071611-25396-01.dmp
Crash Time : 16/07/2011 4:56:06 PM
Bug Check String : KMODE_EXCEPTION_NOT_HANDLED
Bug Check Code : 0x0000001e
Parameter 1 : ffffffff`c0000005
Parameter 2 : fffff880`0105e99b
Parameter 3 : 00000000`00000000
Parameter 4 : 00000000`05d98018
Caused By Driver : fltmgr.sys
Caused By Address : fltmgr.sys+499b
File Description :
Product Name :
Company :
File Version :
Processor : x64
Computer Name :
Full Path : C:\Windows\Minidump\071611-25396-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7601
Dump File Size : 269,848
==================================================
On Sat 16/07/2011 8:53:16 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\071611-25396-01.dmp
This was probably caused by the following module: fltmgr.sys (fltmgr+0x499B)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF8800105E99B, 0x0, 0x5D98018)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32\drivers\fltmgr.sys
product: Microsoft� Windows� Operating System
company: Microsoft Corporation
description: Microsoft Filesystem Filter Manager
Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system which cannot be identified at this time.
On Sat 16/07/2011 8:53:16 PM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: fltmgr.sys (fltmgr!FltIsCallbackDataDirty+0x20AB)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF8800105E99B, 0x0, 0x5D98018)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32\drivers\fltmgr.sys
product: Microsoft� Windows� Operating System
company: Microsoft Corporation
description: Microsoft Filesystem Filter Manager
Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system which cannot be identified at this time.
I can also provide event logs if needed.
This is what I read about the file:
FltMgr.sys is a �system� file used by Windows to help control various aspects of your hard drives & files. Its official name is the �Microsoft Filesystem Filter Manager� and its main duty in the operating system is make sure that the data written to the hard drive is correct and not corrupted. The fltmgr.sys error is caused when Windows cannot read or process files that are on the hard drive, usually because the File System Manager is damaged or unreadable. If this is the case, it can cause hard drives to stop working and the blue screen to appear.
Some places are saying that old drivers can cause this to happen, but I don't know what drivers he has that are outdated, they're all up-to-date as far as I know. Will Driver Verifier determine that?
I have asked for one of the BSOD experts to have a look, did you update your chipset drivers? also on that site are many other drivers for your MB it would probably help to download and install all updates that you have not yet done, as I do at least understand the bit about the BSOD maybe being caused by a driver problem.
I didn't update chipset drivers yet. I'll have to do that later, I'm about to go take care of a few things. I'll check back here later.
Hello,
Try running Memtest86 on all sticks at the same time, immediately upon powering on after a break. No need to run for too long, 5-10 minutes should be plenty for what we are testing for.
Try running Memtest86 on all sticks at the same time, immediately upon powering on after a break. No need to run for too long, 5-10 minutes should be plenty for what we are testing for.
Ran Memtest after a power on after a long break. Nothing happened. Everything was fine.
I've uploaded the dump file for this particular crash if it'll help. It's on SkyDrive here:
https://skydrive.live.com/?cid=e4de9a8be33ed49b&sc=documents&uc=1&id=E4DE9A8BE33ED49B!126#
It's inside the zipped folder.
I'm going to post some pictures of my wiring inside his case, and of the screen running the Memtest. Maybe there's something you can learn from these that I just can't see. But when looking at his wiring, all looked fine, as well as the Memtest. I'll do that when I get a chance, we're now in the new apartment we moved in to, but we don't have a router yet, so we can only use internet on one computer at a time.
Note: when I rebooted from Memtest the computer started up just fine the first time. It didn't crash the first time starting up when it rebooted. So I guess if something else is booted first before Windows, and I restart from it, Windows will start just fine.
I've uploaded the dump file for this particular crash if it'll help. It's on SkyDrive here:
https://skydrive.live.com/?cid=e4de9a8be33ed49b&sc=documents&uc=1&id=E4DE9A8BE33ED49B!126#
It's inside the zipped folder.
I'm going to post some pictures of my wiring inside his case, and of the screen running the Memtest. Maybe there's something you can learn from these that I just can't see. But when looking at his wiring, all looked fine, as well as the Memtest. I'll do that when I get a chance, we're now in the new apartment we moved in to, but we don't have a router yet, so we can only use internet on one computer at a time.
Note: when I rebooted from Memtest the computer started up just fine the first time. It didn't crash the first time starting up when it rebooted. So I guess if something else is booted first before Windows, and I restart from it, Windows will start just fine.
I just received another BSOD this morning when trying to power on again. Well, my boyfriend powered it on. It caught the dump file again and it involves the file cng.sys, stop error 3B, SYSTEM_SERVICE_EXCEPTION.
On Fri 22/07/2011 10:06:14 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\072211-23836-01.dmp
This was probably caused by the following module: cng.sys (cng+0x85AD)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF880010085AD, 0xFFFFF8800942BB60, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\drivers\cng.sys
product: Microsoft� Windows� Operating System
company: Microsoft Corporation
description: Kernel Cryptography, Next Generation
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system which cannot be identified at this time.
On Fri 22/07/2011 10:06:14 AM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: cng.sys (cng!SslImportKey+0x3A5D)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF880010085AD, 0xFFFFF8800942BB60, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\drivers\cng.sys
product: Microsoft� Windows� Operating System
company: Microsoft Corporation
description: Kernel Cryptography, Next Generation
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system which cannot be identified at this time
Here's the original dump file. I attached it in a zip.
On Fri 22/07/2011 10:06:14 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\072211-23836-01.dmp
This was probably caused by the following module: cng.sys (cng+0x85AD)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF880010085AD, 0xFFFFF8800942BB60, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\drivers\cng.sys
product: Microsoft� Windows� Operating System
company: Microsoft Corporation
description: Kernel Cryptography, Next Generation
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system which cannot be identified at this time.
On Fri 22/07/2011 10:06:14 AM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: cng.sys (cng!SslImportKey+0x3A5D)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF880010085AD, 0xFFFFF8800942BB60, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\drivers\cng.sys
product: Microsoft� Windows� Operating System
company: Microsoft Corporation
description: Kernel Cryptography, Next Generation
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system which cannot be identified at this time
Here's the original dump file. I attached it in a zip.
And I tried updating the chipset drivers but it just looks like it's trying to update graphics drivers. The graphics driver is up to date. Is there something else that the chipset driver updates besides graphics? Or do I have to uninstall graphics driver, then install chipset, then update graphics? Kind of a pain, but if that's what I have to do, I'll do it.
If you haven't yet, try running a system file checker that will check and try to repair any damaged system files. Open an elevated command prompt(start button-type cmd in search box-right click on cmd and select run as administrator) in the command window type or copy/paste sfc /scannow it will take a few minutes and will either verify the integrity of system files or give you an error log.
I've done that already. It found nothing wrong.
I tried disabling some non-Microsoft system services and powering on after shutting down and it still crashed every time. The dump files are all contained in this folder.
Since it will cleanly boot up the very first time if something else is booted before it, it makes me think there's something wrong with boot files, but the system doesn't find a single corrupted or missing file. I can't explain it.
I know that ntoskrnl pops up in a LOT of these, too.
I tried disabling some non-Microsoft system services and powering on after shutting down and it still crashed every time. The dump files are all contained in this folder.
Since it will cleanly boot up the very first time if something else is booted before it, it makes me think there's something wrong with boot files, but the system doesn't find a single corrupted or missing file. I can't explain it.
I know that ntoskrnl pops up in a LOT of these, too.
I figured I'd also upload a report of all of the drivers on the system, because, I really don't know what else to do here.
I've been through this before and understand your frustration. Jonathan helped me for quite some time, he's really good. One thing he taught me is that when the system can't find what to blame it on, it blames it on ntoskrnl. And, if the system files are not corrupted, which sfc says they are not, it is an extreme rarity that a Microsoft driver will cause a bsod.
�� Quote: Originally Posted by MelancholyRose And I tried updating the chipset drivers but it just looks like it's trying to update graphics drivers. The graphics driver is up to date. Is there something else that the chipset driver updates besides graphics? Or do I have to uninstall graphics driver, then install chipset, then update graphics? Kind of a pain, but if that's what I have to do, I'll do it.
�� Quote: Originally Posted by essenbe I've been through this before and understand your frustration. Jonathan helped me for quite some time, he's really good. One thing he taught me is that when the system can't find what to blame it on, it blames it on ntoskrnl. And, if the system files are not corrupted, which sfc says they are not, it is an extreme rarity that a Microsoft driver will cause a bsod.
What ended up being the cause when you had this problem?
Quote:
You can leave the graphics drivers installed, The chipset is something else and it just looks like it is for the graphic card, look carefully on the first ATI screen and you will notice chipset drivers is written on the top of it. AMD and ATI work very closely together
I think you should run CHKDSK on your drive I know what you wrote before and I disagree with not being able to run it on a RAID0
Have you made a backup of your RAID drive?
Have you made a backup of your RAID drive?
No, I haven't. I don't have any discs to burn the microsoft image file to. I haven't had much time to go buy any. I also don't have another drive on me right now.
I've ran Chkdsk on his machine once a long time ago. It never found anything wrong and problems continued to happen. That was before I learned I wasn't supposed to do it on a RAID, which could supposedly cause even more damage. For all I know, the reason why this is happening is because I ran that chkdsk. I just don't know.
I've ran Chkdsk on his machine once a long time ago. It never found anything wrong and problems continued to happen. That was before I learned I wasn't supposed to do it on a RAID, which could supposedly cause even more damage. For all I know, the reason why this is happening is because I ran that chkdsk. I just don't know.
�� Quote: Originally Posted by MelancholyRose No, I haven't. I don't have any discs to burn the microsoft image file to. I haven't had much time to go buy any. I also don't have another drive on me right now.
I've ran Chkdsk on his machine once a long time ago. It never found anything wrong and problems continued to happen. That was before I learned I wasn't supposed to do it on a RAID, which could supposedly cause even more damage. For all I know, the reason why this is happening is because I ran that chkdsk. I just don't know.
I've ran Chkdsk on his machine once a long time ago. It never found anything wrong and problems continued to happen. That was before I learned I wasn't supposed to do it on a RAID, which could supposedly cause even more damage. For all I know, the reason why this is happening is because I ran that chkdsk. I just don't know.
I doubt very much that running a CHKDSK is to blame for your problems, but if you ran it before and are reluctant to do it again that is OK by me.
Well if you use it all the time and have no problems, then I'm a little more comfortable. I thought people were speaking from experience, like they had corrupted their registry from using it on RAID. I'll try it out.
Further note. I updated chipset drivers. Still crashed. However, I've been noticing something. On the first power on, it'll get as far as the log in screen, but for some reason the log in screen's resolution is lowered, as if the display driver stopped. The cursor is really large like it is in safe mode. It'll reach the password screen, glitch, hang, and make a buzzing sound. The ntoskrnl BSOD followed immediately afterward. I'm going to put my graphics card into his machine and see if it works. I may also supply his a different power cord, just in case there might not be enough power getting to the card.
Further note. I updated chipset drivers. Still crashed. However, I've been noticing something. On the first power on, it'll get as far as the log in screen, but for some reason the log in screen's resolution is lowered, as if the display driver stopped. The cursor is really large like it is in safe mode. It'll reach the password screen, glitch, hang, and make a buzzing sound. The ntoskrnl BSOD followed immediately afterward. I'm going to put my graphics card into his machine and see if it works. I may also supply his a different power cord, just in case there might not be enough power getting to the card.
I tried replacing the power cord for the graphics card and there were no changes. It still crashed. I got some whole new error types, though.
On Fri 22/07/2011 8:08:41 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\072211-28204-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7FD00)
Bugcheck code: 0x50 (0xFFFFF7FFCECC6030, 0x0, 0xFFFFF80002D6BA19, 0x2)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft� Windows� Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that invalid system memory has been referenced.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.
On Fri 22/07/2011 8:08:41 PM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x50 (0xFFFFF7FFCECC6030, 0x0, 0xFFFFF80002D6BA19, 0x2)
Error: PAGE_FAULT_IN_NONPAGED_AREA
Bug check description: This indicates that invalid system memory has been referenced.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.
On Fri 22/07/2011 7:56:00 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\072211-18033-01.dmp
This was probably caused by the following module: win32k.sys (win32k+0x1D555C)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF9600028555C, 0xFFFFF88003A7C060, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\win32k.sys
product: Microsoft� Windows� Operating System
company: Microsoft Corporation
description: Multi-User Win32 Driver
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system which cannot be identified at this time.
So, I don't think his graphics card is to blame. I could try swapping my own RAM into his machine and see if it helps. I don't know if it could still be RAM despite the test coming back clean.
At this point I guess it's pointless posting BSODs, since they're completely random and they never really explain anything, because they're all different.
On Fri 22/07/2011 8:08:41 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\072211-28204-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7FD00)
Bugcheck code: 0x50 (0xFFFFF7FFCECC6030, 0x0, 0xFFFFF80002D6BA19, 0x2)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft� Windows� Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that invalid system memory has been referenced.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.
On Fri 22/07/2011 8:08:41 PM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x50 (0xFFFFF7FFCECC6030, 0x0, 0xFFFFF80002D6BA19, 0x2)
Error: PAGE_FAULT_IN_NONPAGED_AREA
Bug check description: This indicates that invalid system memory has been referenced.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.
On Fri 22/07/2011 7:56:00 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\072211-18033-01.dmp
This was probably caused by the following module: win32k.sys (win32k+0x1D555C)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF9600028555C, 0xFFFFF88003A7C060, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\win32k.sys
product: Microsoft� Windows� Operating System
company: Microsoft Corporation
description: Multi-User Win32 Driver
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system which cannot be identified at this time.
So, I don't think his graphics card is to blame. I could try swapping my own RAM into his machine and see if it helps. I don't know if it could still be RAM despite the test coming back clean.
At this point I guess it's pointless posting BSODs, since they're completely random and they never really explain anything, because they're all different.
Could it be my PSU? Is it possible that it's not giving enough juice to my CPU/Mobo?
I put my RAM into his computer and it still crashed. Only now it gave me a Memory management error.
I don't think my RAM was bad, either.
At my wit's end, here. Can't find out what's wrong, and the computer doesn't want to tell me. I'm about to just replace every single part in the goddamn thing.
I don't think my RAM was bad, either.
At my wit's end, here. Can't find out what's wrong, and the computer doesn't want to tell me. I'm about to just replace every single part in the goddamn thing.
Here's some pictures of inside the build. Maybe it'll help, I don't know.
More pics, plus one of memtest. The only reason why I took a picture of it is because I don't know if it's supposed to say DDR1. The RAM is supposed to be DDR3.
Going to run a chkdsk, I'll let you know what happens if the computer doesn't fry.
Should I do a full scan, as in automatically fix errors and check system files for bad sectors, as well? Or should I just check the disks?
Should I do a full scan, as in automatically fix errors and check system files for bad sectors, as well? Or should I just check the disks?
Well, I just used the software version inside of Windows and it said no problems were found with the disk and it's ready to use.
I have just looked at your snips and on one the 4pin power lead marked in my snip appears to be the wrong way around The white arrow is pointing to the locking catch, I am almost certain this catch should be on the right side of the socket. If you feel the right side of the socket you should feel the locking lip that runs, I believe the whole length of the socket.
Attachment 166506
It is hard for me to see it because of the cable in the way the top cable on the right side is ground and should be black.to the left of it orange (+3v) under that yellow (+12v) and to the right of that red (+5v)
Attachment 166507
If you could just check this
Attachment 166506
It is hard for me to see it because of the cable in the way the top cable on the right side is ground and should be black.to the left of it orange (+3v) under that yellow (+12v) and to the right of that red (+5v)
Attachment 166507
If you could just check this
Cancel my last I could see it clearer in another picture and it is correct
Do you have a separate power lead for each HDD? It would be better
I have read through the entire post again and would like to go back a bit would you mind disconnecting the optical drive again?
Do you have a separate power lead for each HDD? It would be better
I have read through the entire post again and would like to go back a bit would you mind disconnecting the optical drive again?
Actually I only do have one power cord for both HDDs. It's a single power lead that has two connectors on it. I could do two separate ones if that's recommended.
The next time I get a chance when his computer isn't being used (he's playing games on it right now), I'll d/c the optical drive a second time. I'm also very curious about that. I was able to fully log on and shut down without a crash while that optical wasn't connected, and I'm scratching my chin at this point. I will d/c it again, maybe tomorrow morning or afternoon when I'm alone with the machine.
The next time I get a chance when his computer isn't being used (he's playing games on it right now), I'll d/c the optical drive a second time. I'm also very curious about that. I was able to fully log on and shut down without a crash while that optical wasn't connected, and I'm scratching my chin at this point. I will d/c it again, maybe tomorrow morning or afternoon when I'm alone with the machine.
�� Quote: Originally Posted by MelancholyRose Actually I only do have one power cord for both HDDs. It's a single power lead that has two connectors on it. I could do two separate ones if that's recommended.
�� Quote: Originally Posted by MelancholyRose The next time I get a chance when his computer isn't being used (he's playing games on it right now), I'll d/c the optical drive a second time. I'm also very curious about that. I was able to fully log on and shut down without a crash while that optical wasn't connected, and I'm scratching my chin at this point. I will d/c it again, maybe tomorrow morning or afternoon when I'm alone with the machine.
it gives me more time to think as well lolWhat hardware have you changed so far? we can maybe narrow it down that way as well.
Sorry it took so long. We had an incredibly busy weekend.
So, I unplugged his optical drive a second time. I'm on his computer right now after powering it on without a single crash, and this is the second time without the optical drive plugged in that this has happened, and the only two times there was a clean boot in a very long time.
So it's the optical drive.
What does this mean about it? Is the power cord to it pinched or something? I know that it can't be SATA because I have SATA set to IDE for the optical drive, and I have the motherboard SATA plug still in the optical drive. I only removed the SATA power cable.
And what's more is that his system started up very quickly and smoothly and I'm not having a single problem while using the computer.
So, I unplugged his optical drive a second time. I'm on his computer right now after powering it on without a single crash, and this is the second time without the optical drive plugged in that this has happened, and the only two times there was a clean boot in a very long time.
So it's the optical drive.
What does this mean about it? Is the power cord to it pinched or something? I know that it can't be SATA because I have SATA set to IDE for the optical drive, and I have the motherboard SATA plug still in the optical drive. I only removed the SATA power cable.
And what's more is that his system started up very quickly and smoothly and I'm not having a single problem while using the computer.
Okay, actually what happened, was I had his system powered on and running smooth for several minutes until he began browsing certain websites. Then it crashed again. I still have his optical drive unplugged. From my own personal experience, his computer will remain totally stable when powered on after unplugging the optical drive, but this last time it crashed after about 7 or 8 minutes and using Firefox.
I still have to try using two separate power connectors for the HDDs so I'll do that in a moment.
I still have to try using two separate power connectors for the HDDs so I'll do that in a moment.
Okay, something is terribly wrong, here.
I used a separate SATA power plug for the second drive, right?
It still crashed, with the optical drive unplugged.
But it was a brand new crash. It was a Fatal System Error and it said the computer has been shut down.
Is there something wrong with the power supply?
I used a separate SATA power plug for the second drive, right?
It still crashed, with the optical drive unplugged.
But it was a brand new crash. It was a Fatal System Error and it said the computer has been shut down.
Is there something wrong with the power supply?
My PSU is available to test, so I think I may try plugging it into his machine instead to see if it works better. If it does, then I guess I need to RMA the PSU.
No dice. It's not the PSU. Mine still crashed the system, even with the optical drive unplugged and HDDs with two separate plugs.
Back at square one.
Guess I need to try a startup repair and if that doesn't help, I have to reinstall Windows. What other options do I really have? From what it looks like, none.
Back at square one.
Guess I need to try a startup repair and if that doesn't help, I have to reinstall Windows. What other options do I really have? From what it looks like, none.
Make sure the OS hard drive is listed first in bios. I really don't recall all that you have tried in 74 posts. But, Try with everything unpluged except what is absolutely necessary to run the machine. Use 1 stick of ram. If it crashes, take that stick out and try it with the other stick in. If it runs ok that way, shut down and connect 1 thing at a time and try it each time. That will help identify which component is crashing the machine. When you tried it before you said it ran good until he started using firefox. If you get it running, browse again with ie, don't use firefox.
I actually don't know what HDD the OS is installed on because he has RAID0. There is no partition for the OS on it, either, it's installed on them as if they were one HDD, so I really have no idea how to tell which one the OS is on.
I will try with one RAM stick, though. I tried putting my own RAM into his machine and it was still crashing, but I'll try it this way, too.
I will try with one RAM stick, though. I tried putting my own RAM into his machine and it was still crashing, but I'll try it this way, too.
Are both of your machines identical?
Yes, everything about our machines is 100 percent identical, except that I use RAID1 and he uses RAID0. I actually got a crash MEMORY_MANAGEMENT when I put my RAM in his machine. I don't know if that means my RAM is bad, too, or if something is wrong with the RAM itself being compatible with the motherboard or something.
So I'm trying with one single stick now. The machine has been running solid with a clean boot on powerup for over ten minutes. I'm also using IE instead of Firefox. I tried with the other stick of RAM first before this one, and the first one actually crashed the system. I took a screenshot of what Windows told me when I successfully booted up.
It may be luck, for all I know, or a fluke. I'll power it down and start it up multiple times with this single stick of RAM and see what happens. I find it odd, though, that my own RAM still crashed his machine when I put both sticks in it.
Going to try using Firefox now, just to make sure it isn't Firefox and indeed the RAM, or if the two combined causes issues somehow.
So I'm trying with one single stick now. The machine has been running solid with a clean boot on powerup for over ten minutes. I'm also using IE instead of Firefox. I tried with the other stick of RAM first before this one, and the first one actually crashed the system. I took a screenshot of what Windows told me when I successfully booted up.
It may be luck, for all I know, or a fluke. I'll power it down and start it up multiple times with this single stick of RAM and see what happens. I find it odd, though, that my own RAM still crashed his machine when I put both sticks in it.
Going to try using Firefox now, just to make sure it isn't Firefox and indeed the RAM, or if the two combined causes issues somehow.
That is a normal screen when you startup after a BSOD. You may want to start with this tutorial memtest86 test memory. It is a tedious process tracking down what the problems are. I am sure you have been to Asus website and updated all drivers and gone to AMD and update the drivers for the GPU card. Start with the memory, then test the hard drives with the diagnostic tool from the manufacturers website.
I do find it strange that you built 2 identical machines and they are both unstable. You do get bad parts occasionally but 2 at the same time is strange. At this point the machine is not stable enough to run prime95 (CPU test). The only thing I can suggest is to start checking components 1 at a time, and also go back through the machine and make sure all wiring is securely connected, there are no frayed wires, and all connections are properly connected. There does seem to be something about the CD/DVD player. Correct me if I am wrong, but you have at least booted with it disconnected. If that continues I would suggest another Cd/DVD player. It is the cheapest component in the machine. It at least makes me think it is a contributer to the problem. Keep us advised of your progress.
I do find it strange that you built 2 identical machines and they are both unstable. You do get bad parts occasionally but 2 at the same time is strange. At this point the machine is not stable enough to run prime95 (CPU test). The only thing I can suggest is to start checking components 1 at a time, and also go back through the machine and make sure all wiring is securely connected, there are no frayed wires, and all connections are properly connected. There does seem to be something about the CD/DVD player. Correct me if I am wrong, but you have at least booted with it disconnected. If that continues I would suggest another Cd/DVD player. It is the cheapest component in the machine. It at least makes me think it is a contributer to the problem. Keep us advised of your progress.
�� Quote: Originally Posted by MelancholyRose Sorry it took so long. We had an incredibly busy weekend.
�� Quote: Originally Posted by MelancholyRose What does this mean about it? Is the power cord to it pinched or something? I know that it can't be SATA because I have SATA set to IDE for the optical drive, and I have the motherboard SATA plug still in the optical drive. I only removed the SATA power cable.
�� Quote: Originally Posted by MelancholyRose And what's more is that his system started up very quickly and smoothly and I'm not having a single problem while using the computer.
please come and try to help me! my post is entitled 'please help me' the matter is urgent!
In RAID mode the data is spread over both drives that is why it shows up as a single drive. If your PSU was bad it would be more likely to crash with just one power lead to both drives. with separate cables you are using two power rails which should be easier on the PSU.
I think it may be possible that the RAM is underpowered I need to chase this up and I will get back to you.
I think it may be possible that the RAM is underpowered I need to chase this up and I will get back to you.
�� Quote: Originally Posted by essenbe That is a normal screen when you startup after a BSOD. You may want to start with this tutorial memtest86 test memory. It is a tedious process tracking down what the problems are. I am sure you have been to Asus website and updated all drivers and gone to AMD and update the drivers for the GPU card. Start with the memory, then test the hard drives with the diagnostic tool from the manufacturers website.
Quote:
I do find it strange that you built 2 identical machines and they are both unstable. You do get bad parts occasionally but 2 at the same time is strange. At this point the machine is not stable enough to run prime95 (CPU test). The only thing I can suggest is to start checking components 1 at a time, and also go back through the machine and make sure all wiring is securely connected, there are no frayed wires, and all connections are properly connected. There does seem to be something about the CD/DVD player. Correct me if I am wrong, but you have at least booted with it disconnected. If that continues I would suggest another Cd/DVD player. It is the cheapest component in the machine. It at least makes me think it is a contributer to the problem. Keep us advised of your progress.
I've checked all of the connections and there isn't anything wrong with them. The wires are fine and the connections are secure. Right now I do have the optical drive unplugged while I have the single RAM stick in and the computer is running top notch at the moment. I was able to boot and the system never crashed. What I plan to do is start the computer up a few more times with the single RAM stick and the optical drive unplugged. If it continues to be stable, I'm plugging the optical drive back in to the PSU. If it continues to be stable, I'll try again to boot from the other stick that the system crashed with, and if it crashes again, with or without the optical drive plugged in, I'll have to assume it's the stick of RAM that was in the second DIMM slot.
Right now, software isn't telling me a goddamn thing, and it hasn't been for months. I have to rely on the OS responding to the hardware moving around.
�� Quote: Originally Posted by pooch In RAID mode the data is spread over both drives that is why it shows up as a single drive. If your PSU was bad it would be more likely to crash with just one power lead to both drives. with separate cables you are using two power rails which should be easier on the PSU.
I think it may be possible that the RAM is underpowered I need to chase this up and I will get back to you.
I think it may be possible that the RAM is underpowered I need to chase this up and I will get back to you.
�� Quote: Originally Posted by MelancholyRose �� Quote: Originally Posted by pooch In RAID mode the data is spread over both drives that is why it shows up as a single drive. If your PSU was bad it would be more likely to crash with just one power lead to both drives. with separate cables you are using two power rails which should be easier on the PSU.
I think it may be possible that the RAM is underpowered I need to chase this up and I will get back to you.
I think it may be possible that the RAM is underpowered I need to chase this up and I will get back to you.
Look at the stick of ram you are running and tell me what the voltage, timings and frequency are. Also if you could, post a screenshot with CPUz, of the Memory tab, spd tab and cpu tab. Go into bios and make sure dram voltage is set exactly what it says on the stick of ram. Bios will automatically at default set your timings at 9-9-9-24. Lets see if the voltage could be at least part of the problem.
Also, in bios tell me what the setting for CPU NB is.
I haven't gone into BIOS yet, but I figured I'd update before I do all of that.
I tried booting the system five times with the single stick of RAM. It booted cleanly four times. On the fifth, it crashed to a Fatal System Error. This was with the optical drive still unplugged.
Whatever the problem is, apparently it has to do a lot with RAM. I had a little bit of trouble booting after it crashed, even with the one stick.
I'll go to the BIOS and have a look.
I tried booting the system five times with the single stick of RAM. It booted cleanly four times. On the fifth, it crashed to a Fatal System Error. This was with the optical drive still unplugged.
Whatever the problem is, apparently it has to do a lot with RAM. I had a little bit of trouble booting after it crashed, even with the one stick.
I'll go to the BIOS and have a look.
�� Quote: Originally Posted by essenbe Also, in bios tell me what the setting for CPU NB is.
Yes
Here are the screenshots you asked for.
Don't ask what the difference, but NB and CPU NB are different. If you don't have that particular setting never mind for right now.
CPU/NB offset voltage: 1.100
NB voltage: 1.093
DRAM voltage was up to 1.643, and the sticks say 1.5v.
SATA ports with RAID HDDs are set to RAID and not AHCI. Should they be set to AHCI? I didn't know there was much of a difference, and I figured if they were RAID drives, they should be set as RAID. If that's not what they should be set at, I'll change them. If it doesn't matter, I'll leave it.
I've had a couple problems starting the system up from restarts now, too.
NB voltage: 1.093
DRAM voltage was up to 1.643, and the sticks say 1.5v.
SATA ports with RAID HDDs are set to RAID and not AHCI. Should they be set to AHCI? I didn't know there was much of a difference, and I figured if they were RAID drives, they should be set as RAID. If that's not what they should be set at, I'll change them. If it doesn't matter, I'll leave it.
I've had a couple problems starting the system up from restarts now, too.
Set the dram voltage to 1.5
�� Quote: Originally Posted by essenbe Set the dram voltage to 1.5
�� Quote: Originally Posted by MelancholyRose CPU/NB offset voltage: 1.100
NB voltage: 1.093
DRAM voltage was up to 1.643, and the sticks say 1.5v.
SATA ports with RAID HDDs are set to RAID and not AHCI. Should they be set to AHCI? I didn't know there was much of a difference, and I figured if they were RAID drives, they should be set as RAID. If that's not what they should be set at, I'll change them. If it doesn't matter, I'll leave it.
I've had a couple problems starting the system up from restarts now, too.
NB voltage: 1.093
DRAM voltage was up to 1.643, and the sticks say 1.5v.
SATA ports with RAID HDDs are set to RAID and not AHCI. Should they be set to AHCI? I didn't know there was much of a difference, and I figured if they were RAID drives, they should be set as RAID. If that's not what they should be set at, I'll change them. If it doesn't matter, I'll leave it.
I've had a couple problems starting the system up from restarts now, too.
After setting the voltage, I had 4 successful boot-ups after powering on. The fifth time, the Windows logo froze and the system auto-rebooted. It started fine after that, though. I don't know how stable it'll be. I'm going to attempt putting the second RAM stick in and I'm going to see if it crashes or not.
I still don't consider this solved, but at least the blue screens seemed to have gone away for now. I'll have to see what happens with the other RAM stick in.
When I get a hold of the Windows disc, which is at another location, I'm going to try running startup repair and maybe that will help, too.
I still don't consider this solved, but at least the blue screens seemed to have gone away for now. I'll have to see what happens with the other RAM stick in.
When I get a hold of the Windows disc, which is at another location, I'm going to try running startup repair and maybe that will help, too.
�� Quote: Originally Posted by MelancholyRose After setting the voltage, I had 4 successful boot-ups after powering on. The fifth time, the Windows logo froze and the system auto-rebooted. It started fine after that, though. I don't know how stable it'll be. I'm going to attempt putting the second RAM stick in and I'm going to see if it crashes or not.
I still don't consider this solved, but at least the blue screens seemed to have gone away for now. I'll have to see what happens with the other RAM stick in.
When I get a hold of the Windows disc, which is at another location, I'm going to try running startup repair and maybe that will help, too.
I still don't consider this solved, but at least the blue screens seemed to have gone away for now. I'll have to see what happens with the other RAM stick in.
When I get a hold of the Windows disc, which is at another location, I'm going to try running startup repair and maybe that will help, too.
Well, I tried it with both sticks and instant crash. I'm thinking of trying each of my two sticks in the DIMM slot one by one, and I'll have to see if it helps anything.
Tried putting one of my sticks in, and it auto-rebooted Windows at the startup logo again, but once again, it started fine after that the second time it tried.
So I'm going to assume that that particular stick is okay, since the same thing happened with only one stick. I'm going to test my other stick of RAM in his machine, too, just in case that stick is bad, too, so I can RMA both bad sticks instead of RMA one while I still have one other bad one that I need to send.
So, I may have stopped the BSODs, but Windows is still acting up on startup, but hopefully that's something that a startup repair can mend. I'm still going to work on this, but I need a break right now. I've been working on this since 8 a.m. and it's 2:20 now.
So I'm going to assume that that particular stick is okay, since the same thing happened with only one stick. I'm going to test my other stick of RAM in his machine, too, just in case that stick is bad, too, so I can RMA both bad sticks instead of RMA one while I still have one other bad one that I need to send.
So, I may have stopped the BSODs, but Windows is still acting up on startup, but hopefully that's something that a startup repair can mend. I'm still going to work on this, but I need a break right now. I've been working on this since 8 a.m. and it's 2:20 now.
I tried it with my other RAM stick. Something happened.... The Windows logo appeared in this graphical horror LSD looking puddle that looked as if someone sat on it. I'm actually kind of scared.
If you see that long red band/line at the top of the screen, that happened again after I tried booting again with that other RAM stick, when trying to boot into Safe Mode.
Strangely, I can hear the case and CPU fans picking up speed when this happens.
I'm going to try with just the one stick again. I'm going to assume the other stick is bad if I can boot with it again.
If you see that long red band/line at the top of the screen, that happened again after I tried booting again with that other RAM stick, when trying to boot into Safe Mode.
Strangely, I can hear the case and CPU fans picking up speed when this happens.
I'm going to try with just the one stick again. I'm going to assume the other stick is bad if I can boot with it again.
Tried with one stick again and it booted successfully into Safe Mode, now. So I guess that other stick is bad, too?! This can't be happening to me.
Is it more likely that there's something wrong with the RAM sticks and not with the DIMM slot? If there's something wrong with the slot and I have to RMA another motherboard and wait another month for it... sigh.
I guess I'll try putting each "bad" stick in the first slot and see what happens, and if the same thing happens, I'll know it's the RAM, not the slot.
Either way, I'm this close to drowning myself in both booze and sorrow.
Is it more likely that there's something wrong with the RAM sticks and not with the DIMM slot? If there's something wrong with the slot and I have to RMA another motherboard and wait another month for it... sigh.
I guess I'll try putting each "bad" stick in the first slot and see what happens, and if the same thing happens, I'll know it's the RAM, not the slot.
Either way, I'm this close to drowning myself in both booze and sorrow.
Well, the stick that caused the discoloring still caused it even if it was the only stick, so that's garbage. Although, I'm trying the other bad stick right now on its own and it hasn't crashed yet. I'm going to continue to test it, though.
I put the supposed "bad" stick in slot one. It successfully booted with no freezing or crashing about 4 times.
So now, I'm annoyed. Something has got to be wrong with one of these sticks, but I don't know which one, now. They both can power on the machine. When I have 2 sticks of RAM in the slots, the system freezes. However, I don't know why, but the BSODs stopped. I haven't seen one in a while. All that seems to be happening is the Windows logo freezing. or auto-restarting.
Safe Mode freezes too, but it also doesn't crash to a BSOD anymore.
What in the hell is going on here?
So now, I'm annoyed. Something has got to be wrong with one of these sticks, but I don't know which one, now. They both can power on the machine. When I have 2 sticks of RAM in the slots, the system freezes. However, I don't know why, but the BSODs stopped. I haven't seen one in a while. All that seems to be happening is the Windows logo freezing. or auto-restarting.
Safe Mode freezes too, but it also doesn't crash to a BSOD anymore.
What in the hell is going on here?
You might try the 'good stick' in the bad slot. Sometimes it can be the dimm slot and not the ram. If you have a CD, you can create a repair/rescue disk in control panel that will do startup repair.
I tried that, except only with the bad stick in the "Good" slot. I didn't try only putting the "good" stick in the "bad" slot to see what happens.
I need to stop right now because I'm losing my mind. I'll check back later in case any more ideas come up from others. I can't keep working on this all day and go crazy doing it.
I need to stop right now because I'm losing my mind. I'll check back later in case any more ideas come up from others. I can't keep working on this all day and go crazy doing it.
I've asked someone else to give us a hand on this. He knows more about ram settings than I do. One of our resident ram gurus.
Thanks, man, you've been a big help, I appreciate it.
I'm not going anywhere.
Well, I figured I'd still thank you, lol.
Well, thanks. If you can still boot, I'd like to see screenshots from cpuz. I'd like the CPU tab, the memory tab and the SPD tab. If you don't have it, download it here.
I did post them, they're on the top of page 10. You might not have gotten a chance to see them.
I'll look now. Guess between hopping between threads I missed them.
What did you change in bios to get your ram to run at 1600? AMD CPUs memory controller is on the chip. The fastest they will run ram is 1333 (or 666 on cpuz dual channel). The only way to get them to run at 1600 is to change voltages and settings in bios. Whatever was changed may be what is causing you problems. It is OK to do that. I did that on my AMD rig. But, we need to get you running stable at stock first.
I never changed anything, everything has always been on auto and I never adjusted voltages or speed or anything.
Unless updating the BIOS caused it.
Unless updating the BIOS caused it.
you can try holding f8 just as you start it to bring up startup options , then choose "last known good configuration" that worked for me
Do you have an option in bios called dram/FSB ratio? if you do, set that to default.
�� Quote: Originally Posted by pRUSSIANq you can try holding f8 just as you start it to bring up startup options , then choose "last known good configuration" that worked for me
�� Quote: Originally Posted by essenbe Do you have an option in bios called dram/FSB ratio? if you do, set that to default.
Using F8 to go to start up repairs won't erase anything, but may or may not find your problem.
I've read this whole thread, and here is my 2� worth.
You mentioned something buzzing, which is never good. It could be your PSU, DVD, or some fan hanging.
Go into Bios and reset to factory setting, except what you need for your RAID array.
As essenbe said, your RAM shouldn't run at 1600 without some tweaking, seems yours is though.
CPU NB is the Front side bus for AMD and controls the memory frequency in part.
You DVD drive is probably shot, try another one if possible.
If you got your RAM as 2 4GB kits, you may have mixed the stick up and the matched ones are separated. It would seem that some RAM or a slot is bad.
With sooo many different bug check errors this is quite confusing. Note that I have no RAID experience and I won't try to speak to those issues. But, on my gigabyte board to use RAID I would have to use specific SATA headers.
I've read this whole thread, and here is my 2� worth.
You mentioned something buzzing, which is never good. It could be your PSU, DVD, or some fan hanging.
Go into Bios and reset to factory setting, except what you need for your RAID array.
As essenbe said, your RAM shouldn't run at 1600 without some tweaking, seems yours is though.
CPU NB is the Front side bus for AMD and controls the memory frequency in part.
You DVD drive is probably shot, try another one if possible.
If you got your RAM as 2 4GB kits, you may have mixed the stick up and the matched ones are separated. It would seem that some RAM or a slot is bad.
With sooo many different bug check errors this is quite confusing. Note that I have no RAID experience and I won't try to speak to those issues. But, on my gigabyte board to use RAID I would have to use specific SATA headers.
Quote:
You mentioned something buzzing, which is never good. It could be your PSU, DVD, or some fan hanging.
Quote:
Go into Bios and reset to factory setting, except what you need for your RAID array.
Quote:
If you got your RAM as 2 4GB kits, you may have mixed the stick up and the matched ones are separated. It would seem that some RAM or a slot is bad.
However, I had no idea you could have "mismatched" sticks, even when the two packs are identical. That's a new thing for me to learn. It's possible that I might have done that, since I was ignorant of that fact.
Quote:
With sooo many different bug check errors this is quite confusing. Note that I have no RAID experience and I won't try to speak to those issues. But, on my gigabyte board to use RAID I would have to use specific SATA headers.
Try this. Go into bios and load optimized defaults. Then change the ram voltage to 1.5, then set your sata controllers to raid like you have them. Reboot and post screenshots of CPUz again. Trust me. No phenomII CPU can run ram at 1600 without several tweeks. The highest the chip will run on default settings is 1333 with timings of 9-9-9-24. Some setting is out of whack in bios to have the ram running at that speed. And also set your boot order.
When you have tried essenbe's BIOS treatment, I think that you should try the startup repair or even a new install. If these do not fix the problem I think we can safely say it is the MB or the RAM at fault and we can then concentrate on finding out which.
Quote:
Try this. Go into bios and load optimized defaults. Then change the ram voltage to 1.5, then set your sata controllers to raid like you have them. Reboot and post screenshots of CPUz again. Trust me. No phenomII CPU can run ram at 1600 without several tweeks. The highest the chip will run on default settings is 1333 with timings of 9-9-9-24. Some setting is out of whack in bios to have the ram running at that speed. And also set your boot order
Quote:
When you have tried essenbe's BIOS treatment, I think that you should try the startup repair or even a new install. If these do not fix the problem I think we can safely say it is the MB or the RAM at fault and we can then concentrate on finding out which.
Also, does the graphical glitch with that one RAM stick in mean it's no good? I'm leaning toward "yes" since I've never seen that happen with RAM before, and it's the only stick that does it when in a slot, either the first or second. I just need to know if I should RMA it while I'm still waiting on my motherboard replacement as well.
You will need to explain to G Skill tech support that the computer will not boot with that stick of ram in. I would also suggest that you rma the kit, both sticks. The reason Britton30 asked you about mixing the sticks from the 2 kits is because G Skill tests a kit together, in order to make sure the 2 sticks work together. So, if you can RMA both sticks as a kit, so you will get a kit returned that has been tested to work as a pair.
Oh, I see, gotcha. Okay, I'll remember that.
Hello MelancholyRose, Haven't had time to read the entire thread but have been briefed by one of the members helping you. Will read through it later, if I ask for or request something you have already done just let me know.
The 1600 MHz frequency setting is causing your BSoDs and failure to boot.
Page 2-11 of your motherboard manual:
Your motherboard manual, Asus M4A89TD Pro USB3
Can you confirm this is your RAM?
[ Ripjaws ] F3-12800CL9S-2GBRL (2Gx1) / F3-12800CL9D-4GBRL (2Gx2) / F3-12800CL9Q-8GBRL (2Gx4)
It does list the Asus M4A89TD Pro motherboard in the Qualified Motherboard list, this is close enough to yours to indicate there should be no compatibility issues.
Some RAM and motherboards are a little harder to get running stable, best thing to do is adjust the settings first. If you start RMA'ing the RAM you may have the same issues.
There is a known issue with running RAM above 1333MHz on AMD CPUs, here is a link explaining the issues.
VERY IMPORTANT INFORMATION REGARDING AMD AM3 CPU's and RAM SPEEDS
Q&A for the topic VERY IMPORTANT INFORMATION REGARDING AMD AM3 CPU's & RAM....
This is affecting all motherboards and all types of RAM.
Check your BIOS version, if a newer one mentions improvement for RAM you may consider updating the BIOS.
First thing I would recommend to do is set all the RAM settings manually.
I would save the BIOS settings first the default and then the recommended settings below.
Most motherboards have the ability to save several BIOS settings, just name them so they can easily be identified.
*EDIT: First RAM settings.
The RAM should be in slots A1 & B1, the blue slots.
DRAM frequency: 1333MHz
First four timings:
8
8
8
25
Leave the rest on 'Auto'
Set Command rate to 2T, this will help with stability.
DRAM voltage: 1.50v
CPU/NB voltage: 1.20v
Save the settings to another name.
Re-boot with both RAM cards installed, if you get a good boot then run memtest86+ for a full 8 passes.
Each pass runs a different set of tests and each are important, as always you can stop the test if you get any errors.
This may take several hours to complete, best to run overnight.
Let us know the results.
Have you ran memtest86+ as per this tutorial?
RAM - Test with Memtest86+
If you have errors with the new settings, report here first, and we can proceed from there.
After I read the thread, it will be easier to decide the coarse of action.
The 1600 MHz frequency setting is causing your BSoDs and failure to boot.
Page 2-11 of your motherboard manual:
Quote:
Due to the CPU spec., AMD AM3 100 and 200 series CPUs support up to DDR3 1066MHz. With ASUS design, this motherboard can support up to DDR3 1333MHz.
When overclocking, some AMD CPU models may not support DDR3 1600 or higher frequency DIMMs.
When overclocking, some AMD CPU models may not support DDR3 1600 or higher frequency DIMMs.
Can you confirm this is your RAM?
[ Ripjaws ] F3-12800CL9S-2GBRL (2Gx1) / F3-12800CL9D-4GBRL (2Gx2) / F3-12800CL9Q-8GBRL (2Gx4)
It does list the Asus M4A89TD Pro motherboard in the Qualified Motherboard list, this is close enough to yours to indicate there should be no compatibility issues.
Some RAM and motherboards are a little harder to get running stable, best thing to do is adjust the settings first. If you start RMA'ing the RAM you may have the same issues.
There is a known issue with running RAM above 1333MHz on AMD CPUs, here is a link explaining the issues.
VERY IMPORTANT INFORMATION REGARDING AMD AM3 CPU's and RAM SPEEDS
Q&A for the topic VERY IMPORTANT INFORMATION REGARDING AMD AM3 CPU's & RAM....
This is affecting all motherboards and all types of RAM.
Check your BIOS version, if a newer one mentions improvement for RAM you may consider updating the BIOS.
First thing I would recommend to do is set all the RAM settings manually.
I would save the BIOS settings first the default and then the recommended settings below.
Most motherboards have the ability to save several BIOS settings, just name them so they can easily be identified.
*EDIT: First RAM settings.
The RAM should be in slots A1 & B1, the blue slots.
DRAM frequency: 1333MHz
First four timings:
8
8
8
25
Leave the rest on 'Auto'
Set Command rate to 2T, this will help with stability.
DRAM voltage: 1.50v
CPU/NB voltage: 1.20v
Save the settings to another name.
Re-boot with both RAM cards installed, if you get a good boot then run memtest86+ for a full 8 passes.
Each pass runs a different set of tests and each are important, as always you can stop the test if you get any errors.
This may take several hours to complete, best to run overnight.
Let us know the results.
Have you ran memtest86+ as per this tutorial?
RAM - Test with Memtest86+
If you have errors with the new settings, report here first, and we can proceed from there.
After I read the thread, it will be easier to decide the coarse of action.
Quote:
Can you confirm this is your RAM?
[ Ripjaws ] F3-12800CL9S-2GBRL (2Gx1) / F3-12800CL9D-4GBRL (2Gx2) / F3-12800CL9Q-8GBRL (2Gx4)
It does list the Asus M4A89TD Pro motherboard in the Qualified Motherboard list, this is close enough to yours to indicate there should be no compatibility issues.
[ Ripjaws ] F3-12800CL9S-2GBRL (2Gx1) / F3-12800CL9D-4GBRL (2Gx2) / F3-12800CL9Q-8GBRL (2Gx4)
It does list the Asus M4A89TD Pro motherboard in the Qualified Motherboard list, this is close enough to yours to indicate there should be no compatibility issues.
Quote:
There is a known issue with running RAM above 1333MHz on AMD CPUs, here is a link explaining the issues.
VERY IMPORTANT INFORMATION REGARDING AMD AM3 CPU's and RAM SPEEDS
Q&A for the topic VERY IMPORTANT INFORMATION REGARDING AMD AM3 CPU's & RAM....
This is affecting all motherboards and all types of RAM.
VERY IMPORTANT INFORMATION REGARDING AMD AM3 CPU's and RAM SPEEDS
Q&A for the topic VERY IMPORTANT INFORMATION REGARDING AMD AM3 CPU's & RAM....
This is affecting all motherboards and all types of RAM.
My biggest concern now is that it's too late to save his machine. I'm worried that he may need a replacement CPU, and if it's damaged because of this odd issue with the BIOS, they may not replace it. Buying a new one would hurt our finances. Hell, buying two would even worse.
The reason I say that is
Quote:
The 1600 MHz frequency setting is causing your BSoDs and failure to boot.
Quote:
Have you ran memtest86+ as per this tutorial?
I do have the RAM in A1 and B1.
That's all I know for now. Thanks for the info so far and I'll keep you posted if I change anything further, likely tomorrow.
I have been editing my post above.
Try the settings recommended.
Hopefully there is no permanent damage to any components.
Testing the above settings, and with further settings and tests, we can determine is any components are damaged.
There is a reasonable chance, not definite, that your components are ok and the settings can be adjusted to get a stable system.
Let's take it a step at a time and see what the results are.
Let us know the results.
Try the settings recommended.
Hopefully there is no permanent damage to any components.
Testing the above settings, and with further settings and tests, we can determine is any components are damaged.
There is a reasonable chance, not definite, that your components are ok and the settings can be adjusted to get a stable system.
Let's take it a step at a time and see what the results are.
Let us know the results.
MelancholyRose, don't be overly concerned about your equipment right now. Dave76 is excellent with this. He helped me when I was going through the same thing you are going through. AMD boards can be very finicky about ram. Sometimes you just need the right settings to get them to run stable. Dave is very good at that.
Just tomorrow, after you have set everything to default like we talked about earlier, use the settings Dave gave you and see how that goes.
Just tomorrow, after you have set everything to default like we talked about earlier, use the settings Dave gave you and see how that goes.
MelancholyRose, good morning. Let us know when you get started. When you set bios to default, use Dave76's settings listed in post # 128. you will see a whole list of settings, don't worry about them, just the settings Dave listed, they are usually the first 4 settings. In case it confuses you this is what they will probably be listed as and the settings.
CAS# latency 8
RAS# to CAS# 8
RAS# precharge 8
tRAS 8
TRC 25
CR 2T
You will also want to set dram voltage at 1.5 and CPU NB at 1.2
Set your sata controller to raid and set the boot order then save and exit.
CAS# latency 8
RAS# to CAS# 8
RAS# precharge 8
tRAS 8
TRC 25
CR 2T
You will also want to set dram voltage at 1.5 and CPU NB at 1.2
Set your sata controller to raid and set the boot order then save and exit.
Loading Defaults is "Load Setup Defaults" correct? It's on the exit menu underneath the save options. Is that what I want to do first?
That would probably work, it is usually called optimized defaults. If you have optimized defaults use it otherwise use the one you have. Most MB it is F9. It should tell you in bios.
Okay, I managed to reset defaults and now I'm putting in the RAM info, only I have some questions:
I found CAS #
RAS to CAS #
and RAS # PRE
But what is tRAS?
Is TRC Row Cycle Time, and is CR Command Rate?
The fourth one down for me is ACT Time, that's the one I set to 25 unless you say differently.
I found CAS #
RAS to CAS #
and RAS # PRE
But what is tRAS?
Is TRC Row Cycle Time, and is CR Command Rate?
The fourth one down for me is ACT Time, that's the one I set to 25 unless you say differently.
It is usually the firsr 4 settings that you will change to 8. CR is command rate set it at 2T. If you have the option to set dram frequency, set it at 1333. If you have the option of FSB/Dram ratio set it to auto/default whichever option you have.
Set dram voltage to 1.5 and CPU NB to 1.2. CPU NB is different than NB. Set sata controllers to raid and boot order to however you prefer. I always set CD/DVD 1st and HDD #2. Save and exit.
Set dram voltage to 1.5 and CPU NB to 1.2. CPU NB is different than NB. Set sata controllers to raid and boot order to however you prefer. I always set CD/DVD 1st and HDD #2. Save and exit.
Well, what I'm confused about is the fourth one down doesn't give "8" as an option, but it does give 25.
So right now I set it to
8
8
8
25
before they were
9
9
9
28
Is 28 the right thing to change to 25? I'm assuming that it is, since I think that's what Dave said.
So right now I set it to
8
8
8
25
before they were
9
9
9
28
Is 28 the right thing to change to 25? I'm assuming that it is, since I think that's what Dave said.
My CPU/NB voltage says CPU/NB Offset Voltage. I tried changing that to 1.2 but the numbers turned red. I was really confused, since this is the only CPU/NB option I see that I can change.
The column says this
CPU and NB voltage mode: Offset
CPU Offset Voltage: 1.392
CPU/NB Offset Voltage: 1.100
There's an option to change CPU/NB voltage mode to manual, should I do that? I don't really know what "offset" is supposed to do.
The column says this
CPU and NB voltage mode: Offset
CPU Offset Voltage: 1.392
CPU/NB Offset Voltage: 1.100
There's an option to change CPU/NB voltage mode to manual, should I do that? I don't really know what "offset" is supposed to do.
MelancholyRose, hold on I hope we have help on the way. I would be guessing.
Never mind, I set it to "manual" and I could adjust the voltage. Only now it's yellow >.> Hope I don't break anything here.
Okay, maybe I should wait for help before I do anything else. I don't want to make the problem worse, here.
Okay, maybe I should wait for help before I do anything else. I don't want to make the problem worse, here.
My guess is to set it as manual like you did, put it at 1.2 and change offset to 0.00
Have been reading through the thread and missed the last few posts.
First four settings:
8
8
8
25
Command Rate - CR to 2T
You are correct, change CPU/NB to Manual and 1.20v and offset back to 0.00.
CPU/NB voltage of 1.20v is a safe setting for your system, max should be 1.40v.
Is that the first red setting?
For now, just get the RAM settings changed.
The below information is for reference and should be looked at after the RAM settings are changed and tested.
They will likely need adjusting before we move on.
I will continue editing this post...
Thanks for the clarification essenbe, those are the timing settings that need changed.
You mentioned your BIOS is set to RAID, that is good. RAID actually uses AHCI and will have all of the benefits.
Do you still have the front case USB port cable unplugged from the motherboard?
From reading through the thread, there are a couple of questions.
�� Quote: Originally Posted by MelancholyRose Disconnect SATA and power cables for testing.
Stop 1E.
STOP 0x0000001E: KMODE_EXCEPTION_NOT_HANDLED
Usual causes: Device driver, hardware, System service, compatibility, Remote control programs, memory, BIOS
This is a fairly general Stop code.
Stop 3B.
STOP 0x0000003B: SYSTEM_SERVICE_EXCEPTION
Usual causes: System service, Device driver, graphics driver, ?memory
Things in common with the other stop code are drivers and memory.
Did you get the graphics driver updated?
When the system has a crash and can't find the cause, it usually blames a kernal driver. These are rarely to blame it's just that the crash logs don't know what else to blame.
ntoskrnl is a kernal driver.
�� Quote: Originally Posted by MelancholyRose From the last dump file in this post.
STOP 0x0000007E: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
Usual causes: Insufficient disk space, Device driver, Video card, BIOS, Breakpoint with no debugger attached, Hardware incompatibility, Faulty system service, Memory, 3rd party remote control,
The SYSTEM_THREAD_EXCEPTION_NOT_HANDLED bug check is a very common bug check.
Again, driver, graphics card, memory are listed.
Error code 0xC0000005: STATUS_ACCESS_VIOLATION indicates a memory access violation occurred.
If you haven't updated ahcix64s.sys, let me know what you have tried.
This driver was flagged, and should be updated.
The default MS AHCI driver is preferred by many for AMD boards, we might come back to this.
Post #59, crashes.
STOP 0x00000050: PAGE_FAULT_IN_NONPAGED_AREA
Usual causes: Defective hardware (particularly memory - but not just RAM), Faulty system service, Antivirus, Device driver, NTFS corruption, BIOS
Bug check 0x50 usually occurs after the installation of faulty hardware or in the event of failure of installed hardware (usually related to defective RAM, be it main memory, L2 RAM cache, or video RAM).
Again Graphics card and RAM.
When running tests on your HDDs, use Western Digital Lifeguard � Quick Test and Extended Test.
First four settings:
8
8
8
25
Command Rate - CR to 2T
You are correct, change CPU/NB to Manual and 1.20v and offset back to 0.00.
CPU/NB voltage of 1.20v is a safe setting for your system, max should be 1.40v.
Is that the first red setting?
For now, just get the RAM settings changed.
The below information is for reference and should be looked at after the RAM settings are changed and tested.
They will likely need adjusting before we move on.
I will continue editing this post...
Thanks for the clarification essenbe, those are the timing settings that need changed.
You mentioned your BIOS is set to RAID, that is good. RAID actually uses AHCI and will have all of the benefits.
Do you still have the front case USB port cable unplugged from the motherboard?
From reading through the thread, there are a couple of questions.
�� Quote: Originally Posted by MelancholyRose Okay, well, I plugged the optical drive back in, and I got a BSOD while Windows was starting up.
STOP 1E
fltmgr.sys
STOP 1E
fltmgr.sys
Stop 1E.
STOP 0x0000001E: KMODE_EXCEPTION_NOT_HANDLED
Usual causes: Device driver, hardware, System service, compatibility, Remote control programs, memory, BIOS
This is a fairly general Stop code.
Stop 3B.
STOP 0x0000003B: SYSTEM_SERVICE_EXCEPTION
Usual causes: System service, Device driver, graphics driver, ?memory
Things in common with the other stop code are drivers and memory.
Did you get the graphics driver updated?
When the system has a crash and can't find the cause, it usually blames a kernal driver. These are rarely to blame it's just that the crash logs don't know what else to blame.
ntoskrnl is a kernal driver.
�� Quote: Originally Posted by MelancholyRose I've done that already. It found nothing wrong.
I tried disabling some non-Microsoft system services and powering on after shutting down and it still crashed every time. The dump files are all contained in this folder.
Since it will cleanly boot up the very first time if something else is booted before it, it makes me think there's something wrong with boot files, but the system doesn't find a single corrupted or missing file. I can't explain it.
I know that ntoskrnl pops up in a LOT of these, too.
I tried disabling some non-Microsoft system services and powering on after shutting down and it still crashed every time. The dump files are all contained in this folder.
Since it will cleanly boot up the very first time if something else is booted before it, it makes me think there's something wrong with boot files, but the system doesn't find a single corrupted or missing file. I can't explain it.
I know that ntoskrnl pops up in a LOT of these, too.
STOP 0x0000007E: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
Usual causes: Insufficient disk space, Device driver, Video card, BIOS, Breakpoint with no debugger attached, Hardware incompatibility, Faulty system service, Memory, 3rd party remote control,
The SYSTEM_THREAD_EXCEPTION_NOT_HANDLED bug check is a very common bug check.
Again, driver, graphics card, memory are listed.
Error code 0xC0000005: STATUS_ACCESS_VIOLATION indicates a memory access violation occurred.
Code:
******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e) This is a very common bugcheck. Usually the exception address pinpoints the driver/function that caused the problem. Always note this address as well as the link date of the driver/image that contains this address. Some common problems are exception code 0x80000003. This means a hard coded breakpoint or assertion was hit, but this system was booted /NODEBUG. This is not supposed to happen as developers should never have hardcoded breakpoints in retail code, but ... If this happens, make sure a debugger gets connected, and the system is booted /DEBUG. This will let us see why this breakpoint is happening. Arguments: Arg1: ffffffffc0000005, The exception code that was not handled Arg2: fffff80002d8e945, The address that the exception occurred at Arg3: fffff88003185a48, Exception Record Address Arg4: fffff880031852a0, Context Record Address Debugging Details: ------------------ EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s. FAULTING_IP: nt!ObpProcessRemoveObjectQueue+29 fffff800`02d8e945 488b7b08 mov rdi,qword ptr [rbx+8] EXCEPTION_RECORD: fffff88003185a48 -- (.exr 0xfffff88003185a48) ExceptionAddress: fffff80002d8e945 (nt!ObpProcessRemoveObjectQueue+0x0000000000000029) ExceptionCode: c0000005 (Access violation) ExceptionFlags: 00000000 NumberParameters: 2 Parameter[0]: 0000000000000000 Parameter[1]: 0000000000000009 Attempt to read from address 0000000000000009 CONTEXT: fffff880031852a0 -- (.cxr 0xfffff880031852a0) rax=fffffa8006f3d2a0 rbx=0000000000000001 rcx=0000000000001d10 rdx=fffff880009aa000 rsi=fffffa8003c49b60 rdi=0000000000000000 rip=fffff80002d8e945 rsp=fffff88003185c80 rbp=0000000000000000 r8=000000000000e880 r9=0000000000000080 r10=fffff80002a5d000 r11=00000000000005d0 r12=fffff80002c85180 r13=0000000000000001 r14=0000000000000000 r15=0000000000000001 iopl=0 nv up ei pl zr na po nc cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010246 nt!ObpProcessRemoveObjectQueue+0x29: fffff800`02d8e945 488b7b08 mov rdi,qword ptr [rbx+8] ds:002b:00000000`00000009=???????????????? Resetting default scope CUSTOMER_CRASH_COUNT: 1 PROCESS_NAME: System CURRENT_IRQL: 0 ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s. EXCEPTION_PARAMETER1: 0000000000000000 EXCEPTION_PARAMETER2: 0000000000000009 READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002d0c100 0000000000000009 FOLLOWUP_IP: nt!ObpProcessRemoveObjectQueue+29 fffff800`02d8e945 488b7b08 mov rdi,qword ptr [rbx+8] BUGCHECK_STR: 0x7E DEFAULT_BUCKET_ID: NULL_CLASS_PTR_DEREFERENCE LAST_CONTROL_TRANSFER: from fffff80002ae7021 to fffff80002d8e945 STACK_TEXT: fffff880`03185c80 fffff800`02ae7021 : fffff800`02d8e91c fffff800`02c7a260 fffffa80`03c49b00 00000000`00000003 : nt!ObpProcessRemoveObjectQueue+0x29 fffff880`03185cb0 fffff800`02d7932e : 00000000`00000000 fffffa80`03c49b60 00000000`00000080 fffffa80`03b54040 : nt!ExpWorkerThread+0x111 fffff880`03185d40 fffff800`02ace666 : fffff880`02f70180 fffffa80`03c49b60 fffff880`02f7afc0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a fffff880`03185d80 00000000`00000000 : fffff880`03186000 fffff880`03180000 fffff880`031859e0 00000000`00000000 : nt!KiStartSystemThread+0x16 SYMBOL_STACK_INDEX: 0 SYMBOL_NAME: nt!ObpProcessRemoveObjectQueue+29 FOLLOWUP_NAME: MachineOwner MODULE_NAME: nt IMAGE_NAME: ntkrnlmp.exe DEBUG_FLR_IMAGE_TIMESTAMP: 4d9fdd5b STACK_COMMAND: .cxr 0xfffff880031852a0 ; kb FAILURE_BUCKET_ID: X64_0x7E_nt!ObpProcessRemoveObjectQueue+29 BUCKET_ID: X64_0x7E_nt!ObpProcessRemoveObjectQueue+29 Followup: MachineOwner ---------
This driver was flagged, and should be updated.
The default MS AHCI driver is preferred by many for AMD boards, we might come back to this.
Post #59, crashes.
STOP 0x00000050: PAGE_FAULT_IN_NONPAGED_AREA
Usual causes: Defective hardware (particularly memory - but not just RAM), Faulty system service, Antivirus, Device driver, NTFS corruption, BIOS
Bug check 0x50 usually occurs after the installation of faulty hardware or in the event of failure of installed hardware (usually related to defective RAM, be it main memory, L2 RAM cache, or video RAM).
Again Graphics card and RAM.
When running tests on your HDDs, use Western Digital Lifeguard � Quick Test and Extended Test.
I'm just going to try saving and seeing what happens. If the system is still unstable I'll go back to BIOS. If it stabilizes, I'll run Memtest.
Quote:
Did you get the graphics driver updated?
Quote:
Do you still have the front case USB port cable unplugged from the motherboard?
Quote:
If you haven't updated ahcix64s.sys, let me know what you have tried.
This driver was flagged, and should be updated.
The default MS AHCI driver is preferred by many for AMD boards, we might come back to this
This driver was flagged, and should be updated.
The default MS AHCI driver is preferred by many for AMD boards, we might come back to this
There was a successful boot-up with no crashes or hangs. I'll time it to see how long it lasts. Sometimes it'll be a fluke and crash after 5 minutes or so, but so far it's looking clean.
That's good news and seems to be an improvement. Keeping my fingers crossed for you.
Can you confirm the BIOS settings?
Did you set the first four RAM timings to:
8
8
8
25
Command Rate - CR to 2T
CPU/NB to Manual and 1.20v and offset back to 0.00.
CPU/NB voltage of 1.20v is a safe setting for your system, max should be 1.40v.
Is that the first red setting?
All these settings are important, let us know exactly how you set them.
If it seems stable run memtest86+ for a full 8 passes, best to run overnight.
If you get any errors you can stop the test.
Let us know the results.
Did you set the first four RAM timings to:
8
8
8
25
Command Rate - CR to 2T
CPU/NB to Manual and 1.20v and offset back to 0.00.
CPU/NB voltage of 1.20v is a safe setting for your system, max should be 1.40v.
Is that the first red setting?
All these settings are important, let us know exactly how you set them.
If it seems stable run memtest86+ for a full 8 passes, best to run overnight.
If you get any errors you can stop the test.
Let us know the results.
Quote:
Can you confirm the BIOS settings?
Did you set the first four RAM timings to:
8
8
8
25
Command Rate - CR to 2T
CPU/NB to Manual and 1.20v and offset back to 0.00.
CPU/NB voltage of 1.20v is a safe setting for your system, max should be 1.40v.
Is that the first red setting?
All these settings are important, let us know exactly how you set them.
If it seems stable run memtest86+ for a full 8 passes, best to run overnight.
If you get any errors you can stop the test.
Let us know the results.
Did you set the first four RAM timings to:
8
8
8
25
Command Rate - CR to 2T
CPU/NB to Manual and 1.20v and offset back to 0.00.
CPU/NB voltage of 1.20v is a safe setting for your system, max should be 1.40v.
Is that the first red setting?
All these settings are important, let us know exactly how you set them.
If it seems stable run memtest86+ for a full 8 passes, best to run overnight.
If you get any errors you can stop the test.
Let us know the results.
Yes 1.4 is the first "red." 1.2 is yellow.
Since it seems stable for now, I'm going to try restarting with a memtest.
Well, I would like to think that no news is good news. I did uncross my fingers. It makes it hard to type, but my legs are crossed.
LOL.
Well, a full 8 passes went with no errors.
I'm going to reboot, shut down and power on a second time and tell you what happens.
Well, a full 8 passes went with no errors.
I'm going to reboot, shut down and power on a second time and tell you what happens.
Another successful boot-up with no crashing, hanging, or freezing. I'm going to try a few more times. If I never see a hang or crash, I'll mark it solved.
That's fantastic news. Congratulations. You've at least made progress if not something better.
�� Quote: Originally Posted by MelancholyRose Another successful boot-up with no crashing, hanging, or freezing. I'm going to try a few more times. If I never see a hang or crash, I'll mark it solved.
CPUZ seems to have all the right voltages and timings on it. When he plays games later, I'll see how it performs, but I'm sure it'll be fine, games always ran top notch. If not, I'll mention it, but otherwise I think it's solved.
If the games run fine I'll let you know that too.
Thank you so much for all you've done for me, and all the time you provided.
If the games run fine I'll let you know that too.
Thank you so much for all you've done for me, and all the time you provided.
It was agroup effort. It took a lot of people contributing. I hope it's solved for you. I think we've all learned a lot from this thread. What about your raid? You were going to reinstall if the ram checked out.
The RAID seems like it's functioning normally. Also, he's playing a game right now and it seems to be running fine.
Well, that's very good. I hope it stays working well for you. Seems that some builds go real easy, and some you have to pull your hair out a little to get them right. But, the end result is what counts. If you have a setting in bios to save these settings I think I would. If it gets messed up again you can always go back to here. If you have problems, we'll be right here. Pooch and Dave76 were the real helpers here, it wouldn't be running like it is without them. Good luck.
Glad to hear it's running more stable than before.
There is usually more tweaking to get stability, don't be surprised if the issues rear their ugly head again.
Although memtest86+ is the best RAM testing app, RAM can be very difficult to setup for stability, I have seen several error free passes of memtest86+ and then one will give errors.
This is just the way electronics are, I recommend some more testing, yes I know running memtest86+ is a long process and not the most fun you can have with your computer.
The good news is that the next test, for now, is not memtest86+.
If you want to get confirmation and ensure this doesn't throw crashes at some later date, you should run Prime95 torture test.
CPU - Stress Test with Prime95
Prime95 Torture test
If memtest86+ passes then run Prime95 torture test.
First open Core Temp to monitor CPU temperatures, don't go over 62�C.
Open Prime95 and stop the test if it is running, in Advanced tab select 'Round off checking', in the Options tab select 'Torture Test...', in the window that opens select 'Blend', after 'Number of torture test threads to run' enter 4, then click OK to start the test.
AMD Phenom II x4 965 black edition specs
Some sites/people recommend running this test for 12-24 hours, it has been heavily debated and everyone has their own opinion.
Mine is that 2-3 hours will give you a good idea of the stability of your system.
If you want a system that runs maxed out 24/7 then go for a longer test.
Be sure to watch the temperatures closely for the first 15 minutes, they should stabilize after a minute.
If the temps get too high, stop the test. This can be harmful to your system and indicates a cooling issue.
Let us know what you decide to do.
There is usually more tweaking to get stability, don't be surprised if the issues rear their ugly head again.
Although memtest86+ is the best RAM testing app, RAM can be very difficult to setup for stability, I have seen several error free passes of memtest86+ and then one will give errors.
This is just the way electronics are, I recommend some more testing, yes I know running memtest86+ is a long process and not the most fun you can have with your computer.
The good news is that the next test, for now, is not memtest86+.
If you want to get confirmation and ensure this doesn't throw crashes at some later date, you should run Prime95 torture test.
CPU - Stress Test with Prime95
Prime95 Torture test
If memtest86+ passes then run Prime95 torture test.
First open Core Temp to monitor CPU temperatures, don't go over 62�C.
Open Prime95 and stop the test if it is running, in Advanced tab select 'Round off checking', in the Options tab select 'Torture Test...', in the window that opens select 'Blend', after 'Number of torture test threads to run' enter 4, then click OK to start the test.
AMD Phenom II x4 965 black edition specs
Some sites/people recommend running this test for 12-24 hours, it has been heavily debated and everyone has their own opinion.
Mine is that 2-3 hours will give you a good idea of the stability of your system.
If you want a system that runs maxed out 24/7 then go for a longer test.
Be sure to watch the temperatures closely for the first 15 minutes, they should stabilize after a minute.
If the temps get too high, stop the test. This can be harmful to your system and indicates a cooling issue.
Let us know what you decide to do.
�� Quote: Originally Posted by MelancholyRose �� Quote: Originally Posted by pRUSSIANq you can try holding f8 just as you start it to bring up startup options , then choose "last known good configuration" that worked for me
No, it only affects system settings and won't change your e?mail, photos, or other personal data on your computer.
All right, I'll give those tests a whirl today, as well.
I'll let you know the results.
Thanks for all of your help and input
I'll let you know the results.
Thanks for all of your help and input
Your welcome, let us know the results.
Well I'll run the test for a few minutes and it'll get up to 63 degrees. So I have to stop it then, I assume. I do have a bunch of internet windows open while running this, but I didn't think it would affect it.
What CPU cooler are you using and what thermal paste did you use on it?
Stock cooler. Thermal paste came pre-applied.
�� Quote: Originally Posted by essenbe Well, that's very good. I hope it stays working well for you. Seems that some builds go real easy, and some you have to pull your hair out a little to get them right. But, the end result is what counts. If you have a setting in bios to save these settings I think I would. If it gets messed up again you can always go back to here. If you have problems, we'll be right here. Pooch and Dave76 were the real helpers here, it wouldn't be running like it is without them. Good luck.
63� is not a temperature I would tolerate but you are stressing the system and I wouldn't call it dangerous. A better cooler shouldn't cost you a great deal of money and may well be worth investing in especially as the PC is being used for games.
The max temp is 65� so as long as it stays under maybe leaving the side off and using a normal household ventilator would help
The max temp is 65� so as long as it stays under
maybe leaving the side off and using a normal household ventilator would help Well, it is actually pretty warm and humid in here today and I have no windows open or the A/C on, and I was leaving the side panels on. I could try changing all of those factors and also determining if it stays under 65. If it keeps getting too warm I could look for better coolers.
sounds like a plan to me
ps the CPU thermal cut out should automatically slow it down before it gets dangerously hot
ps the CPU thermal cut out should automatically slow it down before it gets dangerously hot
I've got the A/C on and the side panel off and it hops around from 62 to 64 degrees, but it never stays at any of those solid temps, so I'm sure it's not too bad.
�� Quote: Originally Posted by MelancholyRose I've got the A/C on and the side panel off and it hops around from 62 to 64 degrees, but it never stays at any of those solid temps, so I'm sure it's not too bad.
I believe Tcase is 62�C. If you are using coretemp to read temps, they are reading the core temps. Core temps tend to be 5-10�C higher than Tcase. But the CPU has thermal throttling which will make it shut itself down if it gets too hot before any damage (but I don't trust that). But, if core temp is reading 65�C you should be OK. Personally, I tend to be more conservative than others and would shut it down around 68�. You may consider a little better cooler. There are several that are better than the stock one for 20-$25.
Well I ran the stress test for a couple of hours and everything seems nice and smooth. There were no errors or problems. Thanks guys!
I just have to remember to do all of this on my own machine when I get it put back together!
For the record, core temp never once got to 65. It stayed around 62-64.
I just have to remember to do all of this on my own machine when I get it put back together!
For the record, core temp never once got to 65. It stayed around 62-64.
That's great news. I hope it keeps working well for you.
Thanks. You've been great
Glad to hear the Prime95 torture test passed.
You should be good and not get any more crashes, if there are any issues just post back here, we will all get a notice.
If there are any other issues the settings might need a little tweaking, hopefully you are all set.
Since your two systems are basically identical, the same settings should work on yours.
Those CPU core temps are a bit high, AMD CPUs normally run cool, so this does indicate a cooling issue.
Can you give us the CPU idle and room temperatures?
Your CPU idle temps should be at most a couple �C above ambient temps.
essenbe is right, a rated CPU temp of 62�C is for Tcase, you add 5�C for core temps, this makes the recommended max core temp 67�C.
I tend to be a bit cautious when it comes to component temps, heat + electronics = trouble.
Staying under this temp, the temps you had, is acceptable but, as mentioned this is a high temp for an AMD CPU.
Monitor the CPU temps when stressing the system, playing games is a good test, they should be max in the high 40's.
Have seen many AMD CPUs run Prime95 in the mid 40's.
Check that the CPU cooler is firmly attached, if you need to take it off it is best to clean and then re-apply the thermal paste.
Information on CPU coolers and thermal paste.
80 Thermal Pastes Tested
Best CPU Cooler Performance AMD Socket AM3 Preview
You should be good and not get any more crashes, if there are any issues just post back here, we will all get a notice.
If there are any other issues the settings might need a little tweaking, hopefully you are all set.
Since your two systems are basically identical, the same settings should work on yours.
Those CPU core temps are a bit high, AMD CPUs normally run cool, so this does indicate a cooling issue.
Can you give us the CPU idle and room temperatures?
Your CPU idle temps should be at most a couple �C above ambient temps.
essenbe is right, a rated CPU temp of 62�C is for Tcase, you add 5�C for core temps, this makes the recommended max core temp 67�C.
I tend to be a bit cautious when it comes to component temps, heat + electronics = trouble.
Staying under this temp, the temps you had, is acceptable but, as mentioned this is a high temp for an AMD CPU.
Monitor the CPU temps when stressing the system, playing games is a good test, they should be max in the high 40's.
Have seen many AMD CPUs run Prime95 in the mid 40's.
Check that the CPU cooler is firmly attached, if you need to take it off it is best to clean and then re-apply the thermal paste.
Information on CPU coolers and thermal paste.
80 Thermal Pastes Tested
Best CPU Cooler Performance AMD Socket AM3 Preview
Yeah, right now, his core temps are idle at 48c and I don't think they've been that way all day, but they may have been.
I'm not sure what the best thermal paste is to go with, I don't have any of the "good" stuff, just some off brand kind from Radio Shack, but I didn't use it on the CPU. The CPU heatsink came with thermal paste pre-applied. I don't think I restarted it after the stress test was done, so maybe it would change after I restarted.
What would be the best thermal paste and would it be available on newegg or something? Or from Best Buy or something like that?
I'm not sure what the best thermal paste is to go with, I don't have any of the "good" stuff, just some off brand kind from Radio Shack, but I didn't use it on the CPU. The CPU heatsink came with thermal paste pre-applied. I don't think I restarted it after the stress test was done, so maybe it would change after I restarted.
What would be the best thermal paste and would it be available on newegg or something? Or from Best Buy or something like that?
Most people here prefer artic silver 5.
+1 on the Artic Silver. Very good stuff.
MAx temp is 62�C, 143.6�F
http://products.amd.com/pages/deskto...ookieSupport=1#
MAx temp is 62�C, 143.6�F
http://products.amd.com/pages/deskto...ookieSupport=1#
MelancholyRose, If you are having temps like that, i would recommend a third party cooler. If you are not going to seriously overclock, you don't need to spend a fortune on one. Just buy something better than the stock cooler. It is no secert that both AMD and Intel put out some not so good stock coolers. Install it right and apply the thermal paste right, you will see a big difference, in temps as well as noise.
Agree with essenbe AS5 is good.
That idle temp is way too high.
It will cool down fast after being under load, several seconds usually, a re-start won't help.
You need to get some new thermal paste, should be able to get AS5 just about anywhere, and clean the cooler and CPU, re-apply the thermal paste and re-seat the cooler.
Too much paste is not good, it can make the temps worse.
Read the 80 Thermal Pastes Tested, it is really good information.
You don't have to read the entire article, any paste on the last page Final Thoughts and Conclusion will do the job, if you can't find AS5.
Read the Application on HDT Coolers page, fill the gaps if your cooler has any, if in doubt use less rather than more.
I use the finger spread method, using plastic film (saran wrap) on my finger, to get a even very thin layer. It should be almost transparent, you are filling tiny holes in the metal, not making a layer of paste between the two metal surfaces.
If after applying the new paste and re-seating the cooler, you see any paste coming out on the sides, you put too much.
In a perfect world, no paste would be necessary, the above link will explain things.
That idle temp is way too high.
It will cool down fast after being under load, several seconds usually, a re-start won't help.
You need to get some new thermal paste, should be able to get AS5 just about anywhere, and clean the cooler and CPU, re-apply the thermal paste and re-seat the cooler.
Too much paste is not good, it can make the temps worse.
Read the 80 Thermal Pastes Tested, it is really good information.
You don't have to read the entire article, any paste on the last page Final Thoughts and Conclusion will do the job, if you can't find AS5.
Read the Application on HDT Coolers page, fill the gaps if your cooler has any, if in doubt use less rather than more.
I use the finger spread method, using plastic film (saran wrap) on my finger, to get a even very thin layer. It should be almost transparent, you are filling tiny holes in the metal, not making a layer of paste between the two metal surfaces.
If after applying the new paste and re-seating the cooler, you see any paste coming out on the sides, you put too much.
In a perfect world, no paste would be necessary, the above link will explain things.
�� Quote: Originally Posted by MelancholyRose Well I ran the stress test for a couple of hours and everything seems nice and smooth. There were no errors or problems. Thanks guys!
I just have to remember to do all of this on my own machine when I get it put back together!
For the record, core temp never once got to 65. It stayed around 62-64.
I just have to remember to do all of this on my own machine when I get it put back together!
For the record, core temp never once got to 65. It stayed around 62-64.
This is good news
after all the stress of the last week I hope it stays running good. I am sure that you will get your own PC up and running quickly. All right, I guess I'll have to order some new paste from Newegg and go buy a bottle of alcohol, too. Possibly some plastic wrap as well to spread it.
I think the pre-applied thermal paste may have been over-applied, too, it looked like a lot when I pulled my own heatsink off of my CPU. It was oozed out around all of the edges, I don't know if it was supposed to do that. So, possibly there may be too much.
I also downloaded some AS5 instructions and had a look over them and saved it for later when I apply the new stuff.
I think the pre-applied thermal paste may have been over-applied, too, it looked like a lot when I pulled my own heatsink off of my CPU. It was oozed out around all of the edges, I don't know if it was supposed to do that. So, possibly there may be too much.
I also downloaded some AS5 instructions and had a look over them and saved it for later when I apply the new stuff.
MelancholyRose,ou can also use coffee filters for cleaning it. They work well also. Wax paper works for plastic wrap or most any type of plastic, like a plastic freezer bag.
Oh, cool. Coffee filters, I have plenty of those, haha.
�� Quote: Originally Posted by MelancholyRose Oh, cool. Coffee filters, I have plenty of those, haha.
Sweet, thanks for the heads up
Rubbing alcohol will work to clean the CPUs/heatsinks, right?
Yes. Just get the highest purity you can., and a lot of elbow grease.
Also, don't put the alcohol on the CPU or HSF, Put it on the cloth, and not enough to where it will run. Just a little at a time. It will work with a lot of rubbing. Get it as clean as possible.
Okay, got it. Thank you. I'll remember that.
One other question: do I apply it only to the cap on the CPU or on the bottom of the heatsink, too? Or only the bottom of the heatsink?
I think applying a single dab of Thermal Paste is the best option:
Apply to the top of CPU and align the Heatsink. Putting the heatsink on will spread the paste effectively.
Its a little hard to see in the vid, but it should be about the same as a pea?
In the vid this is shown at about nine minutes in:
Apply to the top of CPU and align the Heatsink. Putting the heatsink on will spread the paste effectively.
Its a little hard to see in the vid, but it should be about the same as a pea?
In the vid this is shown at about nine minutes in:
+1 Thorsen. Much easier to show how it's done than to try and tell how. Very good.
+1, Nice video Thorsen.
Thanks, Thorsen, very helpful, I gave you some rep for the assistance
Thanks for the rep and glad your system is getting back up and running!
I think it is likely he got more than 1 rep for that great video. I hope it helps you get your system back up and running. Just let us know the results.
I put the Arctic Silver on his CPU just like in the video. He dropped as low as 40c, but that's it. How long does it take before I know it's really working? It's still reaching highs of about 45. No, 47, now, and this is idle temps. It keeps jumping up and down.
Is there a time period I have to wait before I know for certain it's working? I know I put the paste on right. I put a pea-sized drop on top of the CPU and put the heatsink down on top of it. The CPU and heatsink were fully cleaned with isopropyl beforehand. So I know I did everything right.
Note: it looks as if it's trying really hard to drop temps but struggling a little.
Is there a time period I have to wait before I know for certain it's working? I know I put the paste on right. I put a pea-sized drop on top of the CPU and put the heatsink down on top of it. The CPU and heatsink were fully cleaned with isopropyl beforehand. So I know I did everything right.
Note: it looks as if it's trying really hard to drop temps but struggling a little.
Maybe it's not so bad, the temps are still trying to drop, he's reaching 41, now and it's trying hard to continue going down.
I also blew some dust out of his heatsink. I lost visibility for several seconds due to a massive dust cloud.
Right now it's just hanging around 41-42c and not getting any lower. Hopefully that doesn't mean I messed up. I know it should be getting closer to like 37c.
When touching the fans blowing air out, they're less warm than before as well, they're blowing a bit cooler.
I might not be getting ideal temps at the moment, but it's definitely running cooler when idle than it did before. Before on idle it was around 48c, so at least it dropped 6-7 degrees. Could drop some more though.
I also blew some dust out of his heatsink. I lost visibility for several seconds due to a massive dust cloud.
Right now it's just hanging around 41-42c and not getting any lower. Hopefully that doesn't mean I messed up. I know it should be getting closer to like 37c.
When touching the fans blowing air out, they're less warm than before as well, they're blowing a bit cooler.
I might not be getting ideal temps at the moment, but it's definitely running cooler when idle than it did before. Before on idle it was around 48c, so at least it dropped 6-7 degrees. Could drop some more though.
Never mind, I just read these things:
Day-um.
Honestly, though, if his CPU has already dropped 6 degree temps right away, before it's actively effective, that must be some good stuff!
Quote:
Arctic Silver says 200 hrs for maximum effectiveness.
Quote:
For Artic Silver 5 as it's says in the website it usually takes around 2 weeks of 8 hour daily operation to make the thermal compound set and performs at best.
Honestly, though, if his CPU has already dropped 6 degree temps right away, before it's actively effective, that must be some good stuff!
Không có nhận xét nào:
Đăng nhận xét