Multiple BSODs, Stop Error 0X0000001E, computer locks up/auto reboots

[JC1]

Hi, this is my first post, so I hope I can provide everything needed.

ISSUE: I have been getting multiple BSOD for several months, came on this forum a couple months ago, and read other posts, and then updated my bios version (flashed it) and that seemed to help for awhile, but getting BSOD's and computer lock ups more and more.

The BSOD's are typically have a stop error message in them. Most recently, Stop: 0X0000001E, 0Xffffffffc0000005, 0Xfffff8000zfb43fa, 0x000000000001, x000000000018.

Also, the computer has been randomly locking up (mouse doesn't move) requiring a reboot, and other times, the system is just automatically rebooting.

Lastly, and more recently, occasionally my computer says it can't start, and does a 'error check' when booting up. Not always, but sometimes, rebooting 1-2X and it goes away. I've also noticed a strange sound (hard drive?) when booting up which started about a month ago, but after the initial BSOD's. I ran the short Seagate HD tests, and they came back clean so far. Will try to run Memtest and post.

Any help is much appreciated. Attaching the performance report and zip of the dump files. Thanks. -JC

Computer specs: Purchased this as build to order about 3 years ago. 64 bit, Asus 6pt Motherboard X58 chipset, I7 Quad Core Processor (920 2.6Ghz), 1 GB video card (9800GT), 6 GB memory, Windows 7 home premium.

 

[JC1]

Well, I guess I need help with how to upload the performance report and zip folder with the dump files acccording to the BSOD post instructions. I zipped it up in a folder using the windows zip option, but the attachment (paper clip) won't attached the folder, it wants me to pick a specific file. There is like 80-100 files in the folder, so don't think I want to attach them all. Anyone know how to attach a zip folder?

 

[writhziden]

View attachment 199799
View attachment 199800
View attachment 199801
View attachment 199802
View attachment 199803
View attachment 199804
View attachment 199805

 

[JC1]

Thank you. But I know the steps above to zip to a folder. The problem is when I select the folder to upload it, the 'file name' field at the bottom of the section is blank - so when I click 'open', it says no FILE is selected (because obviously it's a folder). I tried to manually type the folder name in the file field, but it said there is no file. Don't know why this is so difficult, I've uploaded thousands of other things elsewhere. I just tried 10+ times again, and I can't upload the folder. For that matter, I can even upload the performance test because it's an HTML file, and the upload instructions say it can't upload HTML files, so I don't know why this file is being requested. Frustrated...this thread is turning into how to upload a file...

On the original issue, I ran Memtest and it passed successfully w/no errors.

 

[writhziden]

A .zip file is not a folder, it is a file. As you can see in my images above, there should not be a problem selecting it. The HTML file can be included in the .zip file which you can upload here.

I am wondering if you need: http://www.sevenforums.com/tutorials/19449-default-file-type-associations-restore.html.

For your most recent crash, see Bug Check 0x1E: KMODE_EXCEPTION_NOT_HANDLED

 

[JC1]

Thanks Wwrithziden. I ran the default file type assoc., not sure if that's what solved the issue or not. I think what I did this time is rather than click of the zip file (which appears as a folder) itself, I clicked on 'my Documents' which has the file in it, and was able to upload this time.

So, the file is attached now (I think). Thanks. Any help in it's evaluation is appreciated. Again, I noticed my hard drive making sounds upon bootup today, so not sure if it's failing, but it did pass some of the HD tests I've put it through (Seagate short tests).

 

[writhziden]

Installed Antivirus:

ccsvchst.exe	c:\program files (x86)\norton internet security\engine\19.5.0.145\ccsvchst.exe	1068	8	1024	10240	2/22/2012 5:50 PM	11.2.0.9	135.01 KB (138,248 bytes)	1/31/2012 10:34 AM
ccsvchst.exe	c:\program files (x86)\norton internet security\engine\19.5.0.145\ccsvchst.exe	3780	8	1024	10240	2/22/2012 5:52 PM	11.2.0.9	135.01 KB (138,248 bytes)	1/31/2012 10:34 AM

Build:

6.1.7600 N/A Build 7600

[list=1]
[*]
Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [D:\Kingston\BSODDmpFiles\JC1\Windows_NT6_BSOD_jcgriff2\022212-43321-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16841.amd64fre.win7_gdr.110622-1503
Machine Name:
Kernel base = 0xfffff800`02c4f000 PsLoadedModuleList = 0xfffff800`02e8ce70
Debug session time: Wed Feb 22 17:40:40.825 2012 (UTC - 7:00)
System Uptime: 0 days 0:39:02.965
Loading Kernel Symbols
...............................................................
................................................................
..............................
Loading User Symbols
Loading unloaded module list
..........
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1E, {ffffffffc0000005, fffff80002fb43fa, 1, 18}

Probably caused by : ntkrnlmp.exe ( nt!ObpCreateHandle+29a )

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

4: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

KMODE_EXCEPTION_NOT_HANDLED (1e)
This is a very common bugcheck.  Usually the exception address pinpoints
the driver/function that caused the problem.  Always note this address
as well as the link date of the driver/image that contains this address.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff80002fb43fa, The address that the exception occurred at
Arg3: 0000000000000001, Parameter 0 of the exception
Arg4: 0000000000000018, Parameter 1 of the exception

Debugging Details:
------------------


EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

FAULTING_IP: 
nt!ObpCreateHandle+29a
fffff800`02fb43fa f0480fba6f1800  lock bts qword ptr [rdi+18h],0

EXCEPTION_PARAMETER1:  0000000000000001

EXCEPTION_PARAMETER2:  0000000000000018

WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff80002ef70e0
 0000000000000018 

ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

BUGCHECK_STR:  0x1E_c0000005

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  rundll32.exe

CURRENT_IRQL:  0

EXCEPTION_RECORD:  fffff880035852a8 -- (.exr 0xfffff880035852a8)
ExceptionAddress: fffff80002fb43fa (nt!ObpCreateHandle+0x000000000000029a)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000001
   Parameter[1]: 0000000000000018
Attempt to write to address 0000000000000018

TRAP_FRAME:  fffff88003585350 -- (.trap 0xfffff88003585350)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=fffffa800552b680
rdx=00000000000f001f rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002fb43fa rsp=fffff880035854e0 rbp=0000000000000000
 r8=fffff8a0033010f0  r9=00000000000000e8 r10=0000000000000000
r11=fffff8a0033010a0 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz ac po nc
nt!ObpCreateHandle+0x29a:
fffff800`02fb43fa f0480fba6f1800  lock bts qword ptr [rdi+18h],0 ds:00000000`00000018=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002cf9919 to fffff80002cbf5c0

STACK_TEXT:  
fffff880`03584ad8 fffff800`02cf9919 : 00000000`0000001e ffffffff`c0000005 fffff800`02fb43fa 00000000`00000001 : nt!KeBugCheckEx
fffff880`03584ae0 fffff800`02cbec02 : fffff880`035852a8 00000000`00000000 fffff880`03585350 fffffa80`0552b680 : nt!KiDispatchException+0x1b9
fffff880`03585170 fffff800`02cbd77a : 00000000`00000001 00000000`00000000 00000000`00000000 00000000`00000001 : nt!KiExceptionDispatch+0xc2
fffff880`03585350 fffff800`02fb43fa : 00000000`00000000 fffff880`03585530 fffffa80`0ab46060 fffff8a0`033010f0 : nt!KiPageFault+0x23a
fffff880`035854e0 fffff800`02facf1c : 00000000`00000000 fffff8a0`033010f0 00000000`000f001f fffff8a0`1221f000 : nt!ObpCreateHandle+0x29a
fffff880`035855f0 fffff800`02facd90 : fffffa80`05e0a170 fffff880`035859a0 fffffa80`06568c10 00000000`08000000 : nt!ObInsertObjectEx+0xec
fffff880`03585830 fffff800`02cbe813 : fffffa80`0552b680 fffff880`03585ad8 fffff880`035858c8 fffffa80`0aa8b280 : nt!NtCreateSection+0x1ef
fffff880`035858b0 fffff800`02cbadb0 : fffffa80`07264a76 fffff880`03585bc0 00000000`00000000 fffffa80`07268250 : nt!KiSystemServiceCopyEnd+0x13
fffff880`03585ab8 fffffa80`07264a76 : fffff880`03585bc0 00000000`00000000 fffffa80`07268250 fffffa80`0726b540 : nt!KiServiceLinkage
fffff880`03585ac0 fffff880`03585bc0 : 00000000`00000000 fffffa80`07268250 fffffa80`0726b540 fffffa80`00000002 : 0xfffffa80`07264a76
fffff880`03585ac8 00000000`00000000 : fffffa80`07268250 fffffa80`0726b540 fffffa80`00000002 00000000`08000000 : 0xfffff880`03585bc0


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!ObpCreateHandle+29a
fffff800`02fb43fa f0480fba6f1800  lock bts qword ptr [rdi+18h],0

SYMBOL_STACK_INDEX:  4

SYMBOL_NAME:  nt!ObpCreateHandle+29a

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4e02aa44

FAILURE_BUCKET_ID:  X64_0x1E_c0000005_nt!ObpCreateHandle+29a

BUCKET_ID:  X64_0x1E_c0000005_nt!ObpCreateHandle+29a

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

[*]
Loading Dump File [D:\Kingston\BSODDmpFiles\JC1\Windows_NT6_BSOD_jcgriff2\020812-30248-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16841.amd64fre.win7_gdr.110622-1503
Machine Name:
Kernel base = 0xfffff800`02c1f000 PsLoadedModuleList = 0xfffff800`02e5ce70
Debug session time: Wed Feb  8 13:52:38.685 2012 (UTC - 7:00)
System Uptime: 0 days 1:58:05.841
Loading Kernel Symbols
...............................................................
................................................................
................................
Loading User Symbols
Loading unloaded module list
.......
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 7A, {20, ffffffffc000009d, fffffa8006ee9078, 0}

Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+4c340 )

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

4: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

KERNEL_DATA_INPAGE_ERROR (7a)
The requested page of kernel data could not be read in.  Typically caused by
a bad block in the paging file or disk controller error. Also see
KERNEL_STACK_INPAGE_ERROR.
If the error status is 0xC000000E, 0xC000009C, 0xC000009D or 0xC0000185,
it means the disk subsystem has experienced a failure.
If the error status is 0xC000009A, then it means the request failed because
a filesystem failed to make forward progress.
Arguments:
Arg1: 0000000000000020, lock type that was held (value 1,2,3, or PTE address)
Arg2: ffffffffc000009d, error status (normally i/o status code)
Arg3: fffffa8006ee9078, current process (virtual address for lock type 3, or PTE)
Arg4: 0000000000000000, virtual address that could not be in-paged (or PTE contents if arg1 is a PTE address)

Debugging Details:
------------------


ERROR_CODE: (NTSTATUS) 0xc000009d - STATUS_DEVICE_NOT_CONNECTED

DISK_HARDWARE_ERROR: There was error with disk hardware

BUGCHECK_STR:  0x7a_c000009d

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  1

LAST_CONTROL_TRANSFER:  from fffff80002cc72dc to fffff80002c8f5c0

STACK_TEXT:  
fffff880`035d9a88 fffff800`02cc72dc : 00000000`0000007a 00000000`00000020 ffffffff`c000009d fffffa80`06ee9078 : nt!KeBugCheckEx
fffff880`035d9a90 fffff800`02c794f7 : fffffa80`06ee9010 00000000`c000009d 00000000`00000000 fffffa80`06ee90a8 : nt! ?? ::FNODOBFM::`string'+0x4c340
fffff880`035d9b50 fffff800`02c6c007 : fffffa80`05522b60 fffffa80`05522bb0 00000000`00000000 fffffa80`00000204 : nt!IopCompletePageWrite+0x57
fffff880`035d9b80 fffff800`02c968ed : fffffa80`05522b60 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDeliverApc+0x1d7
fffff880`035d9c00 fffff800`02cd6845 : 00000000`0000000c fffff880`009b7040 00000000`00000000 fffff800`02c299e0 : nt!KiCommitThreadWait+0x3dd
fffff880`035d9c90 fffff800`02c29a3a : fffffa80`05522b60 fffff880`00000008 00000000`00000001 fffffa80`054ef040 : nt!KeWaitForGate+0x101
fffff880`035d9ce0 fffff800`02f2f6fa : fffffa80`05522b60 4b744b74`5cd45cd4 00000000`00000080 00000000`00000001 : nt!MiModifiedPageWriter+0x5a
fffff880`035d9d40 fffff800`02c6db46 : fffff880`009b2180 fffffa80`05522b60 fffff880`009bd0c0 2e3f2e3f`c543c543 : nt!PspSystemThreadStartup+0x5a
fffff880`035d9d80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt! ?? ::FNODOBFM::`string'+4c340
fffff800`02cc72dc cc              int     3

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt! ?? ::FNODOBFM::`string'+4c340

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4e02aa44

FAILURE_BUCKET_ID:  X64_0x7a_c000009d_nt!_??_::FNODOBFM::_string_+4c340

BUCKET_ID:  X64_0x7a_c000009d_nt!_??_::FNODOBFM::_string_+4c340

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


[/list]

1. Possible causes are Memory problems... Viruses... Corrupted hard disk file system... Corrupted System Files... Lack of Windows updates... Drivers...
   Thanks to JMH for helping with my understanding of this crash.
2. Indicates there was a bad cluster on your hard disk.

We will start with the common problems first (see bold possible causes). Do the following steps and test after each step to see if stability increases. Post back your results after each step, and if you get a blue screen crash, upload the files again and await further instructions after we are able to analyze the crash.

• 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
  
  Run the hard disk diagnostics, preferably the long tests.
  
  
  
• Run http://www.sevenforums.com/tutorials/1538-sfc-scannow-command-system-file-checker.html up to three times to fix all errors. Post back if it continues to show errors after a fourth run or if the first run comes back with no integrity violations.
  
  
  
• Update to Service Pack 1 (SP1)
  
  Download Details - Microsoft Download Center - System Update Readiness Tool for Windows 7 (KB947821) [August 2011]
  
  Download Details - Microsoft Download Center - System Update Readiness Tool for Windows 7 for x64-based Systems (KB947821) [August 2011]
  
  Steps to follow before you install Windows 7 Service Pack 1 from the Microsoft Download Center
  
  Service Pack 1 Download site
  ​
  Links to Service Pack 1 (SP1) and preparation for SP1 courtesy of JMH

 

[JC1]

Chkdsk results

Thanks again for your time. I ran the long HD test from seagate, and no errors were reported. I also ran Chkdsk, and the results are below.

At this point, I think I'm going to do a complete reformat of the HD (delete everything), and reinstall the software. Then see if this stabilizes things. I don't believe this would fix any bad clusters on the HD (?), but atleast this might eliminate software / corrupted files /virus issues. Then if still getting errors, more likely a hardware issue. Hope you agree. I will post back once I've reformatted my drive and see if any changes occur. I appreciate your time reviewing.

Results of Chkdsk / Log file:

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)... 397824 file records processed. File verification completed. 712 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)... 465614 index entries processed. Index verification completed. 0 unindexed files scanned. 0 unindexed files recovered.

CHKDSK is verifying security descriptors (stage 3 of 5)... 397824 file SDs/SIDs processed. Cleaning up 2179 unused index entries from index $SII of file 0x9. Cleaning up 2179 unused index entries from index $SDH of file 0x9. Cleaning up 2179 unused security descriptors. CHKDSK is compacting the security descriptor stream 33896 data files processed. CHKDSK is verifying Usn Journal... 35160384 USN bytes processed. Usn Journal verification completed.

CHKDSK is verifying file data (stage 4 of 5)... 397808 files processed. File data verification completed.

CHKDSK is verifying free space (stage 5 of 5)... 150625811 free clusters processed. Free space verification is complete. CHKDSK discovered free space marked as allocated in the master file table (MFT) bitmap. Correcting errors in the Volume Bitmap. Windows has made corrections to the file system. 976657407 KB total disk space. 373406156 KB in 354424 files. 219140 KB in 33899 indexes. 0 KB in bad sectors. 528867 KB in use by the system. 65536 KB occupied by the log file. 602503244 KB available on disk. 4096 bytes in each allocation unit. 244164351 total allocation units on disk. 150625811 allocation units available on disk. Internal Info: 00 12 06 00 eb ec 05 00 04 42 0b 00 00 00 00 00 .........B...... 70 19 00 00 2c 00 00 00 00 00 00 00 00 00 00 00 p...,........... 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.

 

[writhziden]

Thanks again for your time. I ran the long HD test from seagate, and no errors were reported. I also ran Chkdsk, and the results are below.

At this point, I think I'm going to do a complete reformat of the HD (delete everything), and reinstall the software. Then see if this stabilizes things. I don't believe this would fix any bad clusters on the HD (?), but atleast this might eliminate software / corrupted files /virus issues. Then if still getting errors, more likely a hardware issue. Hope you agree. I will post back once I've reformatted my drive and see if any changes occur. I appreciate your time reviewing.

Results of Chkdsk / Log file:

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)... 397824 file records processed. File verification completed. 712 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)... 465614 index entries processed. Index verification completed. 0 unindexed files scanned. 0 unindexed files recovered.

