Multiple random BSODs, different error each time

[meestersquishy]

I've got a custom built PC and since I built it's occasionally BSODed but I never got around to fixing it, and they usually happen about once a month so they weren't too annoying.
I've had 6 since Wednesday so something is definitely wrong, it also happens completely randomly, I've left it on desktop for like 5 minutes twice and BSODed both times.

 

[meestersquishy]

Had a few more BSODs so I'm adding an updated archive.

 

[koolkat77]

Please upload your msinfo32.nfo file. To get this:

1. Click on the Start rb:
2. Type msinfo32 into the Search programs and files box
3. When it opens, go to File, Save
4. Save as msinfo32.nfo and save in a place you will remember
5. Let it finish the process of gathering and saving the system info
6. Right click the .nfo file, click send to compressed (zipped) folder
7. Upload the .zip file here.

There seems to be a problem with the older Broadcom 802.11 USB Network Adapter Driver

3: kd> lmvm bcmwlhigh664
start             end                 module name
fffff880`04210000 fffff880`04347000   bcmwlhigh664 T (no symbols)           
    Loaded symbol image file: bcmwlhigh664.sys
    Image path: \SystemRoot\system32\DRIVERS\bcmwlhigh664.sys
    Image name: [COLOR="red"]bcmwlhigh664.sys[/COLOR]
    Timestamp:        [COLOR="Red"]Tue Apr 19 13:13:08 2011[/COLOR] (4DAD3604)
    CheckSum:         00137E7A
    ImageSize:        00137000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

STOP 0x00000034: CACHE_MANAGER  
Usual causes:  Insufficient physical memory, Indexing, Device driver
BugCheck 34, {50853, fffff88007eb4738, fffff88007eb3f90, fffff800032d6eee}
Probably caused by : ntkrnlmp.exe ( nt!ExAcquireResourceSharedLite+4e )
---------------
STOP 0x0000000A: IRQL_NOT_LESS_OR_EQUAL 
Usual causes:  Kernel mode driver, System Service, BIOS, Windows, Virus scanner, Backup tool, compatibility
BugCheck A, {fffffa802a00d1b0, 2, 1, fffff80003396376}
Probably caused by : memory_corruption ( nt!MiReleaseConfirmedPageFileSpace+86 )
------------------
STOP 0x00000024: NTFS_FILE_SYSTEM 
Usual causes:  Disk corruption, insufficient physical memory, Device driver, Indexing, Resident antivirus, backup, defrag programs, Disk/Drive failing/failure
BugCheck 24, {1904fb, fffff8800b1ee468, fffff8800b1edcc0, fffff80003277f75}
Probably caused by : Ntfs.sys ( Ntfs!NtfsDeleteScb+108 )
------------------
STOP 0x0000003B: SYSTEM_SERVICE_EXCEPTION   
Usual causes:  System service, Device driver, graphics driver, ?memory
BugCheck 3B, {c0000005, fffff8000331730c, fffff8800ba24e50, 0}
Probably caused by : memory_corruption ( nt!MiCaptureProtectionFromProto+1c )
------------------
STOP 0x0000001A: MEMORY_MANAGEMENT
Usual causes:  Device driver, memory, kernel
BugCheck 1A, {411, fffff68000016200, ec00, fffff68000000003}
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+6061 )

Upload a screenshot of crystal disk info

• CrystalDiskInfo - Software - Crystal Dew World
• http://www.sevenforums.com/tutorials/9733-screenshots-files-upload-post-seven-forums.html

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

• http://www.sevenforums.com/tutorials/433-disk-check.html

Hard drive test both short and long with:

• SeaTools for Windows

Also the DOS version of:

• SeaTools for DOS

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

→ http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html
→ Guide to using Memtest86+ - Geeks to Go Forums

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.

 

[meestersquishy]

