[SOLVED] BSOD troubles

piedpiper · Mar 18, 2013

Hi all. Many thanks to anyone who takes a look at this. I was about to purchase a new video card, but stumbled upon this site before I hit checkout over on newegg and thought I'd give some old-fashioned troubleshooting a go. I plan on delving deeper into these forums and all of the excellent information, but figured I'd upload my BSOD info (Output folder + perfmon zipped) straight away.

Also, if it matters, the video card drivers were rolled back to a previous version as neither the newest nor beta drivers helped stop the BSODs. Ultimately, neither did the roll back. Only thing that seems to keep them at bay is constant contact by me with the pc. If I leave it to install updates or go in the other room for more than 10 minutes, the trouble begins.

My system info (as memory serves):
· OS - Windows 7
· x64
· Vista Ultimate
· Full retail version
· Age of system (hardware) ~ initial build - '07, updated gfx card approx. '11, new mobo and processor and memory '12
· Age of OS installation - have you re-installed the OS - initial install 2010, may have reinstalled during previous problems of 2012.

· Intel Core i5-3570K
· GTX 460
· Asus p8z77v
· Power Supply - brand & wattage (if laptop, skip this one) - cannot recall nor find any info in my saved emails. it was purchased/installed with original build in '07

OK, I'm off to verify more drivers and run some extra diagnostics. Again, thank you anyone who can give any help!

-piedpiper

writhziden · Mar 18, 2013

Please open up your case and look for a label on your PSU to provide us with the manufacturer and wattage. That information is important for investigating these problems.

Recommendations:

Please remove any CD/DVD virtualization software, such as Daemon Tools/Alcohol 120%, as they use a driver called sptd.sys that is known to cause BSODs. Use add/remove programs to remove the software. After removing the software, use the sptd.sys uninstaller to remove sptd.sys from the system by choosing to uninstall the software through the installer utility.

sptd.sys Sun Oct 11 14:55:14 2009 (4AD24632)
SCSI Pass Through Direct Host - Daemon Tools (known BSOD issues with Win7)
http://www.carrona.org/drivers/driver.php?id=sptd.sys

The crash shows that the system was forced to shut down when a service used several search time parameters to clear the search handle and reclaim the memory allocated to the search buffers. It was unable to reclaim the memory allocated, which resulted in a blue screen crash.

This primarily indicates a memory fault or incompatibility. Provide the following information about your hardware so we can check compatibility:

Download and install CPU-Z and Upload screenshots of the CPU, Mainboard, Memory, and SPD tabs. In the SPD tab, upload an image of each slot. To upload all screenshots, it would be best to:

generate the images using the Snipping Tool,
go to where the images are saved,
right click in a blank area within the folder where the images are saved,
create a new folder,
name the folder CPUZ,
select all the images,
place the pointer over an image,
press and hold down the left mouse button and drag the image (all images should move with it),
drop the images into the CPUZ directory you created,
create a compressed (zipped) folder of CPUZ
upload the .zip file to the forums.

Run some memory related diagnostics:

NOTE:

If you are overclocking any hardware, please stop.

Run display device memory tests to check the display card for memory problems.
Display device memory tests
Run Memtest86+ for at least 7-10 passes. It may take up to 22 passes to find problems. Make sure to run it once after the system has been on for a few hours and is warm, and then also run it again when the system has been off for a few hours and is cold.
Test RAM with Memtest86+
Run Prime95 to test your CPU, RAM modules, and general hardware.
Prime95 Hardware Stress Testing Steps

BugCheck 0x7A

0x7A:

Windows Dev Center - Hardware said:
Cause

Frequently, you can determine the cause of the KERNEL_DATA_INPAGE_ERROR bug check from the error status (Parameter 2). Some common status codes include the following:

0xC000009A, or STATUS_INSUFFICIENT_RESOURCES, indicates a lack of nonpaged pool resources.

