very frequent BSODs with various BCC codes. Please Help.

[gvstemp]

Hi
I am using Tx2Z touchsmart HP notebook with 4GB RAM.
This is 2 year old laptop running clean install of windows 7.


I am getting regular and frequent BSODs, sometimes even back to back.
I have no clue what needs to be done.
I have followed the BSOD posting instructions ( I think !) and I am attaching the relevant files here. any help is appreciated.
Thanks.

 

[zigzag3143]

These were all over the map in terms of cause. I suspect one or more of these old drivers and that is a good a place to start.

RTSTOR64.SYS    9/19/2008 5:43:57 AM        fffff880`05530000    fffff880`05545000    0x00015000    0x48d3745d                        
mcdbus.sys    2/24/2009 6:34:07 AM        fffff880`01865000    fffff880`018a1880    0x0003c880    0x49a3cd1f                        
Rt64win7.sys    2/26/2009 5:04:13 AM        fffff880`04d56000    fffff880`04d88000    0x00032000    0x49a65b0d                        
enecir.sys    5/20/2009 2:08:57 AM        fffff880`03e0f000    fffff880`03e2c000    0x0001d000    0x4a139e79                        
niorbk.dll    6/14/2009 4:14:57 PM        fffff880`0716f000    fffff880`07181000    0x00012000    0x4a355a41                        
atikmdag.sys    7/2/2009 1:45:07 PM        fffff880`03e3c000    fffff880`04453000    0x00617000    0x4a4cf223                        
nipbcfk.sys    7/7/2009 12:22:16 PM        fffff880`00e70000    fffff880`00e78000    0x00008000    0x4a537638                        
nidimk.dll    7/7/2009 5:43:03 PM        fffff880`07181000    fffff880`071d1000    0x00050000    0x4a53c167

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 Reference Table (DRT)

 

[gvstemp]

thanks a ton !
I will start by updating the drivers listed by you. will report what happened after that.
thanks again.

 

[gvstemp]

OK so I installed all the new drivers (except the ni*** ). The ni*** drivers belong to a specific program which should not be updated. Other than that I have updated all. If there is a crash again... I will post the dumps again. thanks again for your reply.

 

[zigzag3143]

OK so I installed all the new drivers (except the ni*** ). The ni*** drivers belong to a specific program which should not be updated. Other than that I have updated all. If there is a crash again... I will post the dumps again. thanks again for your reply.

Should you be inclined to update *. ni here is a link. NI Measurement Studio - National Instruments

 

[gvstemp]

After a few hours of happy working. I got BSOD again.
I am attaching the new core dump files here.
Please tell me what do I do next.
thanks.

 

[zigzag3143]

After a few hours of happy working. I got BSOD again.
I am attaching the new core dump files here.
Please tell me what do I do next.
thanks.

There are still the old drivers
Related to RTSTOR.SYS Realtek USB Mass Storage Driver for Vista from Realtek Semiconductor.

We arent getting anywhere like this. Lets check both the ram and the drivers by doing these tests.




* If you are overclocking anything reset to default before running these tests.
In other words STOP!!!

* If you have a Raid update its Driver.



Memtest.

*Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder or another ISO burning program. Memtest86+ - Advanced Memory Diagnostic Tool

*Boot from the CD, and leave it running for at least 5-7 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.

Any errors are indicative of a memory problem.

If a known good stick fails in a motherboard slot it is probably the slot.

http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html






Driver Verifier

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.

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

If you are using win 8 add these
- Concurrency Stress Test
- DDI compliance checking

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

Thanks to JCGriff2 & Usasma.

Sysnative Forums

Driver Reference Table (DRT)

Using Driver Verifier to identify issues with Windows drivers for advanced users

Driver Verifier

Using Driver Verifier (Windows Drivers)

 

[gvstemp]

I have some strange results:

Memtest:

