200+ bsod

will do.. Thanks.

FYI the sptd-removal tool cannot locate any sptd.sys so it wont let me repeat the removal. I think im good here.


And the removal tool for AVG finished off AVG while I was in safe mode. When i run it now, it will just look for files and eventualy quit the cmd-window.

Both removals appear to be succesfull.

Fear not.

I got some fresh BSOD for u Some time high frequency BSODs can be a blessing!

Simpe file browsing + while sfc /scannow was running = boooom..

deeptrouble said:

Fear not.

I got some fresh BSOD for u Some time high frequency BSODs can be a blessing!

Simpe file browsing + while sfc /scannow was running = boooom..

Well if you cant even complete an SFC it is time to start thinking a repair (or clean) install.

You still have old drivers in the most current DMP Even your video driver is over a year old

Code:

BASFND.sys        fffff880`05f30000    fffff880`05f37000    0x00007000    0x3ea87078    4/24/2003 19:17:12                                               
GRMNGEN.SYS        fffff880`0478b000    fffff880`04798000    0x0000d000    0x49f9d5a6    4/30/2009 12:45:26                        
grmnusb.sys        fffff880`04782000    fffff880`0478b000    0x00009000    0x49f9d5a7    4/30/2009 12:45:27                        
spldr.sys        fffff880`0175d000    fffff880`01765000    0x00008000    0x4a0858bb    5/11/2009 12:56:27                        
amdxata.sys        fffff880`011eb000    fffff880`011f6000    0x0000b000    0x4a12f2eb    5/19/2009 13:56:59                        
k57nd60a.sys        fffff880`05387000    fffff880`053d8000    0x00051000    0x4a2b6e02    6/7/2009 03:36:34                        
nvBridge.kmd        fffff880`05385000    fffff880`05386180    0x00001180    0x4a54c9db    7/8/2009 12:31:23                        
nvlddmkm.sys        fffff880`04888000    fffff880`05384e00    0x00afce00    0x4a54dae6    7/8/2009 13:44:06   

EDIT: BTW LAST CRASH CAUSED BY MEMORY ORRUPTION

Code:

Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\K\Desktop\Windows7_BSOD_jcgriff2\081810-18735-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

WARNING: Whitespace at end of path element
Symbol search path is: SRV*C:\symbols;*http://msdl.microsoft.com/download/symbols ;srv*e:\symbols
*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Machine Name:
Kernel base = 0xfffff800`02e5b000 PsLoadedModuleList = 0xfffff800`03098e50
Debug session time: Wed Aug 18 16:49:19.830 2010 (GMT-4)
System Uptime: 0 days 0:02:17.970
Loading Kernel Symbols
...............................................................
................................................................
.................
Loading User Symbols
Loading unloaded module list
...
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck D1, {2, 2, 1, fffff880014cc882}

Probably caused by : memory_corruption

Followup: memory_corruption
---------

6: 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: 0000000000000002, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000001, value 0 = read operation, 1 = write operation
Arg4: fffff880014cc882, address which referenced memory

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


WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff800031030e0
 0000000000000002 

CURRENT_IRQL:  2

FAULTING_IP: 
ndis!ndisReferenceTopMiniportByNameForNsi+1b2
fffff880`014cc882 8800            mov     byte ptr [rax],al

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  CODE_CORRUPTION

BUGCHECK_STR:  0xD1

PROCESS_NAME:  svchost.exe

TRAP_FRAME:  fffff88005aad2d0 -- (.trap 0xfffff88005aad2d0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000002 rbx=0000000000000000 rcx=fffffa8005d54d48
rdx=0000000000000002 rsi=0000000000000000 rdi=0000000000000000
rip=fffff880014cc882 rsp=fffff88005aad460 rbp=0000000000000002
 r8=0000000000000000  r9=0000000000000000 r10=0000000000000238
r11=0000000000000002 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl zr na po nc
ndis!ndisReferenceTopMiniportByNameForNsi+0x1b2:
fffff880`014cc882 8800            mov     byte ptr [rax],al ds:a800:00000000`00000002=??
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002ecab69 to fffff80002ecb600

STACK_TEXT:  
fffff880`05aad188 fffff800`02ecab69 : 00000000`0000000a 00000000`00000002 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
fffff880`05aad190 fffff800`02ec97e0 : fffff880`05aad5d0 00000000`00000000 00000000`00000000 fffff880`05aad380 : nt!KiBugCheckDispatch+0x69
fffff880`05aad2d0 fffff880`014cc882 : fffffa80`05d54d48 fffff800`02ed89f2 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x260
fffff880`05aad460 fffff880`014cd6a7 : fffffa80`0432e138 00000000`00000001 fffffa80`04c44802 fffff880`0152a800 : ndis!ndisReferenceTopMiniportByNameForNsi+0x1b2
fffff880`05aad4e0 fffff880`0162f02b : 00000000`00000000 fffffa80`00000008 00000000`00000290 fffffa80`00000238 : ndis!ndisNsiEnumerateAllInterfaceInformation+0x1e8
fffff880`05aad5d0 fffff880`03debe29 : fffffa80`0432e000 fffff8a0`00000070 fffffa80`075b18d0 00000000`00cae390 : NETIO!NsiEnumerateObjectsAllParametersEx+0x24f
fffff880`05aad7b0 fffff880`03ded8e8 : fffffa80`075b18d0 fffffa80`075b1800 fffffa80`0129b790 fffffa80`075b1838 : nsiproxy!NsippEnumerateObjectsAllParameters+0x305
fffff880`05aad9a0 fffff880`03ded9db : fffffa80`05d307f0 00000000`00000000 00000000`00000001 00000000`00000003 : nsiproxy!NsippDispatchDeviceControl+0x70
fffff880`05aad9e0 fffff800`031e76b7 : fffffa80`06b80710 fffffa80`06b80710 fffffa80`075b1918 fffffa80`075b1800 : nsiproxy!NsippDispatch+0x4b
fffff880`05aada10 fffff800`031e7f16 : 00000000`00cae210 00000000`000004e8 00000000`00000000 00000000`00000000 : nt!IopXxxControlFile+0x607
fffff880`05aadb40 fffff800`02eca853 : fffffa80`040d9550 00000000`00cae1f8 fffff880`05aadbc8 00000000`00000001 : nt!NtDeviceIoControlFile+0x56
fffff880`05aadbb0 00000000`76fbfdca : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`00cae288 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x76fbfdca


