Multiple BSODs

[Ran]

I actually ended up running memtest for 16 hours haha. There were no errors, so I'll run prime later on. Heres the full bsod report thing.....

Edit: Had some more bsods and trouble starting up again. I'm running prime now and will let you know how it goes. Thank you for your help.

 

[mgorman87]

Continue with the three Prime95 tests and report back the results. It's definitely a hardware issue but I'm not sure which piece of hardware. What type of power supply do you have?

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


BSOD BUGCHECK SUMMARY

[font=lucida console]
Built by: 7601.17514.amd64fre.win7sp1_rtm.101119-1850
Debug session time: Sun May  8 11:59:28.803 2011 (UTC - 4:00)
System Uptime: 0 days 0:10:50.989
Probably caused by : fileinfo.sys ( fileinfo!FIPfInterfaceOpen+714 )
DRIVER_VERIFIER_DETECTED_VIOLATION (c4)
BUGCHECK_STR:  0xc4_13e
DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
PROCESS_NAME:  svchost.exe
FAILURE_BUCKET_ID:  X64_0xc4_13e_VRFK_fileinfo!FIPfInterfaceOpen+714
BiosReleaseDate = 08/20/2010
SystemManufacturer = System manufacturer
SystemProductName = System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17514.amd64fre.win7sp1_rtm.101119-1850
Debug session time: Sun May  8 11:30:48.267 2011 (UTC - 4:00)
System Uptime: 0 days 0:02:36.454
Probably caused by : ntkrnlmp.exe ( nt!KiKernelCalloutExceptionHandler+e )
BUGCHECK_STR:  0x1E_0
DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x1E_0_VRFK_nt!KiKernelCalloutExceptionHandler+e
BiosReleaseDate = 08/20/2010
SystemManufacturer = System manufacturer
SystemProductName = System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17514.amd64fre.win7sp1_rtm.101119-1850
Debug session time: Sun May  8 11:27:41.324 2011 (UTC - 4:00)
System Uptime: 0 days 3:33:53.886
Probably caused by : memory_corruption ( nt!MiCheckSpecialPoolSlop+83 )
BUGCHECK_STR:  0xC1_32
DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
PROCESS_NAME:  audiodg.exe
FAILURE_BUCKET_ID:  X64_0xC1_32_VRFK_nt!MiCheckSpecialPoolSlop+83
BiosReleaseDate = 08/20/2010
SystemManufacturer = System manufacturer
SystemProductName = System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
  
[/font]

 

[Ran]

I have a corsair 450w power supply. This is it specifically: Link

Edit: My hard drive passed sea tools short and long generic tests. It did show up twice, so I scanned both of them.

Edit 2: All three of the prime tests were successful for 3 hours each. Unfortunately, all these passes are no help at solving the problem :/
And again, thank you for your help its really appreciated.

 

[Ran]

Okay, so my computer passed all the tests, and I haven't had any more bsods since the last ones I posted. I am not sure what to do really, because I do not like driver verifier on, because of how much it slows my computer, but I also want to take care of this problem, instead of ignoring it till it is a problem again. Do you have any advice? Like tests I could run, or other things to try?

 

[Jonathan_King]

Hello,

Please run Memtest86 from a cold boot. There is no need to run 7 passes or anything this time; 15 minutes should suffice.

 

[Dave76]

Cold boot BSoDs can be caused by RAM, sometimes it can be fixed with adjustments.

Just because memtest86+ shows no errors doesn't mean the RAM is 100% and not at fault. It is the best test available but, that is how electronics are, fickle at times.

Do you have or can you borrow other RAM to test with?

How many times did you run memtest86+?
Which test did you get to?

With some information we can try a few adjustments.
D/L CPUZ and post a snip of the CPU, Mainboard, Memory, and SPD tabs.

For posting the information , enter 'Snipping tool' in the Start button > Search box, hit enter. Select the area you want to post and save to a convenient place.
How to Post a Screenshot in Seven Forums


Have you been checking your temperatures?

Use Core Temp, to check the CPU temps when at idle, under load and/or testing.
Let us know the minimum and maximum temps you get.
Go to your BIOS and tell us what the CPU, RAM and the CPU integrated memory controller voltages are.

 

