Windows 7 Forums

Welcome to Windows 7 Forums. Our forum is dedicated to helping you find support and solutions for any problems regarding your Windows 7 PC be it Dell, HP, Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.


Windows 7: BSOD Custom Build. Can't figure out the culprit.

04 Mar 2014   #1
Raveiyn

Windows 7 Home Premium x64 SP1
 
 
BSOD Custom Build. Can't figure out the culprit.

This was my first custom build. Everything has went well for about a month then I received my first BSOD. The PC crashed and upon reboot said Checksum error. This made me believe my MOB battery was bad so I replaced it. This did not fix the problem. I eventually restored to a system image and everything was fine for a day or two. This morning I have had 2 BSOD. Any help would be appreciated.

I have followed the posting instructions, I think.

After checking a few of the other threads, I am going to go ahead and do a few of the beginning suggestions such as SFC scan and disk check. I already have Malwarebytes Pro installed. I have also used ADW.



On Tue 3/4/2014 12:14:54 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\030414-15444-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0x1A (0x41790, 0xFFFFFA80010C0380, 0xFFFF, 0x0)
Error: MEMORY_MANAGEMENT
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a severe memory management error occurred.
This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Tue 3/4/2014 12:14:54 PM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x1A (0x41790, 0xFFFFFA80010C0380, 0xFFFF, 0x0)
Error: MEMORY_MANAGEMENT
Bug check description: This indicates that a severe memory management error occurred.
This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



My System SpecsSystem Spec
.
04 Mar 2014   #2
Raveiyn

Windows 7 Home Premium x64 SP1
 
 



This is a little disturbing..
My System SpecsSystem Spec
04 Mar 2014   #3
Arc

Microsoft Community Contributor Award Recipient

Microsoft Windows 10 Pro Insider Preview 64-bit
 
 

Hi Raveiyn.

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.

If it start showing errors/red lines, stop testing. A single error is enough to determine that something is going bad there.

If it does not show any error, 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   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   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   Tip

Let us know the results, with the subsequent crash dumps, if any.
My System SpecsSystem Spec
.

04 Mar 2014   #4
Raveiyn

Windows 7 Home Premium x64 SP1
 
 

Already ran the Memtest for almost 12 hours, 9 passes I believe, last night. I should have mentioned that, I'm sorry. I can run it again tonight if needed.

I can enable Driver Verifier through the SFdiagnostic tool easy enough. Will update tomorrow. Thank you for your time and the response.
My System SpecsSystem Spec
04 Mar 2014   #5
Raveiyn

Windows 7 Home Premium x64 SP1
 
 

Ok.. system was running really slow which is to be expected with Driver Verifier running. Had 3 BSOD and had to reboot in safe mode with networking to post this.

Who Crashed report.

On Tue 3/4/2014 9:24:39 PM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0xC4 (0x62, 0xFFFFFA800A620368, 0xFFFFFA80096E9700, 0x1)
Error: DRIVER_VERIFIER_DETECTED_VIOLATION
Bug check description: This is the general bug check code for fatal errors found by Driver Verifier.
The driver is unloading without first freeing its pool allocations. A bug check with this parameter occurs only when the Pool Tracking option of Driver Verifier is active. This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Tue 3/4/2014 9:22:19 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\030414-24772-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0xC4 (0x62, 0xFFFFFA800A2D5D18, 0xFFFFFA80090BFB10, 0x1)
Error: DRIVER_VERIFIER_DETECTED_VIOLATION
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This is the general bug check code for fatal errors found by Driver Verifier.
The driver is unloading without first freeing its pool allocations. A bug check with this parameter occurs only when the Pool Tracking option of Driver Verifier is active. This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Tue 3/4/2014 9:19:35 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\030414-22292-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0xC4 (0x62, 0xFFFFFA800A16EA88, 0xFFFFFA800A19A8C0, 0x1)
Error: DRIVER_VERIFIER_DETECTED_VIOLATION
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This is the general bug check code for fatal errors found by Driver Verifier.
The driver is unloading without first freeing its pool allocations. A bug check with this parameter occurs only when the Pool Tracking option of Driver Verifier is active. This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Tue 3/4/2014 9:15:34 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\030414-22666-01.dmp
This was probably caused by the following module: hidclass.sys (HIDCLASS+0x2710)
Bugcheck code: 0xC9 (0x220, 0xFFFFF88007210710, 0xFFFFF980A9202DC0, 0xFFFFFA800AC511F0)
Error: DRIVER_VERIFIER_IOMANAGER_VIOLATION
file path: C:\Windows\system32\drivers\hidclass.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Hid Class Library
Bug check description: This is the bug check code for all Driver Verifier
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.

After these crashes I started looking into drivers that could be wrong or have too many of the same thing. I have on board sound, Realtek, and Nvidia had virtual and another sound driver. I removed both the Nvidia as this MOB is catered to boosting sound. I don;t know if this was the culprit.
My System SpecsSystem Spec
05 Mar 2014   #6
Arc

Microsoft Community Contributor Award Recipient

Microsoft Windows 10 Pro Insider Preview 64-bit
 
 

Update the drivers to your logitech products. Logitech Support - Downloads, Manuals, FAQs & More