0xC000009C, or STATUS_DEVICE_DATA_ERROR, typically indicates bad blocks (sectors) on the hard disk.

0xC000009D, or STATUS_DEVICE_NOT_CONNECTED, indicates defective or loose cabling, termination, or that the controller does not see the hard disk.

0xC000016A, or STATUS_DISK_OPERATION_FAILED, indicates bad blocks (sectors) on the hard disk.

0xC0000185, or STATUS_IO_DEVICE_ERROR, indicates improper termination or defective cabling on SCSI devices or that two devices are trying to use the same IRQ.

These status codes are the most common ones that have specific causes. For more information about other possible status codes that can be returned, see the Ntstatus.h file in the Microsoft Windows Driver Kit (WDK).

Another common cause of this error message is defective hardware or failing RAM.

A virus infection can also cause this bug check.

Resolution

Resolving a bad block problem: An I/O status code of 0xC000009C or 0xC000016A typically indicates that the data could not be read from the disk because of a bad block (sector). If you can restart the computer after the error, Autochk runs automatically and attempts to map the bad sector to prevent it from being used anymore.

If Autochk does not scan the hard disk for errors, you can manually start the disk scanner. Run Chkdsk /f /r on the system partition. You must restart the computer before the disk scan begins. If you cannot start the computer because of the error, use the Recovery Console and run Chkdsk /r.

Warning If your system partition is formatted with the FAT file system, the long file names that the Windows operating system uses might be damaged if you use Scandisk or another MS-DOS-based hard disk tool to verify the integrity of your hard disk from MS-DOS. Always use the version of Chkdsk that matches your version of Windows.

Resolving a defective hardware problem: If the I/O status is C0000185 and the paging file is on an SCSI disk, check the disk cabling and SCSI termination for problems.

Resolving a failing RAM problem: Run the hardware diagnostics that the system manufacturer supplies, especially the memory scanner. For more information about these procedures, see the owner's manual for your computer.

Check that all the adapter cards in the computer are properly seated. Use an ink eraser or an electrical contact treatment, available at electronics supply stores, to ensure adapter card contacts are clean.

Check the System Log in Event Viewer for additional error messages that might help identify the device that is causing the error. You can also disable memory caching of the BIOS to try to resolve this error.

Make sure that the latest Windows Service Pack is installed.

If the preceding steps do not resolve the error, take the system motherboard to a repair facility for diagnostic testing. A crack, a scratched trace, or a defective component on the motherboard can cause this error.

Resolving a virus infection: Check your computer for viruses by using any up-to-date, commercial virus scanning software that examines the Master Boot Record of the hard disk. All Windows file systems can be infected by viruses.

The above was taken from Bug Check 0x7A: KERNEL_DATA_INPAGE_ERROR.

Outdated and Problematic Drivers:

You should update/replace/remove the following drivers. Any drivers that are known to cause BSODs, please remove the software or remove the drivers and then remove the device; steps to do so are given after the list of outdated drivers. If you have ASACPI.sys installed, make sure it is updated and not pre-2009; pre-2009 versions are known to cause BSODs:

aiaufwof.SYS Tue Jul 14 15:12:55 2009 (4A5CF4D7)
Likely part of Daemon Tools dynamic drivers, a known cause of BSODs.
aiaufwof.SYS - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed.

To update drivers, make sure to download the drivers from the manufacturer and not using 3rd party programs. Your drivers should be found from your motherboard support site (ASUS, Gigabyte, MSI, etc.) or your vendor support site (Dell, HP, Toshiba, Sony, etc.) first. If you have devices you bought yourself, the drivers for those devices need to be downloaded from the manufacturer support site for those devices. If you need help, let us know.

To remove drivers, do so by uninstalling the device or software associated with the driver. Devices can be uninstalled through device manager, and then the device itself should be physically removed from the system if no driver updates are available for the device. If it does not make sense to remove the device, i.e. the device is a motherboard, please ask us for further assistance.

