BSOD and Error Help

rwtimmons · Jun 6, 2011

Files are attached per instructions.

I have saved a string of the memory dump files for different occurances. There should be 11 total, but if the program only picked up the one I will post the others.

Windows 7
x64
Original install
System Builder Version
System built May 2010 with all new parts
OS was installed in May 2010
All updates, sans some "recomended" updates, installed

usasma · Jun 11, 2011

The MSINFO32 file in the uploaded reports is corrupt. Not unusual, but I rely on this report. Please do the following:

MSINFO32:
Please go to Start and type in "msinfo32.exe" (without the quotes) and press Enter
Save the report as an .nfo file, then zip up the .nfo file and upload/attach the .zip file with your next post. Also, save a copy as a .txt file and include it also (it's much more difficult to read, but we have greater success in getting the info from it).

If you're having difficulties with the format, please open an elevated (Run as administrator) Command Prompt and type "msinfo32 /nfo C:\Users\Public\Desktop\TEST.NFO" (without the quotes) and press Enter. Then navigate to the C:\Users\Public\Desktop directory to retrieve the TEST.NFO file. If you have difficulties with making this work, please post back.

All of the BSOD errors are STOP 0x1A - Memory Management errors. Please follow the directions here to run a free memory diagnostic test: Memory Diagnostics (read the details at the link)

If the memory test passes, then please run Driver Verifier according to these directions:

Code:
Using Driver Verifier is an iffy proposition. Most times it'll crash and it'll tell you what the driver is. But sometimes it'll crash and won't tell you the driver. Other times it'll crash before you can log in to Windows. If you can't get to Safe Mode, then you'll have to resort to offline editing of the registry to disable Driver Verifier.

So, I'd suggest that you first backup your stuff and then make sure you've got access to another computer so you can contact us if problems arise. Then make a System Restore point (so you can restore the system using the Vista/Win7 Startup Repair feature).

Then, here's the procedure:
- Go to Start and type in "verifier" (without the quotes) and press Enter
- Select "Create custom settings (for code developers)" and click "Next"
- Select "Select individual settings from a full list" and click "Next"
- Select everything EXCEPT FOR "Low Resource Simulation" and click "Next"
NOTE: You can use Low Resource Simulation if you'd like. From my limited experimentation it makes the BSOD's come faster.
- Select "Select driver names from a list" and click "Next"
Then select all drivers NOT provided by Microsoft and click "Next"
- Select "Finish" on the next page.

Reboot the system and wait for it to crash to the Blue Screen. Continue to use your system normally, and if you know what causes the crash, do that repeatedly. The objective here is to get the system to crash because Driver Verifier is stressing the drivers out. If it doesn't crash for you, then let it run for at least 36 hours of continuous operation (an estimate on my part).

Reboot into Windows (after the crash) and turn off Driver Verifier by going back in and selecting "Delete existing settings" on the first page, then locate and zip up the memory dump file and upload it with your next post.

If you can't get into Windows because it crashes too soon, try it in Safe Mode.
If you can't get into Safe Mode, try using System Restore from your installation DVD to set the system back to the previous restore point that you created.

If that doesn't work, post back and we'll have to see about fixing the registry entry off-line:

Code:

Delete these registry keys (works in XP, Vista, Win7): HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\VerifyDrivers HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\VerifyDriverLevel

More info on this at this link: Using Driver Verifier to identify issues with Windows drivers for advanced users

BSOD BUGCHECK SUMMARY

Code:

[font=lucida console]
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\060611-29640-01.dmp]
Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631
Debug session time: Mon Jun  6 10:16:52.956 2011 (UTC - 4:00)
System Uptime: 0 days 0:00:28.939
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+36024 )
BUGCHECK_STR:  0x1a_41790
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  svchost.exe
FAILURE_BUCKET_ID:  X64_0x1a_41790_nt!_??_::FNODOBFM::_string_+36024
Bugcheck code 0000001A
Arguments 00000000`00041790 fffffa80`0239b920 00000000`0000ffff 00000000`00000000
BiosVersion = FE
BiosReleaseDate = 12/23/2010
CPUID:        "Intel(R) Core(TM) i7 CPU         930  @ 2.80GHz"
MaxSpeed:     2800
CurrentSpeed: 2798
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\060611-27861-01.dmp]
Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631
Debug session time: Mon Jun  6 09:55:00.355 2011 (UTC - 4:00)
System Uptime: 0 days 0:05:31.338
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+36024 )
BUGCHECK_STR:  0x1a_41790
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  avgmfapx.exe
FAILURE_BUCKET_ID:  X64_0x1a_41790_nt!_??_::FNODOBFM::_string_+36024
Bugcheck code 0000001A
Arguments 00000000`00041790 fffffa80`012f9de0 00000000`0000ffff 00000000`00000000
BiosVersion = FE
BiosReleaseDate = 12/23/2010
CPUID:        "Intel(R) Core(TM) i7 CPU         930  @ 2.80GHz"
MaxSpeed:     2800
CurrentSpeed: 2798
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\052911-22027-01.dmp]
Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631
Debug session time: Mon May 30 00:54:59.271 2011 (UTC - 4:00)
System Uptime: 0 days 6:41:03.255
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+36024 )
BUGCHECK_STR:  0x1a_41790
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  nTuneCmd.exe
FAILURE_BUCKET_ID:  X64_0x1a_41790_nt!_??_::FNODOBFM::_string_+36024
Bugcheck code 0000001A
Arguments 00000000`00041790 fffffa80`022df220 00000000`0000ffff 00000000`00000000
BiosVersion = FE
BiosReleaseDate = 12/23/2010
CPUID:        "Intel(R) Core(TM) i7 CPU         930  @ 2.80GHz"
MaxSpeed:     2800
CurrentSpeed: 2798
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\052811-31527-01.dmp]
Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631
Debug session time: Sat May 28 12:37:31.554 2011 (UTC - 4:00)
System Uptime: 0 days 0:05:39.538
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+36024 )
BUGCHECK_STR:  0x1a_41790
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  avgmfapx.exe
FAILURE_BUCKET_ID:  X64_0x1a_41790_nt!_??_::FNODOBFM::_string_+36024
Bugcheck code 0000001A
Arguments 00000000`00041790 fffffa80`01dd8220 00000000`0000ffff 00000000`00000000
BiosVersion = FE
BiosReleaseDate = 12/23/2010
CPUID:        "Intel(R) Core(TM) i7 CPU         930  @ 2.80GHz"
MaxSpeed:     2800
CurrentSpeed: 2798
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\052411-18798-01.dmp]
Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631
Debug session time: Tue May 24 09:26:54.884 2011 (UTC - 4:00)
System Uptime: 0 days 0:00:51.868
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+36024 )
BUGCHECK_STR:  0x1a_41790
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  Skype.exe
FAILURE_BUCKET_ID:  X64_0x1a_41790_nt!_??_::FNODOBFM::_string_+36024
Bugcheck code 0000001A
Arguments 00000000`00041790 fffffa80`023c06a0 00000000`0000ffff 00000000`00000000
BiosVersion = FE
BiosReleaseDate = 12/23/2010
CPUID:        "Intel(R) Core(TM) i7 CPU         930  @ 2.80GHz"
MaxSpeed:     2800
CurrentSpeed: 2798
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
  
  [/font]