STACK_COMMAND:  kb

CHKIMG_EXTENSION: !chkimg -lo 50 -db !ndis
24 errors : !ndis (fffff880014cc880-fffff880014ccdb8)
fffff880014cc880 *69  24  88  00  00  00  4c  8b *ea  24  40  48  8b  74  24  48 i$....L..$@H.t$H
fffff880014cc890 *19  8b  9c  24  80  00  00  00 *75  8d  0d  69  02  06  00  40 ...$....u..i...@
fffff880014cc8a0 *84  b6  d5  ff  15  bf  ee  04 *83  41  8a  c4  48  83  c4  50 .........A..H..P
fffff880014cc8b0 *96  5f  41  5d  41  5c  5f  5d *0c  48  8d  4b  60  ff  15  5d ._A]A\_].H.K`..]
...
fffff880014ccd00 *9f  00  00  00  0f  b6  d8  74 *64  83  45  50  ff  0f  84  1b .......td.EP....
fffff880014ccd10 *6d  01  00  80  7c  24  30  00 *23  85  ed  00  00  00  40  84 m...|$0.#.....@.
fffff880014ccd20 *5f  74  19  83  46  50  ff  0f *36  43  94  01  00  45  84  ff _t..FP..6C...E..
fffff880014ccd30 *64  0a  83  46  54  ff  0f  84 *00  94  01  00  48  8d  0d  7d d..FT.......H..}
...
fffff880014ccd80 *58  0f  b6  f0  75  0e  48  83 *ac  68  11  00  00  00  0f  85 X...u.H..h......
fffff880014ccd90 *6a  94  01  00  33  c0  49  8d *60  60  40  0f  b6  d6  49  89 j...3.I.``@...I.
fffff880014ccda0 *5a  08  02  00  00  89  83  08 *da  00  00  ff  15  b7  e9  04 Z...............
fffff880014ccdb0 *b4  48  8b  cb  e8  17  03  08 *1e  48  8b  0d  50  c3  05  00 .H.......H..P...

MODULE_NAME: memory_corruption

IMAGE_NAME:  memory_corruption

FOLLOWUP_NAME:  memory_corruption

DEBUG_FLR_IMAGE_TIMESTAMP:  0

MEMORY_CORRUPTOR:  STRIDE

FAILURE_BUCKET_ID:  X64_MEMORY_CORRUPTION_STRIDE

BUCKET_ID:  X64_MEMORY_CORRUPTION_STRIDE

Followup: memory_corruption
---------

Hello zigzag.

Well im not sure if my computer is able to do a sfc. I just had the BSOD while i was trying. I havent tried to reproduce .. yet.

It would be nice if the computer could get back in shape without any reinstallation.

I agree drivers from 2003 should get updated. Google tells me it is related to broadcom network drivers. Should i update my network driver?

My videodriver is the newest driver recommended from dell for my vostro 430. I can update it to latest generic nvidia if that would be better?

I updated my broadcom network card driver.

how do I confirm the old driver file is unused now?

Im doing a new BSOD_Windows7_Vista_v3.02_jcgriff2_ , but there is no new BSOD. so far..

deeptrouble said:

I updated my broadcom network card driver.

how do I confirm the old driver file is unused now?

Easiest way is to search for the name and look at the modifed date. Failing that wait for the next BSOD.

How To Find Drivers:

- search Google for the name of the driver
- compare the Google results with what's installed on your system to figure out which device/program it belongs to
- visit the web site of the manufacturer of the hardware/program to get the latest drivers (DON'T use Windows Update or the Update driver function of Device Manager).
- if there are difficulties in locating them, post back with questions and someone will try and help you locate the appropriate program.

- - The most common drivers are listed on this page: Driver Reference
- - Driver manufacturer links are on this page: Drivers and Downloads

BASFND.sys belongs to BACS3 which is a management app from broadcom. It was preinstalled when I got the computer.

If it is still to be considered a problem I can remove BACS3 entirely. The network card should work without it.

Or else I will proceed with enable driver verifier.

Or wait for a new BSOD?