Blue Screen 2057 Crashing

No dump file there - JCGriff still running really slowly too...checked dump settings and they are as you instructed so can't see why no dump file is there - do you need the JCGriff file?

Here's the file anyway - about to give up to be honest. May just format hard drive and reinstall. What do you think?

Thanks Wish, will give it a go and see what happens. See you when I'm done!

Hi Wish

I have formatted and partitioned my hard drive and totally reinstalled Windows 7. It didn't go smoothly and initially failed saying it couldn't find files. However, I tried again and it seems to have worked. There were no CHKDSK's when I rebooted and so far it looks to have solved the problems. However, the failure during the install process stills causes concern for me regarding the state of the HDD hardware itself. I'll therefore get the Dell technician out to check it over anyway this week as planned and if there is a hardware problem he can identify it and replace the faulty hardware.

For now, (about 30 minutes at least) all seems to be working ok...will put some basic software on here and see what happens.

Thanks for your help so far and I'll keep this updated.

James

mta00jtl said:

Hi there, I'm new to these forums but it seems to be the place to get some useful answers to Windows 7 problems. And I have a pretty big one at the moment!

I have experienced the Blue Screen crash on loading up my computer in the last couple of days - it is an intermittent problem too so I've been able to restart ok a few times but then other times not. It first happened 2 days ago when I was actually flying on Microsoft FSX and the computer just shut down (maybe overheated??) and came back up with a BSOD. Since then I have totally removed FSX (it was causing all sorts of issues suddenly) but the Blue Screen has been returning forcing me to restart my computer. Just so you also know on restart when it tries to run CHKDSK it fails - I didn't catch the error message but it certainly didn't work.

Blue screen error message below:

Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7600.2.0.0.768.3
Locale ID: 2057


Additional information about the problem:
BCCode: 6b
BCP1: 0000000000000000
BCP2: 0000000000000000
BCP3: 0000000000000000
BCP4: 0000000000000000
OS Version: 6_1_7600
Service Pack: 0_0
Product: 768_1


Files that help describe the problem:
C:\Windows\Minidump\111110-48500-01.dmp
C:\Users\James Long\AppData\Local\Temp\WER-76206-0.sysdata.xml


Read our privacy statement online:
Windows 7 Privacy Statement - Microsoft Windows


If the online privacy statement is not available, please read our privacy statement offline:
C:\Windows\system32\en-US\erofflps.txt

I've seen a couple of posts on this forum with a similar line of messages but whilst I'm ok with computers, I've found some of the solutions well beyond my capabilities to understand! I'd therefore really appreciate someone giving me any assistance they can and if possible putting things in laymans terms! My computer specs should be on my profile but if not they are:

Dell XPS 435T with Intel Core i7 920 @2.67Ghz
12GB RAM
Windows 7 Home Premium 64 bit
ATI Radeon 5800 Series (driver updated yesterday)
1TB Seagate Hard Disk

Any help much appreciated! Many thanks in advance

James

