Multiple, assorted BSODs in 2 days...

[Roundhouse]

Hi all,

I have been experiencing an assorted bunch of BSODs lately. I recently just upgraded my vcard to an nVidia one. I used to have an ATI gpu because I wanted an all AMD setup (790GX mobo + HD4830 gpu). Thinking that it might be a driver conflict prob, I removed the nvidia display drivers and also used DriverSweeper to clean what's left, but I am still experiencing BSODs.

I tried the windows memory diagnostic app. at first it saw errors on my RAM, so I tested both dual-channel pairs (I have 2 pairs btw, a 2GB and a 4GB) separately. The errors were gone. I even tried memtest86+ 4.10. When I tried memtest, I left it for 2 hours, all passed. I even looped test #5, it passed.

So here I am desperate for help...

Attached are al the dumps. The earliest one is when I still had my ATI HD4830 plugged in. Not sure about the 2 "not dated" ones. The others dated August 7th are already using the nVidia GTX460.

NOTE : I couldn't generate a report using perfmon /report as I am getting a "System cannot find the path specified" error. I am currently running on safe mode.

BSODs:
REFERENCE_BY_POINTER
PAGE_FAULT_IN_NON_PAGED_AREA
SYSTEM_SERVICE_EXCEPTION
IRQL_NOT_LESS_OR_EQUAL
"BAD_POOL" - forgot the error... but it was something about POOL or something

System specs:
- Windows 7 x64 Ultimate (Retail)
- AMD Phenom II 720 BE - 1 year 3 months old
- MSI 790GX-G65 - 7 months old
- 1x2 2GB GEIL DDR3 - 7 months old
- 2x2 4GB Team Elite DDR3 - 3 months old
- Inno3D GTX460 1GB - 5 days old
- Corsair HX520 PSU - 1 year 3 months old
- haven't overclocked any components

 

[zigzag3143]

Hi all,

I have been experiencing an assorted bunch of BSODs lately. I recently just upgraded my vcard to an nVidia one. I used to have an ATI gpu because I wanted an all AMD setup (790GX mobo + HD4830 gpu). Thinking that it might be a driver conflict prob, I removed the nvidia display drivers and also used DriverSweeper to clean what's left, but I am still experiencing BSODs.

I tried the windows memory diagnostic app. at first it saw errors on my RAM, so I tested both dual-channel pairs (I have 2 pairs btw, a 2GB and a 4GB) separately. The errors were gone. I even tried memtest86+ 4.10. When I tried memtest, I left it for 2 hours, all passed. I even looped test #5, it passed.

So here I am desperate for help...

Attached are al the dumps. The earliest one is when I still had my ATI HD4830 plugged in. Not sure about the 2 "not dated" ones. The others dated August 7th are already using the nVidia GTX460.

NOTE : I couldn't generate a report using perfmon /report as I am getting a "System cannot find the path specified" error. I am currently running on safe mode.

BSODs:
REFERENCE_BY_POINTER
PAGE_FAULT_IN_NON_PAGED_AREA
SYSTEM_SERVICE_EXCEPTION
IRQL_NOT_LESS_OR_EQUAL
"BAD_POOL" - forgot the error... but it was something about POOL or something

System specs:
- Windows 7 x64 Ultimate (Retail)
- AMD Phenom II 720 BE - 1 year 3 months old
- MSI 790GX-G65 - 7 months old
- 1x2 2GB GEIL DDR3 - 7 months old
- 2x2 4GB Team Elite DDR3 - 3 months old
- Inno3D GTX460 1GB - 5 days old
- Corsair HX520 PSU - 1 year 3 months old
- haven't overclocked any components

Roundhouse

These crashes have 4 apparent causes, that all seem to relate to memory. I see that you have run memtest but wonder if you ran the memory one stick at a time, and checked one mobo slot at a time.

I am assuming you are not overclocking, and not running a raid.

there are a few things you can do to find out the actual cause.

The results from the DMP files do not give a definitive answer. While we investigate further here are a few things that you can do>

1-Run a system file check to verify and repair you system files. You do this by typing cmd in search, then right click and run as admin. SFC/ SCANNOW

2-Download a 3rd party app called memtestx86, burn it so cd, and run memtest for 5-6 passes. (I know but try it one stick at a time)

3-Event viewer
There are several ways to find what the problem is. The best is to go into event viewer (type eventvwr in search). Go to the windows log>application tab.

You want to look for critical errors (they have red in the left column ).

When you find them you want to look for critical errors that say app hang, app crash, or anything that relates to the problem.

When you find them please note the event ID, and the source codes and tell us what they are.

4-Device manager
Please go to start>search>type device manager.
Are there any "unknown devices" with yellow triangles on them?
Is you driver there , listed, and working?

