BSOD and crashing on fresh install

[legoegoman]

A little back story here: So for the past few weeks I was getting tons of BSOD like pfn list corrupt, and other memory related ones. I did memtest for a few days, testing all the slots and sticks and I past all of them. I eventually found out that ntoskrnl.exe was corrupted, so I fixed that with a chkdsk and it worked OK for a few days. Then it would take numerous tries for windows to boot to the desktop, and it black screened when I did, but after a few tries I could use it.
That's why I re-installed windows.
I installed all the manufacture drivers that came with the laptop but it still is BSOD and having problems starting.
Is there an issue with a piece of hardware in my laptop?

 

[Arc]

Welcome aboard, legogoman.

Test your RAM modules for possible errors.
How to Test and Diagnose RAM Issues with Memtest86+
Run memtest for at least 8 passes, preferably overnight.

Seatool for dos: SeaTools | Seagate download. Burn it in a blank cd. boot from the CD, click on "Accept", wait for it to finish detecting the drives, then in the upper left corner select "Basic Tests", then select "Long Test" and let it run.

If both the tests results free of errors, enable Driver Verifier to monitor the drivers.
Driver Verifier - Enable and Disable
Run Driver Verifier for 24 hours or the occurrence of the next crash, whichever is earlier.

   Information

Why Driver Verifier:
It puts a stress on the drivers, ans so it makes the unstable drivers crash. Hopefully the driver that crashes is recorded in the memory dump.

How Can we know that DV is enabled:
It will make the system bit of slow, laggy.

   Warning

Before enabling DV, make it sure that you have earlier System restore points made in your computer. You can check it easily by using CCleaner looking at Tools > System Restore.

If there is no points, make a System Restore Point manually before enabling DV.

   Tip

• If you fail to get on the Desktop because of DV, Boot into Advanced Boot Options > Safe mode. Disable DV there. Now boot normally again, and try following the instruction of enabling DV again.
• If you cannot boot in Safe mode too, do a System Restore to a point you made earlier.

Let us know the results, with the subsequent crash dumps, if any. Post it following the Blue Screen of Death (BSOD) Posting Instructions.

And let us know which antivirus do you use.
______________________________________________________________________________________
BSOD ANALYSIS:

BugCheck 4E, {99, 87f23, 0, 115c4b}

Probably caused by : memory_corruption ( nt!MiBadShareCount+4c )

Followup: MachineOwner
------------------------------------------------------------------------
BugCheck 1A, {5003, fffff70001080000, 459a, 459800008b30}

Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+2a001 )

Followup: MachineOwner
---------

 

[legoegoman]

I ran the seagate test for about half an hour and it made it to about 6% then went black.

It took me a few times for it to boot into the disk again, but I ran the test the second time and within seconds the screen was flooded with scrolling INVALID OPCODE and a bunch of random letters and numbers.
I'll repeat the test and see if it makes the error again.

Also I have no anti-virus installed atm.

 

[Arc]

Use Win32 Disk Imager | Free Development software downloads at SourceForge.net .... to make a bootable USB to run seatools. Is it behaving the same?

Waiting for teh other tests too, but seatools at first, as the earlier report is not very pleasant.

 

[legoegoman]

It passed the third time perfectly. I'll try memtest for a few hours and see if that pulls up anything.

 

[legoegoman]

Memtest did 10 passes in 19 hours and found no errors.

Should I start driver verifier or do some other hard drive tests because it seems to be random whether or not they pass.

 

[legoegoman]

After I installed some updates, I tried to boot windows but it crashed a few times just past the "starting windows" screen.

I eventually got to the desktop and it said you recovered from a blue screen, so i clicked grab all on the BSOD program and it immediately shut it self down, not completing the grab all.

I was able to get the dump files in safe mode though, there attached.

Do all these boot problems point to a hard driver failure? It has scraped a few times in the past 2 years but I didn't think too much of it because it was brand new, and it never crashed after it.

 

[Arc]

Do three tries next.

First, update the touchpad driver from Drivers | Synaptics

Next, boot to System Recovery Options . Try Safe Mode with Command Prompt. In the command prompt .... enter the command ....

start msconfig

It will open the system configuration window, with the "general" tab selected.

• Click the "startup" tab. Click "Disable all" > Apply > OK. (you will need to activate the touchpad driver later again, keep an USB mouse with you)
• Click on "services" tab. Check the "Hide all Microsoft Services"; Click "Disable all" > Apply > OK

Then try to boot again normally. Is it failing still?

If so, boot to System Recovery Options once again. Try Enable Boot Logging. It will create a file named ntbtlog.txt. Collect it and upload it. If you cannot do it within windows, Boot with a live Linux disc and collect it in a USB stick, use the usb stick in another computer and upload it. It is necessary.

Third, disable the GPU and try to boot again.

 

[legoegoman]

I think I fixed the problem right before you just posted.
I turned on driver verifier and right after windows started it BSOD saying a driver used freed memory or something.

I repeated it just to be sure and it happened again.

The driver that caused it was my Realtek Sound Driver, attached is the many BSOD's for that driver that driver verifier found.
Google said to update the driver, but that resulted in the same BSOD
I uninstalled the driver completely and let windows install it, and guess what, no more crashes from driver verifier.
I'll let it run for a few more hours to see if it solved the problem, but I think it was that driver.

I'll report back in a day or two if it worked or not.
Thanks Arc for all your help!

 

[Arc]

All the verifier enabled minidumps are indicating to the audio driver. Even after updating it to latest. Now one thing is remaining there. Let us see how it is running with verifier disabled environment. Disable DV and let the computer run. Is it crashing in the same way?

 

[legoegoman]

Before i could disable verifier, it started doing the exact same crashes when i try to start windows. Same realtek driver as above.

 

[Arc]

Boot into safe mode and then disable verifier

 

[legoegoman]

Done that and it boots windows fine now, what should I do about the driver?

 

[Arc]

Have some more reboots. See if it is causing any trouble with any random reboot.

 

[legoegoman]

Seems to be running alright, no problems with rebooting or shutting down.

It froze for about 10 seconds when I was in chrome, and the speakers beeped quietly when it unfroze but that is the only problem so far.

 

[Arc]

Observe the situation. If it recurs let us know.

 

[legoegoman]

The freeze only happens once in one session. It occurs about 1 minute into opening chrome, and then never happens again until I reboot.
The freeze happens for about 10 seconds every time, my cursor changes to the typing cursor, and the entire screen freezes and the speakers beep when the screen unfreezes.

Event viewer says error event id 3011 and 3012
3011: Unloading the performance counter strings for service WmiApRpl (WmiApRpl) failed. The first DWORD in the Data section contains the error code.

3012: The performance strings in the Performance registry value is corrupted when process Performance extension counter provider. The BaseIndex value from the Performance registry is the first DWORD in the Data section, LastCounter value is the second DWORD in the Data section, and LastHelp value is the third DWORD in the Data section.

 

[Arc]

Try uninstalling and then re-installing Chrome?

And, is it happening with any other browser?

 

[legoegoman]

The reinstall seemed to fix the problem, and it doesn't happen to IE.

 

[Arc]

OK, when you consider your issue is over, please mark this thread as solved.

If the issue reappears later ... unmark it and continue.