Uninstall or change a program

Open Device Manager

3rd Party Drivers:

The following is for information purposes only. My recommendations were given above. The drivers that follow belong to software or devices that were not developed by Microsoft. Any drivers in red should be updated/replaced/removed. You can find links to the driver information and where to update the drivers in the section after the code box:

Code:

[font=lucida console]**************************Thu Mar 14 17:29:21.783 2013 (UTC - 6:00)**************************
lirsgt.sys                  Tue Jun 17 09:17:08 2008 (4857D574)
intelppm.sys                Mon Jul 13 17:19:25 2009 (4A5BC0FD)
[COLOR=RED][B]aiaufwof.SYS                Tue Jul 14 15:12:55 2009 (4A5CF4D7)[/B][/COLOR]
[COLOR=RED][B]sptd.sys                    Sun Oct 11 14:55:14 2009 (4AD24632)[/B][/COLOR]
amdxata.sys                 Fri Mar 19 10:18:18 2010 (4BA3A3CA)
speedfan.sys                Fri Mar 18 10:08:46 2011 (4D83838E)
nvBridge.kmd                Fri May 20 21:58:23 2011 (4DD7385F)
e1c62x64.sys                Wed Jul 20 10:37:53 2011 (4E270461)
LEqdUsb.Sys                 Fri Sep  2 00:22:56 2011 (4E607640)
LHidEqd.Sys                 Fri Sep  2 00:22:59 2011 (4E607643)
LHidFilt.Sys                Fri Sep  2 00:23:09 2011 (4E60764D)
LMouFilt.Sys                Fri Sep  2 00:23:15 2011 (4E607653)
athrx.sys                   Fri Oct 21 03:45:10 2011 (4EA13F26)
asmtxhci.sys                Wed Nov  2 21:00:22 2011 (4EB203C6)
asmthub3.sys                Wed Nov  2 21:00:32 2011 (4EB203D0)
iaStor.sys                  Tue Nov 29 20:39:19 2011 (4ED5A567)
asahci64.sys                Wed Jan  4 22:08:19 2012 (4F053043)
iusb3hub.sys                Thu Jan  5 04:54:43 2012 (4F058F83)
iusb3xhc.sys                Thu Jan  5 04:54:45 2012 (4F058F85)
iusb3hcs.sys                Thu Jan  5 04:56:40 2012 (4F058FF8)
GEARAspiWDM.sys             Thu May  3 13:56:17 2012 (4FA2E2E1)
RTKVHD64.sys                Tue Jun 19 02:50:56 2012 (4FE03D70)
HECIx64.sys                 Mon Jul  2 16:14:58 2012 (4FF21D62)
MpFilter.sys                Wed Oct 31 16:43:06 2012 (5091A97A)
nvhda64v.sys                Tue Dec 18 22:41:41 2012 (50D15395)
nvlddmkm.sys                Wed Feb 27 23:43:51 2013 (512EFCA7)
[/font]

Analysis:

The following is for information purposes only. The following information contains the relevant information from the blue screen analysis:

Code:

