ntoskrnl bluescreens

Windows 7 . . .
- x86 x64 patched to date
- the original installed OS on the system?
- an OEM or full retail version?
- OEM = came pre-installed on system as Vista upgrade


- What is the age of system (hardware)? : 2 years
- What is the age of OS installation ~ 1 year

seems to bluescreen on playing embedded video, but not consistently... java related ?

the ati drivers were installed by win 7 after uninstall, i have been having issues with catalyst and the latest drivers prior

thanks for any suggestions

per BlueScreenView :

ntoskrnl.exe ntoskrnl.exe+6fca9 fffff800`03007000 fffff800`035e3000 0x005dc000 0x4c1c44a9 19/06/2010 3:16:41 PM Microsoft® Windows® Operating System NT Kernel & System 6.1.7600.16617 (win7_gdr.100618-1621) Microsoft Corporation C:\Windows\system32\ntoskrnl.exe

Hello,

Could you run driver verifier?

Driver Verifier - Enable and Disable

...Summary of the dumps:

Code:

Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Mon Jan 10 07:55:19.519 2011 (UTC - 5:00)
System Uptime: 0 days 2:17:57.096
Probably caused by : ntkrnlmp.exe ( nt!PspDereferenceQuotaBlock+17 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x3B
PROCESS_NAME:  plugin-contain
FAILURE_BUCKET_ID:  X64_0x3B_nt!PspDereferenceQuotaBlock+17
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
  

Driver Verifier is used to stress the drivers to crash the system into a BSOD in hopes of pinpoint the faulting driver ... the dump files created by the new BSOD crashes will assist us to determine what is happening, and how to resolve it.. You need to upload the new .dmp files for analysis...

Rar is fine too; we can do either. Zip is easier for me, but the difference between that and RAR is about 3 seconds.

Uninstall ATI Tray Tools; that was the cause of the Verifier_Enabled dump. Hopefully that alone will do the trick; if not, enable verifier again and post any new reports.

...Summary of the dumps:

Code:

Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Tue Jan 11 02:50:50.561 2011 (UTC - 5:00)
System Uptime: 0 days 0:01:37.153
*** WARNING: Unable to verify timestamp for DRIVER_BIN64
*** ERROR: Module load completed but symbols could not be loaded for DRIVER_BIN64
Probably caused by : DRIVER_BIN64 ( DRIVER_BIN64+15a7 )
BUGCHECK_STR:  0xc4_f6
DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
PROCESS_NAME:  _attdrv64.exe
FAILURE_BUCKET_ID:  X64_0xc4_f6_VRFK_DRIVER_BIN64+15a7
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Mon Jan 10 07:55:19.519 2011 (UTC - 5:00)
System Uptime: 0 days 2:17:57.096
Probably caused by : ntkrnlmp.exe ( nt!PspDereferenceQuotaBlock+17 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x3B
PROCESS_NAME:  plugin-contain
FAILURE_BUCKET_ID:  X64_0x3B_nt!PspDereferenceQuotaBlock+17
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
  

You can just wait for the next bluescreen to occur on its own; hopefully there will be none!