CHKDSK is verifying security descriptors (stage 3 of 5)... 397824 file SDs/SIDs processed. Cleaning up 2179 unused index entries from index $SII of file 0x9. Cleaning up 2179 unused index entries from index $SDH of file 0x9. Cleaning up 2179 unused security descriptors. CHKDSK is compacting the security descriptor stream 33896 data files processed. CHKDSK is verifying Usn Journal... 35160384 USN bytes processed. Usn Journal verification completed.

CHKDSK is verifying file data (stage 4 of 5)... 397808 files processed. File data verification completed.

CHKDSK is verifying free space (stage 5 of 5)... 150625811 free clusters processed. Free space verification is complete. CHKDSK discovered free space marked as allocated in the master file table (MFT) bitmap. Correcting errors in the Volume Bitmap. Windows has made corrections to the file system. 976657407 KB total disk space. 373406156 KB in 354424 files. 219140 KB in 33899 indexes. 0 KB in bad sectors. 528867 KB in use by the system. 65536 KB occupied by the log file. 602503244 KB available on disk. 4096 bytes in each allocation unit. 244164351 total allocation units on disk. 150625811 allocation units available on disk. Internal Info: 00 12 06 00 eb ec 05 00 04 42 0b 00 00 00 00 00 .........B...... 70 19 00 00 2c 00 00 00 00 00 00 00 00 00 00 00 p...,........... 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.

