lock ups and BSOD - can someone read these minidumps files please

dougal4chaos · May 16, 2012

recently did a fresh install of win 7 x64 and have had lock ups and BSOD's ever since.

i have latest cpu, bios and graphics drivers.

writhziden · May 16, 2012

Your Minidump zip file contains no files. Please follow the http://www.sevenforums.com/crashes-debugging/96879-blue-screen-death-bsod-posting-instructions.html to provide us with the full crash reports.

dougal4chaos · May 17, 2012

writhziden said:
Your Minidump zip file contains no files. Please follow the http://www.sevenforums.com/crashes-debugging/96879-blue-screen-death-bsod-posting-instructions.html to provide us with the full crash reports.

sorry, should be done correctly now

writhziden · May 17, 2012

You appear to have both avast! and Microsoft Security Essentials running at the same time. Choose one or the other. Having two security programs that accomplish the same task can lead to conflicts because they try to access the same system files and system resources simultaneously. Superantispyware is safe to run alongside either one, but not both.

Problematic Software:

Code:

Start Menu\Programs\O&O Software\O&O Defrag	Public:Start Menu\Programs\O&O Software\O&O Defrag	Public
Start Menu\Programs\Ultimate Windows Tweaker	Public:Start Menu\Programs\Ultimate Windows Tweaker	Public

I recommend against 3rd party defrag tools. Windows has some nice command line flags for the defrag command that will accomplish the same tasks as 3rd party programs. The -b and -w flags will defrag boot files and the boot registry items as well as compact the data to the center of the disk for faster access.

defrag c: -b
defrag -c -v -w

The first command optimizes boot performance for the Windows drive by defragmenting boot files and boot registry items.

The second command includes all drives on the system through the -c command and optimizes the drives by compacting the data to the center of the disk. Verbose output through the -v option is optional to provide the user with more information about the defrag tasks. The commands have to be run in an http://www.sevenforums.com/tutorials/783-elevated-command-prompt.html

Many of us on the forums actually do not recommend automated optimization tools for Windows 7. Windows 7 does a much better job of handling its own optimization than its predecessors did. We especially do not recommend registry cleaning as an "optimization" step because automated registry cleaning causes more harm to the registry than it actually repairs.

In the future, if you need help optimizing Windows 7, please post a thread in Performance & Maintenance - Windows 7 Forums or follow the tutorial enclosed in that forum to http://www.sevenforums.com/tutorial...ws-7-a.html?filter[2]=Performance Maintenance.

Do the above steps, and see how things go. If you still have problems, then we can look into other possible causes.

dougal4chaos · May 18, 2012

ive removed avast as i didnt like it anyway, will keep mse
also removed o&o defrag,

any ideas on the minidumps

writhziden · May 18, 2012

The most recent .dmp file indicated avast! The others indicate possible graphics card driver issues, but they are not conclusive in this regard. I do see signs of a corrupted Windows file and hard disk data corruption.

If you are overclocking any hardware, please stop.
Run Disk Check with both boxes checked for all HDDs and with Automatically fix file system errors checked for all SSDs. Post back your logs for the checks after finding them using http://www.sevenforums.com/tutorials/96938-check-disk-chkdsk-read-event-viewer-log.html.
For any drives that do not give the message:
Windows has checked the file system and found no problems
run disk check again as above. In other words, if it says:
Windows has made corrections to the file system
after running the disk check, run the disk check again.
Check Windows for corruption. Run http://www.sevenforums.com/tutorials/1538-sfc-scannow-command-system-file-checker.html up to three times to fix all errors with a restart in between each. Post back if it continues to show errors after a fourth run or if the first run comes back with no integrity violations. Use OPTION THREE of http://www.sevenforums.com/tutorials/1538-sfc-scannow-command-system-file-checker.html to provide us with the sfcdetails.txt file if errors occur.

dougal4chaos · May 25, 2012

i never overclock anything.

i ran chkdsk 3 times on C: drive
ran it once on all slave drives

Checking file system on C:
The type of the file system is NTFS.

