RPracic

Hello,

I have heard (and read) some good stuff about this site, and I am finally at wits end so I'm coming to the people who know what they are doing.

First off, I apologize if this is posted in the wrong section.. I'm completely new here and I tried to find the most fitting area.

The laptop is almost a year old now (11 months) and was running fine until about 2 or 3 weeks ago. I used modded drivers for the video card (and again, for about 10 months it was fine). Recently, it started crashing to blue screen. It was only with one game (Flight Simulator 2004.. yes, I'm a simmer!), and when I couldn't find out the cause, I reformatted. Before reformatting, I tried rolling back to factory drivers for everything. Then I tried updating to the latest drivers for everything. With the error still occuring, but only with the one game, I decided to reformat (it was a "messy laptop" anyway). Reformat proved to work for a while, 3 or 4 days. Now, after updating drivers, installing 2 games, setting up a network, and some software, it has started crashing with no warning - which seems to be at the most random times. Sometimes while I am playing a game, or sometimes while I am doing work. It once happened almost instantly after rebooting from a preceding crash.

Sorry for the life story, but I figure more information can only be beneficial (I sure hope so anyway!).

Where I am sitting now is at a state of complete confusion. After reverting to factory default drivers again, I thought the problem was solved, but came home from work one day to find it sitting at a blue screen yet again (I left some software running to finish up scans while I was gone). It has only happened twice since the last reformat, so I unfortunately only have the two latest minidumps. I will upload more when they come (let's hope I can change "when" to "if"!).
I have tried clearing the page file and relocating it to a different drive, tried leaving it default. I tried running system check utilities including some stress testing with memtest, the BIOS memory check utility, I tried the hard drive check utility.

Included are the following reports:
DXDIAG (normal and 64 bit reports)
MiniDump (x2)
BELARC Advisor Report

Blue Screen Crash Reports are as follows (I took a picture of each blue screen I got, so here are all the ones I ever got), the two latest will be the ones that are in the dump files (sorry I don't have a date for them):

IRQL_NOT_LESS_OR_EQUAL

STOP: 0x0000000A (0x0000098A0000007E, 0x000000000000000A, 0xFFFFF80001CB5163)

STOP: 0x0000000A (0x0000098A0000007E, 0x000000000000000A, 0xFFFFF80001CB3163)

STOP: 0x0000000A (0x0000098A0000007E, 0x000000000000000A, 0xFFFFF80001CC3163)

STOP: 0x0000000A (0x0000098A0000007E, 0x000000000000000A, 0xFFFFF80001CAB163)

STOP: 0x0000000A (0x0000098A0000007E, 0x000000000000000A, 0xFFFFF80001CA6163)

STOP: 0x0000000A (0x0000098A0000007E, 0x000000000000000A, 0xFFFFF80001C70163)

STOP: 0x0000000A (0x0000098A0000007E, 0x000000000000000A, 0xFFFFF80001C7F163)

STOP: 0x0000000A (0x0000098A0000007E, 0x000000000000000A, 0xFFFFF80001CBB163)

STOP: 0x0000000A (0x0000098A0000007E, 0x000000000000000A, 0xFFFFF80001C76163)

STOP: 0x0000000A (0x0000098A0000007E, 0x000000000000000A, 0xFFFFF80001C68163)

STOP: 0x0000000A (0x0000098A0000007E, 0x000000000000000A, 0xFFFFF80001CA6163)

Those are all in order of occurence top to bottom - from oldest to most recent (including those before the reformat). Clearly, there is some sort of very similar pattern. I think it must be one common thing at fault. The event viewer tells me the Error ID 0 cannot be recognized each time I get the BSOD. I haven't been able to review the minidumps (I tried, but even after I got the symbols, they never worked).

If you need me to post "fresh" ones at any time, you need only ask, I am at your complete "disposal". I only wish to find the cause, so I may consequently find the remedy.

Thank you very much for any and all help! I sincerely appreciate the work you ladies and gentlemen do here!
I'm surprised my laptop hasn't crashed in the 2 hours that I've been preparing this 'report', so I best be heading off, and I will be hoping for the best! Thanks a lot!

-Rob


Computer Specifications (CPU-Z info included)

Intel Mobile Core 2 Duo T5450 @ 1.66GHz.
Quanta 30CB Mainboard, Intel GM965 Chipset.
BIOS - Latest update to version F.45 (01/16/2008).
2048MB DDR2 RAM in Dual Channel, 332.5MHz (SAMSUNG) PC2-5300.
NVIDIA GeForce 8600M GS, 1008MB, drivers 7.15.0011.0123 (factory default due to suspicion of it being cause of crash).
Vista Ultimate 64bit (x64).
Onboard Sound (Using RealTek and Windows Update default drivers)
300GB HD Space. 2 Hard drives, (C) has Vista install, with 140GB, (D) has nothing (at this time) with 150GB, one partition on (D) with 10GB for recovery.
Running AVG Anti-virus (Free Edition).
Vista Firewall, Defender, UAC, all security options enabled, etc.
System writes full dump reports (they go up to 2GB often times).
System set to not reboot after fatal crash (after blue screen, manual reboot necessary).
Shadow copies are disabled (300MB now).
Running through a network with a WiFi Link 4965AGN, Realtek 8168B/8111B PCI-E Gigabit Ethernet.
I also use a cooling station that sits below the laptop. Temperature was never an issue before the cooling station, but it comforts me to have that extra little bit.
I use approximately 8 USB devices that are connected all at once, sometimes more, sometimes less. However, crash still occurs with or without any/all USB devices connected.

I do not overclock (not laptops anyway).

P.S. One thing I just thought of as I was writing up the specs was to do with wireless. If I drew a timeline for the clean operation of the system, then the system BSOD beginning, with reference to wireless networking, it would look like this:

Day 1 - Purchased laptop;
Day 300 - Bought wireless router, began all work through a network, using internet via wireless connection;
Day 330(or so) - BSOD's begin.

The days are not entirely accurate, but what I am sure of is that before I used the router, I never got any BSOD problems. Then I got the router. Then sometime after I started using the router, BSOD problems began (with no other serious change to hardware or drivers other than normal updates).
This may not have any connection but you never know, thought I would add that in. I do have my laptops wireless turned ON pretty much 99% of the time. Whenever the laptop is ON, it is ALWAYS connected to the internet via the wireless connection.

Thanks again for any/all help!!

Attached Files

	DxDiag (32bit).txt (45.3 KB, 1 views)
	DxDiag (64bit).txt (52.6 KB, 2 views)
	MiniDump Files.zip (42.0 KB, 4 views)
	Belarc Advisor Current Profile.zip (36.2 KB, 12 views)

jcgriff2

Hello Rob. . .

Welcome to the Tech Support Forum - Vista Support!

You are in just the right section of TSF for help regarding your recent encounters with the infamous Blue Screen of Death. Hopefully, I can provide you with a probable cause for the BSODs. If you have seen any of my postings you know that I absolutely do like detailed information - and lots of it! You did fine with the explanation of events.

I picked up and downloaded all of the files that you attached - Great job of being prepared, by the way! You have given me all that I need to start with.

Just one question - are the dumps from 64-bit crashes?

I do have several cases ahead of you that I am working on now. So please be patient. Feel free to send me a PM or Email to check on status. Click on my name to the left. OK??

In the interim, should you get any more BSODs let me know as the more memory dumps, the better.

Regards. . .

JCGriff2

RPracic

Thank you very much! I appreciate the prompt response.

As I have seen with many of the other threads, I understand completely that you have others who take priority over me, "first come, first serve". Completely fair, and I am a patient guy.

The crashes are all on 64-bit. The only reason for including both 32 bit and 64 bit DXDIAG reports is because it gave me the option of doing either or. I didn't know whether or not it was necessary, but it's better safe than sorry. Included them both. For the record, the entire system has been 64 bit since the start. Came packed with Vista Ultimate, 64 bit.

Thanks again, I will definitely upload future reports if/when they occur.
I look forward to seeing what you can dig up.

-Rob

Gerald Ferrari

Usually BSOD's I see have a "<filename>.sys" named. This is usually associatable with either specific hardware, or general hardware areas to help limit the search. Do you have a .sys filename named ?

If any of the software is cracked, that could be your problem. Keygens are usually infected. AVG misses stuff sometimes. I'd check the HJT log, double-check AVG against TrendMicro's Housecall.

Check this:

http://www.softwarepatch.com/windows...x0000000a.html

Says these errors are common with Vista, and can be related to the "storeport.sys" driver. Maybe a virtual drive ?

Check your hardware manager for flagged items. Check "show hidden devices" to see the sneaky ones.

It's XP-related, but probably applies to Vista as well. Some basic troubleshooting methods. Remove & uninstall as much hardware as possible and see if the problem goes away. How long will it run without a BSOD ? Can you get it to run longer or indefinately if the wireless is disconnected. 30 days of use might have fried the on-board NIC. You might try cracking the box opening and removing the NIC and see what happens.

http://support.microsoft.com/kb/314063

RPracic

I appreciate your efforts to find a solution, however I do not illegally download software. I use BitComet as a way to send massive files to clients, and if need be, I can download files from them as well. Nothing that I use is illegal and I have never used a "Keygen" on this laptop. I am very aware of the dangers of illegally downloaded software, I've heard and seen the endless complaints of corrupt files due to virus' and such. Thus, with this expensive hardware, I'm not willing to do something as stupid as subject it to such harm.

Where exactly would this <filename>.sys be located? Nothing in the Windows folder... After running a search for *.sys, it came up thousands of .sys files, all of which are undoubtedly essential for windows to run. Storeport.sys shows no signs of harm, and after a reformat, I would assume it is in tip top shape. How I would go about ensuring it's health is beyond me.. what do you suggest?

HJT shows 57 processes running, Task Manager shows the same. I ran TrandMicro HouseCall a few hours before I posted the very first post, it came up with nothing.

The softwarepatch website with the "hotfix" or "patch" for the storport and 3GB memory issue does not seem to relate to my problem. For starters, it looks like it is for 32 bit systems (filename, description, both say it). However, I have downloaded it for the time being. I will install it should the memory dumps and such come up with nothing useful.

The amount of time it can be running without a BSOD is indefinite as it is. Some days it will happen 20 minutes after boot up, some days it will take 8 hours. One time, it occurred twice within a 5 minute (approximately) period.

I do not have any virtual drives installed on the system.
Upon review of the hardware manager, after triple checking, I have come up with nothing. Everything seems perfectly normal to me, comparing it to a few other PC's and laptops I have (and have had) in the past.

I will leave the laptop running tomorrow for 24 hours with the network disabled, and probably let it run some games for "stress testing". I will check back here with the other network laptop and post if I discover anything new.

As for the "basic troubleshooting methods", I'm a couple hundred steps ahead of that. Removed everything external from the laptop, to no avail. One of the first things I tried was exactly that, while also checking all drivers. After the reformat, with no additions beyond factory setup, it still encountered the blue screen error after some time.

Thanks for the suggestions and help! Much appreciated!

RPracic

One more BSOD to add to the mix. Error was:

IRQL_NOT_LESS_OR_EQUAL

STOP: 0x0000000A (0x0000098A0000007E, 0x000000000000000A, 0xFFFFF80001CBB163)

New minidump is included as well.
The BSOD occured with the network running, basically the same as any of the other BSODs. Only thing is that I was not present. It was stalled on a blue screen as soon as I got home from work. I was connected to the network via wireless, but nothing was running on the desktop itself other than anti-virus and such.

-Rob

Attached Files

Mini040208-01.zip (22.0 KB, 3 views)

jcgriff2

I picked up the latest mini dump file.

JC

RPracic

Yet another to add to the bunch.
This one occurred after a good 20 hours of high-load use. I've found that I basically cannot run the laptop for more than 24 hours without running into a BSOD. That is with the wireless enabled and connected. Starting now (after this post), I will disable it and then run the laptop for 48 hours to see if it crashes to another BSOD. I will be checking back here on another laptop and report anything I find through that.

Thanks again for the help!

-Rob

Attached Files

Mini040308-01.zip (22.6 KB, 0 views)

dai

run memtest on the ram 1 stick at a time
http://www.softwarepatch.com/windows...x0000000a.html

RPracic

Thanks for the tip.
I guess I didn't add that to the original post, or maybe you missed it, not sure. Memtest was also on of the first few things I tried. After I realized it wasn't a software (driver) issue, I tested the hardware. Memtest came up with nothing. I can, however, run it again if you think that would be a good idea. I won't be doing that until tomorrow. The laptop is on its 26th hour of straight running without the network. I am about go let it autopilot some games to see if it will blue screen without running on wireless.

Thanks again..

(Edit)

By the way, Gerald Ferrari (above), also provided that same patch for me. I have downloaded it but have yet to install, as I do not believe it pertains to my problem. I would like to wait to see what comes from the dump reports before installing what could very well be unnecessary hotfixes. Thanks though!

jcgriff2

Hi Rob. . .

I have processed the four memory dumps that you submitted for analysis. The all have a single cause - " ntoskrnl.exe".

The executable file "ntoskrnl.exe", related to the Windows Vista NT Kernel, usually comes up in BSOD cases where there is a general hardware failure or if there is a problem with the "boot.ini" file - or if the ntoskrnl file is corrupt. Given the fresh install here, I doubt the BSODs are related to the second or third item. I too received error messages from the symbols and double-checked then triple-checked them with Microsoft. The ones I have are correct for your x64 system. I have found that numerous others have also reported this same symbol issue to Microsoft. This may be why I was unable to obtain a more definitive result - like the name of a specific driver. Something in your system is either referencing an area of memory that it shouldn't or simply can't. But if your memtest came back clean, I would then suspect the former rather than the latter.

Did you run the sfc repair? If not, go to an ELEVATED command prompt and type "sfc /scannow" (no quotes) and let it run (10-15 min or so).

Now... The 32-bit (x86) laptop that I am on has the same Intel® Wireless WiFi Link 4965AGN that you mentioned in your opening statement. I have never had a problem with mine, but I do know that there have been two updates for the 4965AGN in March alone - one 3/19 and the other on 3/28. They are listed in Windows Update as "optional" and I had to install them myself. I went to Intel's site HERE and found that I do have the latest driver installed Netw4v32.sys - v11.5.0.32. Check your Device Manager. Interesting to note here is that the date on the driver is December 2007, so I wonder what the updates last month did exactly. The did come from Fujitsu through Windows Update and not directly from Intel - as far as I can tell anyway.

I also saw in Belarc that you have a wireless connection in addition to Ethernet - and software for Dial-up as well. I don't know if these three can conflict with each other or not, but I did notice that you mentioned the BSODs commenced after installing your router. Were you using both Ethernet and Dial-up prior to the introduction of the wireless router? The rest of the Belarc report including the Windows Update information appears stellar.

I'm sorry that I am unable to provide a specific fix for you at this time, but should I come across anything, I will let you know. If you get any more BSODs, simply post them and send me a PM, and I will gladly take a look at them.

Regards. . .

JC

RPracic

JC,

Thanks for the help!
I ran sfc and left it alone for about a half hour. When I went to check its status, I found that it was complete, and had reported errors in the system files. It gave me the location to the reports, but I was unable to gather anything from them. I will be uploading them shortly in the hopes that you can review them and help me find what exactly the problem is. The drivers for my wireless card are version 11.5.0.34, dates October 31, 2007. I have checked windows update, but it came up with nothing regarding wireless updates. I do recall installing something for the wireless card not too long ago.

I believe the problem lies with the wireless itself. After running the laptop for nearly 40 hours with no crash (with the wireless disabled), I am fairly confident there is something wrong on that part. Especially considering that when the wireless is enabled, it crashed within 24 hours, every time, no exceptions.

I am also running another memtest and SFC scan to be sure there were no issues. I will report back afterwards, and then let it run for another 40 hours, this time with the wireless enabled.

Before I ever used the wireless router, I was only connected to the internet via direct connection (ethernet cable). I have never used the Motorola dial up assistant, it came preloaded with the PC and I was not sure if I would ever need it or not. But it has been unused since I purchased the laptop.


PS- While posting this, I have just discovered new drivers for my wireless card. The description of fixes is as follows:

For the Intel WiFi Link 4965: - Fixes issue where power consumption increases when restarting the notebook after turning the wireless radio off. - Fixes issue where a large ad-hoc file upload failure occurs with bluetooth co-existence. - Fixes issue where WLAN stops functioning during a Hibernation mode stress test. - Fixes issue where a "blue screen" error is displayed after an extended 802.11n stress test. - Fixes intermittent issue where WLAN stops functioning after hours of idle time. - Fixes issue there is a low link speed and frequent fluctuations in 802.11n mode. - Fixes intermittent issue where a "blue screen" error occurs during a 802.11a stress test. Intel WiFi Link 3945: - Fixes issue where the notebook is unable to re-associate with an access point operating with a hidden SSID when creating four profiles.

Two mentions of Blue Screen Errors.

I will install all latest drivers, run all tests, and everything as above. Then report back afterwards (with the uploaded sfc reports).

Thanks again for the help! You've given me some hope in finding and fixing the problem!

-Rob

RPracic

Ok, updates are installed.
I will report back tomorrow (or sooner, should there be another reply here), on the results of further "stress testing" the network.

Thanks again! I'm very excited about this, but always prepared for the worst.

(Unfortunately, the SFC log was in the 37MB range, so I was unable to upload it. Is there any other way I can send it to you? Is it even necessary?)

(Edit - Sorry for the double post. I completely forgot about the ability to edit in my hurry to update the status. My apologies... )

jcgriff2

Hi. . .

Yes, that sfc log can be massive. Refer to my PM for my email address. Please be sure to place your screen name in the subject and a link to this thread in the body.

In the interim, let's trim the CBS log - where the sfc output is added to - and I'll check it to see if anything is apparent. Do the following:

Go to an ELEVATED command prompt (START | type cmd.exe in the Start Search box | right-click on cmd.exe | select Run as Administrator)

Type/paste the following EXACTLY as it appears:

findstr /c:"[SR]" %windir%\logs\cbs\cbs.log >c:\sfcdetails.txt

To paste it in the "DOS" box, go to the top and right-click then select edit. that will alow you to paste and will execute the command instantly.

Go into Windows Explorer and locate the file c:\sfcdetails.txt in the c: root. Attach to your next post.

I'm not sure if this will tell me much, but let's see.

Regards. . .

jcgriff2

OzzyS

I am reading this thread very carefully. I am also having the same issue here mentioned. My problem is the BSOD whenever wireless card tires to connect to a network. I have the same wireless card my hp dv6568se. wired NIC works fine. connects to internet. As long as I do not connect to a wireless network even wireless NIC is fine too. I do dual boot on this system and XP uses the wireless card fine. This issue started yesterday and I haven’t stress tested the XP yet but I am hoping it will work just fine since I really don’t want to replace anything internal. I am using the same install of Vista last 5 months and cant really say I am fan of formatting it.
I home you would have a fix your issue where I am hoping I can catch something from it. Thank you.

OzzyS

I have tried a few drivers as that was the first thing i was thinking. I can not remember the datecodes but what is version of this driver you have found? thx.

Oz

RPracic

I would like to just report that with these latest drivers from the HP Official website for the Intel PRO/Wireless 4965AGN card, I have been running the laptop, connected to internet via wireless, with a 14GB file transfer going (uploading/downloading... client work again) since my last post. No blue screen yet.

I will continue to let it run at this same output for the next 24 hours to see if it blue screens. If not, I believe we have found the solution to the blue screen errors!

OzzyS, the drivers I used can be found here: HP Wireless Drivers Update
They are listed as 7.10C, the official version under the device manager is 11.5.1.8. If you have problems finding it, let me know and I will see if I can get an alternate download for you. Please note though, the drivers on that page are specifically for Vista Ultimate X64, and I got to them by putting in my system number, so you might be better off doing the same to find drivers specific for your system.

JC, the SFC extract was only 31kb, so I will upload it here. First, I am running one more SFC scan to see if it fixes the issues this time around. So I will reply back very shortly with that update.

Thank you very much for all of the help! Looks like we are getting somewhere!!

-Rob

OzzyS

Thank you, i will give that a try when i got home. Will post back here.

Oz.

RPracic

Okay, here is the CBS.log file, with relevant SFC information (from the code you told me to type in). The SFC scan told me there were files it could not repair, once again. So hopefully you can find something in the log that I am missing (on first glance, it doesn't look like there is anything "broken". I am always amazed at how many commands there are for a computer to do these tasks. And this is just a glimpse!


Thanks again!!

Attached Files

sfcdetails.zip (3.6 KB, 1 views)

jcgriff2

Hi again Rob. . .

I hope that you have enjoyed your weekend. I guess that it may still be cold up where you are even though it is now Spring. Here in the Southern California Desert, we are well over 80° again. It won't be long before this area sees triple-digit temperatures (I remember daily temps sometimes around 117°F/ 47°C last August!). New Jersey and 60° sounds nice right about now - and I'll get to see that in a day or so when I return home!

I was glad to see that you found the driver updates. I should have thought to tell you to check your computer manufacturer's site - but I was just thinking about Intel. I couldn't tell whether my updates came from Intel or Fujitsu. The important thing is that you found them.

I wasn't sure about the dial-up either, but thought that I would mention it. I still know of those who use dial-up - even with Vista. For some it is simply an unfortunate case of being the only available option.

Yes, there are many commands for the system - and I still find new ones. I love to do searches for EXE files - and execute them to see what happens - but I don't recommend doing so unless you can afford to re-install Vista at a moments notice!

Your SFC log did not show any errors - at least the trimmed down version that I asked for. I am glad to see that you are doing the testing with a file that I would consider adequate in size - 14GB - WOW! Great work on that end.

I send my warmest regards to you and to our many other friends within your very nice and very great Country of Canada.

JC