Random BSOD and freezes daily.

Zethio · 23 Nov 2012

Hey! I'm the happy owner of a normally well-working PC. But since, I don't remember when, (Probably more than one year) I've getting BSOD and Freezes random, I'll explain more detailed.

For a long period, I've been getting one freeze once a day, everyday. It usually happen after a short while after I've turned on the PC and logged into my account. (It doesn't happen if I just let the PC do nothing, but if I transfer, or anything it will most likely happen within 5-30 min) If I press ALT+CTRL+DELETE a blue screen will pop up and say "Preparing security options, please wait" (Or something like that, I'll upload picture in the following days, when I find my camera) I've no idea what is causing this issue, but I've been having it for almost a year. Until now I've been dealing with it, but it's been too annoying.

Now for the blue screen.

Blue screen has been more of a mystery it comes once everyday, for a month, and then nothing the next month, and keeps on like that. I've fixed other peoples BSOD, (Which was pretty easy) but I can't seem to get of rid of this one. It creates no DMP file, and doesn't give me a driver name. I've no photo of my BSOD, but I've written it all down, and I'll upload the photo later with the freeze. I'll give you the entire summary here. (I've tried to update my drivers, and the most common stuff.)

"A problem has been detected and windows has been shut down to prevent damage

KERNEL_DATA_INPAGE_ERROR

If this is the first time you've seen this stop error screen,
restart your computer. If this screen appears again, follow
these steps:

Check to make sure any new hardware or software is properly installed.
If this is a new installation, ask your hardware or software manufacturer
for any windows updates you might need.

If problems continue, disable or remove any newly installed hardware or software. Disable BIOS memory options such as chacing or shadowing.
If you need to use safe mode to remove or disable components, restart your computer, press F8 to select advanced startup options, and then select safe mode.

Technical information

*** STOP: 0x0000007A (0xfffff6FC4001AC96, 0xFFFFFFFC0000056, XFFFFF88003594000)

Collecting data for crash dump ...Initializing disk for crash dump ...
Physical memory dump failed with status 0xC0000010.
Contact your system admin or technical support group for further assistance."

My spec.
ASUS P8Z68-V PRO, Socket-1155
ATX, Z68, DDR3, 3xPCIe(2.0)x16, CFX&SLI, SATA 6Gb/

orsair XMS3 DDR3 1600MHz 8GB CL9
Kit w/2x 4GB XMS3 modules, CL9-9-9-24, for Core i5 x2

1.00 619274 Intel® Core? i5-2500K Processor
Socket-LGA1155, Quad Core, 3.3Ghz, 6MB, 95W, Boxed

1.00 512803 Noctua NH-D14 CPU cooler
Socket 775/1155/1156/1366, AM2/AM2+/AM3, 1300 RPM,

1.00 591141 Western Digital Caviar® Black 1TB
SATA 6Gb/s (SATA 3.0), 64MB Cache, 7200RPM, 3,5",
1.00 494479 Lite-On DVD±RW Burner IHAS124-19

SATA, DVD±R: 24x, DVD+RW: 8x, DVD-RW: 6x, DVD-RAM:
1.00 622053 MSI GeForce GTX 580 1536MB PhysX

PCI-Express 2.0,"Twin Frozr II", GDDR5, 2xDVI, nat
1.00 635704 Corsair SSD Force Series? 3, 60GB

SATA 6 Gb/s (SATA3.0), 550MB/490MB/s read/write, S
1.00 336044 D-Link DWA-140 Wireless N USB adapter,
802.11n (draft 2.0)

922 HAF and PSU with 750W

Thanks you in advance. :)

koolkat77 · 24 Nov 2012

Welcome to SevenForums.

Please upload the files following: https://www.sevenforums.com/crashes-d...tructions.html

Zethio · 24 Nov 2012

I'm sorry that I forgot to mention is earlier, but I've already tried that out a while ago, and it still creates no DMP file. I've uploaded a picture of settings, just to make sure that the settings are right, and to make sure we won't get stuck by that. I've uploaded all the TXT in a rar file, called SF_24_11_2012.