try 1: 2 passes... no errors
try 2: list of red errors in 1st pass
try 3 and 4: 3 passes no errors
try 5: list of red errors in 1st pass
try 6: 1 pass no error
try 7: 1st pass no errors but now its taking a long time for the 1st pass itself. Its been 1.5 hours and only 48% of the 1st pass is done. Usually 1 pass takes about 45-50 minutes.

There have been a 4-5 BSODs since then but none of them during a memtest.


Should I continue doing multiple memtests ?

what should i do ?

 

[James7679]

First, follow these steps.
1. It is a good idea to buy an anti-static wristband, and follow the instructions for use.(They are sold at most electronics stores.) If you are going to do quite a lot of bench work, you might do well to invest in an anti-static mat.
2. If you don't have a wristband, you are not necessarily out of luck. Assuming that your PC is grounded, you can ground yourself by just keeping one hand in contact with the bare metal frame (not a painted or coated surface) of the computer case. Keep the PC power cord plugged in to a (3-prong) grounded outlet and turn off the rocker switch on the back of the power supply. If the power supply does not have a switch on the back, this won't work, however. Never work on a PC with the power on. In that case, you should buy an anti-static band or try another method of grounding.
3. As an alternative, alter a standard 3-conductor power cord by snipping off the two flat blades, leaving only the grounding portion of the plug. Or simply purchase a cord like this from an electronics supply house. This accomplishes the same thing as turning off the rocker switch.
4. You can employ an LCD Static Discharger. As a simple measure, you can hang it on your key ring and just dangle it. This is less reliable, but when it touches a ground, it should discharge the static electricity. Procedure：①Lightly touch the oval button with a finger. ②Make sure that the end of the conductive material touches a grounded conductor. (such as vehicle, human body, computer, metal or other) to release static electricity, and observe the LCD display.
5. Some people claim that damage can be reduced by wearing little or no clothing, it is said that the less cloth that is in contact with your body, the less static is produced, though these claims remain unproven.

The average person can carry up to 25,000 volts of static energy at any given time. This sounds like a lot, but because the current level is low, you usually won't notice it. Follow safe ESD procedures any time you open a computer.

If the equipment is cold, wait until it has reached room temperature. ESD builds up much faster when it's cold and dry (low humidity).

If you don't take steps to prevent ESD, you may regret it. Your computer can sustain serious damage without you knowing it. CPUs and memory chips of any kind are highly vulnerable to ESD. If you fry your PC with static electricity, you may soon start to notice random memory errors, blue screens, and lock-ups. Normally, you can't see (or even feel) ESD, but it is almost always there, so be sure to do the right thing. Your PC will thank you!

Try not to open up computers while on thick carpets, petting long-haired pets, dressing, emptying the dryer, etc. Use common sense; don't do anything that would cause you to get a shock from touching something made of metal.

After that, open up the case and remove all but the first stick. Run memtest86 for a few passes to see if you get errors. If you do or do not, then remove that stick and set it aside, remembering that it is good or bad. Test remaining sticks in the same manner. If you get errors on all sticks, test them in different slots. Post back with results.

 

[gvstemp]

Ok. So here are the results.
I have 2 RAM sticks (2GB each) and 2 slots on my laptop. RAM1&2 and SlotA&B.

RAM1 in SlotA and Slot B, 6 passes each in both slots. No errors.
(This should mean that both slots and RAM1 is good.)

RAM2 in Slot A, 6 passes, no errors.


This should (I think) mean that both RAM sticks and Both slots are good.

What is the next step ?

As an aside I wanted to know if it will take less time + effort in just reinstalling win7 ? however, I am not sure taht the problem is hardware or software. If its some driver/software, I can just do a clean install of the OS right ?
If its hardware, then it would be nice to know if it is any replaceable part of the hardware (RAM STICKS ?) or not.

However, if its hardware, then its probably time to scrape some cash for a new laptop . I love this laptop.. but i might have to just go for a new one.. as i cant work/live with BSODs.

It would be nice to know which of the two is the cause of these BSODs , so atleast I can make a decision.


