 | |
| |
| 19 Oct 2010 | #1 |
| | Help the BSOD Would someone have a look at some minidumps Many thanks  |
My System Specs | |
| 19 Oct 2010 | #2 |
| | Can you please describe the problem that you are having?? Please fill in your system specs.. it will aid us in diagnosing your problem...  |
| My System Specs |
| 19 Oct 2010 | #3 |
| | The dmp(s) point to ntkrpamp.exe or ntkrnlmp.exe as the probable cause. We know this is not the case, as these are core OS files, and will definitely not cause a BSOD. They are just the default files the debuggers blame when they can't see a better cause. We need to enable driver verifier to further pinpoint the faulting driver... - 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). Code: *******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 3B, {c000001d, fffff88000000000, fffff88005abc160, 0}
Probably caused by : ntkrnlmp.exe ( nt!IoCancelIrp+64 )
Followup: MachineOwner
---------
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 3B, {c000001d, fffff88000000000, fffff88005769160, 0}
Probably caused by : ntkrnlmp.exe ( nt!IoCancelIrp+64 )
Followup: MachineOwner
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 3B, {c000001d, fffff88000000000, fffff880077d2160, 0}
Probably caused by : ntkrnlmp.exe ( nt!IoCancelIrp+64 )
Followup: MachineOwner
---------
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 3B, {c000001d, fffff88000000000, fffff880068a2160, 0}
Probably caused by : ntkrnlmp.exe ( nt!IoCancelIrp+64 )
Followup: MachineOwner
---------
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 3B, {c000001d, fffff88000000000, fffff880079f2160, 0}
Probably caused by : ntkrnlmp.exe ( nt!IoCancelIrp+64 )
Followup: MachineOwner
---------
...
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 3B, {c000001d, fffff88000000000, fffff88005d59160, 0}
Probably caused by : ntkrnlmp.exe ( nt!IoCancelIrp+64 )
Followup: MachineOwner
--------- Code: 1: kd> lmtsmn start end module name fffff880`053ac000 fffff880`053d7000 000 000.fcl Fri Sep 26 09:11:22 2008 (48DCDF7A) fffff880`04045000 fffff880`04189000 bcmwl664 bcmwl664.sys Thu Mar 26 21:06:57 2009 (49CC26B1) fffff880`010e0000 fffff880`011f0000 iaStor iaStor.sys Wed May 07 20:15:59 2008 (4822463F) fffff880`04623000 fffff880`04d23960 igdkmd64 igdkmd64.sys Fri Jul 03 12:42:03 2009 (4A4E34DB) fffff880`04d6d000 fffff880`04d83000 intelppm intelppm.sys Mon Jul 13 19:19:25 2009 (4A5BC0FD) fffff880`01e4d000 fffff880`01e74060 OA013Ufd OA013Ufd.sys Fri Mar 06 02:33:57 2009 (49B0D1E5) fffff880`01e00000 fffff880`01e4c0a0 OA013Vid OA013Vid.sys Mon Mar 09 22:45:53 2009 (49B5D461) fffff880`00ee8000 fffff880`00ef3700 PxHlpa64 PxHlpa64.sys Wed Oct 17 14:25:02 2007 (4716537E) fffff880`04d24000 fffff880`04d6d000 SynTP SynTP.sys Fri Jun 26 14:35:47 2009 (4A451503) fffff880`04196000 fffff880`041fe000 yk60x64 yk60x64.sys Wed Mar 18 12:38:59 2009 (49C123A3) |
| My System Specs |
| . |
| |
| 19 Oct 2010 | #4 |
| | Hi I don't have the machine in front of at the mo, but will get you the details asap Thanks |
| My System Specs |
| 20 Oct 2010 | #5 |
| | Whilst on the subject of drivers, is there a good update program i can use or should i do them manually |
| My System Specs |
