BSOD with no minidump files!

[lhf8]

BSOD: Kernel Data Inpage Error (won't produce minidump files!)

OK guys,

I've tried to do my research on this and I've done a LOT of troubleshooting so far.

For the past 6 months, I have been getting BSOD about 3 times a week at complete random times. It mostly occurs overnight when I'm asleep.

I have tried deactivating all hibernate and sleep functions with no luck. I have tried three different anti-virus softwares and am now using Microsoft Security essentials.

I have tried various settings for creating a minidump file with NO luck but I think I might know why....

My BSOD is a Kernel data inpage error, stop code 0x0000007A

The sys file is lists 80% of the time is volgrx.sys but I've also seen an NTFS.sys listed.

My even viewer doesn't show much other than a Kernel Power failure event ID #41 but I'm not that skilled at reading and sifting through so I surely could be missing something.

Here's my specs:

Windows 7 pro
Intel i5 2500k
MSI P67 G43 board
Kingston HyperX SH100S3 120GB SSD (thinking this is the culprit)
Nvidia 560ti

I know I'm missing more info but please help direct me with more things to try.

Thank you all

EDIT: My page file is on the OS drive, I know that can prevent minidump writes.

 

[lhf8]

I can't change the title to better describe my issue for some reason.

 

[James7679]

Hello Ihf8, please follow the http://www.sevenforums.com/crashes-debugging/96879-blue-screen-death-bsod-posting-instructions.html
Also, to ensure that your mini dumps are being created;

1. Click Start, point to Settings, and then click Control Panel.
2. Double-click System.
3. Click the Advanced tab, and then click Settings under Startup and Recovery.
4. In the Write debugging information list, click Small memory dump.

 

[lhf8]

I have followed those instructions and am still not able to create a dump file and nothing is being collected by the software either.

The I will try rerunning the system health report but I had no known issues when I last ran it.

 

[writhziden]

The blue screen posting instructions still may help us determine the problem. It will also help us check your .dmp settings to make sure they are set to generate the .dmps properly for the jcgriff2 report gathering tool. That will allow us to help you set up the .dmp settings so they will work.

 

[lhf8]

I actually already followed those instructions and I've tried Kernel and small memory dump both saved under the specified location in the directions and the software doesn't capture anything. Nor are there any .dmp files stored in the system folder.

 

[writhziden]

Alright, we'll ask one more time that you please follow the http://www.sevenforums.com/crashes-debugging/96879-blue-screen-death-bsod-posting-instructions.html and upload the reports (with or without the dmps, we do not care), and then we'll move on to other people who do follow those instructions.

 

[lhf8]

Sorry about not posting the report. I misunderstood.

Here are the attached reports.

 

[writhziden]

My apologies for coming down so hard. Been a hectic day.


None of your recent crashes have been written to file or even recognized by Windows. There are a number of reasons that this might happen: Hard disk corruption, bad sectors, a failing hard disk, Windows files or registry corruption, viruses, or memory problems.

• If you are overclocking any hardware, please stop.
  
  
• Run Disk Check with both boxes checked for all HDDs and with Automatically fix file system errors checked for all SSDs. Post back your logs for the checks after finding them using http://www.sevenforums.com/tutorials/96938-check-disk-chkdsk-read-event-viewer-log.html (you may need to search for wininit instead of chkdsk).
  For any drives that do not give the message:
  Windows has checked the file system and found no problems
  run disk check again as above. In other words, if it says:
  Windows has made corrections to the file system
  after running the disk check, run the disk check again.
  
  
• Run all but the advanced tests with SeaTools for HDDs.
  SeaTools for Windows
  
  SeaTools for DOS​
  
  
• If you have an SSD, make sure the following are up to date:
  • SSD firmware
  • BIOS Version
  • Chipset Drivers
  • Hard disk controller drivers/SATA drivers
  • If you have a Marvell IDE ATA/ATAPI device, make sure the drivers are up to date from the Intel site or Marvell site and not from your motherboard/vendor support site.
  
  
• Check Windows for corruption. Run http://www.sevenforums.com/tutorials/1538-sfc-scannow-command-system-file-checker.html up to three times to fix all errors with a restart in between each. Post back if it continues to show errors after a fourth run or if the first run comes back with no integrity violations. Use OPTION THREE of http://www.sevenforums.com/tutorials/1538-sfc-scannow-command-system-file-checker.html to provide us with the sfcdetails.txt file if errors occur.
  
  
• Download and install Malwarebytes, update it, do not start the free trial, and then run a full scan. Also run a full scan with your antivirus software installed on your system. If you do not have antivirus software installed, see the http://www.sevenforums.com/system-s...-system-security-combination.html#post1732627 for better security steps and scanning tools. Make sure to update the security software before running the full scan.
  
  
• Run the boot version of Memtest86+ paying close attention to Parts 2 and 3 of the tutorial. Also, in case Memtest86+ misses anything and comes up with no errors, run the extended version of the Windows Memory Diagnostics Tool for at least five passes. These you may want to run overnight since they take a long time to complete (run them an hour before bed each of the next two nights and check before going to sleep that they are still running).
  
     Warning

  Before you proceed with the following, answer these two questions: Are you still under warranty? Does your warranty allow you to open up the machine to check hardware? If you are unsure of the answers to these questions, contact your system manufacturer. :warn:WARNING: The steps that follow can void your warranty!!!
  
  For Part 3: If You Have Errors: If you swap any memory components, follow these steps for ESD safety:
  1. Shut down and turn off your computer.
  2. Unplug all power supplies to the computer (AC Power then battery for laptops, AC power for desktops)
  3. Hold down the power button for 30 seconds to close the circuit and ensure all power drains from components.
  4. Make sure you are grounded by using proper grounding techniques, i.e. work on an anti-static workbench, anti-static desk, or an anti-static pad. Hold something metallic while touching it to the anti-static surface, or use an anti-static wristband to attach to the anti-static material while working. If you do not have an anti-static workbench, desk, or pad, you can use your computer tower/case by finding a metal hold in it, such as a drive bay.
  Once these steps have been followed, it is safe to remove and replace components within your computer.

 

[lhf8]

Well.....I figured I'd update while I'm trying everything since this may REALLY mean it's my SSD.

My Kingston HyperX 120GB drive WON'T update it's firmware. I'm two revisions behind (320 > 332 > 501) I'm on 320 and I've tried updating when it's the primary drive and slaved....nothing. I'm not in IDEE mode so I think it's the drive.

See the first run of tests I did....I'm in the process of checking memory.

 

[writhziden]

You may want to run the disk check again since Windows made corrections. You only have to run it with Automatically Fix File System Errors checked.

 

[lhf8]

Ahh, I apologize. I did run it, didn't upload it!

 

[writhziden]

Ah, good. Looks better. How is the system behaving at present?

 

[lhf8]

So far so good; however, it has gone an entire week in the past running completely normal, gaming video editing etc with no BSOD and then randomly at night it will blue screen so it's hard to say.

I spoke with Kingston and they've issued an RMA for the drive. They said their old firmware has had several issues with the P67s.....figure it might be worth a try. It's also VERY odd my drive refuses to update firmware.

 

[writhziden]

Yeah, I was a little concerned you could not update the firmware, so a good step to RMA it. Let us know when you get the new drive how things behave.

 

[lhf8]

OK well as an update, I have somewhat good and bad news.

I am BSOD free after I RMAed the Kingston drive....

However, after installing the new OS and transferring everything over I unplugged my old kingston drive went to boot up and magically my newly installed OS is no longer recognized. I booted into my regular old HDD and I can see and read the SSD just fine but it won't boot. Seriously my system is plagued. I realize this is a different topic.

Hopefully when I get it back running there won't be able BSOD

 

[writhziden]

Try going through the steps for http://www.sevenforums.com/tutorials/219533-troubleshooting-windows-7-failure-boot.html. It is unlikely you have a virus or malware, so you can probably skip those steps for now.

 

[lhf8]

I've been working my way through this all morning ha.

I think what happened was all my bootfiles required boot.ini etc was on my old SSD and once I removed it, it doesn't see them anymore.

I'm working on trying to rebuild them and hoping I don't have to do a fresh install, again ha.

 

[karlsnooks]

HOW TO POST A SNAPSHOT OF DISK MANAGEMENT DISPLAY
Run disk management:
WIN | type DISKMGMT.MSC | ENTER
This method gives you a display without the unneeded navigation pane.
WIN=key with Microsoft logo on top.

Maximize the output of Disk Management:
Maximize the output of Disk Management:
ALT-Spacebar key combo | X key (selects Maximize) |
Drag the field separators (such as between Status and Capacity) to show entire field.


Make a snapshot:
WIN | type SNIPPING | ENTER | New
Drag the cursor around the area you want to snip.
File | Save as | select save location and name | Save


Post the snapshot:
Post a File or Screenshot in Seven Forums