BSOD Since New Hard Drive - The bugcheck was: 0x0000007e -EventID 1001

bigint · 30 Jan 2018

Hi,

The PC spec is a Lenovo G510 laptop, Intel i7 4700MQ CPU @ 2.40GHz, 8GB RAM and 1TB Seagate Barracuda ST1000LM048 - 2E7172, running a Windows 10 upgrade.

A few weeks ago my laptop hard drive failed. I had a new drive fitted at the PC shop, but since getting the PC back I have had a few BSOD issues, usually when dealing with images.

I have noted some of the drivers installed by the repair guy are newer than the latest recommended drivers for my PC on the Lenovo and Intel sites, so I'm not sure where he got them from.

After putting my software back on, I got error BSOD with (Code 31) which I think was connected to the driver for the Visual Studio location sensor simulator, installed with SQL Server Management Studio (SSMS) (I think). But, when I uninstalled SSMS the driver was left behind, so my only other option was to uninstall the location sensor simulator driver, which I have done. So I'm not sure whether this is still an issue.

I don't have the Realtak Audio Manager anymore, so I presume the audio driver is different to the original one and the same goes for the graphics studio software - that's missing too.

Events include:

######################

The computer has rebooted from a bugcheck. The bugcheck was: 0x0000007e (0xffffffffc0000005, 0xfffff803ed3699a5, 0xffffe686ca8fd4f8, 0xffffe686ca8fcd40). A dump was saved in: C:\WINDOWS\MEMORY.DMP. Report Id: 8e8fad4

######################

The DRIVER_CORRUPTED_EXPOOL

The computer has rebooted from a bugcheck. The bugcheck was: 0x000000c5 (0x0000000000000008, 0x0000000000000002, 0x0000000000000000, 0xfffff8028b934850). A dump was saved in: C:\WINDOWS\MEMORY.DMP. Report Id: 6c0ff115-2860-4d42-b9b2-

There was an event for each processor, just the event for processor 7 is listed:

The speed of processor 7 in group 0 is being limited by system firmware. The processor has been in this reduced performance state for 71 seconds since the last report.
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">- <System> <Provider Name="Microsoft-Windows-Kernel-Processor-Power" Guid="{0F67E49F-FE51-4E9F-B490-6F2948CC6027}" /> <EventID>37</EventID> <Version>0</Version> <Level>3</Level> <Task>7</Task> <Opcode>0</Opcode> <Keywords>0x8000000000000000</Keywords> <TimeCreated SystemTime="2018-01-16T16:39:14.612297600Z" /> <EventRecordID>3424</EventRecordID> <Correlation /> <Execution ProcessID="4" ThreadID="540" /> <Channel>System</Channel> <Computer>Lenovo-PC</Computer> <Security UserID="S-1-5-18" /> </System>- <EventData> <Data Name="Group">0</Data> <Data Name="Number">7</Data> <Data Name="CapDurationInSeconds">71</Data> <Data Name="PpcChanges">6</Data> <Data Name="TpcChanges">0</Data> <Data Name="PccChanges">0</Data> </EventData> </Event>

######################

Word is crashing too:
- EventID 1000 [ Qualifiers] 0 Level 2 Task 100 Keywords 0x80000000000000 [ SystemTime] 2018-01-24T10:21:23.936635900Z EventRecordID 13975 Channel Application WINWORD.EXE 16.0.8827.2148 5a53538a ntdll.dll 10.0.16299.192 16e7ff7f c0000374 000da8b9 3f98 01d3946a047f33ad C:\Program Files (x86)\Microsoft Office\Root\Office16\WINWORD.EXE C:\WINDOWS\SYSTEM32\ntdll.dll f2afb37f-5841-40e4-b089-422492b9678c

Faulting application name: WINWORD.EXE, version: 16.0.8827.2148, time stamp: 0x5a53538aFaulting module name: ntdll.dll, version: 10.0.16299.192, time stamp: 0x16e7ff7fException code: 0xc0000374

######################

I have attached a log file. Any help with these blue screen, potential driver issues would be appreciated. Thanks.