[font=lucida console]**************************Thu Mar 14 17:29:21.783 2013 (UTC - 6:00)**************************
Loading Dump File [C:\Users\writh ziden\Downloads\2013_03_18\piedpiper\Windows7_Vista_jcgriff2\031413-34086-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Built by: [B]7601[/B].18044.amd64fre.win7sp1_gdr.130104-1431
System Uptime:[B]0 days 2:20:31.000[/B]
Probably caused by :[B]ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+36c1a )[/B]
BugCheck [B]7A, {fffff6fc50070b48, ffffffffc0000056, 1cf530880, fffff8a00e169000}[/B]
BugCheck Info: [url=http://www.carrona.org/bsodindx.html#0x0000007A]KERNEL_DATA_INPAGE_ERROR (7a)[/url]
Arguments: 
Arg1: fffff6fc50070b48, lock type that was held (value 1,2,3, or PTE address)
Arg2: ffffffffc0000056, error status (normally i/o status code)
Arg3: 00000001cf530880, current process (virtual address for lock type 3, or PTE)
Arg4: fffff8a00e169000, virtual address that could not be in-paged (or PTE contents if arg1 is a PTE address)
BUGCHECK_STR:  0x7a_c0000056
PROCESS_NAME:  System
FAILURE_BUCKET_ID: [B]X64_0x7a_c0000056_nt!_??_::FNODOBFM::_string_+36c1a[/B]
CPUID:        "Intel(R) Core(TM) i5-3570K CPU @ 3.40GHz"
MaxSpeed:     3400
CurrentSpeed: [B]3400[/B]
  BIOS Version                  0604
  BIOS Release Date             02/06/2012
  Manufacturer                  System manufacturer
  Product Name                  System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
[/font]

piedpiper · Mar 20, 2013

I want to thank you writhziden for all your help and suggestions! Really nice of you to go out of your way to give a hand to so many folks.

I've followed your advice. I uninstalled the daemon tools, which should have taken care of those two drivers.

My power supply is the COOLER MASTER eXtreme Power Plus RS500-PCARD3 (found newegg.com/Product/Product.aspx?Item=N82E16817171031)

I've attached the CPUZ images.

I ran both the MemtestG80 and MemtestCL with no problems showing up.

I ran the Memtest86+ for 15 passes after the computer had been on for +2hrs and for 16 passes after computer had been off for +2 hours. No errors showed up.

Currently running the prime95. Nothing has popped. BUT.

I installed Speccy and everything seems great except my CPU average temperature is 89 degrees! I imagine this could have something to do with my problems. (edit: I should mention I've only just turned my PC on after it had been shut down for a few hours after completing the second run of the Memtest86+...so it got to that high temp quite quickly :/ )

Please let me know if anyone can help. Thanks again, writhziden!

-piedpiper

Wrench97 · Mar 20, 2013

Couple things I'd like to see.
D/L and run Hardware Monitor do something intense like a virus scan or gaming for a bit, Alt+Tab back to HWM expand all the trees and use the Win7 snipping tool to grab a screen shot of the HWM window, post the screen shot using the paperclip button in the advanced message box(GoAdvanced button). The Screen shot has more info then the text file does.

What CPU fan/heatsink are you using the stock intel uint or a aftermarket one?

There is a newer bios released in January of this year which addresses several "Stability" issues> ASUS - P8Z77-V

piedpiper · Mar 20, 2013

Here is snapshot after a bit of Guild Wars 2. I still have that Prime95 running in the background and I think that may be adding to the performance (I noticed gw2 was running bit sloggy compared to the last time I played).

I had the cpu installed with a new motherboard when I was having problems last year, so I'm not too sure about the heat sink, but after a cursory glance (and an obvious sticker) it looks like it is the intel unit.

I did a bit of reading about upgrading the mobo BIOS and it seems the asus has a Windows utility that can upgrade it or would it be better to flash update (my only experience doing that is with my asus gh73jh).

Currently sitting at about a 86 degree average with said programs still running in background.

Thanks for the reply and help!!

Wrench97 · Mar 20, 2013

Flash update is the way to go.

The cores hitting 96c are way too warm, check to make sure the cooler is still tight to the CPU, the Intel units have 4 push/twist to lock legs that are known to pop up and loosen the cooler.
If you have not air dusted it in awhile use a can of compressed air(available at office supply, hardware even walmart stores) to blow the dust bunnies from the cooler fins.

[SOLVED] BSOD troubles

piedpiper

New member

Attachments

writhziden

Administrator, .NET/UWP Developer

piedpiper

New member

Attachments

Wrench97

Administrator, Hardware Expert

piedpiper

New member

Wrench97

Administrator, Hardware Expert