Multiple BSODs

Ran · 13 May 2011

Okay, when I went back into the bios to change the ram settings I couldn't find them, but did find out what voltages 'auto' was assigning.
CPU Min: .8V Max: "By CPU"
DRAM: 1.5-2.5V
NB: 1.3-1.6V (Googling led me to believe that North Bridge was the same as CPU Integrated Memory Controller)

Edit: I completely uninstalled and then reinstalled my video drivers, but "Windows cannot start this hardware device because its configuration information (in the registry) is incomplete or damaged. (Code 19)" is shown in the device manager. I uninstalled everything again and reinstalled, but am still having the same problem.

mgorman87 · 13 May 2011

Ran said:

Okay, when I went back into the bios to change the ram settings I couldn't find them, but did find out what voltages 'auto' was assigning.
CPU Min: .8V Max: "By CPU"
DRAM: 1.5-2.5V
NB: 1.3-1.6V (Googling led me to believe that North Bridge was the same as CPU Integrated Memory Controller)

Edit: I completely uninstalled and then reinstalled my video drivers, but "Windows cannot start this hardware device because its configuration information (in the registry) is incomplete or damaged. (Code 19)" is shown in the device manager. I uninstalled everything again and reinstalled, but am still having the same problem.

That's happens sometimes when using driver sweeper. The only way that I know to fix that is to do a Repair Install

Read this first before you try the repair install
http://technet.microsoft.com/en-us/l...8WS.10%29.aspx

Ran · 15 May 2011

Wow... that was extremely annoying, after 18 hours of my computer trying to uninstall sp1, it failed. I was going to restore with paragon, but for some reason my external hd did not show up in explorer even though it did in devices/printers and in device manager... Instead, I just used system restore and now its working.

I ran furmark for around 30 min. FPS averaged at around 14, temp started at 45 maxed at 56, and then went back down after about 20 min. I did not see any artifacts or anything, just lowered FPS for the rest of the computer.

Dave76 · 15 May 2011

To check your voltages in BIOS, select the CPU/NB voltage (this is the integrated memory controller), in the right screen it should tell you the options.
You might have to select manual, or the smallest increase to get a voltage reading.

Check the CPU/NB voltage and DRAM voltage.

Ran · 15 May 2011

Okay, I was able to increment up and heres the voltages:
CPU and CPU/NB: .8V
DRAM: 1.5V
NB: 1.3V

So, those were the minimum voltages.
This is kinda an example of the settings
DRAM [Auto] - 1.5V - 1.75V -....... - 2.5V

So I really can't tell you how much voltage everything is getting. Are the minimums enough?

Dave76 · 16 May 2011

Tell me if the CPU/NB and DRAM voltages have set voltages or increases (+0.200v).

Should be voltage settings, actual number to select.

Change the CPU/NB voltage to 1.20v, default setting should be 1.100v.
Change the Dram voltage to 1.550v.

This will help stability, and a good way to check if this is contributing to the crashes.
Run memtest86+ again, overnight, I know you have ran it several times with no errors but, this is a good test for the new settings and it is still possible that the RAM might throw up an error.

If memtest86+ passes then run Prime95 torture test.
First open Core Temp to monitor CPU temperatures, don't go over 71°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.

Ran · 19 May 2011

Sorry it took me a while. Well, I changed the voltages, and ran the tests. There were no errors, and have been no bsods since the last ones I posted. I can not think of anything that I have done that would have fixed the problem, other than maybe windows update installing something. Because of this, I am tempted to redownload a virtual machine, although, they have seemed to caused me a lot of trouble. The thing is, I got the highest amount of bsods AFTER I had restored my computer to a point before I had installed VMware, and they have seemed to magically stop.

Dave76 · 23 May 2011

Thanks for the update.

Glad to hear it's running stable.

Let us know if it crashes again.

Ran · 28 May 2011

Thank you guys for the help so far, but the bsods are back. I installed vmware again like I said, and had no problems for a week, but I recently have been getting more bsods.... There is nothing that I can think of doing that would have triggered them, and I am again lost.

I had backed up my computer when I had not installed vmware, and it seemed to be working fine, and so I restored it to that point when I got the first bsods. Although, even after the restore I am still having problems.

mgorman87 · 28 May 2011

Time to enable driver verifier again
Driver Verifier - Enable and Disable

Run a system file check - SFC /SCANNOW Command - System File Checker

Also run a hard drive scan usings SeaTools - SeaTools for Windows | Seagate - Both long and short tests

BSOD BUGCHECK SUMMARY

Code:


Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631
Debug session time: Sat May 28 18:42:08.460 2011 (UTC - 4:00)
System Uptime: 0 days 10:43:02.021
Probably caused by : Ntfs.sys ( Ntfs!NtfsNonCachedIo+4b6 )
PROCESS_NAME:  svchost.exe
ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
BUGCHECK_STR:  0x24
FAILURE_BUCKET_ID:  X64_0x24_Ntfs!NtfsNonCachedIo+4b6
BiosReleaseDate = 08/20/2010
SystemManufacturer = System manufacturer
SystemProductName = System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631
Debug session time: Fri May 27 18:36:30.296 2011 (UTC - 4:00)
System Uptime: 0 days 0:00:10.857
Probably caused by : rdyboost.sys ( rdyboost!SmdMdlAllocate+31 )
ERROR_CODE: (NTSTATUS) 0 - STATUS_WAIT_0
BUGCHECK_STR:  0x1E_0
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x1E_0_rdyboost!SmdMdlAllocate+31
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631
Debug session time: Fri May 27 18:31:58.042 2011 (UTC - 4:00)
System Uptime: 0 days 1:34:04.603
Probably caused by : ntkrnlmp.exe ( nt!ExpReleaseResourceForThreadLite+46 )
ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
BUGCHECK_STR:  0x1E_c0000005
PROCESS_NAME:  WerFault.exe
FAILURE_BUCKET_ID:  X64_0x1E_c0000005_nt!ExpReleaseResourceForThreadLite+46
BiosReleaseDate = 08/20/2010
SystemManufacturer = System manufacturer
SystemProductName = System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631
Debug session time: Fri May 27 16:56:50.526 2011 (UTC - 4:00)
System Uptime: 0 days 0:00:39.697
Probably caused by : ntkrnlmp.exe ( nt!ExpReleaseResourceForThreadLite+46 )
BUGCHECK_STR:  0x3B
PROCESS_NAME:  explorer.exe
FAILURE_BUCKET_ID:  X64_0x3B_nt!ExpReleaseResourceForThreadLite+46
BiosReleaseDate = 08/20/2010
SystemManufacturer = System manufacturer
SystemProductName = System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``