rwtimmons · Jun 12, 2011

Here are the sysinfo files. I am currently running the driver verifier. I will follow your instructions when I get a BSOD. Though it has not crashed yet I am getting graphical anomalies on the windows I open and on the taskbar. I will run some games and see if it persists in heavy use of the Vid Card.

Thank you very much for your help!

rwt

usasma · Jun 12, 2011

Lot's of STOP 0x117 errors in the MSINFO32 report. They are troubleshot the same way as STOP 0x116 errors, so please follow the steps here: http://www.sevenforums.com/crash-lo...op-0x116-video_tdr_error-troubleshooting.html

You may want to try these free video 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

Click to expand...

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!

Click to expand...

rwtimmons · Jun 12, 2011

I don't believe heat is an issue as the GPU temp rarely goes above 65 C. My understanding is that is a reasonable number for this GPU.

I have also ran memtest for at least 5 passes and encountered no errors.

I will also do the video stress tests and let you know how those go.

rwt

rwtimmons · Jun 12, 2011

I ment to ask...

are the video tests testing specifically video memory and not system memory?

rwt

usasma · Jun 13, 2011

In general, yes they are testing video memory rather than system memory. But you've got to read the documentation for each test to see actually what they're stressing. MemTest tests memory by running different standard patterns and looks for problems, stress testing stresses the system/component and looks for failures in that component.