[Ran]

I do have RAM that I could steal from another of our computers, but it is a different brand.

I have run memtest 3 times now first was 2 passes, the second was 7 or 8, and this last time I just let it run overnight for 16 hours, so it probably went through quite a few passes. (all with no errors) Tomorrow morning I can run memtest for a few min on a cold boot.

My temp stayed at about 34-36 last time I ran prime tests according to Everest. I downloaded coretemp, and while I have been typing this, its ranged from 26-34. I'll stress my computer some and see how high it gets.

I will update this with more info as i get it.

Edit: Ran memtest on a cold boot for 20 min w/o any errors.
Attached the cpuz pictures.
ALL voltage settings were on auto by default in the BIOS

 

[Dave76]

All the RAM settings look good, only thing that might help is going to the BIOS RAM timings and change the 'Command Rate' from 1T to 2T.
Are your two RAM cards an exact match, buy them in a set at the same time?

Can you go to your BIOS and tell us what the CPU, RAM and the CPU integrated memory controller voltages are?

With the hardware tests, memtest86+, chkdisk, Prime95, all passing the basic tests are done, below are some more testing you can try. If none of these stop the crashes then you will need to do hardware replacement testing.
I would start with the RAM.

Did you install SP1?
Install all Windows updates?

Download and run Malwarebytes, be sure to update it before running.

Can you also run a system file check and report the results -
SFC /SCANNOW Command - System File Checker

Have updated or re-installed you graphics driver?

To have both the latest drivers and CCC:
•Download and install Driver Sweeper from:
Guru3D - Driver Sweeper

• Uninstall ATI Catalyst Install Manager from "Control Panel\Programs\Programs and Features"

(If Catalyst Install manager is not installed, uninstall the drivers through device manager)

Go to Control Panel\View by: Small/Large icons\Device manager. In Device manager select Display Adapters :

•In Display Adapters right-click on your device and select uninstall. Tick the box that says "Delete the driver software for this device"

• Re-Boot into Safe Mode and run Driver Sweeper (to ensure complete removal of items, Run Driver Sweeper as admin. "Right-click Driver Sweeper > properties > Compatibility tab tick 'Run this program as Administrator' "

• In Driver Sweeper select the ATI- Display only and then Analyse:

• Now select Clean to remove all ATI software:

Re-boot normally and install the newest official drivers.

Then run Video Card - Stress Test with Furmark - Watch the GPU temps, don't go over 90°C, run for 30 minutes minimum.

Take these one at a time and let us know the results.

 

[Ran]

I will update this post again as I do everything.

I actually have not had a bsod for four days now, and haven't been doing anything differently that I know of. Although, I still do want to find the problem.
Yes, both sticks of RAM are the exact same kind.
When I checked the voltages in the bios last time, everything was set to [Auto].
I have sp1 installed and everything that windows update has presented me with.

Also, I went to download driver sweeper, but download page said "Attention - Guru3D Driver Sweeper has been discontinued as such you will not find any download links here any longer"

Edit: SFC found no "integrity violations"
Edit2: Malware bytes found two PUP.SmsPay.PGen files in the recycle bin, but thats all

 

[Dave76]

Thanks for the update.

You can get Driver Sweeper at this new link, also changed above, Guru3D - Driver Sweeper

Let us know your progress.

 

[Ran]

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]

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 http://www.sevenforums.com/tutorials/3413-repair-install.html

Read this first before you try the repair install
http://technet.microsoft.com/en-us/library/cc772156(WS.10).aspx

 

[Ran]

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]

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]

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]

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]

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]

Thanks for the update.

Glad to hear it's running stable.

Let us know if it crashes again.

 

[Ran]

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]

Time to enable driver verifier again
http://www.sevenforums.com/tutorials/101379-driver-verifier-enable-disable.html

Run a system file check - http://www.sevenforums.com/tutorials/1538-sfc-scannow-command-system-file-checker.html

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





BSOD BUGCHECK SUMMARY

[font=lucida console]
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
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
  
[/font]