Infrequent BSOD.

[grheard]

Hello.

I like many others have been visited by the dreaded BSOD.

I built this computer 2 weeks ago and have had the same BSOD 4 times now. The STOP code is 0x7A (KERNEL_DATA_INPAGE_ERROR).

The computer has rebooted from a bugcheck. The bugcheck was: 0x0000007a (0x0000000000000020, 0xffffffffc000009d, 0xfffffa800bec27c8, 0x0000000000000000). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 082310-46659-01.

From my googling, this is a Disk IO failure.

My system is an ASUS Rampage III Extreme. The harddrive in question is a Western Digital WD1002FAEX-00Z3A0 (Caviar Black 1TB SATA III). It is connected to the motherboard's Marvell 9128 SATA III controller. Both HDTune and Western Digital's Data Lifeguard Diagnostic have scanned the drive and found it to be clean.

What I am trying to determine is whether it is the harddrive or the motherboard/bios.

Any help would be greatly appreciated.

Thanks.

 

[usasma]

You can run a free test on the hard drive using this link: HD Diagnostic (read the details at the link)

I'd suggest updating the program associated with the bcgame.sys file as it's dated from 2006. It's most likely a part of the software for this device: Belkin Nostromo USB HID driver system driver file

The dump file blames fvevol.sys - a Microsoft file (which probably isn't the problem).
I'd suggest running Driver Verifier using these instructions:

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:

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

[font=lucida console]
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Mon Aug 23 21:00:51.992 2010 (UTC - 4:00)
System Uptime: 5 days 1:57:54.179
BugCheck 7A, {20, ffffffffc000009d, fffffa800bec27c8, 0}
*** WARNING: Unable to verify timestamp for fvevol.sys
*** ERROR: Module load completed but symbols could not be loaded for fvevol.sys
Probably caused by : CLASSPNP.SYS ( CLASSPNP!ServiceTransferRequest+355 )
BUGCHECK_STR:  0x7a_c000009d
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
  
  
 
 [/font]

 

[grheard]

I'd suggest updating the program associated with the bcgame.sys file as it's dated from 2006. It's most likely a part of the software for this device: Belkin Nostromo USB HID driver system driver file

You are correct. I'd love to have a newer driver, but I couldn't find one.

The dump file blames fvevol.sys - a Microsoft file (which probably isn't the problem).
I'd suggest running Driver Verifier using these instructions:

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).

I'll hold off on this one until I get the results of the 'HD Diagnostic'.

I found two things after making this post. First, I was not running the latest Marvell driver. Second, all the SATA controllers in the system were set to IDE in the BIOS. I have since make the registry modification and switched them to AHCI.

 

[grheard]

The drive may be the culprit after all...?

Log Name:      System
Source:        mv91xx
Date:          8/24/2010 1:08:01 AM
Event ID:      36
Task Category: None
Level:         Information
Keywords:      Classic
User:          N/A
Computer:      i7
Description:
Command [0x28] on physical disk 0 failed. Sense key=0xb, ASC=0x0, ASCQ=0x0.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="mv91xx" />
    <EventID Qualifiers="24578">36</EventID>
    <Level>4</Level>
    <Task>0</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2010-08-24T05:08:01.669407700Z" />
    <EventRecordID>7357</EventRecordID>
    <Channel>System</Channel>
    <Computer>i7</Computer>
    <Security />
  </System>
  <EventData>
    <Data>
    </Data>
    <Data>0</Data>
    <Data>28</Data>
    <Data>b</Data>
    <Data>0</Data>
    <Data>0</Data>
    <Binary>0000040006003000000000002400026000000000000000000000000000000000000000000000000024000260</Binary>
  </EventData>
</Event>

 

[usasma]

Start with these free diagnostics:

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: Malware (read the details at the link)

 

[grheard]

Memory diagnostics... check. (No problems found)
Hard drive diagnostics... check. (No problems found)
Malware scans... check. (No problems found)

Both SeaTools and WD Data Lifeguard completed their long tests without issue. I repeated their tests several times in a row in case increased temperature might reveal a problem, but none were found. Same thing for the memory tests. I ran Memtest86+ v4.10 non-stop for 16hours without any issues. I then followed the guide's instructions on testing the memory modules singly and then in the various sockets also without issue.

Since my last post I found one more possible issue. My BIOS was horribly out of date. I never thought to check it after receiving it. Like any high performance motherboard there have been several new BIOS(s) released to improve 'system stability'. Since this MB has a dual BIOS setup, I switch to the secondary BIOS and flashed it to the latest released BIOS from ASUS.

Since this BSOD is so infrequent, only time will tell if the BIOS or AHCI configuration change has fixed the issue.

 

[usasma]

Also run CHKDSK on all drives:

CHKDSK /R /F:
Run CHKDSK /R /F from an elevated (Run as adminstrator) Command Prompt. Please do this for each hard drive on your system.
When it tells you it can't do it right now - and asks you if you'd like to do it at the next reboot - answer Y (for Yes) and press Enter. Then reboot and let the test run. It may take a while for it to run, but keep an occasional eye on it to see if it generates any errors. See "CHKDSK LogFile" below in order to check the results of the test.

Elevated Command Prompt:
Go to Start and type in "cmd.exe" (without the quotes)
At the top of the Search Box, right click on Cmd.exe and select "Run as administrator"

CHKDSK LogFile:
Go to Start and type in "eventvwr.msc" (without the quotes) and press Enter
Expand the Windows logs heading, then select the Application log file entry.
Double click on the Source column header.
Scroll down the list until you find the Chkdsk entry (wininit for Win7) (winlogon for XP).
Copy/paste the results into your next post.

Run memory test on both cold and warm system - errors have been known to occur on one and not the other.

More free hardware tests:

FurMark download site: FurMark: VGA Stress Test, Graphics Card and GPU Stability 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).
- 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 you may want to 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.

Two other video stress tests (may be more stressful than FurMark):
Video Memory stress Test - http://nvworld.ru/utilities/vmt/
Artifact Locator - МИРNVIDIA / Утилиты / Artifact Locator
Sorry, but I don't read the language that this website is made in.

 

[usasma]

Duplicate post, please disregard....