I've got a story to tell about video temps. A couple of years ago we had a new system on the bench for testing. It had video issues. I ran tests on the video card and it showed normal temps (around 75ºC). Yet the system still persisted in having video issues.

So, being curious, I started to fuss around inside the case (checking connections, pulling/tugging on parts, etc). When I touched the video card I severely burnt my fingers! (and said several bad words!). We pointed a fan at the video card and the video issues stopped - so we replaced the video card and the customer went home happy!

So, we look for video issues when running stress tests - and that's a clue that there may be something wrong with the video card. When we run FurMark we run it until the GPU temperature stabilizes (usually in the 90ºC range) and look for video issues while it's doing this.

rwtimmons · Jun 16, 2011

Hello,

Thanks again for all your help. There was another crash on the 13th while my wife was using the computer. I have attached the minidump, but the main dump file was too big to upload even zipped.

I tried to run prime95, but seemed to have some problems though I am not sure if they are related to the driver verifier running at the time.

usasma · Jun 18, 2011

What issues are you having with Prime95? Have you run Furmark?

The memory dump is a Driver Verifier Enabled memory dump blaming nvoclk64.sys -
- Are you overclocking your system/video card? If so, stop and reset the system to default values
- Then, uninstall the nvoclk64.sys driver software (which dates from 2009). This is most likely a component of nVidia System Tools or System Monitor and there is no newer version available. It's most likely a part of one of these program groups:

Start Menu\Programs\NVIDIA Corporation\3D Vision Public:Start Menu\Programs\NVIDIA Corporation\3D Vision Public

Start Menu\Programs\NVIDIA Corporation\NVIDIA Control Panel Public:Start Menu\Programs\NVIDIA Corporation\NVIDIA Control Panel Public

Start Menu\Programs\GIGABYTE\GIGABYTE VGA @BIOS Timmons-PC\Robby:Start Menu\Programs\GIGABYTE\GIGABYTE VGA @BIOS Timmons-PC\Robby

NVIDIA System Monitor "c:\program files (x86)\nvidia corporation\nvidia system monitor\nvmonitor.exe" startup Timmons-PC\Robby Startup

- Turn off Driver Verifier
- Test for further BSOD's

rwtimmons · Jun 18, 2011

My memory speed and timings are the only OC that I have. The MB is 1066 and I OC to the memory spec of 1333. The video card is factory over clocked from Gigabyte. Should I try and set the stock specs on the video card?

I turned off Driver Verifier and reran Prime95. Prime95 worked correctly, as far as I can tell. The CPU temps jumped to over 90 C, in less than a min and I terminated the program. There were no reported errors. I was not comfortable running the test for any length of time with the temps at those levels. Should I do anymore with Prime95?

I have run FurMark a couple of times. Without MSAA the temp would get up to 86 C after about 5 min and then level off. With MSAA the temp was slower to rise but did eventually make it up to about the same temp before stabalizing. The avg FPS were 22 and 14 respectively. The GPU fan speed was 93% at the hottest GPU temps. I never noticed any errors during the tests.

Given some of the randomness of my issues it is possible my sys memory is faulty, but the memtest couldn't pick it up? If you don't think so then could a faulty video card cause these types of issues as many of the errors involve drivers related to the video card?

The reason I am working through all this is because I don't want to do an RMA if I am not really sure which component is the issue. The Nvidia 400/500 series lockup club! - NVIDIA Forums - this thread describes some of the issues I have been having, but often not to the extreme described by other users. If you choose to read through I would value your opinion on my situation in relation to the thread claims.

Kind regards,

rwt

usasma · Jun 18, 2011

I suspect that the video card is overheating. Ensure that you have a temperature monitor running at all times in order to see what it is when the system acts up.

Set your memory to 1066 and leave the video card alone for now.
If the system starts to give issues, try pointing a house fan inside the case to cool down the video card.

rwtimmons · Jul 19, 2011

So I have been busy lately and have not taken the time to trouble shoot more until recently. I hope you will see this post and get back to me.