PS Just read the instructions for posting on BSOD (sorry I'm a newbie) and I've attached the requested files/reports now too. Also, bit more system info:

• Windows 7 - now my Program Files says x86 but I thought mine was a 64bit system (it says it is when I find out what version I'm using)...maybe you can tell me more
• It's the original version that was pre-installed on the system OEM
• System is about 1 year old
• OS never reinstalled

Hi and welcome

The cause of these is indeed your HD. I would run a check disk and backup the data to a safe place


CHKDSK /R /F:
Run CHKDSK /R /F from an elevated (Run as adminstrator) Command Prompt. Please do this for each hard drive on your system.
When it tells you it can't do it right now - and asks you if you'd like to do it at the next reboot - answer Y (for Yes) and press Enter. Then reboot and let the test run. It may take a while for it to run, but keep an occasional eye on it to see if it generates any errors. See "CHKDSK LogFile" below in order to check the results of the test.

Elevated Command Prompt:
Go to Start and type in "cmd.exe" (without the quotes)
At the top of the Search Box, right click on Cmd.exe and select "Run as administrator"

CHKDSK LogFile:
Go to Start and type in "eventvwr.msc" (without the quotes) and press Enter
Expand the Windows logs heading, then select the Application log file entry.
Double click on the Source column header.
Scroll down the list until you find the Chkdsk entry (wininit for Win7) (winlogon for XP).
Copy/paste the results into your next post.

Code:

Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\K\Desktop\Windows_NT6_BSOD_jcgriff2\111110-28204-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;srv*e:\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.16617.amd64fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0xfffff800`02e56000 PsLoadedModuleList = 0xfffff800`03093e50
Debug session time: Wed Nov 10 19:22:53.519 2010 (GMT-5)
System Uptime: 0 days 0:00:18.423
Loading Kernel Symbols
.................................................
Loading User Symbols
Loading unloaded module list
..
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000007E, {ffffffffc0000006, fffff80002f5b4f3, fffff880009a97f8, fffff880009a9060}

Probably caused by : hardware_disk

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

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

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
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.
Some common problems are exception code 0x80000003.  This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG.  This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG.  This will let us see why this breakpoint is
happening.
Arguments:
Arg1: ffffffffc0000006, The exception code that was not handled
Arg2: fffff80002f5b4f3, The address that the exception occurred at
Arg3: fffff880009a97f8, Exception Record Address
Arg4: fffff880009a9060, Context Record Address

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


EXCEPTION_CODE: (NTSTATUS) 0xc0000006 - The instruction at 0x%p referenced memory at 0x%p. The required data was not placed into memory because of an I/O error status of 0x%x.

FAULTING_IP: 
nt!_report_gsfailure+53
fffff800`02f5b4f3 438b1491        mov     edx,dword ptr [r9+r10*4]

EXCEPTION_RECORD:  fffff880009a97f8 -- (.exr 0xfffff880009a97f8)
ExceptionAddress: fffff80002f5b4f3 (nt!_report_gsfailure+0x0000000000000053)
   ExceptionCode: c0000006 (In-page I/O error)
  ExceptionFlags: 00000000
NumberParameters: 3
   Parameter[0]: 0000000000000000
   Parameter[1]: 0000000077503168
   Parameter[2]: 00000000c0000428
Inpage operation failed at 0000000077503168, due to I/O error 00000000c0000428

CONTEXT:  fffff880009a9060 -- (.cxr 0xfffff880009a9060)
rax=fffff800033a2ab8 rbx=00000000774f0000 rcx=fffff800033a2ab8
rdx=00000000774f0000 rsi=fffff880009a9ad0 rdi=fffff800033a2ab8
rip=fffff80002f5b4f3 rsp=fffff880009a9a38 rbp=fffff800033a2ab8
 r8=00000000000007e7  r9=000000007750219c r10=00000000000003f3
r11=0000000077504138 r12=fffff80003391800 r13=0000000000000000
r14=0000000000000007 r15=0000000000000002
iopl=0         nv up ei pl nz na po cy
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010207
nt!_report_gsfailure+0x53:
fffff800`02f5b4f3 438b1491        mov     edx,dword ptr [r9+r10*4] ds:002b:00000000`77503168=????????
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  0

ERROR_CODE: (NTSTATUS) 0xc0000006 - The instruction at 0x%p referenced memory at 0x%p. The required data was not placed into memory because of an I/O error status of 0x%x.

EXCEPTION_PARAMETER1:  0000000000000000

EXCEPTION_PARAMETER2:  0000000077503168

EXCEPTION_PARAMETER3:  00000000c0000428

IO_ERROR: (NTSTATUS) 0xc0000428 - Windows cannot verify the digital signature for this file. A recent hardware or software change might have installed a file that is signed incorrectly or damaged, or that might be malicious software from an unknown source.

BUGCHECK_STR:  0x7E

EXCEPTION_STR:  0xc0000006_c0000428

FOLLOWUP_IP: 
+5185952f035bdc40
00000000`77503168 ??              ???

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: hardware_disk

IMAGE_NAME:  hardware_disk

DEBUG_FLR_IMAGE_TIMESTAMP:  0

STACK_COMMAND:  kb

FAILURE_BUCKET_ID:  X64_0x7E_IMAGE_hardware_disk

BUCKET_ID:  X64_0x7E_IMAGE_hardware_disk

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

Then I would update the below drivers


Old Drivers

Code:

OA002Afx.sys        fffff880`02ba7f80    0x00033f80    6/8/2007 03:00:36            0x46690ca4    fffff880`02b74000                
SaiH0BAC.sys        fffff880`02bd1b00    0x00029b00    7/2/2007 04:25:35            0x4688c48f    fffff880`02ba8000                
SaiH0763.sys        fffff880`067f4380    0x0002a380    2/15/2008 08:15:05            0x47b59059    fffff880`067ca000                
OA002Ufd.sys        fffff880`02b483a0    0x000293a0    6/3/2008 04:30:37            0x48450f3d    fffff880`02b1f000                
adfs.SYS        fffff880`0774b000    0x00018000    6/26/2008 15:52:37            0x48640195    fffff880`07733000                
OA002Vid.sys        fffff880`02b1ed80    0x0004ad80    8/1/2008 04:34:52            0x4892d8bc    fffff880`02ad4000                
spldr.sys        fffff880`01654000    0x00008000    5/11/2009 11:56:27            0x4a0858bb    fffff880`0164c000

How To Find Drivers:

- search Google for the name of the driver
- compare the Google results with what's installed on your system to figure out which device/program it belongs to
- visit the web site of the manufacturer of the hardware/program to get the latest drivers (DON'T use Windows Update or the Update driver function of Device Manager).
- if there are difficulties in locating them, post back with questions and someone will try and help you locate the appropriate program.

- - The most common drivers are listed on this page: Driver Reference
- - Driver manufacturer links are on this page: Drivers and Downloads

Hi there Zig Zag

Thank you for your input. I've actually done a full reinstall of my Windows 7 software - it hasn't asked me to do a CHKDSK since I've done this and I have rebooted a couple of times. I'm still a bit nervous about the BSODs I've been having so will run a CHKDSK anyway on next start up and see what it says - I'll post the responses on here. It does (touchwood) seem to be working again which makes me think it's either faulty/conflicting drivers (which I've now got rid of) or the HD itself being faulty. If it's the latter then I'll have a technician here in the next couple of days and get it replaced.

Thanks for your help, will post my CHKDSK results shortly and you can let me know your thoughts.

James

Hi guys

CHKDSK has finally finished. Just to let you know, the first time I rebooted, CHKDSK froze at the following message for more than 10 minutes forcing me to hard restart the computer:

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

A disk check has been scheduled.
To skip disk checking, press any key within 1 second(s).

It literally sat like this for ages making me wonder if there is a serious problem with the HDD. After hard restarting (pushing power button for a few seconds) CHKDSK performed normally and found no problems as below:

Log Name: Application
Source: Microsoft-Windows-Wininit
Date: 14/11/2010 22:01:50
Event ID: 1001
Task Category: None
Level: Information
Keywords: Classic
User: N/A
Computer: My-PC
Description:


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)...
60416 file records processed.

File verification completed.
265 large file records processed.

0 bad file records processed.

0 EA records processed.

44 reparse records processed.

CHKDSK is verifying indexes (stage 2 of 5)...
88288 index entries processed.

Index verification completed.
0 unindexed files scanned.

0 unindexed files recovered.

CHKDSK is verifying security descriptors (stage 3 of 5)...
60416 file SDs/SIDs processed.

Cleaning up 149 unused index entries from index $SII of file 0x9.
Cleaning up 149 unused index entries from index $SDH of file 0x9.
Cleaning up 149 unused security descriptors.
Security descriptor verification completed.
13937 data files processed.

CHKDSK is verifying Usn Journal...
9676688 USN bytes processed.

Usn Journal verification completed.
CHKDSK is verifying file data (stage 4 of 5)...
60400 files processed.

File data verification completed.
CHKDSK is verifying free space (stage 5 of 5)...
235583189 free clusters processed.

Free space verification is complete.
Windows has checked the file system and found no problems.

976657407 KB total disk space.
34122228 KB in 45903 files.
36168 KB in 13938 indexes.
0 KB in bad sectors.
166251 KB in use by the system.
65536 KB occupied by the log file.
942332760 KB available on disk.

4096 bytes in each allocation unit.
244164351 total allocation units on disk.
235583190 allocation units available on disk.

Internal Info:
00 ec 00 00 cd e9 00 00 8c e1 01 00 00 00 00 00 ................
7f 00 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.

Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Microsoft-Windows-Wininit" Guid="{206f6dea-d3c5-4d10-bc72-989f03c8b84b}" EventSourceName="Wininit" />
<EventID Qualifiers="16384">1001</EventID>
<Version>0</Version>
<Level>4</Level>
<Task>0</Task>
<Opcode>0</Opcode>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2010-11-14T14:01:50.000000000Z" />
<EventRecordID>270</EventRecordID>
<Correlation />
<Execution ProcessID="0" ThreadID="0" />
<Channel>Application</Channel>
<Computer>JamesLong-PC</Computer>
<Security />
</System>
<EventData>
<Data>

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)...
60416 file records processed.