A disk check has been scheduled.
Windows will now check the disk.

CHKDSK is verifying files (stage 1 of 5)...
141056 file records processed. File verification completed.
141 large file records processed. 0 bad file records processed. 2 EA records processed. 44 reparse records processed. CHKDSK is verifying indexes (stage 2 of 5)...
191748 index entries processed. Index verification completed.
0 unindexed files scanned. 0 unindexed files recovered. CHKDSK is verifying security descriptors (stage 3 of 5)...
141056 file SDs/SIDs processed. Cleaning up 4 unused index entries from index $SII of file 0x9.
Cleaning up 4 unused index entries from index $SDH of file 0x9.
Cleaning up 4 unused security descriptors.
Security descriptor verification completed.
25347 data files processed. CHKDSK is verifying Usn Journal...
36600120 USN bytes processed. Usn Journal verification completed.
CHKDSK is verifying file data (stage 4 of 5)...
141040 files processed. File data verification completed.
CHKDSK is verifying free space (stage 5 of 5)...
171344258 free clusters processed. Free space verification is complete.
Windows has checked the file system and found no problems.

732572000 KB total disk space.
46858532 KB in 107276 files.
70464 KB in 25348 indexes.
0 KB in bad sectors.
265972 KB in use by the system.
65536 KB occupied by the log file.
685377032 KB available on disk.

4096 bytes in each allocation unit.
183143000 total allocation units on disk.
171344258 allocation units available on disk.

Internal Info:
00 27 02 00 1b 06 02 00 e7 b3 03 00 00 00 00 00 .'..............
3b 02 00 00 2c 00 00 00 00 00 00 00 00 00 00 00 ;...,...........
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................

Windows has finished checking your disk.
Please wait while your computer restarts.

ran SFC /SCANNOW 4 times

ps pc hasnt crashed or blue screened since i removed avast, although it was crashing before i installed avast

jcgriff2 · May 25, 2012

Hi -

Dumps indicate no overclockng.

Video seems the common theme.

See if Driiver Verifier flags any 3rd party drivers - Driver Verifier - BSOD related

Regards. . .

jcgriff2

