BSOD on Dell Studio 15 1558

[tonyvr4]

Recently I have been getting the annoying blue screen and crashes on my one month old Dell Studio 15.

Attached are the minidumps from windows. I have ran whocrashed and it has not identified the issue, other that it points to a driver.

I have not upgraded any drivers since getting the laptop new from dell, a little more than a month ago. I contacted their support and they were absolutely useless.

But I did run their diagnostics immediately after the last crash and it came through clean. I ran the memory diagnostic 5 times, and the complete system diagnostic once, including the extended drive test. All were clean and the tests overall ran for 3.5-4 hours.

I even ran the driver verifier yesterday and it did not detect anything. Since I do not know what do do with it, I turned it off for now.

Any help is greatly appreciated. Thanks everyone

 

[Tews]

All three of your .dmp files are reporting the same cause... ntkrnlmp.exe.. As this is a core system file, we know that this is not the problem... Make sure that you have driver verifier enabled... this wlll stress the drivers, and should result in a BSOD... NOTE: It may take up to 36 hours to do, so be patient.. upload the new .dmp files when you get them...

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck A, {ffffffffffffffd0, 2, 1, fffff80002c7c2b0}

Probably caused by : ntkrnlmp.exe ( nt!KiPageFault+260 )

Followup: MachineOwner
---------

 

[tonyvr4]

Can you advise on the correct procedure and options for enabling driver verifier?

Also, how do I disable it?
Thanks

 

[ttran]

run Verifier with these settings:

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.

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

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.

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

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.

If that doesn't work, post back and we'll have to see about fixing the registry entry off-line:

Delete these registry keys (works in XP, Vista, Win7):
        HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\VerifyDrivers
        HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\VerifyDriverLevel

More info on this at this link: Using Driver Verifier to identify issues with Windows drivers for advanced users

To turn off DV--> verifier /reset

 

[Jonathan_King]

In addition to Tom's good advice, be sure to remove McAfee with this tool: http://download.mcafee.com/products/licensed/cust_support_patches/MCPR.exe

Install MSE instead: www.microsoft.com/Security_Essentials/

 

[tonyvr4]

After my last post I had removed dell quickset and the system has been clean. Today I noticed that the function keys were not working and reinstalled the latest quickset. It crashed a few minutes ago, minidump attached

I will be removing quickset again until this can be resolved

 

[tonyvr4]

Sorry I forgot to include the whocrashed report:

[FONT=Segoe UI, Arial]On Fri Fri 7 30 2010 1:00:10 AM your computer crashed
This was likely caused by the following module: [FONT=Segoe UI, Arial]ntoskrnl.exe[/FONT]
Bugcheck code: 0xA (0x76DE2FD0, 0x2, 0x1, 0xFFFFF80002CE22B0)
Error: [FONT=Segoe UI, Arial]IRQL_NOT_LESS_OR_EQUAL[/FONT]
Dump file: C:\Windows\Minidump\073010-22963-01.dmp
[/FONT][FONT=Segoe UI, Arial]file path: C:\Windows\system32\ntoskrnl.exe
product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.
[/FONT]

 

[CarlTR6]

Tony, do you have a mini dump for this crash? If so please upload it. Never mind. I was just blind and didn't see it.

 

[tonyvr4]

Here is some additional info from event viewer:
Event 1001, Windows Error Reporting
Fault bucket X64_0xA_nt!IopDisassociateThreadIrp+9c, type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 0

Event 1001, BugCheck
The computer has rebooted from a bugcheck. The bugcheck was: 0x0000000a (0x0000000076de2fd0, 0x0000000000000002, 0x0000000000000001, 0xfffff80002ce22b0). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 073010-22963-01.

 

[ttran]

I haven't seen Driver Verifier is on, can you please enable it so that we can know if there are any faulty drivers. Also, Mcafee is there, make sure you uninstall it as Jonathan King suggest to eliminate the cause.

 

[tonyvr4]

I haven't seen Driver Verifier is on, can you please enable it so that we can know if there are any faulty drivers. Also, Mcafee is there, make sure you uninstall it as Jonathan King suggest to eliminate the cause.

I apologize I did not see the post regarding unistalling Mcafee. I will be happy to do that. But to remain protected, what should I do?
I do have Macfee Enterprise from the college I attend and can install that if needed.

 

[ttran]

