BSOD. Nothing in Event Viewer.

I got a BSOD today right after rebooting to install the new security fix from Microsoft. I looked all through Event Viewer and the only thing I could find was warnings about no Ethernet cable being plugged in, but their shouldn't be, as I have a wireless connection. I also updated a few drivers the other day, but no reference to any driver was made in Event Viewer. I'm hopeless when it comes to reading these things so I zipped the minidump file for someone to look at.

I'm going to look up that command that test system integrity and run it in the mean time.
Attachment 89013

EDIT: while running SFC /scannow I got another BSOD during the first part of the test. It said something about BAD_POOL_CALLER
Attachment 89016

Looks like your getting BugCheck C2

*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
BAD_POOL_CALLER (c2)
The current thread is making a bad pool request. Typically this is at a bad IRQL level or double freeing the same allocation, etc.
Arguments:
Arg1: 0000000000000007, Attempt to free pool which was already freed
Arg2: 0000000000001097, (reserved)
Arg3: 0000000000000000, Memory contents of the pool block
Arg4: fffff8a00bea0010, Address of the block of pool being deallocated

Could be faulty RAM. Run MemTestx86 to be sure...

http://www.computing.net/answers/win...ss/146929.html

The first minidmp:

NTFS_FILE_SYSTEM (24)
If you see NtfsExceptionFilter on the stack then the 2nd and 3rd
parameters are the exception record and context record. Do a .cxr
on the 3rd parameter and then kb to obtain a more informative stack
trace.
Arguments:
Arg1: 00000000001904fb
Arg2: fffff88002439c08
Arg3: fffff88002439470
Arg4: fffff80002ad7805

This points also to bad ram (or possibly bad hd)

But with both, I'd say the ram is at fault...

Letting memtest run for 5 or 6 passes will take forever. But I'm the one that asked for help and I have some good 1GB sticks I can use if one stick is bad until I can buy some new RAM, so I'll do it and report back. Should I go ahead and do 1 stick at a time or do both at the same time?

One stick at a time would help determine which stick is at fault...

That's what I figured, but thought I'd ask first.

Update your Intel Wifi drivers:

Code:

igdkmd64.sys Wed Sep 23 15:22:57 2009 (4ABA7591)

Your Broadcom drivers are almost 4 years out of date, before Vista was released even. Make sure to update them, I suspect they are the cause.

Code:

b44amd64.sys Tue Nov 21 07:23:06 2006 (4562EFAA)

...Summary of the Dumps:

Code:

Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Mon Aug  2 18:37:42.372 2010 (UTC - 4:00)
System Uptime: 0 days 0:30:31.963
BugCheck C2, {7, 1097, 0, fffff8a00bea0010}
Probably caused by : Ntfs.sys ( Ntfs!NtfsDeleteFcb+3b7 )
BUGCHECK_STR:  0xc2_7
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
*** WARNING: Unable to verify timestamp for ?????????????????????????????????
*** ERROR: Module load completed but symbols could not be loaded for ?????????????????????????????????
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Mon Aug  2 18:06:47.835 2010 (UTC - 4:00)
System Uptime: 0 days 0:10:39.426
*** WARNING: Unable to verify timestamp for ?????????????????????????????????
*** ERROR: Module load completed but symbols could not be loaded for ?????????????????????????????????
*** WARNING: Unable to verify timestamp for ?????????????????????????????????????
*** ERROR: Module load completed but symbols could not be loaded for ?????????????????????????????????????
BugCheck 24, {1904fb, fffff88002439c08, fffff88002439470, fffff80002ad7805}
Probably caused by : ????????????????????????????????????? ( ______________________________________fffff8800125c000+213d8 )
BUGCHECK_STR:  0x24
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
  
  
 

As for the Memtest, run it on all sticks at the same time. That will tell us if there is a problem. Chances are RAM isn't even the problem, given the situation in which the BSODs arose.

If you get errors, test each stick individually.

I'm going to go ahead and make the disc for memtest and do at least 1 pass. The broadcam drivers are the Windows default drivers, hence the date (I've noticed that all windows 7 default drivers have the same date from 2006). I'm not sure if they make new drivers for my wireless card, but I will definitely look on Dell.com. I'm willing to bet that the drivers can be found on a page other than the one specifically for my computer. I've found a couple drivers that way. BTW I was wondering about the very drivers you mentioned Jon, so I know I need to do something if you and I have the same opinion about them.

I've ran into a little snag. I can't seem to find a 64-bit driver for the Broadcam ethernet port. Is there some kind of work around I can do, like disabling it or using a Realtek driver?

Go ahead and try the Realtek drivers.

Default Windows 7 drivers have the date July 13, 2009. 2006 drivers are not Windows 7.

The exception is secdrv.sys, dated 2006, which is not provided by Microsoft, but rather Macrovision. Amdxata.sys and Amdsata.sys are also default Windows drivers, dated April 2009, but are from AMD, not Microsoft.