Windows 7 32bit BSOD

[Luckydad]

Hi-

First time poster, appreciate any help.

Dump files attached. Performance monitor gets path not found.

Dell Latitude 1 year old.
Windows 7 32 bit.
Was installed as original operating system (OEM).
OS is original install, has not been re-installed.

Last major task before experiencing problems was major vlookup in MS Excel 2007 in file with almost million records.

Thanks in advance.

 

[zigzag3143]

Hi-

First time poster, appreciate any help.

Dump files attached. Performance monitor gets path not found.

Dell Latitude 1 year old.
Windows 7 32 bit.
Was installed as original operating system (OEM).
OS is original install, has not been re-installed.

Last major task before experiencing problems was major vlookup in MS Excel 2007 in file with almost million records.

Thanks in advance.

Blamed on ntkernlmp, but practically impossible so I would run driver verifier to find which driver is causing it

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.

Old drivers needing update

PBADRV.sys    1/7/2008 2:52:14 PM        0x8bb78000    0x8bb83000    0x0000b000    0x478274de                        
OA001Ufd.sys    6/3/2008 5:30:22 AM        0x821bd000    0x821e0520    0x00023520    0x48450f2e                        
OA001Vid.sys    9/19/2008 5:29:51 AM        0x82179000    0x821bcbc0    0x00043bc0    0x48d3710f                        
btwl2cap.sys    4/3/2009 8:28:35 PM        0xb3096000    0xb30a1000    0x0000b000    0x49d6a9b3                        
spldr.sys    5/11/2009 12:13:47 PM        0x8bdf0000    0x8bdf8000    0x00008000    0x4a084ebb                        
GEARAspiWDM.sys    5/18/2009 8:16:53 AM        0x93365000    0x9336a280    0x00005280    0x4a1151b5                        
IntcHdmi.sys    5/26/2009 7:12:34 AM        0x820d1000    0x820f4000    0x00023000    0x4a1bcea2                        
e1y6232.sys    6/12/2009 9:16:04 PM        0x9172a000    0x91764000    0x0003a000    0x4a32fdd4                        
CtClsFlt.sys    6/15/2009 1:05:16 AM        0x9339f000    0x933c2260    0x00023260    0x4a35d68c                        
cvusbdrv.sys    6/24/2009 4:42:04 PM        0x901d1000    0x901dd000    0x0000c000    0x4a428f9c                        
btwavdt.sys    6/25/2009 1:49:48 AM        0xb075a000    0xb07cd000    0x00073000    0x4a430ffc                        
btwrchid.sys    6/25/2009 1:51:31 AM        0xb30a1000    0xb30a3d80    0x00002d80    0x4a431063                        
rimmptsk.sys    6/25/2009 3:58:09 AM        0x932df000    0x932f0000    0x00011000    0x4a432e11                        
btwaudio.sys    7/1/2009 9:54:29 AM        0xb3015000    0xb3096000    0x00081000    0x4a4b6a95                        
BCM42RLY.sys    7/7/2009 8:35:04 PM        0xb62cf000    0xb62d7000    0x00008000    0x4a53e9b8                        
bcmwl6.sys    7/7/2009 8:44:47 PM        0x93029000    0x93290000    0x00267000    0x4a53ebff

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

 

[Luckydad]

Hi-
Thanks so much for the reply.
I have done everything you suggested.
After going through steps you list above for running Verifier, I shut down and attempted to start again, and I got a message about having no disk to boot from. "No boot sector in Internal HDD (IRRT). No bootable devices--strike F1 to retry boot, F2 for setup utility. Press F5 to run onboard diagnostics." I hit F5. It offered an option to do a test, and it is running through that now. It says Pre-boot Assessment Build 4117 on a blue screen with white type.

1. When this test is over, what should I do next?
2. Should I restart and hit F8 to start in Safe Mode? Will that work?
3. Should I use the recover disk you suggested I create and boot from that?
4. Once I am able to reboot and I am able to get the machine to blue screen, I understand that I should do that repeatedly, but what is the next step?
5. Does Verifier create some log that identifies the driver(s) that are the culprit?
6. Should I be tracking down the drivers you list above at the same time to update them?
7. A day or two before the Excel activity, a Windows Update occurred, and I'm pretty sure was successful. Is that relevant?
8. Malwarebytes found a virus called rootkit or something like that and was able to remove it. Relevant?
9. McAfee also found W32/Autorun.worm.aabl related to svchost.exe but could not remove it. Relevant?

The Pre-boot Assessment is over. I have tried hitting F1 to retry but it won't reboot. I put the startup repair CD in my drive to see if it would boot with that and it starts booting but put me into selecting your operating system (no choices available) or restore from image made earlier. No image available.

10. When you said backup in instructions above should I have done an image?

Because I didn't. I just copied the main documents folders to an external hard drive.

I can't get it to bluescreen. I can't get it even to Safe Mode.

It's currently doing Startup Repair.

Thanks in advance.

 

[Luckydad]

Hi-

I did not make an image but I did create a restore point but when I tried to reboot with repair disc the restore point was not found.

Thanks.

 

[Luckydad]

Hi-

Ok, I think I get it now.

I was able to use the restore CD and the steps listed here:

http://www.sevenforums.com/installa...-repair-menu-doesnt-see-operating-system.html

to get the computer to boot.

I had also removed some programs that I had installed as Add-ins to Excel. I suspect the culprit may have been the virus mentioned above and/or the add-in (SQLDrill). No bsod in almost 24 hours after turning on verifier. I even did the uber-vlookup that caused the problem originally in Excel and no BSOD. I have kept verifier settings on and will for 36 hours as recommended.

But if it does go to BSOD I will post the dump files, because I read here:

http://www.sevenforums.com/crash-lo...-driver-verifier-identify-issues-drivers.html

the idea is to purposefully get the system to BSOD so you can identify what driver is causing the problem by uploading the dumps.

But since I have had not BSOD in 24 hours, I will wait til 36 hours and then disable Verifier as discussed here:

http://www.sevenforums.com/tutorials/101379-driver-verifier-enable-disable.html

I think I see light at the end of the tunnel.

Don't want to jinx myself, but thank you very much for all the help. Really quite amazed even now at how far back to normal I've been able to get to, particularly from how bad it got. Seemed to be BSOD if I just looked at it the wrong way. Then after turning on Verifier it wouldn't even boot from hard drive. That was scary. But I just used the repair disc and followed the partition steps mentioned above when no operating system listed and I'm back.

(Most of above is really for next person who finds himself in same position as me, figured I would put a bunch of links all in one place.)

Awesome. Will post again after 36 hours.

Assuming all works out, above it says "Please rep anyone who helps you". What does that mean? And do I "rep" someone?

Thanks,
luckydad

 

[zigzag3143]

Our pleasure and let us know how it turns out.

ken