Agreed, a reformat will remove all doubt and point to hardware if you still have crashes, but only if you do not install any other software or drivers after the re-install. Test for a while after re-installing Windows without installing any other software, updates, or drivers. You can install Microsoft Security Essentials - Free Antivirus for Windows if you want antivirus protection that is known not to cause crashes.

Then install software and drivers in clusters, but create a restore point before each cluster. That way, if one cluster causes a crash, you can revert to the restore point and then install things one at a time within that cluster to determine which installation caused the crash. Start by installing one driver at a time with a restore point before each, then do clusters of Windows updates (5 or 10 updates at a time with a restore point before each), and finally do one program at a time starting with the programs you use the most and create a restore point before each program is installed.


How did things go after the reformat?

 

[JC1]

Thanks for asking, I was about to add a new post.

I think it 'cleaned up' some of the issues, and I may be down to the root of the issue. I reinstalled Windows, and a few critical apps (MS office, Adobe photoshop, and I tunes . Everything ran fine for awhile, booted up quicker, etc.

However, I did run into another BSOD. This was after I re-installed a game (Battlefield 3), and ran it. It runs well most of the times, but 2-3 times, I got the BSOD, and the following error:

Stop Error: 00000000000101, "Clock interupt on secondary processor not received within allocated time interval".

This is the original error I kept getting before I ran into other issues (which I think were cleaned up by reformatting). So, the crux of the issue is related to the error above. I think I've read this may be a CPU or possibly GPU issue? Again, I have a intel I-7 Quad core processor, and a 9800 GT video card. Not sure where to go from here...

 

[JC1]

I should add, this processor has 'Turboboost' which is essentially automatic overclocking up to I believe around 20%. I'm sure it will be suggested to disable it - but wanted to mention it for full disclosure.

 

[writhziden]

Can you upload the crash reports? 0x101 is occasionally caused by driver faults, as well. Usually it is hardware as you said, but it can also be an underlying driver conflict.

 

[JC1]

Attached is the jcgriff zipped file (hopefully with everything you need to analyze) and a new performance report. I'll add after2-3 BSOD's, the computer locked up once or twice and I shut it down hard, so that might have generated a crash report as well. Look forward to your next comments.

 

[writhziden]

Problem Devices:

WD SES Device USB Device	USBSTOR\OTHER&VEN_WD&PROD_SES_DEVICE&REV_1003\575844314139315439333534&1	The drivers for this device are not installed.
Not Available	ACPI\ATK0110\1010110	The drivers for this device are not installed.
psc 2500 series	ROOT\MULTIFUNCTION\0000	This device is disabled.

Security Software:

ccsvchst.exe	c:\program files (x86)\norton internet security\engine\19.6.1.8\ccsvchst.exe	1656	8	1024	10240	3/20/2012 10:22 AM	11.2.1.4	134.99 KB (138,232 bytes)	3/8/2012 9:15 PM
ccsvchst.exe	c:\program files (x86)\norton internet security\engine\19.6.1.8\ccsvchst.exe	2528	8	1024	10240	3/20/2012 10:22 AM	11.2.1.4	134.99 KB (138,232 bytes)	3/8/2012 9:15 PM
[code]


The .dmp file was corrupted... It was: [url]http://www.sevenforums.com/crash-lockup-debug-how/63501-stop-0x101-clock_watchdog_timeout-troubleshtg.html[/url] as you said, but beyond that, I could not determine anything useful from it. I would suggest turning off all overclocking and setting all hardware to stable default settings (this does include disabling turboboost).


Due to the corrupted .dmp file, check for data corruption:[list][*]Run [url=http://www.sevenforums.com/tutorials/433-disk-check.html]Disk Check[/url] 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 [url]http://www.sevenforums.com/tutorials/96938-check-disk-chkdsk-read-event-viewer-log.html[/url]. 
For any drives that do not give the message: 
[COLOR="Blue"]Windows has checked the file system and found no problems[/COLOR]
run disk check again as above. In other words, if it says: 
[COLOR="Red"]Windows has made corrections to the file system[/COLOR]
after running the disk check, run the disk check again.


[*]Run [url]http://www.sevenforums.com/tutorials/1538-sfc-scannow-command-system-file-checker.html[/url] up to [B]three times[/B] 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. [/list]