If your driver is missing, or there is a yellow triangle on it, you will need to update it.

5-Driver verifier
Beyond that, please run Verifier with these settings:

Using Driver Verifier is an iffy proposition. Most times it'll crash and it'll tell you what the driver is. But sometimes it'll crash and won't tell you the driver. Other times it'll crash before you can log in to Windows. If you can't get to Safe Mode, then you'll have to resort to offline editing of the registry to disable Driver Verifier.

So, I'd suggest that you first backup your stuff and then make sure you've got access to another computer so you can contact us if problems arise. Then make a System Restore point (so you can restore the system using the Vista/Win7 Startup Repair feature).

Then, here's the procedure:
- Go to Start and type in "verifier" (without the quotes) and press Enter
- Select "Create custom settings (for code developers)" and click "Next"
- Select "Select individual settings from a full list" and click "Next"
- Select everything EXCEPT FOR "Low Resource Simulation" and click "Next"
NOTE: You can use Low Resource Simulation if you'd like. From my limited experimentation it makes the BSOD's come faster.
- Select "Select driver names from a list" and click "Next"
Then select all drivers NOT provided by Microsoft and click "Next"
- Select "Finish" on the next page.

Reboot the system and wait for it to crash to the Blue Screen. Continue to use your system normally, and if you know what causes the crash, do that repeatedly. The objective here is to get the system to crash because Driver Verifier is stressing the drivers out. If it doesn't crash for you, then let it run for at least 36 hours of continuous operation (an estimate on my part).

Reboot into Windows (after the crash) and turn off Driver Verifier by going back in and selecting "Delete existing settings" on the first page, then locate and zip up the memory dump file and upload it with your next post.

If you can't get into Windows because it crashes too soon, try it in Safe Mode.
If you can't get into Safe Mode, try using System Restore from your installation DVD to set the system back to the previous restore point that you created.

If that doesn't work, post back and we'll have to see about fixing the registry entry off-line:

Delete these registry keys (works in XP, Vista, Win7):
        HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\VerifyDrivers
        HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\VerifyDriverLevel

More info on this at this link: Using Driver Verifier to identify issues with Windows drivers for advanced users

Let us know if you need assistance with this


Ken

 

[Roundhouse]

Hi Ken,

Thanks for the reply.

Yes you are right, I tested all four sticks on all four slots. So I need to test each stick on its own on all 4 slots? or just on the DIMM 1 slot?

As for your instructions:

for #1, the scan returned no integrity violations
for #2, im currently working on it
- memtest86+ right?
- each stick on DIMM 1?
- what tests do i run? would looping just test #5 for 5-6 passes be alright?
for #3, i saw a couple of app hangs for explorer.exe (evet id 1002). But i think this was when i tried to boot normally but everything was black so I ended the explorer.exe process and ran a new one. so not much help on the event viewer.
for #4, i currently uninstalled the nVidia drivers and also am currently on safe mode and usually only lasts 15 seconds if i ran normally before i again see a BSOD. Is it ok for me to run the verifier while on safe mode?

 

[Roundhouse]

Just an update...

I just finished running tests on my 2x2GB Team Elite DDR3 sticks and they passed (5 passes, standard tests). When I wake up later, I'll test the 2x1GB GEIL DDR3 sticks.

EDIT : I just used the first memory slot for all the tests.

 

[Roundhouse]

If all the mem sticks have no errors, is it safe to say that the problem is software/driver related?

I was thinking, since my mobo has an ATI chipset and I now have an nVidia GPU, will installing the ATI southbridge drivers conflict with the nVidia GPU drivers?

 

[ttran]

Please update these old drivers:

wdcsam64 wdcsam64.sys Wed Apr 16 15:39:08 2008 (4805BB2C)
Western Digital External Drive RAID Manager download at WD Support > Downloads > Select Product

Please remove any CD virtualization programs such as Daemon Tools and Alcohol 120%. They use a driver, found in your dmp, sptd.sys, that is notorious for causing BSODs. Use this SPTD uninstaller when you're done: DuplexSecure - Downloads

What is the result from system file check?

The next step should be enable Driver Verifier as Ken (Zigzag3143) suggested. Look at the instruction he posted. If you like more visible instruction, have a look at this:
http://www.sevenforums.com/tutorials/101379-driver-verifier-enable-disable.html

regard,

Tuan

 

[Roundhouse]

Thanks for the reply man!

I'll try to do that once I get back home... Now that you mention it, while doing all these restarts/boot-ups in doing the memtest and all, i experienced a problem when, upon booting-up in safe mode, windows reported an error about a USB device. So I unplugged the WD External Drive, and then was able to boot-up safe mode.

The system file check which I ran yesterday showed no integrity violations.