Look at JK's post last page, he suggest you to use Microsoft security essential and I agree with it, it is known for BSOD free:
http://www.microsoft.com/security_essentials

 

[tonyvr4]

Sorry about missing the Microsoft Security Essentials.

I had just done the following in this order:

1) Removed Mcafee using the tool provided
2) Rebooted as requested to complete uninstall
3) Installed Microsoft Security Essentials
4) MSE download latest update
5) MSE now runnig full system scan
6) Uninstalled Quickset in case Mcafee caused install issues
7) Reinstalled Quickset
8) Enabled driver verifier using options
create custom settings
select individual settings from full list
select all except low resource simulation
select all drivers not from microsoft

Anything I missed? Should I wait now and see what happens?

 

[ttran]

Yep, let's wait for it to crash

 

[tonyvr4]

Ok here goes. I will let you know and thanks

 

[tonyvr4]

It crashed today while I was dismounting my external Sata drive. I haven't done anything yet, but here is the whocrashed report:

[FONT=Segoe UI, Arial]On Sat Sat 7 31 2010 7:46:47 PM your computer crashed
This was likely caused by the following module: [FONT=Segoe UI, Arial]ntoskrnl.exe[/FONT]
Bugcheck code: 0xC9 (0x2, 0xFFFFF9801C8D8EA0, 0x0, 0x0)
Error: [FONT=Segoe UI, Arial]DRIVER_VERIFIER_IOMANAGER_VIOLATION[/FONT]
Dump file: C:\Windows\Minidump\073110-42728-01.dmp
[/FONT][FONT=Segoe UI, Arial]file path: C:\Windows\system32\ntoskrnl.exe
product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.
[/FONT][FONT=Segoe UI, Arial]
Event Viewer:
Event 1001, BugCheck
The computer has rebooted from a bugcheck. The bugcheck was: 0x000000c9 (0x0000000000000002, 0xfffff9801c8d8ea0, 0x0000000000000000, 0x0000000000000000). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 073110-42728-01.

What is the next step?


[/FONT]

 

[tonyvr4]

Just turned off driver verifier and will post the system dump file in a minute after it reboots

 

[tonyvr4]

Here is the minidump file

 

[tonyvr4]

4:57PM got another crash. This time I wasn't doing anything special, just browsing in firefox

The computer has rebooted from a bugcheck. The bugcheck was: 0x0000000a (0xffffffffffffffd0, 0x0000000000000002, 0x0000000000000001, 0xfffff80002cca2b0). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 073110-25662-01.

[FONT=Segoe UI, Arial]On Sat Sat 7 31 2010 8:55:39 PM your computer crashed
This was likely caused by the following module: [FONT=Segoe UI, Arial]ntoskrnl.exe[/FONT]
Bugcheck code: 0xA (0xFFFFFFFFFFFFFFD0, 0x2, 0x1, 0xFFFFF80002CCA2B0)
Error: [FONT=Segoe UI, Arial]IRQL_NOT_LESS_OR_EQUAL[/FONT]
Dump file: C:\Windows\Minidump\073110-25662-01.dmp
[/FONT][FONT=Segoe UI, Arial]file path: C:\Windows\system32\ntoskrnl.exe
product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.
[/FONT]

 

[Jonathan_King]

The dumps are pointing to stdflt.sys, which appears to be an Accelerometer driver. I believe the program has something to do with speeding up your network or something? I see it related to Dell machines, if it helps any.

Whatever it is, please remove the program.

...Summary of the Dumps:

[FONT=lucida console]
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Sat Jul 31 16:54:39.952 2010 (UTC - 4:00)
System Uptime: 0 days 0:54:41.123
BugCheck A, {ffffffffffffffd0, 2, 1, fffff80002cca2b0}
Probably caused by : ntkrnlmp.exe ( nt!KiPageFault+260 )
BUGCHECK_STR:  0xA
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Sat Jul 31 15:45:16.019 2010 (UTC - 4:00)
System Uptime: 0 days 18:00:44.206
BugCheck C9, {2, fffff9801c8d8ea0, 0, 0}
*** WARNING: Unable to verify timestamp for stdflt.sys
*** ERROR: Module load completed but symbols could not be loaded for stdflt.sys
Probably caused by : stdflt.sys ( stdflt+1d54 )
BUGCHECK_STR:  0xc9_2
DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
[/FONT]