I have been trying to run the blend test on Prime95, but it stops after less than a minute of testing. I have attached the log file maybe it will mean more to you than me.

I ran the other two tourture tests and was able to run them for quite a while with no errors ever showing up.

Any ideas?

Thanks!

usasma · Jul 20, 2011

Sorry for any confusion, but my eye problems are getting worse as each day passes.
When running Prime95 your CPU jumped to 90ºC within a minute? You need to check the cooling solution for your CPU immediately. Check the fan for operation, check the cooler for any clogs/dust bunnies, and finally check the CPU to ensure that it has the correct amount of thermal compound between it and the cooler. Please post back with your results.

Did you run Prime95 with the Small FFT test and the Large FFT test?
If so, and you had no further errors, then the issue is most likely memory.
If it wasn't Prime95, what were the names/links for the other 2 tests that you ran?

But, with the overheating of the CPU, it can be the CPU component of the memory interface that's shutting down and stopping the Prime95 test.

I quickly read over the link that you provided (for the nVidia problem) - and I must conclude that the most effective fix is to get another video card that doesn't have that problem (But I'm battling EventViewer SPAM from my ATI card's drivers right now - so I don't know what to suggest!)

So, we're looking at:
- RAM issues
- video issues
- CPU issues (maybe mobo)

rwtimmons · Jul 20, 2011

I am sorry to hear about your eye problems. I hope you can find some help and have your vision restored.

Well, I went and bought some different memory (same speed different brand and only 4 gb) and reran the Prime95 blend test. This time I was able to get through multiple tests with no errors. So, I think my RAM is bad.

I am going to continue testing to verify the RAM was the issue and not the video card.

Thanks again for your help...and I promise to get a CPU cooler!

rwt

rwtimmons · Oct 9, 2011

So I am back to having problems. I did have a bad stick of memory so got a new set from the manufacturer. The system was much more stable but now I am getting an occational BSOD.

Prime95 runs fine, Memtest shows no errors, and I only seem to be having problems when the computer comes out of sleep mode. The computer sleeps after 30 min and sometimes when I attempt to wake it I get a BSOD. I recently reinstalled Windows 7 again because I was getting some file corruption messages. I did a clean install, not just a repair.

In the BIOS I have disabled HPET (though this didn't seem to have any effect except slightly less latency), CPU Enhanced Halt and C3/C6/C7 State Support.

After the install I have waited to install some drivers of components I am not using often. I am also waiting to install most programs because I don't want to have to redo everything multiple times if I end up having to reload Windows again.

I have attached the files, so any insight you can give would be helpful.

rwt

usasma · Oct 9, 2011

NOTE: I have severe eye problems. If I do not respond to your postings, please PM another staff member for assistance.

USB, Ethernet, and Marvell Storage controller drivers are not installed. The Storage controller drivers can cause the BSOD when resuming from sleep - and I'm starting to suspsect that the Ethernet stuff may be involved in sleep transitions also. USB drivers involve your chipset - and those are involved in sleep transitions also.

Windows Update is disabled. Please enable it and get all available updates.

The BSOD's show I/O errors (likely hardware) and memory access errors (likely a driver). Most likely this is a low-level issue (such as malware) - but we can't rule out hardware.

Please run the hard drive test and the CPU stress test (along with any other tests that you haven't run). This includes a malware test - looking for things like the TDSS rootkit that hides in the partition table (so that even a format won't get rid of it).:

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) - Test ALL of the hard drives.

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)
There are also free, bootable antivirus disks at this link: Free Online AntiMalware Resources - Bootable Disks

Click to expand...

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!!!
If the temperature gets above 100ºC, quit the test - the video card is overheating.
- Click "Quit" to exit

Click to expand...

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).
Monitor the CPU temperature and DON'T let it exceed 85ºC. If it does, then you probably have a CPU cooling problem.
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

Click to expand...

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):
NOTE: I have had reports that some ISP's will block this website
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!

Click to expand...

CPU Stress Tests:
Only need to run 1 or 2 of the tests under most circumstances. I haven't used any of the tests myself, so I listed all that I was able to find.
- 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
- the test(s) suggested at this link are bootable: Headless CPU Stress Testing - Tech Support Forum

Click to expand...

BSOD BUGCHECK SUMMARY

Code:

