Windows 7 BSOD In My PC

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

Use !analyze -v to get detailed debugging information.

BugCheck A, {9788f000, 2, 0, 82e50e63}

Unable to load image \SystemRoot\system32\DRIVERS\VirtDiskBus.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for VirtDiskBus.sys
*** ERROR: Module load completed but symbols could not be loaded for VirtDiskBus.sys
Probably caused by : VirtDiskBus.sys ( VirtDiskBus+1286 )

Followup: MachineOwner
Hi,
the driver VirtDiskBus.sys is actually the Gigabyte 3Terabyte unlock utility or so I'm led to believe.
VirtDiskBus.sys Tue Feb 08 07:58:54 2011: Try checking the link found here for a later version of the software:
http://www.gigabyte.com/microsite/276/3tb.html

AppleCharger.sys Mon Jan 10 09:58:02 2011: GIGABYTE On/Off Charge driver. See here for details -http://www.gigabyte.us/MicroSite/185/on-off-charge.htm
May cause BSOD on Win7/8 systems - uninstall to test

Other than the above your drivers appear to be in decent shape.
 
I'd wait to see if you have another bsod. If you do then try removing the on/off driver.
 
Code:
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck D1, {28, 2, 0, fffff8800158f6fd}

Probably caused by : NETIO.SYS ( NETIO!RtlCopyBufferToMdl+1d )

Followup: MachineOwner
Hi,
it looks like your issue was network related and i notice your running:
AVG anti-virus
Baidu Antivirus
AVG is known to cause issues from time to time and hving two AV apps running could also lead to conflicts. Try removing both and just using MSE coupled with Malwarebytes:
MSE:
http://windows.microsoft.com/en-GB/windows/security-essentials-download
Malwarebytes:
https://www.malwarebytes.org/

EtronHub3.sys Fri Feb 25 17:51:55 2011: USB 3 driver. Later version on motherboard support page:
http://www.gigabyte.com/products/product-page.aspx?pid=3863#driver

Rt64win7.sys Thu Jan 13 11:57:19 2011: Realtek RTL8168D/8111D Family PCI-E Gigabit Ethernet please update:
http://www.realtek.com.tw/downloads...d=5&Level=5&Conn=4&DownTypeID=3&GetDown=false

RTKVHD64.sys Fri Feb 11 10:16:05 2011: Realtek High Definition Audio Function Driver please update:
http://www.realtek.com.tw/downloads...=24&Level=4&Conn=3&DownTypeID=3&GetDown=false

Post any new dump files..
 
Code:
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1A, {41790, fffffa80047f3fd0, ffff, 0}

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

Followup: MachineOwner

Code:
PROCESS_NAME:  Jingling.exe

Hi,
your pc blue screened whilst using the above process. jingling.exe. This app is apparently for creating hits on sites and sounds extremely dodgy. Please remove. Bugcheck 1A means a memory fault occurred which could be down to a driver or faulty RAM.

I see you still have AVG installed, see suggestion above.

EtronHub3.sys Wed Jun 13 11:59:07 2012: USB 3 driver. Later version (2013) on motherboard support page:

gdrv.sys Fri Mar 13 03:22:29 2009: Gigabyte Easy Saver - mobo power utility driver please update using motherboard support page:
http://www.gigabyte.com/products/product-page.aspx?pid=3863#driver

HECIx64.sys Wed Oct 20 00:33:43 2010: Intel chipset management update via Intel update utility:
http://www.intel.com/p/en_US/support/detect

ISODrv64.sys Fri Jan 29 03:39:02 2010: ISO CD-ROM Device Driver - ISODrive please update:
http://www.ezbsystems.com/download.htm

VirtDiskBus64.sys Tue Feb 08 07:59:23 2011: Gigabyte 3TB+ Unlock Bus Enumerator later version under utility section on website:
http://www.gigabyte.com/products/product-page.aspx?pid=3863#utility

If after making the above changes you still get the bsod then you need to test your RAM.
Windows does have it's own memory testing app but it can often miss errors and the best app for the job is Memtest86. The latest version of which can be found here:
http://www.memtest.org/

To run Memtest86 you need to either burn a copy of it to disk or use a USB stick. If you look down the page you'll eventually find the latest version and it's associated downloads. If your burning to disk choose the pre-compiled iso zip. If your using a USB method then the corresponding download is the auto installer for a USB stick.
Once you have Memtest86 on the media you selected you'll then need to enter your bios and change the boot order so that the machine will boot from either the disk or stick you have Memtest86 on.
Run for at least 12hrs if possible unless it becomes clear that there is a issue. If there is a problem with the RAM you'll see the errors pop up in red so you can't miss them.
 
For how long? Anyhoo try the changes I posted first and only think about Memtest86 if the bsods continue
 
Code:
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1A, {41790, fffffa80047f3fd0, ffff, 0}

Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_PROCESS_HEAP::FreeBlock+53 )

Followup: MachineOwner
Yup same bugcheck but that isn't really surprising as you didn't follow any of my suggestions above. It looks like this was generated by the graphics card, try running this test:
http://mikelab.kiev.ua/index_en.php?page=PROGRAMS/vmt_en
 
Back
Top