Thanks for getting back to me!
If there is a problem with Broadcom 802.11 USB Network Adapter Driver, should I update those drivers?
I've uploaded the crystaldisk screenshots and the msinfo.
I ran a disk check on my ssd (my boot drive) before and there were no errors as far as i know since Windows just came back on.
I'll run memtest when I go to sleep which is in about an hour, although I did run Windows Memory Diagnostic before and got no errors.
SeaTools is running the long test now on my HDD, it passed the short tests.

It might be worth mentioning that I use a Razer Lycosa keyboard, and I saw a post that said they were notorious for BSOD, so I removed those drivers. I haven't had a BSOD since then but that was only about an hour ago.

 

[koolkat77]

Thanks for the snips.
Yes avoid the Razer Lycosa Keyboard, and update the broadcom drivers. Did you get the latest firmware for the SSD?
Keep us posted

 

[meestersquishy]

Ran memtest overnight on one stick of RAM, no errors with 7 passes, will test the other one tonight if the BSODs continue.
There is no newer firmware for the Corsair Nova 2 series SSD according to the official Corsair forums, also the Broadcom driver I have installed is actually the latest one, so I did a complete re install of the driver as per this forum post on here.
No BSODs since I uninstalled the Razer Lycosa driver, so far so good, I'll keep you posted and thanks very much for the help!

 

[koolkat77]

No problem, keep us posted either way

 

[meestersquishy]

I just got another BSOD a few minutes ago whilst playing Battlefield 3, I've uploaded another data archive.
Something I've noticed that might be worth mentioning, when my pc restarts afterwards, my Netgear N300 wireless usb network adapter (the hardware for the driver I reinstalled) isn't recognised, and I have to unplug it and plug it back in.

 

[koolkat77]

Please remove the Intel Rapid Storage things you have or get the latest version installed.

fffff880`09fec028  fffff880`045b0dd0Unable to load image \SystemRoot\System32\Drivers\dump_iaStor.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for dump_iaStor.sys
*** ERROR: Module load completed but symbols could not be loaded for dump_iaStor.sys
 dump_iaStor+0x376dd0

The seem to be causing some problems for you.

Also reinstall your graphic card drivers.

 

[meestersquishy]

Okay I removed it. What is Intel Rapid Storage for? Do I need it?
I'll re install my graphics card drivers now.

 

[koolkat77]

I'm not sure what it does, but if you think you don't need it you should uninstall it.

 

[meestersquishy]

Okay so I had a bit of trouble since my pc froze when I was uninstalling my GPU drivers, kept getting errors when trying to reinstall them. I finally got the display driver installed, but the 3D vision and PhysX drivers failed to install, and they are optional (I think).
Just got another BSOD and I've attached another archive.
I'm thinking of ordering some new RAM and returning my old RAM since that is starting to feel like the likely cause

 

[koolkat77]

MEMORY_MANAGEMENT (1a) does seem to be related to memory.
What were the results from memtest?

 

[meestersquishy]

Haven't been able to run a second test yet, leaving my pc on for 20+ hours isn't friendly on the electricity bill haha Will do it tonight.

 

[koolkat77]

Okay, update the thread when you're ready

 

[meestersquishy]

In the meantime I ran drive verifier, here is the archive which contains the stop code generated by it.

 

[meestersquishy]

Most recent archive with more crashes.

 

[koolkat77]

Update this driver from here: Driver Reference Table
Let us know the results from memtest.

2: kd> lmvm bcmwlhigh664
start             end                 module name
fffff880`03e75000 fffff880`03fac000   bcmwlhigh664 T (no symbols)           
    Loaded symbol image file: bcmwlhigh664.sys
    Image path: \SystemRoot\system32\DRIVERS\bcmwlhigh664.sys
    Image name: [COLOR="Blue"]bcmwlhigh664.sys[/COLOR]
    Timestamp:        [COLOR="blue"]Tue Apr 19 13:13:08 2011[/COLOR] (4DAD3604)
    CheckSum:         00137E7A
    ImageSize:        00137000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

 

[meestersquishy]

That is the latest version of that driver, and I have it installed, so I just reinstalled it again.

 

[koolkat77]

OK. Let us know the results of memtest when you're ready.