[font=lucida console]
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\100911-18578-01.dmp]
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Sun Oct  9 14:22:32.559 2011 (UTC - 4:00)
System Uptime: 1 days 4:21:22.614
BugCheck F4, {3, fffffa80077c9060, fffffa80077c9340, fffff80002f848b0}
Probably caused by : wininit.exe
PROCESS_NAME:  wininit.exe
BUGCHECK_STR:  0xF4_IOERR
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
FAILURE_BUCKET_ID:  X64_0xF4_IOERR_IMAGE_wininit.exe
Bugcheck code 000000F4
Arguments 00000000`00000003 fffffa80`077c9060 fffffa80`077c9340 fffff800`02f848b0
BiosVersion = FE
BiosReleaseDate = 12/23/2010
CPUID:        "Intel(R) Core(TM) i7 CPU         930  @ 2.80GHz"
MaxSpeed:     2800
CurrentSpeed: 2798
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\100811-17581-01.dmp]
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Sat Oct  8 08:43:36.793 2011 (UTC - 4:00)
System Uptime: 0 days 4:43:55.761
BugCheck F4, {3, fffffa8006942950, fffffa8006942c30, fffff80002f808b0}
Probably caused by : csrss.exe
PROCESS_NAME:  csrss.exe
BUGCHECK_STR:  0xF4_C0000005
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
FAILURE_BUCKET_ID:  X64_0xF4_C0000005_IMAGE_csrss.exe
Bugcheck code 000000F4
Arguments 00000000`00000003 fffffa80`06942950 fffffa80`06942c30 fffff800`02f808b0
BiosVersion = FE
BiosReleaseDate = 12/23/2010
CPUID:        "Intel(R) Core(TM) i7 CPU         930  @ 2.80GHz"
MaxSpeed:     2800
CurrentSpeed: 2798
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\100811-17674-01.dmp]
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Sat Oct  8 03:58:32.078 2011 (UTC - 4:00)
System Uptime: 0 days 4:52:57.046
BugCheck F4, {3, fffffa80077fcb30, fffffa80077fce10, fffff80002f8e8b0}
Probably caused by : csrss.exe
PROCESS_NAME:  csrss.exe
BUGCHECK_STR:  0xF4_C0000005
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
FAILURE_BUCKET_ID:  X64_0xF4_C0000005_IMAGE_csrss.exe
Bugcheck code 000000F4
Arguments 00000000`00000003 fffffa80`077fcb30 fffffa80`077fce10 fffff800`02f8e8b0
BiosVersion = FE
BiosReleaseDate = 12/23/2010
CPUID:        "Intel(R) Core(TM) i7 CPU         930  @ 2.80GHz"
MaxSpeed:     2800
CurrentSpeed: 2798
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\100711-19312-01.dmp]
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Fri Oct  7 22:13:16.932 2011 (UTC - 4:00)
System Uptime: 3 days 6:07:39.869
BugCheck F4, {3, fffffa800b238630, fffffa800b238910, fffff80002fde8b0}
Probably caused by : csrss.exe
PROCESS_NAME:  csrss.exe
BUGCHECK_STR:  0xF4_C0000005
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
FAILURE_BUCKET_ID:  X64_0xF4_C0000005_IMAGE_csrss.exe
Bugcheck code 000000F4
Arguments 00000000`00000003 fffffa80`0b238630 fffffa80`0b238910 fffff800`02fde8b0
BiosVersion = FE
BiosReleaseDate = 12/23/2010
CPUID:        "Intel(R) Core(TM) i7 CPU         930  @ 2.80GHz"
MaxSpeed:     2800
CurrentSpeed: 2798
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\100411-16910-01.dmp]
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Tue Oct  4 16:04:46.224 2011 (UTC - 4:00)
System Uptime: 0 days 3:36:33.176
BugCheck F4, {3, fffffa800c00d8b0, fffffa800c00db90, fffff80002fcf8b0}
Probably caused by : csrss.exe
PROCESS_NAME:  csrss.exe
BUGCHECK_STR:  0xF4_IOERR
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
FAILURE_BUCKET_ID:  X64_0xF4_IOERR_IMAGE_csrss.exe
Bugcheck code 000000F4
Arguments 00000000`00000003 fffffa80`0c00d8b0 fffffa80`0c00db90 fffff800`02fcf8b0
BiosVersion = FE
BiosReleaseDate = 12/23/2010
CPUID:        "Intel(R) Core(TM) i7 CPU         930  @ 2.80GHz"
MaxSpeed:     2800
CurrentSpeed: 2798
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\100411-19968-01.dmp]
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Tue Oct  4 12:27:20.295 2011 (UTC - 4:00)
System Uptime: 0 days 0:05:25.247
Probably caused by : ntkrnlmp.exe ( nt!KiProcessExpiredTimerList+103 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xA
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0xA_nt!KiProcessExpiredTimerList+103
Bugcheck code 0000000A
Arguments 00000000`0000002b 00000000`00000002 00000000`00000000 fffff800`02cd74d3
BiosVersion = FE
BiosReleaseDate = 12/23/2010
CPUID:        "Intel(R) Core(TM) i7 CPU         930  @ 2.80GHz"
MaxSpeed:     2800
CurrentSpeed: 2798
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\100311-19281-01.dmp]
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Mon Oct  3 19:03:15.124 2011 (UTC - 4:00)
System Uptime: 0 days 1:17:46.076
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+4977d )
BUGCHECK_STR:  0x1E_c0000005
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  svchost.exe
FAILURE_BUCKET_ID:  X64_0x1E_c0000005_nt!_??_::FNODOBFM::_string_+4977d
Bugcheck code 0000001E
Arguments ffffffff`c0000005 fffff800`02c9752c 00000000`00000000 00000000`00000088
BiosVersion = FE
BiosReleaseDate = 12/23/2010
CPUID:        "Intel(R) Core(TM) i7 CPU         930  @ 2.80GHz"
MaxSpeed:     2800
CurrentSpeed: 2798
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
  
  [/font]

