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
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
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... 
Code:
******************************************************************************* * * * 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 --------- Can you advise on the correct procedure and options for enabling driver verifier?
Also, how do I disable it?
Thanks
Also, how do I disable it?
Thanks
run Verifier with these settings:
To turn off DV--> verifier /reset
Quote:
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:
More info on this at this link: Using Driver Verifier to identify issues with Windows drivers for advanced users
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:
Code:
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
In addition to Tom's good advice, be sure to remove McAfee with this tool: http://download.mcafee.com/products/...tches/MCPR.exe
Install MSE instead: www.microsoft.com/Security_Essentials/
Install MSE instead: www.microsoft.com/Security_Essentials/
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
I will be removing quickset again until this can be resolved
Sorry I forgot to include the whocrashed report:
On Fri Fri 7 30 2010 1:00:10 AM your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0xA (0x76DE2FD0, 0x2, 0x1, 0xFFFFF80002CE22B0)
Error: IRQL_NOT_LESS_OR_EQUAL
Dump file: C:\Windows\Minidump\073010-22963-01.dmp
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft� Windows� Operating System
company: Microsoft Corporation
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.
On Fri Fri 7 30 2010 1:00:10 AM your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0xA (0x76DE2FD0, 0x2, 0x1, 0xFFFFF80002CE22B0)
Error: IRQL_NOT_LESS_OR_EQUAL
Dump file: C:\Windows\Minidump\073010-22963-01.dmp
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft� Windows� Operating System
company: Microsoft Corporation
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.
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.
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.
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.
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 do have Macfee Enterprise from the college I attend and can install that if needed.
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
http://www.microsoft.com/security_essentials
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?
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?
Yep, let's wait for it to crash
Ok here goes. I will let you know and thanks
It crashed today while I was dismounting my external Sata drive. I haven't done anything yet, but here is the whocrashed report:
On Sat Sat 7 31 2010 7:46:47 PM your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0xC9 (0x2, 0xFFFFF9801C8D8EA0, 0x0, 0x0)
Error: DRIVER_VERIFIER_IOMANAGER_VIOLATION
Dump file: C:\Windows\Minidump\073110-42728-01.dmp
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft� Windows� Operating System
company: Microsoft Corporation
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.
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?
On Sat Sat 7 31 2010 7:46:47 PM your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0xC9 (0x2, 0xFFFFF9801C8D8EA0, 0x0, 0x0)
Error: DRIVER_VERIFIER_IOMANAGER_VIOLATION
Dump file: C:\Windows\Minidump\073110-42728-01.dmp
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft� Windows� Operating System
company: Microsoft Corporation
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.
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?
Just turned off driver verifier and will post the system dump file in a minute after it reboots
Here is the minidump file
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.
On Sat Sat 7 31 2010 8:55:39 PM your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0xA (0xFFFFFFFFFFFFFFD0, 0x2, 0x1, 0xFFFFF80002CCA2B0)
Error: IRQL_NOT_LESS_OR_EQUAL
Dump file: C:\Windows\Minidump\073110-25662-01.dmp
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft� Windows� Operating System
company: Microsoft Corporation
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.
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.
On Sat Sat 7 31 2010 8:55:39 PM your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0xA (0xFFFFFFFFFFFFFFD0, 0x2, 0x1, 0xFFFFF80002CCA2B0)
Error: IRQL_NOT_LESS_OR_EQUAL
Dump file: C:\Windows\Minidump\073110-25662-01.dmp
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft� Windows� Operating System
company: Microsoft Corporation
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.
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:
Whatever it is, please remove the program.
...Summary of the Dumps:
Code:
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 �������������������������������������������������������������������������������������� The accelerometer is for shock detection. It is supposed to protect the hard drive from extreme motion.
It did see an updated driver for that. Should I give that a try?
Also, should I turn driver verifier back on?
It did see an updated driver for that. Should I give that a try?
Also, should I turn driver verifier back on?
Keep Verifier off for the time being, we may ask you to turn it back on later.
Give the updated driver a try, it can't hurt. If that doesn't help, remove the program completely, and see what happens.
If that still does not work, enable verifier again, and post back with the dumps it creates.
Give the updated driver a try, it can't hurt. If that doesn't help, remove the program completely, and see what happens.
If that still does not work, enable verifier again, and post back with the dumps it creates.
I installed the new driver and it is the same version. So it just resulted in a removal/reinstall.
I have driver verifier off for the moment
I have driver verifier off for the moment
In these last two dumps, it looks like indeed stdflt.sys is passing incorrect memory information to the stack, causing the next functions to fail. In both, the RDX register is supposed to be populated with the virtual address to be freed, but in both scenarios this register points to invalid VA. Again, in both the stack has just exited some routine in stdflt.sys, and given there's nothing else before it on the stack in either (other than base thread starts), I'm going to say it's a pretty obvious culprit here. Stdflt.sys' driver timestamp is Thu Jul 16 11:36:50 2009, and from what I gather (and reading this thread), this is the accelerometer driver for the HDD.
It might be worth removing this package to remove the driver for a bit to see if it indeed makes the problem go away (it should).
It might be worth removing this package to remove the driver for a bit to see if it indeed makes the problem go away (it should).
Wow that's pretty impressive troubleshooting! You are correct, this is the accelerometer driver for the HDD shock protection.
I just reinstalled the driver. How can I get the timestamp that you mentioned?
I looked in the file properties, and found Digital Signature:
Timestamp July 23, 2009 1:27:39PM
I just reinstalled the driver. How can I get the timestamp that you mentioned?
I looked in the file properties, and found Digital Signature:
Timestamp July 23, 2009 1:27:39PM
I'm not sure if they have released an updated version. If they have, try installing it. Otherwise, just uninstall the program.
Hey tonyvr4, I have the exact same computer (Dell Studio 15) with the exact same problem as you. What seemed to work for me is by disabling the Dell Bluetooth Module.
Go to Start > Right-click My Computer > Manage
Choose Device Manager on the left. Under Bluetooth Radios, Right-click on the Dell Wireless 365 Bluetooth Module and choose Disable
Choose Yes.
Go to Start > Right-click My Computer > Manage
Choose Device Manager on the left. Under Bluetooth Radios, Right-click on the Dell Wireless 365 Bluetooth Module and choose Disable
Choose Yes.
That is very interesting. The only problem is that I can't disable the bluetooth as I have a bluetooth mouse
Did your bluetooth mouse come with its own USB dongle. If so, you can safely disable the Dell Bluetooth and use the included USB dongle for your mouse.
My mouse doesn't come with a dongle. I have one of those little adapters but it kept getting caught when I put my old laptop in the case at school and it could easily have broken
I want to let everyone know that the problem is resolved and to offer many thanks.
The accelerometer driver must have been corrupted from day one since the laptop was never stable, until now thanks to you all.
I reinstalled the driver and it works great now. Thanks for all the help and perseverance required. Dell support didn't even know what a blue screen was when I spoke to them on the phone
The accelerometer driver must have been corrupted from day one since the laptop was never stable, until now thanks to you all.
I reinstalled the driver and it works great now. Thanks for all the help and perseverance required. Dell support didn't even know what a blue screen was when I spoke to them on the phone
Very good, Tony. Good work. I am pleased to hear you are running smoothly. Thank you for reporting back with your solution.
After many days of working without issue, there were two crashes today. It could have been related to the A08 BIOS
Immediately after these crashes I put the BIOS back to the previous version
Attached is the two minidumps. Any help is greatly appreciated
Thanks
Immediately after these crashes I put the BIOS back to the previous version
Attached is the two minidumps. Any help is greatly appreciated
Thanks
Here is the info from the event viewer
The computer has rebooted from a bugcheck. The bugcheck was: 0x0000000a (0xffffffffffffffd0, 0x0000000000000002, 0x0000000000000001, 0xfffff80002c866e0). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 081610-23649-01.
The computer has rebooted from a bugcheck. The bugcheck was: 0x0000000a (0xffffffffffffffd0, 0x0000000000000002, 0x0000000000000001, 0xfffff80002c976e0). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 081610-17830-01.
The computer has rebooted from a bugcheck. The bugcheck was: 0x0000000a (0xffffffffffffffd0, 0x0000000000000002, 0x0000000000000001, 0xfffff80002c866e0). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 081610-23649-01.
The computer has rebooted from a bugcheck. The bugcheck was: 0x0000000a (0xffffffffffffffd0, 0x0000000000000002, 0x0000000000000001, 0xfffff80002c976e0). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 081610-17830-01.
Tony, since you rolled back the BIOS, lets see if you get any more crashes. Error code A is a hardware error. Usual causes are Kernel mode driver, System Service, BIOS, Windows, Virus scanner, Backup tool, compatibility. Because BIOS is a possibility. We need to see what rolling it back did.
The dumps are nearly identical and do not tell much. Both dumps reference memory.
I do find some older drivers.
I can't say these drivers are causing the problem; but Win 7 generally does not like out of date drivers. See if you can update these drivers. If you need help, please post.
The dumps are nearly identical and do not tell much. Both dumps reference memory.
Code:
******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck A, {ffffffffffffffd0, 2, 1, fffff80002c976e0} Probably caused by : ntkrnlmp.exe ( nt!KiPageFault+260 ) Followup: MachineOwner --------- 4: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* IRQL_NOT_LESS_OR_EQUAL (a) An attempt was made to access a pageable (or completely invalid) address at an interrupt request level (IRQL) that is too high. This is usually caused by drivers using improper addresses. If a kernel debugger is available get the stack backtrace. Arguments: Arg1: ffffffffffffffd0, memory referenced Arg2: 0000000000000002, IRQL Arg3: 0000000000000001, bitfield : bit 0 : value 0 = read operation, 1 = write operation bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status) Arg4: fffff80002c976e0, address which referenced memory Debugging Details: ------------------ WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff80002ec30e0 ffffffffffffffd0 CURRENT_IRQL: 2 FAULTING_IP: nt!ObfReferenceObject+20 fffff800`02c976e0 f0480fc11f lock xadd qword ptr [rdi],rbx CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0xA PROCESS_NAME: System TRAP_FRAME: fffff88003387a50 -- (.trap 0xfffff88003387a50) NOTE: The trap frame does not contain all registers. Some register values may be zeroed or incorrect. rax=0000000000000001 rbx=0000000000000000 rcx=0000000000000000 rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000 rip=fffff80002c976e0 rsp=fffff88003387be0 rbp=0000000000000001 r8=0000000000000002 r9=0000000000000000 r10=fffff80002c1b000 r11=0000000000007532 r12=0000000000000000 r13=0000000000000000 r14=0000000000000000 r15=0000000000000000 iopl=0 nv up ei pl zr na po nc nt!ObfReferenceObject+0x20: fffff800`02c976e0 f0480fc11f lock xadd qword ptr [rdi],rbx ds:3428:00000000`00000000=???????????????? Resetting default scope LAST_CONTROL_TRANSFER: from fffff80002c8aca9 to fffff80002c8b740 STACK_TEXT: fffff880`03387908 fffff800`02c8aca9 : 00000000`0000000a ffffffff`ffffffd0 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx fffff880`03387910 fffff800`02c89920 : 00000000`00000000 00000000`00000001 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69 fffff880`03387a50 fffff800`02c976e0 : fffffa80`000000cb 00000000`00000030 00000000`00000030 00000000`0000000b : nt!KiPageFault+0x260 fffff880`03387be0 fffff800`02d75afc : fffffa80`04ab3428 fffffa80`04ab3428 00000000`00000001 00000000`00000000 : nt!ObfReferenceObject+0x20 fffff880`03387c10 fffff800`02ef4daf : fffffa80`04ab3428 00000000`00000001 00000000`00000000 00000000`00007533 : nt!IopDisassociateThreadIrp+0x9c fffff880`03387c40 fffff800`02f70a2b : 00000000`00000000 ffffffff`fffe7960 00000000`00000000 00000000`00000000 : nt! ?? ::NNGAKEGL::`string'+0x1e7aa fffff880`03387c70 fffff800`02f7472d : 00000000`00000000 fffff800`02f2fc00 fffffa80`04ab3000 00000000`00000000 : nt!PspExitThread+0x58b fffff880`03387d30 fffff800`02c69c26 : fffff880`009b1180 00000000`00000080 fffffa80`04ab3040 00000000`00000000 : nt!PspTerminateThreadByPointer+0x4d fffff880`03387d80 00000000`00000000 : fffff880`03388000 fffff880`03382000 fffff880`033879c0 00000000`00000000 : nt!KxStartSystemThread+0x16 STACK_COMMAND: kb FOLLOWUP_IP: nt!KiPageFault+260 fffff800`02c89920 440f20c0 mov rax,cr8 SYMBOL_STACK_INDEX: 2 SYMBOL_NAME: nt!KiPageFault+260 FOLLOWUP_NAME: MachineOwner MODULE_NAME: nt IMAGE_NAME: ntkrnlmp.exe DEBUG_FLR_IMAGE_TIMESTAMP: 4c1c44a9 FAILURE_BUCKET_ID: X64_0xA_nt!KiPageFault+260 BUCKET_ID: X64_0xA_nt!KiPageFault+260 Followup: MachineOwner --------- ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck A, {ffffffffffffffd0, 2, 1, fffff80002c866e0} Probably caused by : ntkrnlmp.exe ( nt!KiPageFault+260 ) Followup: MachineOwner --------- 4: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* IRQL_NOT_LESS_OR_EQUAL (a) An attempt was made to access a pageable (or completely invalid) address at an interrupt request level (IRQL) that is too high. This is usually caused by drivers using improper addresses. If a kernel debugger is available get the stack backtrace. Arguments: Arg1: ffffffffffffffd0, memory referenced Arg2: 0000000000000002, IRQL Arg3: 0000000000000001, bitfield : bit 0 : value 0 = read operation, 1 = write operation bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status) Arg4: fffff80002c866e0, address which referenced memory Debugging Details: ------------------ WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff80002eb20e0 ffffffffffffffd0 CURRENT_IRQL: 2 FAULTING_IP: nt!ObfReferenceObject+20 fffff800`02c866e0 f0480fc11f lock xadd qword ptr [rdi],rbx CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0xA PROCESS_NAME: System TRAP_FRAME: fffff88009667a50 -- (.trap 0xfffff88009667a50) NOTE: The trap frame does not contain all registers. Some register values may be zeroed or incorrect. rax=0000000000000001 rbx=0000000000000000 rcx=0000000000000000 rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000 rip=fffff80002c866e0 rsp=fffff88009667be0 rbp=0000000000000001 r8=0000000000000002 r9=0000000000000000 r10=fffff80002c0a000 r11=0000000000007532 r12=0000000000000000 r13=0000000000000000 r14=0000000000000000 r15=0000000000000000 iopl=0 nv up ei pl zr na po nc nt!ObfReferenceObject+0x20: fffff800`02c866e0 f0480fc11f lock xadd qword ptr [rdi],rbx ds:3f48:00000000`00000000=???????????????? Resetting default scope LAST_CONTROL_TRANSFER: from fffff80002c79ca9 to fffff80002c7a740 STACK_TEXT: fffff880`09667908 fffff800`02c79ca9 : 00000000`0000000a ffffffff`ffffffd0 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx fffff880`09667910 fffff800`02c78920 : 00000000`00000000 00000000`00000001 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69 fffff880`09667a50 fffff800`02c866e0 : fffffa80`0000009d 00000000`00000030 00000000`00000030 00000000`0000000b : nt!KiPageFault+0x260 fffff880`09667be0 fffff800`02d64afc : fffffa80`051c3f48 fffffa80`051c3f48 00000000`00000001 00000000`00000000 : nt!ObfReferenceObject+0x20 fffff880`09667c10 fffff800`02ee3daf : fffffa80`051c3f48 00000000`00000001 00000000`00000000 00000000`00007533 : nt!IopDisassociateThreadIrp+0x9c fffff880`09667c40 fffff800`02f5fa2b : 00000000`00000000 ffffffff`fffe7960 00000000`00000000 00000000`00000000 : nt! ?? ::NNGAKEGL::`string'+0x1e7aa fffff880`09667c70 fffff800`02f6372d : 00000000`00000000 fffff800`02f1ec00 fffffa80`051c3b00 00000000`00000000 : nt!PspExitThread+0x58b fffff880`09667d30 fffff800`02c58c26 : fffff800`02df4e80 00000000`00000080 fffffa80`051c3b60 00000000`00000000 : nt!PspTerminateThreadByPointer+0x4d fffff880`09667d80 00000000`00000000 : fffff880`09668000 fffff880`09662000 fffff880`096679c0 00000000`00000000 : nt!KxStartSystemThread+0x16 STACK_COMMAND: kb FOLLOWUP_IP: nt!KiPageFault+260 fffff800`02c78920 440f20c0 mov rax,cr8 SYMBOL_STACK_INDEX: 2 SYMBOL_NAME: nt!KiPageFault+260 FOLLOWUP_NAME: MachineOwner MODULE_NAME: nt IMAGE_NAME: ntkrnlmp.exe DEBUG_FLR_IMAGE_TIMESTAMP: 4c1c44a9 FAILURE_BUCKET_ID: X64_0xA_nt!KiPageFault+260 BUCKET_ID: X64_0xA_nt!KiPageFault+260 Followup: MachineOwner --------- Quote:
Acceler.sys Fri Jun 26 16:56:34 2009
btwaudio.sys Wed Jul 01 09:54:56 2009
btwavdt.sys Thu Jun 25 01:50:13 2009
btwl2cap.sys Fri Apr 03 20:28:45 2009
btwrchid.sys Thu Jun 25 01:51:37 2009
CtClsFlt.sys Mon Jun 15 01:06:41 2009
rimspe64.sys Wed Jul 01 19:54:49 2009
risdpe64.sys Wed Jul 01 05:31:57 2009
rixdpe64.sys Sat Jul 04 06:27:00 2009
btwaudio.sys Wed Jul 01 09:54:56 2009
btwavdt.sys Thu Jun 25 01:50:13 2009
btwl2cap.sys Fri Apr 03 20:28:45 2009
btwrchid.sys Thu Jun 25 01:51:37 2009
CtClsFlt.sys Mon Jun 15 01:06:41 2009
rimspe64.sys Wed Jul 01 19:54:49 2009
risdpe64.sys Wed Jul 01 05:31:57 2009
rixdpe64.sys Sat Jul 04 06:27:00 2009
Will monitor it as requested. How would I find out what these drivers are for so that I can update them?
Thanks
Thanks
Search Google for the driver name, ending in .sys.
For example search for Acceler.sys, and see what it belongs to. Most drivers can be updated on the computer manufacturer's site, but some will have to be downloaded from the product manufacturer's site.
For example search for Acceler.sys, and see what it belongs to. Most drivers can be updated on the computer manufacturer's site, but some will have to be downloaded from the product manufacturer's site.
Acceler.sys - Accelerometer Port I/O is a driver file from company ST Microelectronics belonging to product Accelerometer Sensor Driver.
btwaudio.sys and btwavdt.sys - Broadcom Bluetooth Audio DeviceBroadcom.com - Downloads & Support
btwl2cap.sys and btwrchid.sys - See above
CtClsFlt.sys - Creative Camera Class Upper Filter DriverCreative Worldwide Support
rimspe64.sys, risdpe64.sys and rixdpe64.sys - RICOH Memory Stick drivers http://www.ricoh.com. There may not be updated drivers. This is older hardware.
Hope this helps.
btwaudio.sys and btwavdt.sys - Broadcom Bluetooth Audio DeviceBroadcom.com - Downloads & Support
btwl2cap.sys and btwrchid.sys - See above
CtClsFlt.sys - Creative Camera Class Upper Filter DriverCreative Worldwide Support
rimspe64.sys, risdpe64.sys and rixdpe64.sys - RICOH Memory Stick drivers http://www.ricoh.com. There may not be updated drivers. This is older hardware.
Hope this helps.
I wasn't able to find drivers on any of the pages listed. I looked on the dell site and was only able to find an updated driver for the Ricoh card reader
System running and steady.
System running and steady.
That is good news! Good job on trying to find the drivers and updating the card reader drivers. Here's hoping you continue to run smoothly. 
Just crashed, but it was very strange. I wasn't even using the laptop at the time. I went downstairs for a few minutes and saw the crash popop.
Minidump attached. I checked the dump in bluescreen view and the details are just like the past two occasions.
Detail from event viewer
The computer has rebooted from a bugcheck. The bugcheck was: 0x0000000a (0x0000000000000098, 0x0000000000000002, 0x0000000000000000, 0xfffff80002db1b42). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 081710-16957-01.
Minidump attached. I checked the dump in bluescreen view and the details are just like the past two occasions.
Detail from event viewer
The computer has rebooted from a bugcheck. The bugcheck was: 0x0000000a (0x0000000000000098, 0x0000000000000002, 0x0000000000000000, 0xfffff80002db1b42). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 081710-16957-01.
Well, I have bad news - this particular dump is an IRP being called to complete in stdflt.sys, but an access violation occurs (also, the stack base pointer is corrupt, which may be part of the failure). Unless this system is running out of resources, likely PTEs given the symptoms (I can't run !VM on a minidump to check right now, so you're going to have to provide at the least a kernel memory dump for the next time this occurs), there's a fault in the stdflt.sys driver as I suspected days ago.
As long as stdflt.sys is not updated, I will not be happy.
But good news! I found this driver for you!
Drivers and Downloads
Install that, and see how it goes.
Good luck!
...Summary of the Dumps:
But good news! I found this driver for you!
Drivers and Downloads
Install that, and see how it goes.
Good luck!
...Summary of the Dumps:
Code:
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621 Debug session time: Tue Aug 17 13:35:19.545 2010 (UTC - 4:00) System Uptime: 0 days 16:29:41.716 BugCheck A, {98, 2, 0, fffff80002db1b42} Probably caused by : ntkrnlmp.exe ( nt!IopDisassociateThreadIrp+e2 ) BUGCHECK_STR: 0xA PROCESS_NAME: System �������������������������������������������������������������������������������������� So if I understand it correctly, we are back the the stinkin accelerometer causing crashes again?
You confused me with the other information though. I don't think it can be running out of resources because the one time it crashed, I didn't have anything open. I went downstairs and left the laptop on but nothing was running.
The driver you mentioned is the one that I am running. Unless it got corrupted somehow. I installed it after the last series of crashes and it ran great until the recent group
You confused me with the other information though. I don't think it can be running out of resources because the one time it crashed, I didn't have anything open. I went downstairs and left the laptop on but nothing was running.
The driver you mentioned is the one that I am running. Unless it got corrupted somehow. I installed it after the last series of crashes and it ran great until the recent group
clubreti is saying that if you are not running out of resources, then the trouble is stdflt.sys. And you are apparently not running out of resources.
Ah sorry for the misunderstanding.
I will remove and reinstall the driver you mentioned. If that doesn't work, I am at the point that I will remove the driver.
Dell does absolutely nothing to help. Multiple contacts to tech support were useless. They didn't even know what a crash or blue screen was!
Also two letters to dell headquarters were useless also
I will remove and reinstall the driver you mentioned. If that doesn't work, I am at the point that I will remove the driver.
Dell does absolutely nothing to help. Multiple contacts to tech support were useless. They didn't even know what a crash or blue screen was!
Also two letters to dell headquarters were useless also
Good luck with the new driver, I hope it works!
Sorry to hear about their tech support, I would have expected more from Dell than that. Oh well, that's why we're here, right?
Sorry to hear about their tech support, I would have expected more from Dell than that. Oh well, that's why we're here, right?
Yeah, Dell's business/commercial support is fairly good, but their home/personal support folks are utter crap most of the time. I guess that's why business support costs so much more.
Let us know if the new driver works. I hope it does.
Just adding some personal advice, as i too have a dell 1558 that has BSOD'd and has 30 sec freezing. Laptop is only 1 month old
Dell support only wanted to wipe the laptop, to me (an IT manager( that is the last option, not the first.
Anyway, i used Blue screen viewer from nirsoft and saw that the free Mcafee Dell supplies seemed to be the problem (from what i could tell). So removed mcafee and used thier clean up tool MCPR.exe, rebooted, installed microsofts free security centre and so far, all ok.
I also updated the BIOS and video drivers, no bluetooth on mine, Accelorometer driver seems to be up to date.
One thing i dont seem to be getting any software update message from Dell, i assume i should be.
Dell support only wanted to wipe the laptop, to me (an IT manager( that is the last option, not the first.
Anyway, i used Blue screen viewer from nirsoft and saw that the free Mcafee Dell supplies seemed to be the problem (from what i could tell). So removed mcafee and used thier clean up tool MCPR.exe, rebooted, installed microsofts free security centre and so far, all ok.
I also updated the BIOS and video drivers, no bluetooth on mine, Accelorometer driver seems to be up to date.
One thing i dont seem to be getting any software update message from Dell, i assume i should be.
Quote:
One thing i dont seem to be getting any software update message from Dell, i assume i should be.
Just in case it helps anyone else.
Since deleting free mcafee 14month licence that came with my Dell 1558, and installing Microsoft Essential security, ive not had a single freeze or BSOD.
Since deleting free mcafee 14month licence that came with my Dell 1558, and installing Microsoft Essential security, ive not had a single freeze or BSOD.
�� Quote: Originally Posted by mreco99 
Just in case it helps anyone else.
Since deleting free mcafee 14month licence that came with my Dell 1558, and installing Microsoft Essential security, ive not had a single freeze or BSOD.
Since deleting free mcafee 14month licence that came with my Dell 1558, and installing Microsoft Essential security, ive not had a single freeze or BSOD.
Mreco99, thank you for letting us know. I am glad you solved your problem.
Sorry i was a bit premature, still freezes.
was ok for a few days, but now it can freeze every 10 mins for 30 seconds, then nothing for a couple of hours.
When it freezes nothing works, i get the circle cursor timer, firefox greys out, i have tried just using IE, same.
i keep updating drivers from Dell website, Bios is now on A11.
This has happened since day 1 of the laptop
were not alone
http://en.community.dell.com/support....aspx#19765196
unbelievable.
was ok for a few days, but now it can freeze every 10 mins for 30 seconds, then nothing for a couple of hours.
When it freezes nothing works, i get the circle cursor timer, firefox greys out, i have tried just using IE, same.
i keep updating drivers from Dell website, Bios is now on A11.
This has happened since day 1 of the laptop
were not alone
http://en.community.dell.com/support....aspx#19765196
unbelievable.
Wow, that article is not good news at all. It looks like this is a Dell problem.
Không có nhận xét nào:
Đăng nhận xét