Anyway, as of now, it seems like RAM sticks and slots are good. Whats the next step ? Should I do the Driver Verifier step ? or any other suggestion ?

Thanks in advance,

 

[gvstemp]

ok... another update.

With the RAM2 in SlotA, my laptop worked fine for entire day.

Just for the heck... I plugged in the RAM2 in Slot B and ran the test again.
at 8% of 1st pass it gave 130,000+ errors !

I rebooted the laptop and restarted the test. Next run, at 5% of 1st pass there were 330 errors, and again at 8% the error counter went berserk till 200,000 errors ! I had to hit escape to stop this.

Now I dont get it, is the RAM stick bad or is the SlotB bad ?
RAM1 was good in both SlotA & B , I would conclude that both slots are good (as well as RAM1).
RAM2 was good in SlotA, so I 'should' conclude that RAM2 is also good.
Can RAM show Slot-specific error behavior ?

At the end, what do I do ?

PLEASE HELP.

 

[James7679]

Hi gvstemp. Sorry for the lack of response. I have been very busy and not in the forums. Best advice, mark the sticks as you suspect them, 1x good and 1x bad. Run the "bad" stick in slot 1. If you get errors, remove the "bad" stick and replace it with the "good" stick. From the information you have given, you should get no errors. After confirming, remove the "good" stick from slot 1 and put the "bad" stick in slot 2. After you get errors, replace the "bad" stick in slot 2, with the "good" stick. Again, according to what you have stated, you should get no errors. If the "bad" stick, test bad in slot 1 and 2, and the "good" stick, tests good in slot 1 and 2, then you have your answer. Either RMA the set, or go buy a new set. Let us know.

 

[writhziden]

Ignore my last post. Did not see a RAM module was found to be bad. That should be dealt with first since it is the most likely cause. Good work!

 

[gvstemp]

Ok I was already doing almost what you wrote here, but there is a confusion here:

Good stick=no error in both slots.
Bad stick= error in Slot B.. but NO ERRORS (after mutliples passes and multiple restarts) in slot A.

can you help me conclude now ?

 

[James7679]

While I will say that it is strange that the bad stick only presents as bad in slot b, it's not unheard of. The only other suggestion that I have, is to run the "good" stick in slot b in the OS for a few days to be sure it isn't a bad slot. But honestly, with the information you have provided, I would suggest replacing the RAM.

 

[gvstemp]

Thanks.
I really appreciate your help.
I will run the good RAM in slotB again and see if something comes up.

 

[gvstemp]

This is confusing.
It looks like the longer i test on these RAMs... the more errors puts out. Now even the GOOD RAM (which never showed error before on either slots) started to show errors in both slots. It was matter of testing for longer time.

1. So in summary, both RAMs, in both Slots give errors.
2. Both RAMS on a different computer (samsung) gave NO errors
3. RAM from that samsung computer on my laptop .. again gave errors.


Could it be a non-RAM related failure of another part of hardware ? say GPU ? (this unit is sort of infamous for bad soldering of GPU) however, since for last 1.5 years i had flawless performance.. I didnt think that was the problem with my unit. But maybe aftr 1.5 years it is a problem after all.

Any more ideas/suggestions please ?

 

[James7679]

Question, is this the same memory that shipped with the unit?

Have you made any changes in the BIOS at all?

Please upload all of the tabs from CPUz.

Have you checked for any BIOS updates that would correct instability?

 

[gvstemp]

The unit came with 3GB (2GB + 1GB). I replaced this with new 4GB (2x2GB) in the first couple of months of this laptop.
I have checked on the to the HP website and I think I have the latest BIOS updates.
I am attaching screenshots of CPUz. (currently I have only one of the RAMs installed as I was memtesting it)

 

[writhziden]

How did you determine the RAM that you ordered? Did you make sure it was compatible with your system by checking for compatible RAM for your HP model? Or did you just buy RAM blindly? What was your method for determining what RAM to get for your system?