Ztruker · 01 Feb 2018

One dump in the zip file:

Code:

BugCheck 1000007E, {ffffffffc0000005, fffff803ed3699a5, ffffe686ca8fd4f8, ffffe686ca8fcd40}

*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : memory_corruption ( nt!MiViewMayContainPage+19 )

No driver indicated so it would be a good idea to test your RAM as follows:

===================================================
Follow this tutorial: MemTest86+ - Test RAM - Windows 10 Forums

MemTest86+ is a diagnostic tool designed to test Random Access Memory (RAM) for faults. MemTest86+ will verify that:

RAM will accept and keep random patterns of data sent to it
There are no errors when different parts of memory try to interact
There are no conflicts between memory addresses

Memtest86+ runs from bootable media to isolate the RAM from the system, no other components are taken into account during the test.

Warning

MemTest86+ needs to run for at least 8 passes to be anywhere near conclusive, anything less will not give a complete analysis of the RAM.

If you are asked to run MemTest86+ by a Ten Forums member make sure you run the full 8 passes for conclusive results. If you run less than 8 passes you will be asked to run it again. Any error indicates a defective DIMM that needs to be replaced. Halt the test and replace the DIMM.

Note

MemTest86+ has been known to discover errors in RAM in later passes than the eighth pass. This is for information only; if you feel there is a definite problem with the RAM and 8 passes have shown no errors feel free to continue for longer.

Running 8 passes of MemTest86+ is a long and drawn out exercise and the more RAM you have the longer it will take. It's recommended to run MemTest86+ just before you go to bed and leave it overnight.

Take a picture when done and post in the forum please.

bigint · 04 Feb 2018

Hi Ztruker,

Thank you, for your time and expertise.

Please find a screenshot of the memory test results below. The eight passes took about 12 hours to complete; each pass seemed slower than the last for some reason.

Thanks again.

Attachment 175517

Ztruker · 05 Feb 2018

Looks like your RAM is okay. Now try running with Driver Verifier enabled, see if that shows us any driver problems.
===================================================
Driver Verifier is a diagnostic tool built into Windows 10, it is designed to verify both native Microsoft drivers and third party drivers. Driver Verifier's verification process involves putting heavy stress on drivers with the intention of making bad, outdated, incompatible or misbehaving drivers fail. The required result is a BSOD (Blue Screen of Death) which will generate a crash dump for debugging purposes.
Machines exposed to Driver Verifier will run very sluggishly due to the stress being applied to the drivers.

Driver Verifier - Enable and Disable in Windows 10

Pay close attention to

PART TWO

and make sure the correct boxes are checked.

Warning:
It is not advised to run Driver Verifier for more than 48 hours at a time. Disable Driver Verifier after 48 hours or after receiving a BSOD, whichever happens soonest.

Always create a Restore Point prior to enabling Driver Verifier.

What we're looking for is a verifier generated BSOD with a mini dump that will tell us what driver caused it. If you get a BSOD, rerun dm_log_collector and upload the resulting zip file.

bigint · 01 Mar 2018

Hi,

Please forgive me for not getting back sooner, I have had issues with my back, so I have not been working. Hopefully, I am going to try to run the driver software this weekend and then report back.

Thank you, for your help and patience.

Ztruker · 01 Mar 2018

No problem, hope you are you are doing better now.

bigint · 23 Nov 2018

Hi ZTrucker,It's been a while, but would it please be possible to pick this up again? Where this post was left, I wasn't able to run Driver Verifier because I needed the PC - this is the only working PC I had. Then, I had other issues to deal with.I have created a restore point and I'm ready to run Driver Verifier, if you are still willing to help.I am now able to see this through. Thanks either way.

BSODHunter · 23 Nov 2018

Hi there,

could also be a problem with the disk. You should check the disk:

Run HDTune (YT) to check health and scan for errors.
You can also run a disk or health check using CrystalDiskInfo (YT) or chkdsk (YT). Refer to the tutorial for details of how to do this.
Take Screenshots of it and post it here.