koolkat77 · 24 Nov 2012

OK. Please check this thread for configuring the dumps: Dump Files - Configure Windows to Create on BSOD

We'll need the small memory dumps.

*How does the computer work in Safe Mode?

Do not use CCleaner during your troubleshooting here, it will wipe the dump files out.

We'll try doing some tests seeing to that error code and its usual causes:

STOP 0x0000007A: KERNEL_DATA_INPAGE_ERROR
Usual causes: Memory, Paging file corruption, File system, Hard drive, Cabling, Virus infection, Improperly seated cards, BIOS, Bad motherboard, Missing Service Pack.

If you have a SSD, make sure the firmware is up-to-date.

Run these tools and delete anything they may find:

Anti-rootkit utility TDSSKiller

ESET online scanner:

Free Online Virus Scanner | ESET

Upload screenshots of your hard drive(s) using crystal disk info:

Run Disk Check on your hard disk for file system errors and bad sectors on it:

Disk Check

Test your hard drive(s):

Hard Drive Diagnostic Procedure

Stop overclocking if you are.

Run the System File Checker that scans the of all protected Windows 7 system files and replaces incorrect corrupted, changed/modified, or damaged versions with the correct versions if possible:

Click on the
Type CMD on Search
Left click and Run as Administrator
Type SFC /scannow

Full tutorial here:

SFC /SCANNOW Command - System File Checker

Daemon Tools

Code:

Start Menu\Programs\DAEMON Tools Pro	Public:Start Menu\Programs\DAEMON Tools Pro	Public

Please uninstall DAEMON Tools. It uses a driver called sptd.sys which is known to cause BSODs in Windows 7. Uninstall the software using Add/Remove Programs. Reboot the system. Once the program is uninstalled, run sptd.sys uninstaller to remove the driver from your system.

As an alternative, many people recommend the use of Total Mounter or Magic ISO

Update the thread with results of above and if the system is stable or not?

Then test RAM. Take memtest. Run for 8 passes and test each stick in a know good slot for an additional 6 passes.

The goal is to test all the RAM sticks and all the motherboard slots.

Check your motherboard manual to ensure the RAM sticks are in the recommended motherboard slots. Some motherboards have very specific slots required for the number of RAM sticks installed.

If you get errors, stop the test and continue with the next step.

