Regular BSOD seemingly while idling

Kable72 · Nov 14, 2012

Hey guys

Getting a BSOD error that happens on a regular occasion. Has happened nearly everyday this month and isn't uncommon for it to BSOD just after the first one. Seems to be the same driver that is causing the issue and I don't know where to start. Attached are my minidumps

Arc · Nov 15, 2012

Hello Kable72.

► Install Service pack 1.

Code:

[COLOR=Red]Windows 7 Kernel Version 7600 MP [/COLOR](4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.17118.amd64fre.win7_gdr.120830-0334

Learn how to install Windows 7 Service Pack 1 (SP1)
Service Pack Center - Microsoft Windows

► Enable Driver Verifier.

Code:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

[COLOR=Red]BugCheck 19[/COLOR], {20, fffff8800c701c40, fffff8800c702bc0, 5f88361}

GetPointerFromAddress: unable to read from fffff8000330c0e0
GetUlongFromAddress: unable to read from fffff8000330c198
GetUlongFromAddress: unable to read from fffff8000327a1b0
Probably caused by : ntkrnlmp.exe ( nt!ExAllocatePoolWithTag+1a64 )

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

1: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

[COLOR=Red]BAD_POOL_HEADER (19)[/COLOR]
The pool is already corrupt at the time of the current request.
This may or may not be due to the caller.
The internal pool links must be walked to figure out a possible cause of
the problem, and [COLOR=Red]then special pool applied to the suspect tags or the driver
verifier to a suspect driver.[/COLOR]
Arguments:
Arg1: 0000000000000020, a pool block header size is corrupt.
Arg2: fffff8800c701c40, The pool entry we were looking for within the page.
Arg3: fffff8800c702bc0, The next pool entry.
Arg4: 0000000005f88361, (reserved)

Debugging Details:
------------------

GetUlongFromAddress: unable to read from fffff8000327a1b0

BUGCHECK_STR:  0x19_20

POOL_ADDRESS:  fffff8800c701c40 Nonpaged pool

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

PROCESS_NAME:  sidebar.exe

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from fffff800032076d3 to fffff800030d55c0

STACK_TEXT:  
fffff880`063ad8c8 fffff800`032076d3 : 00000000`00000019 00000000`00000020 fffff880`0c701c40 fffff880`0c702bc0 : nt!KeBugCheckEx
fffff880`063ad8d0 fffff800`03486536 : fffff8a0`00b545f0 fffff880`063adca0 fffff880`69634d43 00000000`000004ef : nt!ExAllocatePoolWithTag+0x1a64
fffff880`063ad980 fffff800`033adf4e : 00000000`00000016 fffff880`063adb48 fffffa80`09d32300 fffff800`00000016 : nt!CmpCallCallBacks+0x4f6
fffff880`063ada50 fffff800`030d4813 : fffffa80`0b603060 fffff800`00000007 00000000`028466d8 00000000`02e554f0 : nt!NtQueryKey+0x44c
fffff880`063adbb0 00000000`772cf81a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`028466b8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x772cf81a


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!ExAllocatePoolWithTag+1a64
fffff800`032076d3 cc              int     3

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt!ExAllocatePoolWithTag+1a64

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  503f857d

FAILURE_BUCKET_ID:  X64_0x19_20_nt!ExAllocatePoolWithTag+1a64

BUCKET_ID:  X64_0x19_20_nt!ExAllocatePoolWithTag+1a64

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

In such a situation, it is better to 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.

► upload your MSINFO32.nfo file.

Click on the start button
Type "msinfo32" (without quotes) in the search bar of the start menu, click the resulting link. It will open the System Information window.
File>Save. In the "File Name" filed, put "MSINFO32" (without Quote), give the save location to desktop, and click the "save" button.
Give the time for processing, it will save a .nfo file on your desktop.
Zip it, and upload it following the instruction.

Let us know the results, with the subsequent crash dumps, if any.

Kable72 · Dec 10, 2012

Hey sorry been REALLY busy with work recently. Attached is the .nfo and driver verifier has been activated.

Kable72 · Dec 10, 2012

okay when I activated Driver Verifier, it had crashed twice before windows had successfully loaded. I assume 2 dump files will be sufficient?

Kable72 · Dec 10, 2012

2 BSOD since this morning.

Kable72 · Dec 11, 2012

Arc · Dec 11, 2012

Code:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck C9, {23e, fffff880015b6324, fffff980085c8ee0, 0}

Unable to load image dtsoftbus01.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for dtsoftbus01.sys
*** ERROR: Module load completed but symbols could not be loaded for dtsoftbus01.sys
[COLOR=Red]Probably caused by : dtsoftbus01.sys [/COLOR]( dtsoftbus01+1324 )

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

Uninstall Daemon tools.

Code:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 3B, {c0000005, fffff800030c2bd6, fffff880063c9850, 0}

Probably caused by : fileinfo.sys ( fileinfo!FIStreamGetInfo+11f )

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

Do some disc checks.

Update your SSD's Firmware (skip it, if it is not a SSD)
Re-seat the sata and power.
Run chkdsk /f/r, following the option two of the tutorial Disk Check
Seatool for dos: SeaTools | Seagate download
Burn it in a blank cd. boot from the CD, click on "Accept", wait for it to finish detecting the drives, then in the upper left corner select "Basic Tests", then select "Long Test" and let it run.

Let us know the results.

Kable72 · Dec 11, 2012

Uninstalled Daemon tools and running the chkdsk now. Hopefully be done by the time I'm home at lunch time. Will let you know, thanks

Kable72 · Dec 11, 2012

Chkdsk finished running, running the SeaTools now. Will let you know

Kable72 · Dec 12, 2012

SeaTools ran and passed on the LongTest

Arc · Dec 12, 2012

All is good

Let us know ... is it crashing still?

Kable72 · Dec 12, 2012

Left the PC on over night and not a single crash

On another note, it seems to have also solved my network drop outs as well. 2 birds with one stone?

Arc · Dec 13, 2012

Kable72 said:
Left the PC on over night and not a single crash

On another note, it seems to have also solved my network drop outs as well. 2 birds with one stone?

Really a very good news!

Kable72 · Dec 13, 2012

Okay some I seem to have been jumping the gun a little, had a crash about 5 minutes ago. Uploading dump

Arc · Dec 14, 2012

It is caused by Broadcom 802.11 USB Network Adapter Driver.

Code:

fffff880`0319ab98  fffff880`060fe1efUnable to load image bcmwlhigh664.sys, Win32 error 0n2
[COLOR=Red]*** WARNING: Unable to verify timestamp for bcmwlhigh664.sys
*** ERROR: Module load completed but symbols could not be loaded for bcmwlhigh664.sys
 bcmwlhigh664+0x951e[/COLOR]f

Which is kinda old.

Code:

  lmvm bcmwlhigh664
start             end                 module name
fffff880`06069000 fffff880`061a0000   bcmwlhigh664 T (no symbols)           
    Loaded symbol image file: bcmwlhigh664.sys
    Image path: bcmwlhigh664.sys
   [COLOR=Red] Image name: bcmwlhigh664.sys
    Timestamp:        Tue Apr 19 12:43:08 2011 [/COLOR](4DAD3604)
    CheckSum:         00137E7A
    ImageSize:        00137000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Update it from Welcome to NETGEAR Support.

Kable72 · Dec 14, 2012

Gone ahead and updated those drivers. Hopefully that will be the end of this

Kable72 · Dec 26, 2012

All is not well with my PC. 3 BSOD in about the period of about 6 hours, uploading mini dumps

Arc · Dec 27, 2012

Realtek RTL8168D/8111D Family PCI-E Gigabit Ethernet NIC driver

Code:

fffff880`031bcf08  fffff880`0402ad5aUnable to load image Rt64win7.sys, Win32 error 0n2
[COLOR=Red]*** WARNING: Unable to verify timestamp for Rt64win7.sys
*** ERROR: Module load completed but symbols could not be loaded for Rt64win7.sys
 Rt64win7+0x6d5a[/COLOR]

And that is very old .....

Code:

 lmvm rt64win7
start             end                 module name
fffff880`04024000 fffff880`04056000   Rt64win7 T (no symbols)           
    Loaded symbol image file: Rt64win7.sys
    Image path: Rt64win7.sys
[COLOR=Red]    Image name: Rt64win7.sys
    Timestamp:        Thu Feb 26 14:34:13 2009 [/COLOR](49A65B0D)
    CheckSum:         000361A5
    ImageSize:        00032000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Update it from Realtek.

Update your ATI/AMD display driver.
You can get it from the link in our forum, http://www.sevenforums.com/graphic-...alyst-video-driver-windows-7-a.html#post17671, or you may go to AMD Graphics Driver and Software and opt for Automatically Detect and Install the appropriate driver for your card.

During installation, you may opt for advanced installation, and install the display driver only, not the Catalyst Control Center.

Let us know the results.

Kable72 · Dec 27, 2012

Would it matter if I don't have Ethernet cables plugged in as I use WiFi

Arc · Dec 27, 2012

It should not matter.

Regular BSOD seemingly while idling

Banned

My Computer

New member

My Computer

Banned

My Computer

Banned

My Computer

Banned

My Computer

Banned

My Computer

New member

My Computer

Banned

My Computer

Banned

My Computer

Banned

My Computer

New member

My Computer

Banned

My Computer

New member

My Computer

Banned

My Computer

New member

My Computer

Banned

My Computer

Banned

My Computer

New member

My Computer

Banned

My Computer

New member

My Computer

Similar threads