rwtimmons · Oct 10, 2011

Usasma,

I have installed the drivers from the mb's website. I also have ran the Furmark, Prime95, Malware and memtests with no errors. I did get another BSOD today after my computer went to sleep and I tried to wake it up. Everything seems to come up correctly and then if I try and start a program I get an error saying "explorer.exe" (other running programs, i.e. skype, steam...) was not written to the memory address it was assigned.

After a restart or initial start after being shut down everything runs great and plenty fast (except for the HD). I think the hard drive is the bottle neck (Scored 5.9 on windows) because it is only a 7200 rpm drive even though my sata ports and drive is supposed to be 6.0 gb.

The only thing I can think of is that sleep is not being initiated correctly or something is happening while it sleeps or during the wakeup. I don't fully know the process of the computer going to sleep or waking up so I am a bit at a loss as to possible issues. I would hope it is not my memory as this is the third set I have used. Could the MB be the issue?

I am leaving for a trip so I will not be able to work with it for the next three days, but I will post a new perfmon report and BSOD report when I get home. Thanks again for all your input.

rwt

usasma · Oct 10, 2011

IN the old days (XP), sleep/hibernate problems were mostly caused by video drivers.
Since Vista and Win7 came out, there seem to be more drivers involved. I had issues with sleep in Win7 that Microsoft tech's diagnosed as my storage drivers (turns out they were wrong - it was the mobo). So now we have to contend with video, storage, and chipset drivers at a minimum. I'm starting to question the Ethernet/wifi drivers also - both because of the ability of network adapters to bring devices out of sleep/hibernate, and the fact that the network connections have to be reinitialized after waking from sleep/hibernate.

rwtimmons · Oct 15, 2011

Usasma,

I have attached another BSOD report and system report. I just changed my power settings to prevent the computer from going to sleep. At this point if I can't figure out what is causing the sleep problems I am just not going to let it sleep in the first place.

No sleep = No problem!

If you see anything I can do I will take any suggestions you have, but sometimes Occam's Razor just has to win out.

rwt

usasma · Oct 15, 2011

Please run the Hard Drive diagnostics on all of your hard drives ( HD Diagnostic )
There are several memory dumps that cite I/O Errors (including all 4 of the latest dumps) - so that's a likely problem area. If it's not the hard drive, then we have to wonder if there's an issue with the hard drive controller on the mobo.

BSOD BUGCHECK SUMMARY

Code:

