Driver BSODs on Windows 8 and 7

[NoelDP]

All of the files here are in the original list - I missed them

2014-01-19 08:21:26, Info                  CSI    000001e2 [SR] Repairing 3 components
2014-01-19 08:21:26, Info                  CSI    000001e3 [SR] Beginning Verify and Repair transaction
2014-01-19 08:21:26, Info                  CSI    000001e5 [SR] Cannot repair member file [l:24{12}]"keyboard.drv" of Microsoft-Windows-NTVDM-System, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
2014-01-19 08:21:26, Info                  CSI    000001e7 [SR] Cannot repair member file [l:18{9}]"l2057.dlm" of Microsoft-Windows-SpeechRecognizerENG.ale, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture = [l:10{5}]"en-GB", VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
2014-01-19 08:21:27, Info                  CSI    000001e9 [SR] Cannot repair member file [l:20{10}]"wp2057.bin" of Microsoft-Windows-SpeechRecognizerENG.ale, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture = [l:10{5}]"en-GB", VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
2014-01-19 08:21:27, Info                  CSI    000001eb [SR] Cannot repair member file [l:20{10}]"tn2057.bin" of Microsoft-Windows-SpeechRecognizerENG.ale, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture = [l:10{5}]"en-GB", VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch

I can't see the third affected component - perhaps it'll show up once we fix the others.

I've uploaded a file - mmsab.zip - to my SkyDrive at Noel's SkyDrive

