Windows 7: Frequently random BSOD.

schwartz31 · 28 Oct 2012

I've been getting BSOD frequently. When i'm playing games, surfing on the web, even while it's in idle. It's rly annoying.

Any help is welcome. thx

Gigabyte GA-870A-UD3 v2
QuadCore AMD Phenom II X4 Black Edition B55, 3.8 GHz
2x4Gb Exceleram DDR3 1600 MHz
NVIDIA GeForce GTX 275
WD Caviar Green 1 TB
Chieftec CTG-600-80P

Edit: ASUS W-card model: WL-138G V2

koolkat77 · 29 Oct 2012

Welcome

Please uninstall the following while troubleshooting with your computer:

Problematic software:

Code:

Start Menu\Programs\DAEMON Tools Lite	Public:Start Menu\Programs\DAEMON Tools Lite	Public

Remove Daemon Tools, sptd.sys is known to cause BSODs.

How to remove sptd.sys from system

Code:

Start Menu\Programs\ESET	Public:Start Menu\Programs\ESET	Public
Start Menu\Programs\ESET\ESET Smart Security	Public:Start Menu\Programs\ESET\ESET Smart Security	Public

ESET antivirus contributes in BSODs, please uninstall it with its removal tool (search in google) and replace with MSE (at least to test)

Recommended antivirus program for Windows 7 based on stability compared to others:-

Run a full scan with both (separately) once downloaded, installed and updated.

BSOD Analyze

Uninstall the drivers from program from control panel first then delete remnants of the drivers above using Driver Sweeper, then install the latest.

Get the latest drivers for Realtek RTL8168D/8111D Family PCI-E Gigabit Ethernet NIC installed. Source

Code:

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

Use !analyze -v to get detailed debugging information.

BugCheck D1, {0, 2, 0, fffff88007a1ae8d}

*** WARNING: Unable to verify timestamp for Rt64win7.sys
*** ERROR: Module load completed but symbols could not be loaded for Rt64win7.sys
Probably caused by : Rt64win7.sys ( Rt64win7+18e8d )

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

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

DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high.  This is usually
caused by drivers using improper addresses.
If kernel debugger is available get stack backtrace.
Arguments:
Arg1: 0000000000000000, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
Arg4: fffff88007a1ae8d, address which referenced memory

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


READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002efb100
GetUlongFromAddress: unable to read from fffff80002efb1c0
 0000000000000000 Nonpaged pool

CURRENT_IRQL:  2

FAULTING_IP: 
Rt64win7+18e8d
fffff880`07a1ae8d 418bc6          mov     eax,r14d

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

BUGCHECK_STR:  0xD1

PROCESS_NAME:  System

TAG_NOT_DEFINED_c000000f:  FFFFF80000BA2FB0

TRAP_FRAME:  fffff80000b9c330 -- (.trap 0xfffff80000b9c330)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000002 rbx=0000000000000000 rcx=0000000000000000
rdx=fffffa80084dd000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff88007a1ae8d rsp=fffff80000b9c4c0 rbp=fffffa800886a500
 r8=0000000000000000  r9=0000000000000000 r10=fffff80002e3ee80
r11=0000000000000002 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz na pe nc
Rt64win7+0x18e8d:
fffff880`07a1ae8d 418bc6          mov     eax,r14d
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002ccb569 to fffff80002ccbfc0

STACK_TEXT:  
fffff800`00b9c1e8 fffff800`02ccb569 : 00000000`0000000a 00000000`00000000 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff800`00b9c1f0 fffff800`02cca1e0 : fffff800`00040001 00000000`0000000f 00000000`00000000 fffffa80`084dd000 : nt!KiBugCheckDispatch+0x69
fffff800`00b9c330 fffff880`07a1ae8d : 00000000`00000000 00000000`00000000 fffff800`00b9c660 fffff800`02dba421 : nt!KiPageFault+0x260
fffff800`00b9c4c0 00000000`00000000 : 00000000`00000000 fffff800`00b9c660 fffff800`02dba421 fffff800`02e40100 : Rt64win7+0x18e8d


STACK_COMMAND:  kb

