Transient BSODs every 2 weeks.

R

Riandrill

Member
Joined
Jul 21, 2013
Posts
10
Location
New York City
Hi,

I've been getting transient BSOD's every 2 weeks or so. When I say transient, I mean 0x000000(7A,1A,F4). In other words the BSOD is not always the same. I get hangs as well. The timing remains the same whether or not I reboot during that 2 week period. It would be interesting to know if there is something they OS does every 2 weeks.

I've attached the files and also included a picture of the BSOD. Something to note the crash dump never completes.

· OS - Windows 7
· x86: x64
· What was original installed OS on system: Windows 7
· Is the OS an OEM version: OEM
· Age of system (hardware): Several Months
· Age of OS installation - have you re-installed the OS: Reinstalled the OS 3 months ago

· CPU: i7-3630QM
· Video Card: NVIDIA GTX 660M 2GB PCIe Video (NB-380-101)
· MotherBoard: Mobile Intel HM77 Express Chipset Mainboard
· Power Supply - brand & wattage (if laptop, skip this one)

· System Manufacturer: Clevo / Cyberpower
· Exact model number (if laptop, check label on bottom): Xplorer X6-6000
Wireless NC: Killer Wireless - N1202

Much appreciate your help
Riandrill
 

Attachments

Hi,

We need all the files producer by the collection app, not just those few. Zip up the entire output folder and attach it to your next post please.

Stephen
 
Hi,

No dumps are included in the attached file. We need the dumps as they are the only record of events leading up to the BSOD. To stop them being deleted when/if you have more crashes, don't use CCleaner or any temporary file cleaners until troubleshooting is finished as they can delete dump files.

Check in C:\Windows\Minidump for any files. If you find files in that folder, please zip them up and upload them. If not, check C:\Windows\ for a file called MEMORY.DMP. This will be a big file, so zip it up and upload it to a free file sharing site such as SkyDrive or Dropbox.

To the computer is set up for future dumps, follow these steps.

  1. Click Start, right-click Computer -> Properties.
  2. Click Advanced system settings, and then click the Advanced tab.
  3. Click Settings under the Writing debugging information area, and then make sure Kernel Memory Dump is selected.


When you have your next BSOD, Windows will create dump files. Run the BSOD collection app from the posting instructions once you have had some more BSOD's.

The MSInfo32 file is also missing from the attachment. To obtain this manually:

Click Start --> Type msinfo32 into the Search programs and files box --> When it opens, click File, Save --> Save this file as msinfo32.nfo to a place you will remember --> Once it has finished gathering and saving info, right click this msinfo32.nfo file --> Click send to compressed (zipped) folder -> Upload the .zip file here.

Kind Regards,
Stephen
 
The hint for that, Tekno, is his mention that the crashdump never seems to complete. Also, the syslog shows only one crash event that happened to successfully write to the log; all other crashes are not listed. Therefore it's evident we're dealing with a hardware issue, and the 0xF4 crashes are especially suspect of that.

If you have an SSD, make sure to check for any firmware update for it. Also do the same for your BIOS and chipset drivers for your motherboard, as well as your disk controller drivers. Also check that your drive is attached correctly and if it has cables attached to it to reattach both ends.

If none of that works, I'm afraid we might be looking at a failing hard drive. Send us a screenshot from CrystalDiskInfo output for some extra info on it. If you have more than one drive, show us the screenshot for each drive.
 
Last edited:
You've got better eyes than I have Vir, I didn't spot that! That's why it's good to have someone else look over threads!

In that case, I agree, a hardware fault is certainly on the cards. Some other diagnostics may be useful for the HDD, other than Crystal Disk Info

HDD - Check your HDD for errors using Seatools. A tutorial for this is available here: Hard Drive (HDD) Diagnostics - Sysnative Forums

Thanks Vir!

Stephen
 
1. I have a laptop

2. I do not know how to check my BIOS is the latest that said, the release date is: 12/13/2012, American Megatrends, v4.6.5

3. Microsoft System Mgmt BIOS Drive up-to-date

4. Disk controller drivers, Microsoft says it's up to date

5. Chipset drivers, Microsoft says it's up to date

6. Also check that your drive is attached correctly and if it has cables attached to it to reattach both ends, again this is a laptop I prefer not opening the box and tool around inside of it.

7. CrystalDiskInfo is attached

8. I have a Western Digital drive, Seatools did not see the disk control, hence it did not see the hard drive.

9. I ran WDC's Data Lifeguard Diagnostics, extended test - Windows Version. It came up clean. If you think the DOS version is called for let me know

10. I'm trying to avoid popping open an under warranty Laptop.

11. On a whim from reading in the past about power supply issues, I've removed the battery for the time being and will run it for 3 weeks on AC only, and then 3 weeks on battery only. Do you think it worth trying?

Thanks for the help.
Rian
 