[font=lucida console]
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\101411-19562-01.dmp]
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Sat Oct 15 00:15:08.171 2011 (UTC - 4:00)
System Uptime: 0 days 10:37:47.756
BugCheck F4, {3, fffffa8007488060, fffffa8007488340, fffff80002fce8b0}
Probably caused by : wininit.exe
PROCESS_NAME:  wininit.exe
BUGCHECK_STR:  0xF4_IOERR
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
FAILURE_BUCKET_ID:  X64_0xF4_IOERR_IMAGE_wininit.exe
Bugcheck code 000000F4
Arguments 00000000`00000003 fffffa80`07488060 fffffa80`07488340 fffff800`02fce8b0
BiosVersion = FE
BiosReleaseDate = 12/23/2010
CPUID:        "Intel(R) Core(TM) i7 CPU         930  @ 2.80GHz"
MaxSpeed:     2800
CurrentSpeed: 2798
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\101211-17515-01.dmp]
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Wed Oct 12 14:48:13.031 2011 (UTC - 4:00)
System Uptime: 0 days 0:44:07.062
BugCheck F4, {3, fffffa8007d276b0, fffffa8007d27990, fffff80002f868b0}
Probably caused by : wininit.exe
PROCESS_NAME:  wininit.exe
BUGCHECK_STR:  0xF4_IOERR
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
FAILURE_BUCKET_ID:  X64_0xF4_IOERR_IMAGE_wininit.exe
Bugcheck code 000000F4
Arguments 00000000`00000003 fffffa80`07d276b0 fffffa80`07d27990 fffff800`02f868b0
BiosVersion = FE
BiosReleaseDate = 12/23/2010
CPUID:        "Intel(R) Core(TM) i7 CPU         930  @ 2.80GHz"
MaxSpeed:     2800
CurrentSpeed: 2798
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\101111-17859-01.dmp]
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Tue Oct 11 23:15:03.234 2011 (UTC - 4:00)
System Uptime: 0 days 3:14:11.203
BugCheck F4, {3, fffffa8007cbd060, fffffa8007cbd340, fffff80002fce8b0}
Probably caused by : wininit.exe
PROCESS_NAME:  wininit.exe
BUGCHECK_STR:  0xF4_IOERR
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
FAILURE_BUCKET_ID:  X64_0xF4_IOERR_IMAGE_wininit.exe
Bugcheck code 000000F4
Arguments 00000000`00000003 fffffa80`07cbd060 fffffa80`07cbd340 fffff800`02fce8b0
BiosVersion = FE
BiosReleaseDate = 12/23/2010
CPUID:        "Intel(R) Core(TM) i7 CPU         930  @ 2.80GHz"
MaxSpeed:     2800
CurrentSpeed: 2798
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\101011-24000-01.dmp]
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Mon Oct 10 12:49:28.545 2011 (UTC - 4:00)
System Uptime: 0 days 3:28:34.514
BugCheck F4, {3, fffffa8007c62860, fffffa8007c62b40, fffff80002fe88b0}
Probably caused by : wininit.exe
PROCESS_NAME:  wininit.exe
BUGCHECK_STR:  0xF4_IOERR
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
FAILURE_BUCKET_ID:  X64_0xF4_IOERR_IMAGE_wininit.exe
Bugcheck code 000000F4
Arguments 00000000`00000003 fffffa80`07c62860 fffffa80`07c62b40 fffff800`02fe88b0
BiosVersion = FE
BiosReleaseDate = 12/23/2010
CPUID:        "Intel(R) Core(TM) i7 CPU         930  @ 2.80GHz"
MaxSpeed:     2800
CurrentSpeed: 2798
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
  
  [/font]

BSOD and Error Help

New member

My Computer

Mr. Cranky Pants

My Computer

New member

My Computer

Mr. Cranky Pants

My Computer

New member

My Computer

New member

My Computer

Mr. Cranky Pants

My Computer

New member

My Computer

Mr. Cranky Pants

My Computer

New member

My Computer

Mr. Cranky Pants

My Computer

New member

My Computer

Mr. Cranky Pants

My Computer

New member

My Computer

New member

My Computer

Mr. Cranky Pants

My Computer

New member

My Computer

Mr. Cranky Pants

My Computer

New member

My Computer

Mr. Cranky Pants

My Computer