FOLLOWUP_IP: 
Rt64win7+18e8d
fffff880`07a1ae8d 418bc6          mov     eax,r14d

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  Rt64win7+18e8d

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: Rt64win7

IMAGE_NAME:  Rt64win7.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4e81e2b9

FAILURE_BUCKET_ID:  X64_0xD1_Rt64win7+18e8d

BUCKET_ID:  X64_0xD1_Rt64win7+18e8d

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

0: kd> lmvm Rt64win7
start             end                 module name
fffff880`07a02000 fffff880`07aa2000   Rt64win7 T (no symbols)           
    Loaded symbol image file: Rt64win7.sys
    Image path: \SystemRoot\system32\DRIVERS\Rt64win7.sys
    Image name: Rt64win7.sys
    Timestamp:        Tue Sep 27 20:50:33 2011 (4E81E2B9)
    CheckSum:         0009FB77
    ImageSize:        000A0000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Get the latest drivers for Broadcom 802.11g Network Adapter - Dell Wireless 1390 WLAN Mini-Card.

Code:

2: kd> lmvm bcmwl664
start             end                 module name
fffff880`072c9000 fffff880`07582000   bcmwl664 T (no symbols)           
    Loaded symbol image file: bcmwl664.sys
    Image path: \SystemRoot\system32\DRIVERS\bcmwl664.sys
    Image name: bcmwl664.sys
    Timestamp:        Fri Oct 23 23:32:30 2009 (4AE1E8AE)
    CheckSum:         002C4C85
    ImageSize:        002B9000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Run the System File Checker that scans the of all protected Windows 7 system files and replaces incorrect corrupted, changed/modified, or damaged versions with the correct versions if possible:

SFC /SCANNOW Command - System File Checker

Run Disk Check on your hard disk for file system errors and bad sectors on it:

Disk Check

Let us know the results

schwartz31 · 29 Oct 2012

Thx for reply.

I'm done with everything u said, just scan left to take care and..

I'm scanning with MSE atm. And have one question. My PC using ASUS W-card model: WL-138G V2. You said to update my W-card Dell Wireless?

Quote:

Get the latest drivers for Broadcom 802.11g Network Adapter - Dell Wireless 1390 WLAN Mini-Card.

My bad i forgot to add model for my Wireless card in first post. So should i install Dell driver or download from ASUS for my model ? thx

koolkat77 · 29 Oct 2012

Yes you can do that and sorry I forgot to post the link to it, Driver Reference Table

schwartz31 · 30 Oct 2012

Another BSOD occurred. :\ Dell Wireless driver was installed. Last dmp file is in attachment.

MSE and Malwarebytes says nothing about infections.
Last Realtek drivers are installed.
Currently Wireless driver is installed from ASUS site for Windows 7 x64. Tell me if im doing something wrong..

Code:

http://www.asus.com/Networks/Wireless_Adapters/WL138g_V2/#download

Also Daemon tools has been removed from system.

Thx.

koolkat77 · 30 Oct 2012

Code:

STOP 0x0000003B: SYSTEM_SERVICE_EXCEPTION  
Usual causes:  System service, Device driver, graphics driver, ?memory
BugCheck 3B, {c0000005, fffff80002f9c210, fffff88009477700, 0}
Probably caused by : ntkrnlmp.exe ( nt!ObDereferenceSecurityDescriptor+20 )
PROCESS_NAME:  uTorrent.exe

Take memtest. Run for 8 passes and test each stick in a know good slot for an additional 6 passes.

Quote:

The goal is to test all the RAM sticks and all the motherboard slots.

Check your motherboard manual to ensure the RAM sticks are in the recommended motherboard slots. Some motherboards have very specific slots required for the number of RAM sticks installed.

If you get errors, stop the test and continue with the next step.

1. Remove all but one stick of RAM from your computer (this will be RAM stick #1), and run Memtest86 again, for 7 passes.
Be sure to note the RAM stick, use a piece of tape with a number, and note the motherboard slot.
If this stick passes the test then go to step #3.

2. If RAM stick #1 has errors, repeat the test with RAM stick #2 in the same motherboard slot.
If RAM stick #2 passes, this indicates that RAM stick #1 may be bad. If you want to be absolutely sure, re-test RAM stick #1 in another known good slot.
If RAM stick #2 has errors, this indicates another possible bad RAM stick, a possible motherboard slot failure or inadequate settings.
3. Test the next stick of RAM (stick #2) in the next motherboard slot.
If this RAM stick has errors repeat step #2 using a known good stick if possible, or another stick.
If this RAM stick has no errors and both sticks failed in slot#1, test RAM stick #1 in this slot.
4. If you find a stick that passes the test, test it in all the other motherboard slots.

If Part 2 testing shows errors, and all tests in Part 3 show errors, you will need to test the RAM sticks in another computer and/or test other RAM in your computer to identify the problem.

In this way, you can identify whether it is a bad stick of RAM, a bad motherboard, or incompatibility between the sticks.

schwartz31 · 31 Oct 2012

Test is still working (more then 10hours). So far no errors.
Do i need to test each stick if test doesnt say any error at the end?

I have one more graph. card available for testing. if its graph card fault. Let me know what to do next.

Thx for help so far. Really appreciate.

koolkat77 · 31 Oct 2012

OK, test the ram that way later. And yes you could try the other graphics card

Keep us posted

schwartz31 · 02 Nov 2012

Here we go again.

After changing graph. cards. both PC's was working ok till this morning. dmp file is in attachment.

Back to RAM tests i guess. Or should i try to do something new?

koolkat77 · 02 Nov 2012

Proceed with ram test, I will let you know if I find anything interesting from the .dmp

Edit: Looks like the drivers weren't updated.

Check if this link is helpful: Broadcom Wireless Win64bit BSOD bcmwl664.sys Fix - RRTech...The SOURCE for Extreme Liquid Cooling or this Downloads | Broadcom

Code:

3: kd> lmvm bcmwl664
start             end                 module name
fffff880`05664000 fffff880`0591d000   bcmwl664 T (no symbols)           
    Loaded symbol image file: bcmwl664.sys
    Image path: \SystemRoot\system32\DRIVERS\bcmwl664.sys
    Image name: bcmwl664.sys
    Timestamp:        Fri Oct 23 23:32:30 2009 (4AE1E8AE)
    CheckSum:         002C4C85
    ImageSize:        002B9000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Windows 7: Frequently random BSOD.

Frequently random BSOD. problems?