I'll try to remove the installed DAEMON TOOLS LITE and also run the verifier. BTW, is it ok to run the verifier in safe mode or i should run it in a normal boot-up of windows?

 

[CarlTR6]

It should be run in the normal mode while you use your computer. The idea is for it to stress the drivers and find faulty ones. In the safe mode many drivers do not load. However, it you can't get it to run in normal mode, do try safe mode.

 

[Roundhouse]

Ok, I'll try to run the verifier on a normal boot.

I still have a question about ATI chipset - nVidia GPU compatibility. Will the ATI southbridge drivers interfere with the nVidia GPU drivers?

 

[ttran]

It will run just fine. Nvidia make good card. I usually see Nvidia GPU with intel chipset but yours is fine

 

[Roundhouse]

It will run just fine. Nvidia make good card. I usually see Nvidia GPU with intel chipset but yours is fine

Cool! Thanks for the reply! I'm still working on the memtest. Will post updates after I have tried all that you guys have posted.

 

[Roundhouse]

Where can I get updates for "Western Digital External Drive RAID Manager" (wdcsam64.sys)?

I mean I have a WD My Book Essential 1TB. It has that nasty virtual drive of which I already took care of about 2 months ago and even updated the drivers for the SES thingy. My prob now is where to locate an updated version of wdcsam64.sys? I can't seem to find anything about Drive Manager drivers on their site and even on Google...

 

[Roundhouse]

BSOD (Verifier was ON)

Hi guys, this is just a follow-up on my thread:
http://www.sevenforums.com/crashes-debugging/102785-multiple-assorted-bsods-2-days-2.html

I enabled the Verifier and upon restarting Windows failed to start so I selected Startup Repair, of which it wasnt able to repair anything =P So then I proceeded to start the machine once again and then encountered a BSOD. Attached is the dump. Since I got a BSOD, I went into safe mode then disabled the Verifier.

Thanks in advance!

 

[Jonathan_King]

What USB device(s) do you have attached, if any?

The dump is blaming usbfilter.sys, which is a Microsoft USB driver. Don't worry about updating it or anything, it is symptomatic of another cause.

I am suspicious of the driver Tpkd.sys, so check out this link: TPkd.sys Windows process - What is it?

Remove any programs listed there, and see what happens.

I have asked the staff if this thread could be merged with your previous one, just a heads-up.

...Summary of the Dumps:

[font=lucida console]
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Mon Aug  9 20:16:00.936 2010 (UTC - 4:00)
System Uptime: 0 days 0:00:11.668
BugCheck D5, {fffff98006dd8e40, 0, fffff880149f51aa, 0}
*** WARNING: Unable to verify timestamp for usbfilter.sys
*** ERROR: Module load completed but symbols could not be loaded for usbfilter.sys
Probably caused by : usbfilter.sys ( usbfilter+41aa )
DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
BUGCHECK_STR:  0xD5
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
[/font]

 

[Roundhouse]

Thanks Jonathan_King!

Sorry if I kept on creating new threads for updates. I just wasn't sure if people would be able to see my updates if I used my old thread.

When I enabled the verifier, only the keyboard, mouse, and my netgear usb wifi were connected.

As for Tpkd.sys, it is an InterLok driver for my M-Audio USB Condenser Mic. The mic is the actual InterLok device in order for me to be able to use ProTools on my PC.

After all the memtests, I am now able to use my PC on normal boot-up. So far no BSODs. I was even able to play StarCraft 2 for 18 mins. Usually it doesnt last that long before BSODs creep-in. Seems like my WD My Book external is the culprit. I still need to verify that though. I'll try to connect it again and try to update the firmware and the smartware drivers for it. If BSODs arise, I'll post asap.

 

[CarlTR6]

Roundhouse, I have a WD My Book for my backups and I have no trouble with it at all. Assuming your My Book itself is good, I would suspect something else is triggering the BSOD's.

 

[Roundhouse]

I'll try to reconfigure my WD My Book later. I need to update the firmware and drivers in order to update the wdcsam64.sys...

I searched around in google though and there are a number of similar incidents where their WD My Book crashed and threw a BAD_POOL_HEADER BSOD. I also experienced that one. It even came to a point that my machine won't boot into safe mode and was telling me that a USB device was causing an error. When I unplugged it, I was abel to boot-up. So far everything is stable. Will check though after I reconnect the external disk later.

 

[CarlTR6]

Keep us posted.

 

[Roundhouse]

CarlTR6, You mentioned that you have a WD My Book right? Do you have your Indexing Service running on that drive?

 

[CarlTR6]

I apologize; I have been offline running errands. No, I do not have indexing service running on mine. I use it for backups and I have it organized. I am not a real big fan of indexing service.