Getting 2-4 BSODs a day (dmps uploaded)

[dave87]

Hey guys, I would really appericiate it if you could help me.. I used to have BSOD few times a day, so I replaced my HDD thinking that was the problem.. But I still get them.

Here's the message and dumps for the last BSODs:

Download bsods.rar for free on Filesonic.com

Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7601.2.1.0.256.1
Locale ID: 1037

Additional information about the problem:
BCCode: 3b
BCP1: 00000000C0000005
BCP2: FFFFF880010E936F
BCP3: FFFFF8800B4110D0
BCP4: 0000000000000000
OS Version: 6_1_7601
Service Pack: 1_0
Product: 256_1

Files that help describe the problem:
C:\Windows\Minidump\062411-17503-01.dmp
C:\Users\admin\AppData\Local\Temp\WER-33353-0.sysdata.xml

Read our privacy statement online:
Windows 7 Privacy Statement - Microsoft Windows

If the online privacy statement is not available, please read our privacy statement offline:
C:\Windows\system32\en-US\erofflps.txt

I'm really worn out about this.. could it be my ram? I have no idea

 

[usasma]

Please don't use the file upload sites such as FileSonic.com - it's painful to wait for their prompts and then the instructions aren't easy to follow. Here's a link to a tutorial on how to upload stuff here: http://www.sevenforums.com/tutorials/9733-screenshots-files-upload-post-seven-forums.html

Please provide this info for a more complete analysis: http://www.sevenforums.com/crashes-debugging/96879-blue-screen-death-bsod-posting-instructions.html

The memory dumps seem to point to a hardware issue - most likely with the video card or memory. BUT - this could also be a compatibilty/driver/malware problem.

I'd first suggest removing the ATI video driver software from the system.
Then download and install the Driver Only from the ATI website (Advanced Micro Devices)
I'd also update your networking driver simply because it dates from 2009.

Then I'd suggest starting troubleshooting with the following diagnostic tests. They'll save you a lot of time and heartache if there is a hardware failure, and you'll have the disks on hand in case you need them in the future:

H/W Diagnostics:
Please start by running these bootable hardware diagnostics:
Memory Diagnostics (read the details at the link)
HD Diagnostic (read the details at the link)

Also, please run one of these free, independent online malware scans to ensure that your current protection hasn't been compromised: Free Online AntiMalware Resources (read the details at the link)

If all of those pass, then we'll move on to trying these stress tests:

Then, if the above tests pass, I'd try these free stress tests:

FurMark download site: FurMark: VGA Stress Test, Graphics Card and GPU Stability Test, Burn-in Test, OpenGL Benchmark and GPU Temperature | oZone3D.Net
FurMark Setup:
- If you have more than one GPU, select Multi-GPU during setup
- In the Run mode box, select "Stability Test" and "Log GPU Temperature"
Click "Go" to start the test
- Run the test until the GPU temperature maxes out - or until you start having problems (whichever comes first).
NOTE: Set the alarm to go off at 90ºC. Then watch the system from that point on. If the system doesn't display a temperature, watch it constantly and turn it off at the first sign of video problems. DO NOT leave it it unmonitored, it can DAMAGE your video card!!!
- Click "Quit" to exit

Prime95 download site: Free Software - GIMPS
Prime95 Setup:
- extract the contents of the zip file to a location of your choice
- double click on the executable file
- select "Just stress testing"
- select the "Blend" test. If you've already run MemTest overnight please run the "Small FFTs" test instead. (run all 3 if you find a problem and note how long it takes to error out with each)
- "Number of torture test threads to run" should equal the number of CPU's times 2 (if you're using hyperthreading).
The easiest way to figure this out is to go to Task Manager...Performance tab - and see the number of boxes under CPU Usage History
Then run the test for 6 to 24 hours - or until you get errors (whichever comes first).
This won't necessarily crash the system - but check the output in the test window for errors.
The Test selection box and the stress.txt file describes what components that the program stresses.
More details on the use of this test: Torture test your CPU with Prime95

More Video Stress Tests:
1. Thanks to VirGnarus for finding this test: https://simtk.org/home/memtest
2. Two other video stress tests (may be more stressful than FurMark):
Video Memory stress Test - МИРNVIDIA / Утилиты / VMT
Artifact Locator - МИРNVIDIA / Утилиты / Artifact Locator
Sorry, but I don't read the language that this website is made in.
3. Another interesting test that came to my attention: Download - OCCT Website english
USE AT YOUR OWN RISK - the program doesn't have a whole bunch of safety features to protect you from yourself!

CPU Stress Tests:
- http://downloadcenter.intel.com/Detail_Desc.aspx?agr=Y&DwnldID=19182&lang=eng
- 7Byte : Hot CPU Tester Pro
- 7Byte : BurnIn64
- CPU Stress test - Overclock.net - Overclocking.net
- Fossil Free Online CPU Load or Stress Test.
- CPU Stability Test description, System Resources Tune-Up. Downloads List By All Time Popularity | PCWorld | PCWorld
- CPU Stress test - Overclock.net - Overclocking.net
- |MG| CPU Stability Test 6.0 Download
- LinX - A simple Linpack interface

BSOD BUGCHECK SUMMARY