1. Remove all but one stick of RAM from your computer (this will be RAM stick #1), and run Memtest86 again, for 7 passes.
Be sure to note the RAM stick, use a piece of tape with a number, and note the motherboard slot.
If this stick passes the test then go to step #3.

2. If RAM stick #1 has errors, repeat the test with RAM stick #2 in the same motherboard slot.
If RAM stick #2 passes, this indicates that RAM stick #1 may be bad. If you want to be absolutely sure, re-test RAM stick #1 in another known good slot.
If RAM stick #2 has errors, this indicates another possible bad RAM stick, a possible motherboard slot failure or inadequate settings.
3. Test the next stick of RAM (stick #2) in the next motherboard slot.
If this RAM stick has errors repeat step #2 using a known good stick if possible, or another stick.
If this RAM stick has no errors and both sticks failed in slot#1, test RAM stick #1 in this slot.
4. If you find a stick that passes the test, test it in all the other motherboard slots.

If Part 2 testing shows errors, and all tests in Part 3 show errors, you will need to test the RAM sticks in another computer and/or test other RAM in your computer to identify the problem.

In this way, you can identify whether it is a bad stick of RAM, a bad motherboard, or incompatibility between the sticks.

Errors are sometimes found after 8 passes.

Do this test overnight, before going to bed.

Let us know the results.

Zethio · 24 Nov 2012

Update for now - It has not been possible for me to update my SSD since it require I flash the entire thing, and lose my OS. I've lost my CD and CD-key to my OS, so I would not be able to re-install the entire thing after flashing it, so updating firmware seems impossible.
Another thing is my computer WON'T create a dump file. I've checked my setting as you can see in the screenshot in my earlier comment, and it DOES NOT work.the only message I get is:
"Collecting data for crash dump ...Initializing disk for crash dump ...
Physical memory dump failed with status 0xC0000010.
Contact your system admin or technical support group for further assistance."

It does NOT create the DMP file, even when I've changed my settings.

About the safe-mode nothing changed while being in it. I still get the 1 minute long freeze after a while, but I didn't get a BSOD. (Most likely because I've already had my BSOD of the day. (Only get once a day.)

As for virus scanning, it whent like this. Microsoft Security Essentials found nothing.
ESET Online Scanner found 3 threats:
A variant of Jave/Exploit.Biacole.AK Trojan
A variant of Java/JShrink.A application
A variant of Win32/Packed.VMProject.AAA trojan.

Anti-Rookit utility (TDSSKiller) found nothing. But I noticed that there was 2 options that was on, should I try rescan with both of them on? (Verify file digital signatures) and (Detect TDLFS file system)

I've also uploaded a screenshot in this post of my SSD and my HDD as you can see.

I haven't been able to run the disc checks yet. And the HDD and SSD diagnostic won't work on my SSD since it's the "Corsair Force Series 3" The link you gave me, gave me not solution for a Corsair SSD, only Intel.
I was not able to find an iso for it on Google. I have yet to check my HDD, but I've made the disc for it.

I've not been overclocking, but now that we're on the subject, I think that my graphic card was per-overclocked.Not that it matters, but after a BSOD I have sometimes (rarely) seen messages after auto-restart saying "Overclocking failed." This only happen LONG ago, but it has happen, the screen looked somewhat like this.

http://www.google.dk/imgres?q=overcl...70,s:200,i:214

I've done the SFC /Scannow many times, and it says nothing is wrong.

As for Daemen tools, it says it already is uninstalled for some reason, I've an idea about what happen, but not exactly sure. I still have Shortcuts for it tho.

As for the ram, I've not checked it yet, and will do it overnight, I highly doubt it is my ram tho, be cause I've just bought new 8GB ram, same kind as the old one, and the BSOD still came, so I just used both, and took up ALL my motherboards slots. (Got 16GB now)

Zethio · 24 Nov 2012

I just found this post, and it reminds REALLY a lot about my own problem.

Same BSOD daily, no minidump - TechSpot Forums

koolkat77 · 24 Nov 2012

Ok. Proceed with memtest first and let us know the results.

Then we'll enable driver verifier: Driver Verifier - Enable and Disable

It needs to be enabled for around 36 hours. Configure the settings following Dump Files - Configure Windows to Create on BSOD again and upload all the dumps you get with verifier enabled.

essenbe · 24 Nov 2012

For your SSD firmware update, read this link, Force Series 3 and Force GT Firmware Update Ver 1.3 - The Corsair Support Forums
As I understand it, the firmware update is not supposed to be destructive (will not lose your OS and data), but accidents do happen. It is therefore suggested that you back up before doing the update. There are instructions in the firmware download. Make sure your SSD is in AHCI mode and is connected to an Intel port and not a Marvel port.

See if the firmware update resolves your problems. You will have to reset BIOS to optimized defaults after the update, so make note of what your current settings are now. After setting optimized defaults, you can reset BIOS however you like. Let us know how it goes. The link I gave you is to the Corsair forums which is an excellent place to get help.

Zethio · 24 Nov 2012

No matter how many times I try to get my pc to write the DMP it won't. I've done that tutorial 3 times now, with no result, I've also tried to use your regedit files, NONE of it helps.

I don't mean to be rude, and I'm thankful for the help, but I can't see why it should help the fifth time.

gregrocker · 25 Nov 2012

With that level of infection and corruption I'd consider a Clean Reinstall - Factory OEM Windows 7 which steps are the same for retail and assure a perfect install.

If you have a legal Product Key the step to audit the HD with Belarc will produce it for reinstall. You seem rather casual about losing a $100+ Product Key which you own for life. That carelessness contrasts with a thoroughness you also demonstrate which if applied to the reinstall will assure you get and keep it perfect.