(note - this may take a while to finish uploading - it's a large file, and I have a slow connection today)

Please download and save it.
Right-click on the saved file and select Extract all...
Change the target to C:\ and click on Extract
Close all windows (it would be a good idea to print these instructions!)
Now reboot to the Repair Environment - as soon as the machine restarts, start tapping F8 - this should bring up the Advanced Boot Menu, at the top of which should be the option 'Repair my Computer'
Pick that
You'll have to log in with your username and password.
Pick the option to use a Command Prompt
At the prompt type
DIR C:\mmsab
hit the enter key - if you get a 'Not Found' error try
DIR D:\mmsab
or
DIR E:\mmsab

The drive letter in use when you find the folder will need to be substituted (for<drive>) into the following command...

XCOPY <drive>:\mmsab <drive>:\windows\winsxs /y /i /s /v /h

(e.g.XCOPY P:\wfire P:\windows\winsxs /y /i /s /v /h )

run the command (it should take almost no time)and when the prompt returns, type
EXIT
and hit the Enter key to exit Command Prompt - reboot to Normal Mode Windows.
Now run SFC /SCANNOW in an Elevated Command Prompt
then reboot and upload the new CBS.log file to your reply. we need the FULL data this time.

 

[Anak]

I'm here, but I'm just watching and, learning.

 

[moromis]

Ok, after this second round, it gave me: "found corrupt files and successfully repaired them."

Here's the CBS folder: View attachment 302347

 

[NoelDP]

Here's the SFC summary

 Line 22524: 2014-01-19 12:38:35, Info                  CSI    000001c2 [SR] Repairing 1 components
 Line 22525: 2014-01-19 12:38:35, Info                  CSI    000001c3 [SR] Beginning Verify and Repair transaction
 Line 22528: 2014-01-19 12:38:35, Info                  CSI    000001c5 [SR] Repairing corrupted file [ml:520{260},l:42{21}]"\??\C:\Windows\system"\[l:24{12}]"keyboard.drv" from store
 Line 22537: 2014-01-19 12:38:35, Info                  CSI    000001c7 [SR] Repair complete

The CBS log appears to be otherwise error-free.

Before I hand you back to the BSOD specialists, perhaps we'd better run CheckSUR as well...

Please download and save the CheckSUR tool from http://support.microsoft.com/kb/947821
(you'll need to look in the details for Windows 7, downloading from the Microsoft Download Center)

Run it - The tool can take anywhere from 5 mins to a couple of hours to run (or 'Install') depending on how much it has to do, and may exit silently - it may appear to freeze for most of that time, but be patient.
The result is logged in the C:\Windows\Logs\CBS\CheckSUR.log file - and an archive …\checksur.persist.log file

Then zip the CheckSUR.log and upload it to your reply

 

[moromis]

Ok - strange things. I downloaded the tool as per request, and while it was downloading, I went to Windows Update to see if I had any Service Packs installed, as the article that contained the CheckSUR tool talked about reinstalling updates or service packs, and it just piqued my interest. Strangely enough, Windows Update wouldn't load. Since it seemed frozen, I closed it with Task Manager, and ran the CheckSUR tool. It returned an error code, and then when I tried to navigate to my Downloads folder to run it from there (I originally ran it from Chrome), Windows Explorer crashed and restarted. I'm going to now try running CheckSUR again to see if it returns an error code again.

EDIT: Nope, still returns an error code, 0xc80003f3 I'm going to try re-downloading it now.

 

[NoelDP]

The 0xc80003f3 error is an 'put of memory' error - which often means something completely different
Perhaps the BSOD guys should take back over again? -
:waves:

 

[Anak]

You were downloading a 174.8MB chksur file and you decided to run a query for windows updates? It is no wonder you received an out of memory error. What type of ISP do you have, is it fast or somewhat fast?

I would've rebooted my machine and used Internet Explorer (IE) to download chksur, not Chrome. Maybe its me, but anytime a download has anything to do with the Windows OS, I use IE.

If you're still having problems reboot and use IE to navigate to and download: Download System Update Readiness Tool for Windows 7 (KB947821) [November 2013] from Official Microsoft Download Center

Noel, hopefully we can get those chksur logs for you.

 

[moromis]

ISP is 22 mb. I'll reboot and download with IE. Sorry. I didn't think just going into the Windows Update center would conflict with Chrome, but I see I'm wrong.

I haven't had any BSOD since the Scannow fixed files, but I want to mention that I was having BSOD even on Windows CDs (7 and 8), as well as in the repair environment. I had a friend tell me that might indicate hardware...?

EDIT: I rebooted and got a BSOD during boot: View attachment 302386

I then rebooted from that, and when I came into Windows, it showed a "driver not installed" dialog, with an unknown device - cryptic. I then used IE to download the file, and got the same error upon running it.

 

[Anak]

The ,dmp file wouldn't open for me, please re-run and post the SF Diagnostic tool results. See Edit.

Were you able to run the chksur file and get logs for Noel?


EDIT:

I was looking around to see if I could find a reason why your .dmp file wouldn't open and using a different cmd - !analyze –v - I was able to open it.

Listen to your friend:

1: kd> [COLOR=Blue]!analyze –v [/COLOR]
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

[U][COLOR=Blue]BugCheck 50[/COLOR][/U], {f6c72c74, 0, 919b4835, 2}


[U][COLOR=Blue]Could not read faulting driver name
Probably caused by : hardware ( dxgmms1!VIDMM_GLOBAL::BeginCPUAccess+36d )[/COLOR][/U]

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

Cause

• Bug check 0x50 usually occurs after the installation of faulty hardware or in the event of failure of installed hardware (usually related to defective RAM, be it main memory, L2 RAM cache, or video RAM).
• Another common cause is the installation of a faulty system service.
• Antivirus software can also trigger this error, as can a corrupted NTFS volume.

Source: Bug Check 0x50: PAGE_FAULT_IN_NONPAGED_AREA (Windows Debuggers)

Looks like you're in for running a few stress tests:

Memory:
http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html

Those two Hard Drives although the first one you list in your specs is a SSD, but you say you don't have one.

The Seagate:
SeaTools for Windows | Seagate

For the Corsair if it is a SSD:
Crystal Dew World

 

[moromis]

Chksur is still running into the same error upon running the installer. Also, sorry. The 128 gb drive is a SSD, just not my main drive. Sorry for the confusion. I'll run the tests and report back.

EDIT:
Here's the results from Crystal and SeaTools.
View attachment 302510
I'm going to run the Memtest now.

 

[Anak]

Even though it is not the main drive it is connected to the system and needs checked. As you already know both your drives passed both, Seatools and Crystal Disk tests.

I failed to mention earlier but I was pressed for time, that with memtest, and assuming your RAM is good it will take at least 8 passes and up to 12 to 14 hours to run, most users will start the testing and let memtest run over-nite.

If you have RAM failures earlier than that or immediately follow the procedures for testing each stick and motherboard (MB) slots.

 

[moromis]

16.5 hours of Memtest86+, 10 passes with no errors.

EDIT: I should also mention there haven't been any BSODs since the fix that Noel had me install.

 

[Anak]

Okay, lets just sit tight for now and if you get another BSOD, "you know the drill".

 

[moromis]

Yep, got a BSOD when I got home just now. Here's the dump:
View attachment 302661

 

[moromis]

Got home, shook my monitor awake, and was glad to see no blue screen. Clicked on Chrome, and got a BSOD.

Here's the zip:
View attachment 302832

 

[Anak]

This is frustrating, yep it was chrome.........

Do you have this installed? GIGABYTE Download Center when you run it it can tell if you need drivers for the MB.

If you do, run it and see what it tells you.

If not well, I can't force you to run it but it might tell us if your MB could use some new drivers, and it may tell you if you have a BIOS update that you asked about back in post #11.

   Information

Note the warning about: Microsoft update 912945 will cause conflict with GIGABYTE Download Center. Please remove Microsoft update 912945 first before using GIGABYTE Download Center.

.

 

[moromis]

Yep, it is frustrating. Here's another BSOD.
View attachment 302857

I'm downloading the Gigabyte Download Center now, and I'll see if there's updates available.

EDIT: I guess it's not a download, it runs right in the website? I don't know, as I can't get it to work. Opened it up with IE and clicked on the "Check out download center" button. Then I clicked "GO!!" - disregarding the foreign english... I said yes to a couple of popups for activex and the like, but it wouldn't do anything. In the end, every time I clicked on the "GO!!" button, the IE page would just crash and restore. Weird.

2ND EDIT: I rebooted and tried again, and now it's giving me a dialog box saying: "open driver handle failure."

 

[Anak]

Your latest .dmp: STOP 0x00000019: BAD_POOL_HEADER | Usual causes: Device driver More on this below.


The situation with installing the Gbyte utility is it needs the Gbyte service, gdrv.sys, can you check to see if it is listed in Services?

You can check this by going to Option One Step #2 here: http://www.sevenforums.com/tutorials/2495-services-start-disable.html after Step #3 and Services opens scroll down to the "G's" and see if gdrv.sys is listed, and its status.

The problem I've seen is it can cause more harm than good - more BSOD's.

I would have checked but 99% of your System Information file is blank. Did you delete any of it? If not try running the SF_Diagnostic_ Tool again and use the grab all button and upload that resulting log. You can wait until a new BSOD comes to post the result.

See if gdrv.sys is listed, its status and post if its there or not, if it is its status.


Since every BSOD is driver related please run: http://www.sevenforums.com/tutorials/101379-driver-verifier-enable-disable.html follow Option One, post results.


Where did you get the Gbyte MB, how old is it? Newegg has it as out of stock.

Are you using any type of RAM that is different than specified by Gbyte? See download.

1. 2 x 1.8V DDR2 DIMM sockets supporting up to 4 GB of system memory
2. Dual channel memory architecture
3. Support for DDR2 1066(O.C.)/800/667 MHz memory modules
   (Go to GIGABYTE's website for the latest memory support list.)

Are you doing any overclocking, different voltages with the RAM? If you are please stop.

Any custom settings by you in the BIOS? Have you tried resetting the BIOS to its defaults?

 

[moromis]

gdrv.sys is not running.

Here's the new SFTools zip:
View attachment 302924

I believe the motherboard was bought online along with the case and all other internal pieces, excluding the graphics card. I'll double check with the builder of the computer when I can.

Memory is 2x OCZ PC2 6400 [email protected] DDR2 2GB Gold Series, so it should be fine.

No overclocking of any part of the machine, and BIOS is factory defaults.

I'm going to go through Driver Verifier now.

 

[Anak]

Here's the new SFTools zip:
View attachment 302924

Your new .dmp is: STOP 0x0000008E: KERNEL_MODE_EXCEPTION_NOT_HANDLED

Usual causes: Insufficient disk space, Device driver, Video card, BIOS, Breakpoint in startup without having a debugger attached, Hardware incompatibility, Faulty system service, 3rd party remote control, Memory

Memory is 2x OCZ PC2 6400 [email protected] DDR2 2GB Gold Series, so it should be fine.

Should be is not the same as will be.

This Gbyte MB is very picky as to what Ram sticks will run on it. In looking at GIGABYTE's memory support list the only OCZ that has been tested and found to run okay is the 1GB OCZ OCZ2VU8002GK model. Your sticks have the Model number OCZ2G8002GK

I believe the motherboard was bought online along with the case and all other internal pieces, excluding the graphics card. I'll double check with the builder of the computer when I can.

Also check with him or her if you can borrow before you try, a different type of RAM. Even though memtest shows your RAM to be okay, it only tests the RAM, not the compatibility between the MB and the RAM.

Even if you have known good RAM spares stored somewhere, try them.

Your .dmps consistently show hardware incompatibility, and memory, mostly memory.


Okay on all the rest.