Random BSOD's when Under Load / just after closing loading application

Hi

LaptopSpecs::
CLEVO P170HMx
i7-2760QM @ 2.4GHz
16GB DDR3
nVIDIA GTX 580M 2GB DDR5
Realtek ALC892
OCZ Vertex 3 - 240GB
Seagate 500GB SataII
Wireless Xbox adapter


Problem::

I'm losing the will to live. So im hoping that you can help! :)
Basically, ive had this laptop since the start of the year (Jan) and have had various problems with it. I sent it back to the seller and they replaced the GPU (Had a faulty GPU originally, causing all sorts of weird BSODs)

Spent a chunk of change sending it back to htem for repair. Got it back and everything seemed good!

First set of BSODs were ESET NOD32 Related. (old version, seemed to cause a BSOD whenever the Sandybridge CPU clocked down... guessing it was to do with the SB CPU drops 'below' the minimum requirement for Win7 - and causes the issue... Removed it and running Microsoft Security Essentials (although it appears some reminents are still there - going to be running a removal tool ASAP!)

Then i had a range of BSODs which were relating to the wireless card... (Intel Centrino ultimate-n 6300) after about a week of fiddling around with varying drivers (and finally resorting to a 'driver update' tools.. which found a version which i couldnt find anywhere else...) and thats cured the problem.... (known problem with this wifi card driver..)
(Narrowed the issue down originally as it only occurred when downloading from Steam (7MB/s) over WiFi would cause the BSOD).


Now thats fine. and hunky dory i removed all the DMP files, and started over.

Now Im randomly getting either:
IRQL_NOT_LESS_OR_EQUAL
DRIVER_IRQL_NOT_LESS_OR_EQUAL
PAGE_FAULT_IN_NONPAGED_AREA
DRIVER_VERIFIER_IOMANAGER_VIOLATION

These are normally occurring when im playing F1 2011 (through Steam). Issue is becoming a PITA. When running Driver verifier (dropping the FPS so that it was JUST playable..) I couldnt get the machine to BSOD!! ... F1 2011 just did an AppCrash - which one ended could be relaunched.

I've ran Windows Memtest and Memtest+ for *hours* (leaving memtest running for 24hr) and not had any errors found at all...

Notes:although in the conclusion bit it says remove dtsoftbus01.sys - its already been done, Driver Verifier prevented boot with it installed.

Currently running the BETA Driver for the nVIDIA card (always use the latest driver, regardless of WHQL or BETA - and both the latest WHQL & Latest BETA driver cause the issue)

All other drivers are upto date from what I can see...
Bluescreenview & whocrashed results for the dumps are available at

www.matt2k34.co.uk/bsod/

if that helps / saves you time analysing the DMP files :)
also the performance monitor /report is saved there too. (as is a copy of Windows_NT6_BSOD_jcgriff2)
　
Any help pinpointing this would be greatly appreciated.

Regards

Matt

P.S. feel free to be technical and ask things, i've done so many tests and things ive forgotten what ive done really tbh..! :) I'm normally the 'go to' guy for problems with machines, but this ones got me totally stumped.. :/

Most this error code were Related to NETwNs64.sys Wireless WiFi Link Driver from Intel Corporation. I would re-install newest driver available.


Also I would remove the driver Related to dtsoftbus01.sys Virtual Bus Driver from DT Soft Ltd
as it like Daemon tools is often the cause of BSOD's.

None of these appear to have driver verifier enabled.

If you are overclocking or under volting I would stop AT LEAST TILL STABLE

Apologies for the long opening thread.

Couldnt get the machine to BSOD when running Driver verifier.

The 'middle' crash which was a Driver Verifier related BSOD was when DaemonTools was removed.

Just going to run a quick cleanup to remove some reminant trace of ESETs NOD32 & i'll try to redo that Wifi Driver.

Thanks for the superfast response :)

Hello again..
Just been able to play for 1hr with no issues (which is like, super rare...!) however cant continue testing tonight.

All i've done is update the Intel wifi driver to the latest version (which for some reason i couldnt find before you posted...?) and removed the last trace of NOD32.

Fingers crossed - I'll update the post on first BSOD, or in a few days if its all clear (hopefully!)

Many Thanks

Matt2k said:

Hello again..
Just been able to play for 1hr with no issues (which is like, super rare...!) however cant continue testing tonight.

All i've done is update the Intel wifi driver to the latest version (which for some reason i couldnt find before you posted...?) and removed the last trace of NOD32.

Fingers crossed - I'll update the post on first BSOD, or in a few days if its all clear (hopefully!)

Many Thanks

My pleasure and good luck.

Matt2k said:

Hi

After spending all day with not one BSOD (some 11 or so hours) I've just had one completely randomly (just flicking around the net...)

Seems to point to vwifibus.sys again, even after updating the Wifi drivers as indicated. (to 15.1.1.1)

Any insight would be much appreciated!

Matt





edit: its also worth noting that this is the most stable its ever been... So the new drivers have had some part to play! it seems that its a common issue with this NIC & Driver to get a BSOD error though. Flickin around Intel community forums suggests disabling Wifi-N Mode may prevent the BSOD. I'm going to try it, but i'd prefer to be using higher speeds - so if you can think of anything else, I'm all ears!

Matt

Do you by chance have a USB wifi device?

No, its an internal (i assume PCI-E ?) laptop form factor wifi card.

Intel® Centrino® Ultimate-N 6300

is the card in question. ironically when i chose this laptop it was highly customisable - and i picked this (the most expensive card) as the others were cheaper branding and not wifi-n compatible. Beginning to wish i'd saved the money :)

NETw5s64.sys keeps on giving me bluescreens

This is what I was looking at regarding their driver (although Intel dont seem to see it as a widespread problem, despite this card and some of its 'family' are all causing the issue).

Thanks for the help so far :)

Again we run into Bluescreen views limitations

This one was indeed networking related but NETIO.SYS not raspptp.sys.

Lets try this. Driver verifier will give us a more certain cause to the underlying issue.


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

* If you have a Raid update its Driver.




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

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

Driver Verifier

Using Driver Verifier (Windows Drivers)