Code:
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck C9, {220, fffff88007210710, fffff980a9202dc0, fffffa800ac511f0}

*** WARNING: Unable to verify timestamp for LGVirHid.sys
*** ERROR: Module load completed but symbols could not be loaded for LGVirHid.sys
Probably caused by : HIDCLASS.SYS ( HIDCLASS!HidpMajorHandler+0 )

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

2: kd> lmvm LGVirHid
start             end                 module name
fffff880`08616000 fffff880`08618480   LGVirHid T (no symbols)           
    Loaded symbol image file: LGVirHid.sys
    Image path: \SystemRoot\system32\drivers\LGVirHid.sys
    Image name: LGVirHid.sys
    Timestamp:        Tue Nov 24 07:06:48 2009 (4B0B38B0)
    CheckSum:         00012CDE
    ImageSize:        00002480
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
Also Scan the system for possible virus infection with the following programs only.
Let us know the results. WhoCrashed output is not needed.
My System SpecsSystem Spec
05 Mar 2014   #7
Raveiyn

Windows 7 Home Premium x64 SP1
 
 

Quote   Quote: Originally Posted by Arc View Post
Update the drivers to your logitech products. Also Scan the system for possible virus infection with the following programs only.
Let us know the results. WhoCrashed output is not needed.
Updated the drivers for the mouse (the headset was already up-to-date)

Will run both programs you suggested.

I am guessing everything you needed was in the SF, sorry!

_____________________________________________________
TDSSKiller ran




Creating a Windows Defender DVD on boyfriends computer JIC.

_______________________________________________________

Windows Defender Offline scan came back clean
My System SpecsSystem Spec
05 Mar 2014   #8
Britton30
Microsoft MVP

Windows 7 Ultimate X64 SP1
 
 

Being a new build it would be a good idea to re-check all the power cable connections by pulling them out and reattaching them fully.

The same can be done with all the memory sticks, graphics card and any other PCIe devices.
My System SpecsSystem Spec
05 Mar 2014   #9
Raveiyn

Windows 7 Home Premium x64 SP1
 
 

Quote   Quote: Originally Posted by Britton30 View Post
Being a new build it would be a good idea to re-check all the power cable connections by pulling them out and reattaching them fully.

The same can be done with all the memory sticks, graphics card and any other PCIe devices.
That's the first thing I thought of Britton and pulled out just about everything. This is a modular PSU. Reseated the RAM, GPU and reattached power to everything. Then I ran the Memtest overnight. I haven't had a BSOD since my last posting of them which is also before I uninstalled Nvidia HD audio and Nvidia Virtual Audio as well as Arc's suggestion of updating the logitech devices.

Thank you for the help!
My System SpecsSystem Spec
05 Mar 2014   #10
Layback Bear

Windows 7 Pro. 64/SP-1
 
 

Just a suggestion. Windows System Files must be correct.
Did you run sfc /scannow according to this tutorial by Brink.

Pay close attention to paragraph #4

SFC /SCANNOW Command - System File Checker

My thoughts are if Windows 7 System Files aren't correct things are
not going to work properly.

http://i245.photobucket.com/albums/g...es/SFCscan.jpg

I'm not a expert, just my thoughts.
I will go back to watching.
My System SpecsSystem Spec
Reply

 BSOD Custom Build. Can't figure out the culprit.




Thread Tools Search this Thread
Search this Thread:

Advanced Search




Similar help and support threads
Thread Forum
BSOD Custom Build
So mainly while gaming I get various BSODs. Not much else to say but here are the required files and my computer and specs may be seen under my profile. Thank you in advance for taking the time to help with this.
BSOD Help and Support
BSOD on new custom build PC
Hello folks, I just built a new PC and have been having random BSOD issues since. It's a new MB, processor, RAM and main HDD (SSD), but I reused 2 hard drives from my previous PC, video card, optical drive and case from my last PC. I'm kinda thinking it might be RAM that's causing my issue but...
BSOD Help and Support
New Custom Build Please help BSOD
Am new here. And I too am suffering from random BSODs. Had faulty RAMs, and have replaced them. And still BSOD I seriously need help guys.
BSOD Help and Support
Custom Build Computer, BSOD on first day.
I just built my first (cheap) gaming computer today. However, I keep getting blue screened, and it happens very frequently. Within the last 3 hours of trying to troubleshoot this issue myself, it has blue screened on me about 12 times. I cannot be certain when/why it occurs. It's happened...
BSOD Help and Support
BSoD on Custom Build
Hello, I've been having persistent BSoD problems on a custom rig. It happens mostly when I'm away. Of the few times I have been at my computer at the time of crash, I saw no warning signs. Basic system info: Windows 7 Professional (x64) retail Fresh installation in March onto SSD...
BSOD Help and Support
BSOD on custom build
Hey folks, here's my basic info: Is Windows 7 . . . - 64 bit - original installed OS on system - student version of OS, counts as full retail (can install on multiple machines) - All components are approximately 6 months old - Reinstalled OS recently (2-3wks ago?) to see if that would fix...
BSOD Help and Support


Our Sites

Site Links

About Us

Find Us

Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd

All times are GMT -5. The time now is 11:51.

Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App