BSOD Every 40-50 mins, error 0x0000003b

[gigglebeans]

Hello everyone, first post on this forum but I have been to this site many times to try and fix my crashing error with the code 0x0000003b. I recently built a PC little by little using an older PC. I would swap out parts on the old one as I received them. Looking back on it now I regret not just performing a one time swap. Everything is new except for dvd drive and hard drive and the windows that was on the hard drive. (I used sysprep.exe to prepare the windows install for the out of box experience then reactivated windows. I did this about 3 weeks ago. Every since I fired up I have been having regular crashes every 40-50 minutes after using the keyboard. I thought it was a driver so I went to the sites of every new product i bought and got new drivers and even went through the device manger and updated drivers for everything in their but still no luck. I also checked that everything hardware wise was connected and re-seated. I ran memtest with no errors for more than 7 passes. I got rid of Norton and replaced with Microsoft essentials. It was weird because I only got the actual blue screen twice and it was during gta IV, but spat out the same error code. normally the screen goes into lines and the audio skips then it restarts. It doesn't appear to happen in safe mode or when I use my xbox controller. I then thought it was something wrong with my mouse, keyboard which is a logitech mx3200 keyboard and a logitech mx600 mouse both wireless. I tried using a different keyboard and mouse but still same problems. I attached dump files and system health below. I hope one of you smarter-than-me gentlemen can see something I don't. The blue screen view program spits out the same error code: 0x0000003b and always highlights ntoskrnl.exe and another driver/program like: usbohci.exe, VirtDiskBus64.exe, blbdrvie.exe, and RTKVHD.exe and etc. Any help would be greatly appreciated my debugger doesn't wan't to work Thank you in advance.

 

[zigzag3143]

I normally say "virtually" all of these but in this case literally every one of these were related to a memory exception (probably caused by gdrv.sys/ snmp.exe)


These crashes were caused by memory corruption/exception (Cx05) probably a driver.
Please run these two tests to verify your memory and find which driver is causing the problem.

* If you are overclocking anything reset to default before running these tests.
In other words STOP!!!

* If you have a Raid update its Driver.



Memtest. Yes I know you have run it before but did you run it for the 6-8 passes? Did you run the sticks individually? Every one of these was at approximately the same memory address.

*Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder or another ISO burning program. Memtest86+ - Advanced Memory Diagnostic Tool

*Boot from the CD, and leave it running for at least 5-7 passes.

Just remember, any time Memtest reports errors, it can be either bad RAM or a bad motherboard slot.

Test the sticks individually, and if you find a good one, test it in all slots.

Any errors are indicative of a memory problem.

If a known good stick fails in a motherboard slot it is probably the slot.

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






Driver Verifier

Using Driver Verifier is an iffy proposition.
Most times it'll crash and it'll tell you what the driver is.
But sometimes it'll crash and won't tell you the driver.
Other times it'll crash before you can log in to Windows.
If you can't get to Safe Mode, then you'll have to resort to offline editing of the registry to disable Driver Verifier.

I'd suggest that you first backup your stuff and then make sure you've got access to another computer so you can contact us if problems arise.
Then make a System Restore point (so you can restore the system using the Vista/Win7 Startup Repair feature).

In Windows 7 you can make a Startup Repair disk by going to Start....All Programs...Maintenance...Create a System Repair Disc - with Windows Vista you'll have to use your installation disk or the "Repair your computer" option at the top of the Safe Mode menu .

Then, here's the procedure:
- Go to Start and type in "verifier" (without the quotes) and press Enter
- Select "Create custom settings (for code developers)" and click "Next"
- Select "Select individual settings from a full list" and click "Next"
- Select everything EXCEPT FOR "Low Resource Simulation"IRP Logging and Force Pending I/O Requests. and click "Next"
NOTE: You can use Low Resource Simulation if you'd like.
From my limited experimentation it makes the BSOD's come faster.
- Select "Select driver names from a list" and click "Next"
Then select all drivers NOT provided by Microsoft and click "Next"
- Select "Finish" on the next page.

If you are using win 8 add these
- Concurrency Stress Test
- DDI compliance checking


Reboot the system and wait for it to crash to the Blue Screen.
Continue to use your system normally, and if you know what causes the crash, do that repeatedly.
The objective here is to get the system to crash because Driver Verifier is stressing the drivers out.
If it doesn't crash for you, then let it run for at least 36 hours of continuous operation.
Reboot into Windows (after the crash) and turn off Driver Verifier by going back in and selecting "Delete existing settings" on the first page, then locate and zip up the memory dump file and upload it with your next post.


If you can't get into Windows because it crashes too soon, try it in Safe Mode.
If you can't get into Safe Mode, try using System Restore from your installation DVD to set the system back to the previous restore point that you created.

Thanks to JCGriff2 & Usasma.

Sysnative Forums

Driver Reference Table (DRT)

Using Driver Verifier to identify issues with Windows drivers for advanced users

Driver Verifier

Using Driver Verifier (Windows Drivers)

 

[gigglebeans]

ZigZag, thank you for responding promptly and your input on my problem. I ran memtest today on one of the sticks (I only have 2 Kingston T1 4gb sticks totaling 8gb) I left it running for 11 passes because i had to go to work and no errors on that stick by itself. I ran the other stick before in another slot and that was what I was mentioning in my original post. I will test that stick again. When I went to take out the ram stick that I had already tested I noticed there was a hair on the connectors of the ram stick ( oops ) would that have caused my problem? I also forgot to mention everything I put in my comp so you could see if everything was compatible.
Gigabyte GA-970A-D3
AMD Phenom x4 960T unlocked to six core
2x Kingston T1 4gb
XFX ATI 6870
Corsair 750W Modular Enthusiast
I will run driver verify tomorrow after I retest the other ram stick. Thank you again.

 

[gigglebeans]

Zig, I ran memtest last night on the other stick for 9 passes and no errors. I just now did driver verify following your steps exactly ( I didn't check low resource simulation) and It started into a restart cycle. It would show load operating system... then recognize that something was off and showed the boot options like safe mode safe mode w/ networking and launch windows normally so i selected launch windows normally and it showed the windows logo but restarted before the user login screen. I was able to get into safe mode and stop driver verify. No what do i do? Since it didn't show a blue screen or any driver problem? Thanks for your help.

 

[zigzag3143]

Verifier is supposed to crash. When you reboot it writes the crash log to the DMPS. Please upload the new ones.

 

[gigglebeans]

Oh okay thank you. Here they are. I just ran the program provided by the forum again. Thanks again.

 

[zigzag3143]

I am not sure verifier is enabled for none of these show it.

Please type verifier /query. If it comes back no drivers verifier isnt looking at anything.

If it says it is verifiying some drivers it is just not doing the right ones. IF SO lets go back in and test ALL drivers.

These crashes have been absolutely consistent from the first until now. That is actually a good thing.

Currently it is showing Related to gdrv.sys Microsoft Register Server.

Have you run a malwarebytes scan?

Please download the free version of Malwarebytes.
Update it immediately.
Do a full system scan
Let us know the results at the end.

Malwarebytes : Download free malware, virus and spyware tools to get your computer back in shape!

Have you run WGA?

http://go.microsoft.com/fwlink/?linkid=52012

 

[gigglebeans]

I typed verifier /query and it came back with the message no drivers are verified. Does that mean I should run it again? and I have done Malwarebytes malware scan but have not done WGA.

 

[gigglebeans]

This is what WGA spat out when I select copy after it did it's diagnose.
Diagnostic Report (1.9.0027.0):
-----------------------------------------

Windows Validation Data-->

Validation Code: 0
Cached Online Validation Code: N/A, hr = 0xc004f012
Windows Product Key: *****-*****-FGC8J-6HWK9-92GG3
Windows Product Key Hash: uqWbZHsRmu7w0ZcxiM00pZUcwrg=
Windows Product ID: 00359-OEM-9805526-73024
Windows Product ID Type: 8
Windows License Type: COA SLP
Windows OS version: 6.1.7601.2.00010300.1.0.003
ID: {25ABC633-A890-4B06-A898-EB487296DEC2}(1)
Is Admin: Yes
TestCab: 0x0
LegitcheckControl ActiveX: N/A, hr = 0x80070002
Signed By: N/A, hr = 0x80070002
Product Name: Windows 7 Home Premium
Architecture: 0x00000009
Build lab: 7601.win7sp1_gdr.120305-1505
TTS Error: 
Validation Diagnostic: 
Resolution Status: N/A

Vista WgaER Data-->
ThreatID(s): N/A, hr = 0x80070002
Version: N/A, hr = 0x80070002

Windows XP Notifications Data-->
Cached Result: N/A, hr = 0x80070002
File Exists: No
Version: N/A, hr = 0x80070002
WgaTray.exe Signed By: N/A, hr = 0x80070002
WgaLogon.dll Signed By: N/A, hr = 0x80070002

OGA Notifications Data-->
Cached Result: N/A, hr = 0x80070002
Version: N/A, hr = 0x80070002
OGAExec.exe Signed By: N/A, hr = 0x80070002
OGAAddin.dll Signed By: N/A, hr = 0x80070002

OGA Data-->
Office Status: 100 Genuine
Microsoft Office Enterprise 2007 - 100 Genuine
OGA Version: N/A, 0x80070002
Signed By: N/A, hr = 0x80070002
Office Diagnostics: B4D0AA8B-604-645_025D1FF3-364-80041010_025D1FF3-229-80041010_025D1FF3-230-1_025D1FF3-517-80040154_025D1FF3-237-80040154_025D1FF3-238-2_025D1FF3-244-80070002_025D1FF3-258-3_E2AD56EA-765-d003_E2AD56EA-766-0_E2AD56EA-134-80004005

Browser Data-->
Proxy settings: N/A
User Agent: Mozilla/4.0 (compatible; MSIE 8.0; Win32)
Default Browser: C:\Users\Nick\AppData\Local\Google\Chrome\Application\chrome.exe
Download signed ActiveX controls: Prompt
Download unsigned ActiveX controls: Prompt
Run ActiveX controls and plug-ins: Allowed
Initialize and script ActiveX controls not marked as safe: Prompt
Allow scripting of Internet Explorer Webbrowser control: Disabled
Active scripting: Allowed
Script ActiveX controls marked as safe for scripting: Allowed

File Scan Data-->

Other data-->
Office Details: <GenuineResults><MachineData><UGUID>{25ABC633-A890-4B06-A898-EB487296DEC2}</UGUID><Version>1.9.0027.0</Version><OS>6.1.7601.2.00010300.1.0.003</OS><Architecture>x64</Architecture><PKey>*****-*****-*****-*****-92GG3</PKey><PID>00359-OEM-9805526-73024</PID><PIDType>8</PIDType><SID>S-1-5-21-3923463704-3075569368-2313806837</SID><SYSTEM><Manufacturer>Gigabyte Technology Co., Ltd.</Manufacturer><Model>GA-970A-D3</Model></SYSTEM><BIOS><Manufacturer>Award Software International, Inc.</Manufacturer><Version>F8</Version><SMBIOSVersion major="2" minor="4"/><Date>20120330000000.000000+000</Date></BIOS><HWID>04883907018400F6</HWID><UserLCID>0409</UserLCID><SystemLCID>0409</SystemLCID><TimeZone>US Mountain Standard Time(GMT-07:00)</TimeZone><iJoin>0</iJoin><SBID><stat>3</stat><msppid></msppid><name></name><model></model></SBID><OEM/><GANotification/></MachineData><Software><Office><Result>100</Result><Products><Product GUID="{90120000-0030-0000-0000-0000000FF1CE}"><LegitResult>100</LegitResult><Name>Microsoft Office Enterprise 2007</Name><Ver>12</Ver><Val>7480B9502DF0D86</Val><Hash>oYWOW5ayFE3pZ+jvTpuXYsY64JE=</Hash><Pid>89388-707-8722531-65290</Pid><PidType>14</PidType></Product></Products><Applications><App Id="15" Version="12" Result="100"/><App Id="16" Version="12" Result="100"/><App Id="18" Version="12" Result="100"/><App Id="19" Version="12" Result="100"/><App Id="1A" Version="12" Result="100"/><App Id="1B" Version="12" Result="100"/><App Id="44" Version="12" Result="100"/><App Id="A1" Version="12" Result="100"/><App Id="BA" Version="12" Result="100"/></Applications></Office></Software></GenuineResults>  

Spsys.log Content: 0x80070002

Licensing Data-->
Software licensing service version: 6.1.7601.17514

Name: Windows(R) 7, HomePremium edition
Description: Windows Operating System - Windows(R) 7, OEM_COA_SLP channel
Activation ID: 5e017a8a-f3f9-4167-b1bd-ba3e236a4d8f
Application ID: 55c92734-d682-4d71-983e-d6ec3f16059f
Extended PID: 00359-00196-055-273024-02-1033-7601.0000-1312012
Installation ID: 000380745006340303098090421312898305355486499762353863
Processor Certificate URL: [URL]http://go.microsoft.com/fwlink/?LinkID=88338[/URL]
Machine Certificate URL: [URL]http://go.microsoft.com/fwlink/?LinkID=88339[/URL]
Use License URL: [URL]http://go.microsoft.com/fwlink/?LinkID=88341[/URL]
Product Key Certificate URL: [URL]http://go.microsoft.com/fwlink/?LinkID=88340[/URL]
Partial Product Key: 92GG3
License Status: Licensed
Remaining Windows rearm count: 2
Trusted time: 5/31/2012 10:38:28 AM

Windows Activation Technologies-->
HrOffline: 0x00000000
HrOnline: N/A
HealthStatus: 0x0000000000000000
Event Time Stamp: N/A
ActiveX: Registered, Version: 7.1.7600.16395
Admin Service: Registered, Version: 7.1.7600.16395
HealthStatus Bitmask Output:


HWID Data-->
HWID Hash Current: OgAAAAEABAABAAIAAAACAAAABAABAAEAln1wMBpSVPIQM9zf3BWYqibkRrBiPc6a2JWElnCzkkoC0A==

OEM Activation 1.0 Data-->
N/A

OEM Activation 2.0 Data-->
BIOS valid for OA 2.0: yes, but no SLIC table
Windows marker version: N/A
OEMID and OEMTableID Consistent: N/A
BIOS Information: 
  ACPI Table Name    OEMID Value    OEMTableID Value
  APIC            GBT           GBTUACPI
  FACP            GBT           GBTUACPI
  HPET            GBT           GBTUACPI
  MCFG            GBT           GBTUACPI
  SSDT            PTLTD         POWERNOW
  MSDM            GBT           GBTUACPI
  MATS            GBT           
  TAMG            GBT           GBT   B0
  MATS            GBT

 

[writhziden]

Go through the Verifier steps more carefully; it definitely was not enabled properly. The MGADiag report looks good to the naked eye, but I am no expert on such matters.

You can delete a post. Click the Edit button, and then you will see a Delete button in the bottom right corner of the edited post. Give a reason for deleting if you want, put a dot in the Delete Message circle, click Delete this Message, and that is all you need to do.

 

[gigglebeans]

I ran driver verifier following the steps exactly how ZigZag described them and I still could not boot into windows unless I choose safe mode. But when I choose safe mode windows only loads necessary drivers so verifier can not test any of the drivers that need to be tested. What do I do if verifier will not test the drivers because it crashes before I can log in to my account? Thank you. Also thanks for the help with deleting posts writhziden I read on another forum with the similar error code and same driver (gdrv.sys) that they said to just delete gdrv.sys. Will this get rid of my problem? Thanks again.
One more thing: When selecting drivers in driver verifier i see the gdrv.sys driver. If I do not select that driver and run verifier will it still crash? And if it doesn't does that mean for sure that gdrv.sys is my problem? I also forgot to mention that verifier is crashing the computer before it shows the login screen for windows and does not display a blue screen and does not create a verifier enabled bsod dump.

 

[writhziden]

I also analyzed your crashes and saw gdrv.sys in nearly all of them. That is the Gigabyte Easy Saver - mobo power utility driver; I would recommend uninstalling all Gigabyte power related utilities since they can cause conflicts on some systems. Start Menu -> Control Panel -> Uninstall a program

Disable Verifier, then uninstall the power utilities. After that, do your normal routine (with Verifier still disabled) for twice as long as it generally takes for you to get a crash to see if the system is stable. Post back if you get a crash or after that twice as long period, whichever comes first.

 

[gigglebeans]

Writh: I actually uninstalled all the gigabyte utilities that I downloaded because it was mentioned in the other forum that said to delete gdrv.sys to also uninstall the utilities just like you recommended. I did this yesterday and since then I have not had a crash with verifier disabled and constant use of the machine for 6 hours. I went to the location of gdrv.sys and it showed it was last modified at the same time I uninstalled the utilities. So what ever I did must have worked. Should I still delete gdrv.sys since it was provided by gigabyte? Thank you both ZigZag and Writh for your outstanding help with my problem. You guys rock! If the problem comes back I know now where to go for help! Thanks again!

 

[writhziden]

You're welcome.

You could try renaming it to gdrv.sys.bak instead of deleting it. That way, if it causes issues, we can walk you through steps to rename it back. Do you have access to another system in case for some strange reason Windows will not start with that driver renamed?