BSOD

Hi
I have been having BSOD problem in the last day or two and can't figure out what the problem is. I hope someone could help. I have attached the dump files zip.

BTW when I try to do a perf report, it gives me an error saying . the system cannot find the path specified.


As far as system spec:

HP Elitebook 6930p
Win 7 Enterprise
64 bit
Intel core 2 Duo CPU P8600 2.4 GHZ
4GB RAM
Less than 2 years old

Appreciate any help.

Br
S

WIN7ISSUE said:

Hi
I have been having BSOD problem in the last day or two and can't figure out what the problem is. I hope someone could help. I have attached the dump files zip.

BTW when I try to do a perf report, it gives me an error saying . the system cannot find the path specified.


As far as system spec:

HP Elitebook 6930p
Win 7 Enterprise
64 bit
Intel core 2 Duo CPU P8600 2.4 GHZ
4GB RAM
Less than 2 years old

Appreciate any help.

Br
S

Quite a few problems

1- Symantec. A known cause of bsod. remove and replace with Microsoft security essentials

Download and run the Norton Removal Tool to uninstall your Norton product | Norton Support

http://www.microsoft.com/security_essentials/

2-Old drivers needing update

Code:

SbAlg.sys    4/24/2007 06:37:52 AM    fffff880`011bb000    fffff880`011cd000    0x00012000    0x462dde00                            
e1y60x64.sys    8/18/2008 05:45:05 PM    fffff880`0538f000    fffff880`053d8000    0x00049000    0x48a9ed61                            
agrsm64.sys    11/10/2008 11:01:35 AM    fffff880`07c1f000    fffff880`07d41000    0x00122000    0x49184ccf                            
dsNcAdpt.sys    3/30/2009 10:33:33 PM    fffff880`0417a000    fffff880`04187000    0x0000d000    0x49d180fd                            
cpqbttn64.sys    4/20/2009 10:40:33 AM    fffff880`0413c000    fffff880`0413ec00    0x00002c00    0x49ec8961                            
HpqKbFiltr.sys    4/29/2009 09:48:30 AM    fffff880`040ee000    fffff880`040fa000    0x0000c000    0x49f85aae                            
spldr.sys    5/11/2009 12:56:27 PM    fffff880`01610000    fffff880`01618000    0x00008000    0x4a0858bb                            
GEARAspiWDM.sys    5/18/2009 08:17:04 AM    fffff880`04123000    fffff880`04130000    0x0000d000    0x4a1151c0                            
amdxata.sys    5/19/2009 01:56:59 PM    fffff880`011b0000    fffff880`011bb000    0x0000b000    0x4a12f2eb                            
HECIx64.sys    6/23/2009 03:50:00 PM    fffff880`05372000    fffff880`05383000    0x00011000    0x4a4131e8                            
rimmpx64.sys    6/25/2009 04:04:18 AM    fffff880`05620000    fffff880`05636000    0x00016000    0x4a432f82                            
ATSwpWDF.sys    7/7/2009 02:13:43 PM    fffff880`080cf000    fffff880`0815b000    0x0008c000    0x4a539057                            
hpdskflt.sys    7/8/2009 02:41:38 PM    fffff880`015ea000    fffff880`015f4000    0x0000a000    0x4a54e862

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 Reference
- - Driver manufacturer links are on this page: Drivers and Downloads

3- since all of these were memory exceptions I would run memtest

Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder or another ISO burning program.

Boot from the CD, and leave it running for at least 5 or 6 passes.

Just remember, any time Memtest reports errors, it can be either bad RAM or a bad motherboard slot.

Test the sticks individually, and if you find a good one, test it in all slots.

4- I would run driver verifier to determine which driver is causing the issue ( I suspect it is symantec)

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).

In Windows 7 you can make a Startup Repair disk by going to Start....All Programs...Maintenance...Create a System Repair Disc - with Windows Vista you'll have to use your installation disk or the "Repair your computer" option at the top of the Safe Mode menu .

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"
- 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).

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.

Thank you so much for the fast reply. I am going to follow all the steps and come back (hopefully not) if still have problems.

Thanks again,
S

Hi
I think that I am running in some bigger problem. I have:
1) removed Symantec
2) checked most drivers and most of them were current
3) Created the CD and run the memory memtest. i think there is a problem here. When I run it, it all looks relatively fine (ie some errors) until 50% scan is hit. After that, the number of errors sky rocks to the hundreds of thousands of errors. I have attached two screen shots to show it. What should I do?

Since I did the memtest, it now wont boot anymore ie it says Non-system disk or disk error replace ans trike anykey when ready.

Once again, thanks in advance for any help.
S

Hi
yes I am still running issues and I am stuck badly

First of all as I am new to memtest, not sure what is the process to run the test for each individual stick separately. How do I configure it to test each separately?

As far as the non-system disk error (which I am even more worried about), yes I have removed the memtest cd from the drive and when I boot it gives me the error. When I press F9 ( boot device options), the 2 options are: notebook HD and notebook upgrade bay - in both cases it goes back to the error message.
If it try to F10 BIOS set up, it ask BIOS admin password which I dont have. Neverthless the F9 set up should do the right boot anyway.

Any last ideas?

Thanks
S

Thanks. Ok I was able somehow by using the Recovery CD to now have it to boot from HD and not the CD drive anymore. Since memtest had detected some memory errors, I have replaced all the 4GB memory with new ones so that should not be a problem anymore but still not working. The laptop won t bough in any mode. When I start it it asks for safe, safe with network and normal and which ever I select it, it goes to the first Windows logo screen and goes back to the error page. When i try safe mode, it hungs at classpnp.sys.
Anything I could try at this point?
Thanks
S

Hi,

I was able to take photos of the sequence of what happens. Hope that it will help figure out what is going on.

When I start the PC, it goes to the HP logo (where you can select ESC) and if i let it go, it goes to the Windows Error recovery (image 57). Then it goes to the starting windows (image 59) and after abut 6-7 seconds it goes to the BSOD (image 62) which stays less than a second (was hard to capture the images) and then it goes back to the Windows Error recovery.
BTW it does this cycle independently on what start option is selected
S