File verification completed.
265 large file records processed.

0 bad file records processed.

0 EA records processed.

44 reparse records processed.

CHKDSK is verifying indexes (stage 2 of 5)...
88288 index entries processed.

Index verification completed.
0 unindexed files scanned.

0 unindexed files recovered.

CHKDSK is verifying security descriptors (stage 3 of 5)...
60416 file SDs/SIDs processed.

Cleaning up 149 unused index entries from index $SII of file 0x9.
Cleaning up 149 unused index entries from index $SDH of file 0x9.
Cleaning up 149 unused security descriptors.
Security descriptor verification completed.
13937 data files processed.

CHKDSK is verifying Usn Journal...
9676688 USN bytes processed.

Usn Journal verification completed.
CHKDSK is verifying file data (stage 4 of 5)...
60400 files processed.

File data verification completed.
CHKDSK is verifying free space (stage 5 of 5)...
235583189 free clusters processed.

Free space verification is complete.
Windows has checked the file system and found no problems.

976657407 KB total disk space.
34122228 KB in 45903 files.
36168 KB in 13938 indexes.
0 KB in bad sectors.
166251 KB in use by the system.
65536 KB occupied by the log file.
942332760 KB available on disk.

4096 bytes in each allocation unit.
244164351 total allocation units on disk.
235583190 allocation units available on disk.

Internal Info:
00 ec 00 00 cd e9 00 00 8c e1 01 00 00 00 00 00 ................
7f 00 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.
</Data>
</EventData>
</Event>

Do you have any thoughts on the above? Does the first failure of CHKDSK indicate hard disk problems still? If so do they seem intermittent?

As it is, Windows seems to be working ok - I should have a Dell technician here in the next couple of days - what do you advise I ask him to check specifically based on the info in the thread so far? Should I just get the HD replaced anyway to be safe?

As always, your thoughts and advice is hugely appreciated - this has been a bit of a saga but I feeling we're nearing the end (even if the end means dunking this stupid HD into my bath to "fix it" once and for all!)

James

Hi Wish

Perhaps I could just ask a last opinion based on my latest updates. Since the reinstall all seems to be working ok - it's much quicker.

Did the CHKDSK info yesterday reveal anything to you? Also I'm getting the Dell technician in tomorrow and tempted to just ask him to replace my HD to be on the safe side. Would you say this is worthwhile based on my experiences?

Thanks and look forward to hearing from you.

James