`

BSOD SUMMARY

Code:

[font=lucida console]
Loading Dump File [C:\Users\PalmDesert\_jcgriff2_\dbug\__Kernel__\050512-36207-01.dmp]
Built by: 7601.17790.amd64fre.win7sp1_gdr.120305-1505
Debug session time: Sat May  5 16:39:02.784 2012 (GMT-4)
System Uptime: 0 days 4:17:29.516
BugCheck 1000007E, {ffffffffc0000005, fffff80002ce8bf6, fffff880031d2908, fffff880031d2160}
Probably caused by : ntkrnlmp.exe ( nt!PspReturnQuota+46 )
DEFAULT_BUCKET_ID:  NULL_DEREFERENCE
PROCESS_NAME:  System
BUGCHECK_STR:  0x7E
FAILURE_BUCKET_ID:  X64_0x7E_nt!PspReturnQuota+46
Bugcheck code 1000007E
Arguments ffffffff`c0000005 fffff800`02ce8bf6 fffff880`031d2908 fffff880`031d2160
BiosVersion = 2102   
BiosReleaseDate = 02/23/2009
SystemManufacturer = System manufacturer
SystemProductName = P5Q-PRO
MaxSpeed:     2830
CurrentSpeed: 2833
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\PalmDesert\_jcgriff2_\dbug\__Kernel__\050712-37268-01.dmp]
Built by: 7601.17790.amd64fre.win7sp1_gdr.120305-1505
Debug session time: Mon May  7 05:49:27.649 2012 (GMT-4)
System Uptime: 0 days 5:54:36.008
BugCheck 1A, {41790, fffffa8006020460, ffff, 0}
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+355d4 )
BUGCHECK_STR:  0x1a_41790
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  SearchProtocol
FAILURE_BUCKET_ID:  X64_0x1a_41790_nt!_??_::FNODOBFM::_string_+355d4
Bugcheck code 0000001A
Arguments 00000000`00041790 fffffa80`06020460 00000000`0000ffff 00000000`00000000
BiosVersion = 2102   
BiosReleaseDate = 02/23/2009
SystemManufacturer = System manufacturer
SystemProductName = P5Q-PRO
MaxSpeed:     2830
CurrentSpeed: 2833
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\PalmDesert\_jcgriff2_\dbug\__Kernel__\050812-38844-01.dmp]
Built by: 7601.17790.amd64fre.win7sp1_gdr.120305-1505
Debug session time: Mon May  7 20:29:40.613 2012 (GMT-4)
System Uptime: 0 days 7:59:17.361
BugCheck 3B, {c0000005, fffff8800454c50a, fffff880082f4ad0, 0}
Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_GLOBAL::CloseOneAllocation+182 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x3B
PROCESS_NAME:  daorigins.exe
FAILURE_BUCKET_ID:  X64_0x3B_dxgmms1!VIDMM_GLOBAL::CloseOneAllocation+182
Bugcheck code 0000003B
Arguments 00000000`c0000005 fffff880`0454c50a fffff880`082f4ad0 00000000`00000000
BiosVersion = 2102   
BiosReleaseDate = 02/23/2009
SystemManufacturer = System manufacturer
SystemProductName = P5Q-PRO
MaxSpeed:     2830
CurrentSpeed: 2833
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\PalmDesert\_jcgriff2_\dbug\__Kernel__\050912-38126-01.dmp]
Built by: 7601.17790.amd64fre.win7sp1_gdr.120305-1505
Debug session time: Wed May  9 18:41:31.051 2012 (GMT-4)
System Uptime: 0 days 1:32:53.409
BugCheck 3B, {c0000005, fffff88002c1d50a, fffff8800925dc30, 0}
Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_GLOBAL::CloseOneAllocation+182 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x3B
PROCESS_NAME:  daorigins.exe
FAILURE_BUCKET_ID:  X64_0x3B_dxgmms1!VIDMM_GLOBAL::CloseOneAllocation+182
Bugcheck code 0000003B
Arguments 00000000`c0000005 fffff880`02c1d50a fffff880`0925dc30 00000000`00000000
BiosVersion = 2102   
BiosReleaseDate = 02/23/2009
SystemManufacturer = System manufacturer
SystemProductName = P5Q-PRO
MaxSpeed:     2830
CurrentSpeed: 2833
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\PalmDesert\_jcgriff2_\dbug\__Kernel__\051012-36785-01.dmp]
Built by: 7601.17790.amd64fre.win7sp1_gdr.120305-1505
Debug session time: Wed May  9 19:00:26.894 2012 (GMT-4)
System Uptime: 0 days 0:17:33.626
BugCheck 1E, {ffffffffc0000005, fffff80002f4bb5e, 0, ffffffffffffffff}
Probably caused by : ntkrnlmp.exe ( nt!CmpKcbCacheLookup+1de )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x1E
PROCESS_NAME:  svchost.exe
FAILURE_BUCKET_ID:  X64_0x1E_nt!CmpKcbCacheLookup+1de
Bugcheck code 0000001E
Arguments ffffffff`c0000005 fffff800`02f4bb5e 00000000`00000000 ffffffff`ffffffff
BiosVersion = 2102   
BiosReleaseDate = 02/23/2009
SystemManufacturer = System manufacturer
SystemProductName = P5Q-PRO
MaxSpeed:     2830
CurrentSpeed: 2833
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\PalmDesert\_jcgriff2_\dbug\__Kernel__\051112-37565-01.dmp]
Built by: 7601.17790.amd64fre.win7sp1_gdr.120305-1505
Debug session time: Fri May 11 14:39:10.299 2012 (GMT-4)
System Uptime: 0 days 3:12:11.031
BugCheck 3B, {c0000005, fffff80002cd65e4, fffff88009593130, 0}
Probably caused by : win32k.sys ( win32k!NtUserWaitMessage+4d )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x3B
PROCESS_NAME:  iexplore.exe
FAILURE_BUCKET_ID:  X64_0x3B_win32k!NtUserWaitMessage+4d
Bugcheck code 0000003B
Arguments 00000000`c0000005 fffff800`02cd65e4 fffff880`09593130 00000000`00000000
BiosVersion = 2102   
BiosReleaseDate = 02/23/2009
SystemManufacturer = System manufacturer
SystemProductName = P5Q-PRO
MaxSpeed:     2830
CurrentSpeed: 2833
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\PalmDesert\_jcgriff2_\dbug\__Kernel__\051312-27081-01.dmp]
Built by: 7601.17803.amd64fre.win7sp1_gdr.120330-1504
Debug session time: Sun May 13 08:57:10.804 2012 (GMT-4)
System Uptime: 0 days 2:47:53.163
BugCheck 3B, {c0000005, fffff80002d3dbef, fffff88008910880, 0}
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+25c00 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x3B
PROCESS_NAME:  csrss.exe
FAILURE_BUCKET_ID:  X64_0x3B_nt!_??_::FNODOBFM::_string_+25c00
Bugcheck code 0000003B
Arguments 00000000`c0000005 fffff800`02d3dbef fffff880`08910880 00000000`00000000
BiosVersion = 2102   
BiosReleaseDate = 02/23/2009
SystemManufacturer = System manufacturer
SystemProductName = P5Q-PRO
MaxSpeed:     2830
CurrentSpeed: 2833
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\PalmDesert\_jcgriff2_\dbug\__Kernel__\051312-28828-01.dmp]
Built by: 7601.17803.amd64fre.win7sp1_gdr.120330-1504
Debug session time: Sun May 13 16:41:15.252 2012 (GMT-4)
System Uptime: 0 days 7:42:36.000
BugCheck 1E, {0, 0, 0, 0}
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : cdrom.sys ( cdrom!SequentialQueueEvtIoDeviceControl+177 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x1E
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x1E_cdrom!SequentialQueueEvtIoDeviceControl+177
Bugcheck code 0000001E
Arguments 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000
BiosVersion = 2102   
BiosReleaseDate = 02/23/2009
SystemManufacturer = System manufacturer
SystemProductName = P5Q-PRO
MaxSpeed:     2830
CurrentSpeed: 2833
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\PalmDesert\_jcgriff2_\dbug\__Kernel__\051612-25428-01.dmp]
Built by: 7601.17803.amd64fre.win7sp1_gdr.120330-1504
Debug session time: Wed May 16 10:48:16.274 2012 (GMT-4)
System Uptime: 0 days 6:03:42.022
BugCheck 3B, {c0000005, fffff80002f5e9ae, fffff88009d6b720, 0}
Probably caused by : ntkrnlmp.exe ( nt!CmpKcbCacheLookup+1de )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x3B
PROCESS_NAME:  avast.setup
FAILURE_BUCKET_ID:  X64_0x3B_nt!CmpKcbCacheLookup+1de
Bugcheck code 0000003B
Arguments 00000000`c0000005 fffff800`02f5e9ae fffff880`09d6b720 00000000`00000000
BiosVersion = 2102   
BiosReleaseDate = 02/23/2009
SystemManufacturer = System manufacturer
SystemProductName = P5Q-PRO
MaxSpeed:     2830
CurrentSpeed: 2833
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\PalmDesert\_jcgriff2_\dbug\__Kernel__\051612-29312-01.dmp]
Built by: 7601.17803.amd64fre.win7sp1_gdr.120330-1504
Debug session time: Wed May 16 02:02:25.504 2012 (GMT-4)
System Uptime: 0 days 1:29:25.862
BugCheck 3B, {c0000005, fffff80002ccfb24, fffff88009452100, 0}
Probably caused by : win32k.sys ( win32k!NtUserPostMessage+fe )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x3B
PROCESS_NAME:  plugin-contain
FAILURE_BUCKET_ID:  X64_0x3B_win32k!NtUserPostMessage+fe
Bugcheck code 0000003B
Arguments 00000000`c0000005 fffff800`02ccfb24 fffff880`09452100 00000000`00000000
BiosVersion = 2102   
BiosReleaseDate = 02/23/2009
SystemManufacturer = System manufacturer
SystemProductName = P5Q-PRO
MaxSpeed:     2830
CurrentSpeed: 2833
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\PalmDesert\_jcgriff2_\dbug\__Kernel__\051612-31730-01.dmp]
Built by: 7601.17803.amd64fre.win7sp1_gdr.120330-1504
Debug session time: Wed May 16 03:06:00.268 2012 (GMT-4)
System Uptime: 0 days 1:02:02.626
BugCheck 3B, {c0000005, fffff80002fe230b, fffff880069d1020, 0}
Probably caused by : ntkrnlmp.exe ( nt!AlpcpReceiveMessagePort+27b )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x3B
PROCESS_NAME:  svchost.exe
FAILURE_BUCKET_ID:  X64_0x3B_nt!AlpcpReceiveMessagePort+27b
Bugcheck code 0000003B
Arguments 00000000`c0000005 fffff800`02fe230b fffff880`069d1020 00000000`00000000
BiosVersion = 2102   
BiosReleaseDate = 02/23/2009
SystemManufacturer = System manufacturer
SystemProductName = P5Q-PRO
MaxSpeed:     2830
CurrentSpeed: 2833
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``


	    
             
       [color=#000033]J. C. Griffith, Microsoft MVP (jcgriff2)[/color]   
             
           [url=https://mvp.support.microsoft.com/profile/Griffith][color=#000055][u]https://mvp.support.microsoft.com/profile/Griffith[/u][/color][/url]   

           [url=http://sysnative.com][color=#000033][u]www.sysnative.com[/u][/color][/url]
             
           [url=http://jcgriff2.com][color=#000055][u]www.jcgriff2.com[/u][/color][/url] 


¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨


  
[/font]

dougal4chaos · May 25, 2012

jcgriff2 said:
Hi -

Dumps indicate no overclockng.

Video seems the common theme.

See if Driiver Verifier flags any 3rd party drivers - Driver Verifier - BSOD related

Regards. . .

jcgriff2

it says to run for a minimum of 24 hours, is that a continous 24 hours or can i reboot in between ?

also i type verifier /query in a dos box and it just brings up a new dos box, scrolls through some text quickly and then disappears, so i cant read anything

writhziden · May 27, 2012

You can reboot in between. It means you should do your normal routine for a minimum of 24 hours while Verifier is enabled. Try to do tasks that ordinarily cause crashes, though.

That is odd about the verifier /query. The fact that you saw it scroll means drivers are verified, though. Otherwise, you would get a short message as in my image:
View attachment 213822

dougal4chaos · May 29, 2012

had a new blue screen while Verifier is enabled so added new minidump

writhziden · May 29, 2012

The .zip file contained an empty directory. Please follow the http://www.sevenforums.com/crashes-debugging/96879-blue-screen-death-bsod-posting-instructions.html to provide us with the crash reports.

dougal4chaos · May 30, 2012

writhziden said:
The .zip file contained an empty directory. Please follow the http://www.sevenforums.com/crashes-debugging/96879-blue-screen-death-bsod-posting-instructions.html to provide us with the crash reports.

ok not sure how that happened.

writhziden · May 30, 2012

Your Verifier enabled crash indicates your ATI driver. Try installing the 11.9 driver and see if the problems persist. Some have had problems with the 12.x drivers on their systems.

Download the drivers you want for your display card(s)
Click Start Menu
Click Control Panel
Click Uninstall a program
For AMD:
- Uninstall AMD Catalyst Install Manager if it is listed (this should remove all AMD graphics software and drivers)
- If AMD Catalyst Install Manager is not listed, use the following method to uninstall the graphics drivers (this applies to onboard graphics, as well):
  1. Click Start Menu
  2. Right Click My Computer/Computer
  3. Click Manage
  4. Click Device Manager from the list on the left
  5. Expand Display adapters
  6. Do the following for each adapter (in case you have multiple display cards)
    - Right click the adapter
    - Click Uninstall (do not click OK in the dialog box that pops up after hitting Uninstall)
    - Put a tick in Delete driver software for this device (if this option is available, otherwise just hit OK) and hit OK
    Alternatively:
    1. Login as an adminstrative user
    2. Click Start Menu
    3. Click Control Panel
    4. Click Hardware and Sound
    5. Click Device Manager (the last link under Devices and Printers)
    6. Expand Display adapters
    7. Do the following for each adapter (in case you have multiple display cards)
      - Right click the adapter
      - Click Uninstall (do not click OK in the dialog box that pops up after hitting Uninstall)
      - Put a tick in Delete driver software for this device (if this option is available, otherwise just hit OK) and hit OK
- Restart your computer after uninstalling drivers for all display cards
- Install the driver you selected for the display cards once Windows starts

dougal4chaos · May 31, 2012

i installed cat 12.3 on 19th april 2012
got a message today to install cat 12.4

if i get another blue screen i'll revert back to cat 11.9 as you suggest.

ive had a lot less blue screens since i got the help from this thread

writhziden · May 31, 2012

If you still have Verifier enabled, you will continue to get crashes because it intentionally stresses the drivers. They may be false positives, but we cannot be sure until we see the reports.

dougal4chaos · May 31, 2012

writhziden said:
If you still have Verifier enabled, you will continue to get crashes because it intentionally stresses the drivers. They may be false positives, but we cannot be sure until we see the reports.

yeah it is still enabled
installed 12.4
had another blue screen, dumpfile attached.

i'll disable verifier and see if any more blue screens appear.

writhziden · May 31, 2012

Verifier enabled .dmp file still indicates your graphics card driver as the cause.

Strange...

dougal4chaos · Jun 6, 2012

writhziden said:
Verifier enabled .dmp file still indicates your graphics card driver as the cause. Strange...

i turned pc on and a lot of little squares appeared all over the screen including the taskbar, screen then went grey, when i restarted pc i got nothing on my monitor at all. not even any text when booting up so im guessing my graphics card has died.

writhziden · Jun 6, 2012

Pretty safe bet the graphics card failed on you. However, just to be sure, try a hardware stripdown.

Warning

Before you proceed with the following, answer these two questions: Are you still under warranty? Does your warranty allow you to open up the machine to check hardware? If you are unsure of the answers to these questions, contact your system manufacturer. :warn:WARNING: The steps that follow can void your warranty!!!

Strip down your system to run only the bare essentials: one RAM module, the CPU, motherboard, one hard disk, one graphics card (or use onboard graphics if you have it), keyboard, mouse, and one monitor. See how the system behaves. If it is able to start, add one piece of hardware back at a time until you can no longer start. Take notes of what hardware you add and how the system responds to the hardware changes.

As you add and remove hardware, follow these steps for ESD safety:

Shut down and turn off your computer.
Unplug all power supplies to the computer (AC Power then battery for laptops, AC power for desktops)
Hold down the power button for 30 seconds to close the circuit and ensure all power drains from components.
Make sure you are grounded by using proper grounding techniques, i.e. work on an anti-static workbench, anti-static desk, or an anti-static pad. Hold something metallic while touching it to the anti-static surface, or use an anti-static wristband to attach to the anti-static material while working. If you do not have an anti-static workbench, desk, or pad, you can use your computer tower/case by finding a metal hold in it, such as a drive bay.

Once these steps have been followed, it is safe to remove and replace components within your computer.

lock ups and BSOD - can someone read these minidumps files please

New member

My Computer

Closed by request.

My Computer

New member

My Computer

Closed by request.

My Computer

New member

My Computer

Closed by request.

My Computer

New member

My Computer

Account closed

My Computer

New member

My Computer

Closed by request.

My Computer

New member

My Computer

Closed by request.

My Computer

New member

My Computer

Closed by request.

My Computer

New member

My Computer

Closed by request.

My Computer

New member

My Computer

Closed by request.

My Computer

New member

My Computer

Closed by request.

My Computer