[font=lucida console]
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\062411-17503-01.dmp]
Built by: 7601.17514.amd64fre.win7sp1_rtm.101119-1850
Debug session time: Fri Jun 24 04:19:45.242 2011 (UTC - 4:00)
System Uptime: 0 days 14:48:50.818
Probably caused by : luafv.sys ( luafv!LuafvGenerateFileName+82 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x3B
PROCESS_NAME:  SearchIndexer.
FAILURE_BUCKET_ID:  X64_0x3B_luafv!LuafvGenerateFileName+82
Bugcheck code 0000003B
Arguments 00000000`c0000005 fffff880`010e936f fffff880`0b4110d0 00000000`00000000
BiosVersion = F8
BiosReleaseDate = 04/16/2010
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\062311-16411-01.dmp]
Built by: 7601.17514.amd64fre.win7sp1_rtm.101119-1850
Debug session time: Thu Jun 23 13:29:58.151 2011 (UTC - 4:00)
System Uptime: 0 days 21:39:42.727
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+49e1a )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x18
PROCESS_NAME:  explorer.exe
FAILURE_BUCKET_ID:  X64_0x18_CORRUPT_REF_COUNT_nt!_??_::FNODOBFM::_string_+49e1a
Bugcheck code 00000018
Arguments fffffa80`03a05200 fffffa80`061e14b0 00000000`00000001 00080000`00000000
BiosVersion = F8
BiosReleaseDate = 04/16/2010
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\062211-18096-01.dmp]
Built by: 7601.17514.amd64fre.win7sp1_rtm.101119-1850
Debug session time: Wed Jun 22 15:49:16.589 2011 (UTC - 4:00)
System Uptime: 0 days 7:28:56.181
*** WARNING: Unable to verify timestamp for atikmdag.sys
*** ERROR: Module load completed but symbols could not be loaded for atikmdag.sys
Probably caused by : atikmdag.sys ( atikmdag+3bbf8c )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  csrss.exe
BUGCHECK_STR:  0x7E
FAILURE_BUCKET_ID:  X64_0x7E_atikmdag+3bbf8c
Bugcheck code 1000007E
Arguments ffffffff`c0000005 fffff880`07676f8c fffff880`0b8b2be8 fffff880`0b8b2440
BiosVersion = F8
BiosReleaseDate = 04/16/2010
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\062211-18252-01.dmp]
Built by: 7601.17514.amd64fre.win7sp1_rtm.101119-1850
Debug session time: Wed Jun 22 08:19:50.388 2011 (UTC - 4:00)
System Uptime: 0 days 1:25:53.980
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+46585 )
BUGCHECK_STR:  0x1a_41287
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  httpd.exe
FAILURE_BUCKET_ID:  X64_0x1a_41287_nt!_??_::FNODOBFM::_string_+46585
Bugcheck code 0000001A
Arguments 00000000`00041287 00000000`00e03ff8 00000000`00000000 00000000`00000000
BiosVersion = F8
BiosReleaseDate = 04/16/2010
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\062211-19999-01.dmp]
Built by: 7601.17514.amd64fre.win7sp1_rtm.101119-1850
Debug session time: Wed Jun 22 06:53:25.531 2011 (UTC - 4:00)
System Uptime: 0 days 3:48:34.108
Probably caused by : ntkrnlmp.exe ( nt!KiSystemServiceExit+13f )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x3B
PROCESS_NAME:  wmplayer.exe
FAILURE_BUCKET_ID:  X64_0x3B_nt!KiSystemServiceExit+13f
Bugcheck code 0000003B
Arguments 00000000`c0000005 fffff800`02a85a1a fffff880`0b8ad1d0 00000000`00000000
BiosVersion = F8
BiosReleaseDate = 04/16/2010
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\062211-15553-01.dmp]
Built by: 7601.17514.amd64fre.win7sp1_rtm.101119-1850
Debug session time: Wed Jun 22 03:04:15.173 2011 (UTC - 4:00)
System Uptime: 0 days 14:33:50.749
Probably caused by : dxgmms1.sys ( dxgmms1!VidSchIsWorkerThread+0 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x3B
PROCESS_NAME:  csrss.exe
FAILURE_BUCKET_ID:  X64_0x3B_dxgmms1!VidSchIsWorkerThread+0
Bugcheck code 0000003B
Arguments 00000000`c0000005 fffff880`06e0ef9c fffff880`03e589d0 00000000`00000000
BiosVersion = F8
BiosReleaseDate = 04/16/2010
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\062111-17799-01.dmp]
Built by: 7601.17514.amd64fre.win7sp1_rtm.101119-1850
Debug session time: Tue Jun 21 07:23:39.483 2011 (UTC - 4:00)
System Uptime: 0 days 0:16:52.685
Probably caused by : ntkrnlmp.exe ( nt!ObInsertObjectEx+87 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x3B
PROCESS_NAME:  explorer.exe
FAILURE_BUCKET_ID:  X64_0x3B_nt!ObInsertObjectEx+87
Bugcheck code 0000003B
Arguments 00000000`c0000005 fffff800`02dd2777 fffff880`09085790 00000000`00000000
BiosVersion = F8
BiosReleaseDate = 04/16/2010
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\062111-18220-01.dmp]
Built by: 7601.17514.amd64fre.win7sp1_rtm.101119-1850
Debug session time: Tue Jun 21 07:05:47.709 2011 (UTC - 4:00)
System Uptime: 0 days 2:35:40.285
Probably caused by : Ntfs.sys ( Ntfs!NtfsExtendedCompleteRequestInternal+e5 )
BUGCHECK_STR:  0x1E_c0000005
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  svchost.exe
FAILURE_BUCKET_ID:  X64_0x1E_c0000005_Ntfs!NtfsExtendedCompleteRequestInternal+e5
Bugcheck code 0000001E
Arguments ffffffff`c0000005 fffff880`01223e55 00000000`00000000 ffffffff`ffffffff
BiosVersion = F8
BiosReleaseDate = 04/16/2010
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
  
  [/font]