Attachments

  • Crystalinfo.JPG
    Crystalinfo.JPG
    176 KB · Views: 3
If you want to try the power supply thing, go ahead. Understand there is a component that receives power from either source, so if that component is bugged, then it won't matter which source it's getting power from.

The drive stuff looks all clean, but I would not sit the drive out of this cuz of that. I still suspect the drive is somehow dying, and if it dies at sudden moments, SMART will not record the event nor drive tests will show up anything.

Here are the software that usually affect this kind of thing that could be suspect causes, beyond what drivers you've already updated:

1. Antivirus software
2. File/Drive Encryption software
3. Virtual drive (e.g Daemon Tools) software
4. File/Directory Utility software
5. Cloud Storage software (e.g. Dropbox)

Update - and in some cases cleanup and uninstall - all of those that may be present on your system, especially the A/V.

Also, I'm pretty confident re-seating your hard drive will not void your warranty. It is one of the few items in a laptop that's designed to be easily accessible and replaceable. Still, if you are unsure, consult your warranty on it before attempting to re-seat the hard drive. As for the actual process, it's very simple. Typically there's a plate on the back of the laptop that you unscrew to reveal the drive, then you unscrew and slip the drive out then back in and screw back in.

Since you are under warranty, you may wanna bring it in for servicing or replacement by your OEM.
 
Of the 5 software apps you noted, I have A/V and Dropbox. I dont use Dropbox, so uninstalling it is not a problem. I do use Kaspersky. I can unisinstall it but would feel uncomfortable not having A/V on the machine. Can you suggest another A/V

I'll look into the hard drive warranty.

Thank you.
 
You don't have to use an application in order for it to bug out. Dropbox can drop a driver into the driver stack for disk I/O which may be interfering with disk I/O in an improper manner. It doesn't have to be actively used in order for the driver to be present and active.

You can switch to MSE temporarily. Again, if it still crashes, you can switch back over to Kaspersky.
 
Hi,

So far no problems.
I've uninstalled both Dropbox and Kaspersky and installed MSE.
I spoke with the techs they said I can reseat the drive without voiding the warranty. I havent yet.

I checked at Microsoft about KIS and 0xF4 BSODs. Apparently it is well known for BSODs as are other av's.
But, their method of doing a dump was a Mini Dump. I'll keep it at the kernal as you suggest.
Out of my own curiousity I'd like to force a BSOD. I want to make sure that if I should get a BSOD I my machine is doing both the mini and kernal

Can I force a BSOD and if so, how?

Thanks
 
Trust me, it will. If it's able to create a kernel dump, it will create a mini. Once the kernel dump is generated, the minidump is shaved off of the kernel dump and saved as its own file in the /Windows/Minidump directory. Minidumps are supposed to always be made regardless whether you select Mini, Kernel or even Complete dump for crashes.

AVs are the most common software issue that triggers 0xF4 bugchecks, because of their intense filtering of disk I/O, but hardware issues are the most common cause of 0xF4 bugchecks overall - at least from my personal dealings with them. That's why I wanted to approach hardware first before tackling software, which is I admit a backwards approach.

If you wish to force a BSOD, follow instructions here.
 
Hi, Time for an update because I got a new BSOD with a full dump. A x109.

It almost a month to the day since my first BSOD. Since then I've removed the AV, Dropbox and battery.

**I put the battery back in about a week or so ago because the system was stable.
**3 days ago I installed iTunes. A program I've always been leery of, anything that does that much can't be good. However in todays world it almost seems to be a necessity.

I've uploaded the jcgriff2.zip. In it is the Perfmon.html. I think you have everything you need.

I would much appreciate your thoughts.

Thanks
Rian
 

Attachments

Code: 
[COLOR=#ff0000]BugCheck 109[/COLOR], {a3a039d8a0d076d3, b3b7465ef34eb2b5, fffff88002f70640, [COLOR=#0000cd]3[/COLOR]}

Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )

Code: 
[B]Usual causes:[/B]  Device driver, Breakpoint set with no debugger attached, Hardware (Memory in particular)

This bugcheck indicates that the GDT (Global Descriptor Table) has become corrupt, which is used to inform the CPU about the location of memory segments.

Follow this guide for testing the RAM - https://www.sysnative.com/forums/hardware-tutorials/3909-test-ram-memtest86.html
 
Hi,

I let Memtest run for something like 21+ hours, when I saw it last before shutting it down, it was at 14 passes.

No errors.

I'm open for suggestions.

Thanks
 
I'm guessing that was from running Driver Verifier?

A Black screen usually indicates hardware incompatibility or failure in my opinion and from what I've seen in other threads.
 
I hadn't run verifier yet. I am RMA'ing the machine back to the company. Hopefully they can actually fix it this time. Transient errors are always such a pain.

Thanks for your help
 
They probably won't fix it in my opinion, most likely replace something and then give you the machine back. Please run Driver Verifier when the computer is returned.
 

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top