Go Back   Hardware Canucks > PC BUILDERS & TWEAKERS CORNER > Troubleshooting

    
Reply
 
LinkBack Thread Tools Display Modes
  #1 (permalink)  
Old December 6, 2011, 04:00 PM
ern88's Avatar
MVP
 
Join Date: Jan 2011
Location: Halifax, Nova Scotia
Posts: 275

My System Specs

Default Odd BSOD. Anyone help me?

Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64

Copyright (c) Microsoft Corporation. All rights reserved.





Loading Dump File [C:\Users\Ernie\Dump folder\120411-28282-01.dmp]

Mini Kernel Dump File: Only registers and stack trace are available



Symbol search path is: *** Invalid ***

************************************************** **************************

* Symbol loading may be unreliable without a symbol search path. *

* Use .symfix to have the debugger choose a symbol path. *

* After setting your symbol path, use .reload to refresh symbol locations. *

************************************************** **************************

Executable search path is:

************************************************** *******************

* Symbols can not be loaded because symbol path is not initialized. *

* *

* The Symbol Path can be set by: *

* using the _NT_SYMBOL_PATH environment variable. *

* using the -y argument when starting the debugger. *

* using .sympath and .sympath+ *

************************************************** *******************

Unable to load image ntoskrnl.exe, Win32 error 0n2

*** WARNING: Unable to verify timestamp for ntoskrnl.exe

*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe

Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64

Product: WinNt, suite: TerminalServer SingleUserTS

Machine Name:

Kernel base = 0xfffff800`0300a000 PsLoadedModuleList = 0xfffff800`0324f670

Debug session time: Sun Dec 4 01:19:13.906 2011 (UTC - 4:00)

System Uptime: 0 days 1:22:15.092

************************************************** *******************

* Symbols can not be loaded because symbol path is not initialized. *

* *

* The Symbol Path can be set by: *

* using the _NT_SYMBOL_PATH environment variable. *

* using the -y argument when starting the debugger. *

* using .sympath and .sympath+ *

************************************************** *******************

Unable to load image ntoskrnl.exe, Win32 error 0n2

*** WARNING: Unable to verify timestamp for ntoskrnl.exe

*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe

Loading Kernel Symbols

.................................................. .............

.................................................. ..............

............................................

Loading User Symbols

Loading unloaded module list

.....

************************************************** *****************************

* *

* Bugcheck Analysis *

* *

************************************************** *****************************



Use !analyze -v to get detailed debugging information.



BugCheck 7A, {fffff6fc400085f0, ffffffffc0000185, 10d971860, fffff880010be93c}



*** WARNING: Unable to verify timestamp for mssmbios.sys

*** ERROR: Module load completed but symbols could not be loaded for mssmbios.sys

Unable to load image ataport.SYS, Win32 error 0n2

*** WARNING: Unable to verify timestamp for ataport.SYS

*** ERROR: Module load completed but symbols could not be loaded for ataport.SYS

***** Kernel symbols are WRONG. Please fix symbols to do analysis.



************************************************** ***********************

*** ***

*** ***

*** Your debugger is not using the correct symbols ***

*** ***

*** In order for this command to work properly, your symbol path ***

*** must point to .pdb files that have full type information. ***

*** ***

*** Certain .pdb files (such as the public OS symbols) do not ***

*** contain the required information. Contact the group that ***

*** provided you with these symbols if you need this command to ***

*** work. ***

*** ***

*** Type referenced: nt!_KPRCB ***

*** ***

************************************************** ***********************

************************************************** ***********************

*** ***

*** ***

*** Your debugger is not using the correct symbols ***

*** ***

*** In order for this command to work properly, your symbol path ***

*** must point to .pdb files that have full type information. ***

*** ***

*** Certain .pdb files (such as the public OS symbols) do not ***

*** contain the required information. Contact the group that ***

*** provided you with these symbols if you need this command to ***

*** work. ***

*** ***

*** Type referenced: nt!_KPRCB ***

*** ***

************************************************** ***********************

************************************************** ***********************

*** ***

*** ***

*** Your debugger is not using the correct symbols ***

*** ***

*** In order for this command to work properly, your symbol path ***

*** must point to .pdb files that have full type information. ***

*** ***

*** Certain .pdb files (such as the public OS symbols) do not ***

*** contain the required information. Contact the group that ***

*** provided you with these symbols if you need this command to ***

*** work. ***

*** ***

*** Type referenced: nt!_KPRCB ***

*** ***

************************************************** ***********************

Probably caused by : ataport.SYS ( ataport+1e93c )



Followup: MachineOwner

---------



3: 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: fffff6fc400085f0, lock type that was held (value 1,2,3, or PTE address)

Arg2: ffffffffc0000185, error status (normally i/o status code)

Arg3: 000000010d971860, current process (virtual address for lock type 3, or PTE)

Arg4: fffff880010be93c, virtual address that could not be in-paged (or PTE contents if arg1 is a PTE address)



Debugging Details:

------------------



***** Kernel symbols are WRONG. Please fix symbols to do analysis.



************************************************** ***********************

*** ***

*** ***

*** Your debugger is not using the correct symbols ***

*** ***

*** In order for this command to work properly, your symbol path ***

*** must point to .pdb files that have full type information. ***

*** ***

*** Certain .pdb files (such as the public OS symbols) do not ***

*** contain the required information. Contact the group that ***

*** provided you with these symbols if you need this command to ***

*** work. ***

*** ***

*** Type referenced: nt!_KPRCB ***

*** ***

************************************************** ***********************

************************************************** ***********************

*** ***

*** ***

*** Your debugger is not using the correct symbols ***

*** ***

*** In order for this command to work properly, your symbol path ***

*** must point to .pdb files that have full type information. ***

*** ***

*** Certain .pdb files (such as the public OS symbols) do not ***

*** contain the required information. Contact the group that ***

*** provided you with these symbols if you need this command to ***

*** work. ***

*** ***

*** Type referenced: nt!_KPRCB ***

*** ***

************************************************** ***********************

************************************************** ***********************

*** ***

*** ***

*** Your debugger is not using the correct symbols ***

*** ***

*** In order for this command to work properly, your symbol path ***

*** must point to .pdb files that have full type information. ***

*** ***

*** Certain .pdb files (such as the public OS symbols) do not ***

*** contain the required information. Contact the group that ***

*** provided you with these symbols if you need this command to ***

*** work. ***

*** ***

*** Type referenced: nt!_KPRCB ***

*** ***

************************************************** ***********************



ADDITIONAL_DEBUG_TEXT:

Use '!findthebuild' command to search for the target build information.

If the build information is available, run '!findthebuild -s ; .reload' to set symbol path and load symbols.



MODULE_NAME: ataport



FAULTING_MODULE: fffff8000300a000 nt



DEBUG_FLR_IMAGE_TIMESTAMP: 4ce79293



ERROR_CODE: (NTSTATUS) 0xc0000185 - The I/O device reported an I/O error.



DISK_HARDWARE_ERROR: There was error with disk hardware



BUGCHECK_STR: 0x7a_c0000185



CUSTOMER_CRASH_COUNT: 1



DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT



CURRENT_IRQL: 0



LAST_CONTROL_TRANSFER: from fffff800030f7b52 to fffff80003086c40



STACK_TEXT:

fffff880`031a81c8 fffff800`030f7b52 : 00000000`0000007a fffff6fc`400085f0 ffffffff`c0000185 00000001`0d971860 : nt+0x7cc40

fffff880`031a81d0 00000000`0000007a : fffff6fc`400085f0 ffffffff`c0000185 00000001`0d971860 fffff880`010be93c : nt+0xedb52

fffff880`031a81d8 fffff6fc`400085f0 : ffffffff`c0000185 00000001`0d971860 fffff880`010be93c fffffa80`0b157bf0 : 0x7a

fffff880`031a81e0 ffffffff`c0000185 : 00000001`0d971860 fffff880`010be93c fffffa80`0b157bf0 00000000`c0000185 : 0xfffff6fc`400085f0

fffff880`031a81e8 00000001`0d971860 : fffff880`010be93c fffffa80`0b157bf0 00000000`c0000185 fffffa80`00000000 : 0xffffffff`c0000185

fffff880`031a81f0 fffff880`010be93c : fffffa80`0b157bf0 00000000`c0000185 fffffa80`00000000 fffff880`010be93c : 0x1`0d971860

fffff880`031a81f8 fffffa80`0b157bf0 : 00000000`c0000185 fffffa80`00000000 fffff880`010be93c fffff800`030aebc5 : ataport+0x1e93c

fffff880`031a8200 00000000`c0000185 : fffffa80`00000000 fffff880`010be93c fffff800`030aebc5 fffffa80`0b157cc0 : 0xfffffa80`0b157bf0

fffff880`031a8208 fffffa80`00000000 : fffff880`010be93c fffff800`030aebc5 fffffa80`0b157cc0 fffffa80`0b157cc0 : 0xc0000185

fffff880`031a8210 fffff880`010be93c : fffff800`030aebc5 fffffa80`0b157cc0 fffffa80`0b157cc0 fffffa80`06d2e680 : 0xfffffa80`00000000

fffff880`031a8218 fffff800`030aebc5 : fffffa80`0b157cc0 fffffa80`0b157cc0 fffffa80`06d2e680 fffffa80`0328c530 : ataport+0x1e93c

fffff880`031a8220 fffffa80`0b157cc0 : fffffa80`0b157cc0 fffffa80`06d2e680 fffffa80`0328c530 00000000`00002000 : nt+0xa4bc5

fffff880`031a8228 fffffa80`0b157cc0 : fffffa80`06d2e680 fffffa80`0328c530 00000000`00002000 fffff6fc`400085f0 : 0xfffffa80`0b157cc0

fffff880`031a8230 fffffa80`06d2e680 : fffffa80`0328c530 00000000`00002000 fffff6fc`400085f0 ffffffff`ffffffff : 0xfffffa80`0b157cc0

fffff880`031a8238 fffffa80`0328c530 : 00000000`00002000 fffff6fc`400085f0 ffffffff`ffffffff 00000000`00000000 : 0xfffffa80`06d2e680

fffff880`031a8240 00000000`00002000 : fffff6fc`400085f0 ffffffff`ffffffff 00000000`00000000 00000000`00000000 : 0xfffffa80`0328c530

fffff880`031a8248 fffff6fc`400085f0 : ffffffff`ffffffff 00000000`00000000 00000000`00000000 fffffa80`06d18820 : 0x2000

fffff880`031a8250 ffffffff`ffffffff : 00000000`00000000 00000000`00000000 fffffa80`06d18820 fffff800`032bc500 : 0xfffff6fc`400085f0

fffff880`031a8258 00000000`00000000 : 00000000`00000000 fffffa80`06d18820 fffff800`032bc500 fffffa80`0328c530 : 0xffffffff`ffffffff





STACK_COMMAND: kb



FOLLOWUP_IP:

ataport+1e93c

fffff880`010be93c ?? ???



SYMBOL_STACK_INDEX: 6



SYMBOL_NAME: ataport+1e93c



FOLLOWUP_NAME: MachineOwner



IMAGE_NAME: ataport.SYS



BUCKET_ID: WRONG_SYMBOLS



Followup: MachineOwner

---------



3: kd> lmvm ataport

start end module name

fffff880`010a0000 fffff880`010ca000 ataport T (no symbols)

Loaded symbol image file: ataport.SYS

Image path: ataport.SYS

Image name: ataport.SYS

Timestamp: Sat Nov 20 05:19:15 2010 (4CE79293)

CheckSum: 000287EF

ImageSize: 0002A000

Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4

3: kd> lmvm nt

start end module name

fffff800`0300a000 fffff800`035f3000 nt T (no symbols)

Loaded symbol image file: ntoskrnl.exe

Image path: ntoskrnl.exe

Image name: ntoskrnl.exe

Timestamp: Wed Jun 22 23:53:23 2011 (4E02AAA3)

CheckSum: 0055C228

ImageSize: 005E9000

Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4

I also completed a scan disk with these results:

CHKDSK is verifying files (stage 1 of 5)...

220160 file records processed.



File verification completed.

386 large file records processed.



0 bad file records processed.



2 EA records processed.



92 reparse records processed.



CHKDSK is verifying indexes (stage 2 of 5)...

282154 index entries processed.



Index verification completed.

0 unindexed files scanned.



0 unindexed files recovered.



CHKDSK is verifying security descriptors (stage 3 of 5)...

220160 file SDs/SIDs processed.



Cleaning up 467 unused index entries from index $SII of file 0x9.

Cleaning up 467 unused index entries from index $SDH of file 0x9.

Cleaning up 467 unused security descriptors.

Security descriptor verification completed.

30998 data files processed.



CHKDSK is verifying Usn Journal...

33836832 USN bytes processed.



Usn Journal verification completed.

CHKDSK is verifying file data (stage 4 of 5)...

220144 files processed.



File data verification completed.

CHKDSK is verifying free space (stage 5 of 5)...

87908547 free clusters processed.



Free space verification is complete.

CHKDSK discovered free space marked as allocated in the

master file table (MFT) bitmap.

CHKDSK discovered free space marked as allocated in the volume bitmap.

Windows has made corrections to the file system.



488282111 KB total disk space.

136212344 KB in 178386 files.

100584 KB in 30999 indexes.

0 KB in bad sectors.

334991 KB in use by the system.

65536 KB occupied by the log file.

351634192 KB available on disk.



4096 bytes in each allocation unit.

122070527 total allocation units on disk.

87908548 allocation units available on disk.



Internal Info:

00 5c 03 00 f4 31 03 00 24 5f 05 00 00 00 00 00 .\...1..$_......

de 72 00 00 5c 00 00 00 00 00 00 00 00 00 00 00 .r..\...........

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:







1001

0

4

0

0

0x80000000000000



4360





Application













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)...

220160 file records processed.



File verification completed.

386 large file records processed.



0 bad file records processed.



2 EA records processed.



92 reparse records processed.



CHKDSK is verifying indexes (stage 2 of 5)...

282154 index entries processed.



Index verification completed.

0 unindexed files scanned.



0 unindexed files recovered.



CHKDSK is verifying security descriptors (stage 3 of 5)...

220160 file SDs/SIDs processed.



Cleaning up 467 unused index entries from index $SII of file 0x9.

Cleaning up 467 unused index entries from index $SDH of file 0x9.

Cleaning up 467 unused security descriptors.

Security descriptor verification completed.

30998 data files processed.



CHKDSK is verifying Usn Journal...

33836832 USN bytes processed.



Usn Journal verification completed.

CHKDSK is verifying file data (stage 4 of 5)...

220144 files processed.



File data verification completed.

CHKDSK is verifying free space (stage 5 of 5)...

87908547 free clusters processed.



Free space verification is complete.

CHKDSK discovered free space marked as allocated in the

master file table (MFT) bitmap.

CHKDSK discovered free space marked as allocated in the volume bitmap.

Windows has made corrections to the file system.



488282111 KB total disk space.

136212344 KB in 178386 files.

100584 KB in 30999 indexes.

0 KB in bad sectors.

334991 KB in use by the system.

65536 KB occupied by the log file.

351634192 KB available on disk.



4096 bytes in each allocation unit.

122070527 total allocation units on disk.

87908548 allocation units available on disk.



Internal Info:

00 5c 03 00 f4 31 03 00 24 5f 05 00 00 00 00 00 .\...1..$_......

de 72 00 00 5c 00 00 00 00 00 00 00 00 00 00 00 .r..\...........

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.


Thanks for the help!!!!
Reply With Quote
  #2 (permalink)  
Old December 6, 2011, 04:31 PM
Killswitch's Avatar
Allstar
 
Join Date: Sep 2007
Location: Sault Ste Marie, Ontario
Posts: 839

My System Specs

Default

I'll admit, I can't make heads or tails out of any of that. haha
If your CPU is overclocked I would start there. I've had BSOD's during gaming which pointed to memory and video card drivers when meanwhile it was an unstable CPU.

Just a thought. Take it with a grain of salt. :)
Reply With Quote
  #3 (permalink)  
Old December 6, 2011, 04:41 PM
Hall Of Fame
 
Join Date: Apr 2009
Location: laval Qc
Posts: 1,072
Default

harware specs?
overclocked?
__________________
maximus IV extreme @ 5.1 1.41v

evga e760 +920 4.8 water5.0+ on phase linx stable
gtx285 tri-sli
dfi ut-p35 lt
e8600@4.6 1.38v
too much ram
Reply With Quote
  #4 (permalink)  
Old December 6, 2011, 04:49 PM
Killswitch's Avatar
Allstar
 
Join Date: Sep 2007
Location: Sault Ste Marie, Ontario
Posts: 839

My System Specs

Default

Quote:
Originally Posted by zsamz_ View Post
harware specs?
overclocked?
Specs are in his drop down menu thingy.... and I beat you to the OC question.
Reply With Quote
  #5 (permalink)  
Old December 6, 2011, 05:49 PM
Hall Of Fame
 
Join Date: Apr 2009
Location: laval Qc
Posts: 1,072
Default

Quote:
Originally Posted by Killswitch View Post
Specs are in his drop down menu thingy.... and I beat you to the OC question.




well either its ati driver related or the cpu voltage is dropping too low
use 50% loadline calibration

i have the same board overclocked to 5.0 n i use 75% its rock solid
dissable c1 c3 crap too

memtest your ram too
__________________
maximus IV extreme @ 5.1 1.41v

evga e760 +920 4.8 water5.0+ on phase linx stable
gtx285 tri-sli
dfi ut-p35 lt
e8600@4.6 1.38v
too much ram
Reply With Quote
  #6 (permalink)  
Old December 6, 2011, 06:17 PM
Top Prospect
 
Join Date: Nov 2011
Posts: 159

My System Specs

Default

waste of a maximus if cpu isnt oc'ed
Reply With Quote
  #7 (permalink)  
Old December 6, 2011, 07:15 PM
LaughingCrow's Avatar
MVP
F@H
 
Join Date: Feb 2010
Location: Southern Ontario
Posts: 379
Default

Note that Debugger keeps saying it has not located and downloaded the symbol files it needs... While you can actually download the files, there are a lot, much easier to just give Windebug the links and let it get what it needs.

When you started Windbg did you go to File>Symbol File Path and paste this in the box:

SRV*c:\symbols*http://msdl.microsoft.com/download/symbols

also you can check this Youtube series by Mark Russinovich (the 1st of 9:

Windows Hang and Crash Dump Analysis 1/9 - YouTube
Reply With Quote
  #8 (permalink)  
Old December 6, 2011, 07:17 PM
Soultribunal's Avatar
Moderator
F@H
 
Join Date: Dec 2008
Location: Mississauga
Posts: 8,048

My System Specs

Default

If its OC'd then take the suggestions above, give the RAM a good test too. I know pinning down issues like this can suck but work through it one component at at time.

RAM is usually the best culprit.

-ST
__________________




"We know not why he calls for us, only that when he does we must answer" - DMP 2009

"Dear Iceberg, I am sorry to hear about global warming. Karma is a bitch. Signed - Titanic"

I would rather believe and find god doesn't exist than to not believe and find that he does.

www.realhardwarereviews.com
Reply With Quote
  #9 (permalink)  
Old December 8, 2011, 07:04 AM
ern88's Avatar
MVP
 
Join Date: Jan 2011
Location: Halifax, Nova Scotia
Posts: 275

My System Specs

Default

I did memtest86+ for 7 hours and no errors? I am suspecting it might be something else. Because I changed out motherboard ram and cpu. Maybe a MoBo issue? I had 2 BSOD about a month ago. I reformatted and this is the first one since then.
Reply With Quote
  #10 (permalink)  
Old December 8, 2011, 08:30 AM
Hall Of Fame
 
Join Date: Apr 2009
Location: laval Qc
Posts: 1,072
Default

Quote:
Originally Posted by ern88 View Post
I did memtest86+ for 7 hours and no errors? I am suspecting it might be something else. Because I changed out motherboard ram and cpu. Maybe a MoBo issue? I had 2 BSOD about a month ago. I reformatted and this is the first one since then.
post your bios setting if you really want help
__________________
maximus IV extreme @ 5.1 1.41v

evga e760 +920 4.8 water5.0+ on phase linx stable
gtx285 tri-sli
dfi ut-p35 lt
e8600@4.6 1.38v
too much ram
Reply With Quote
Reply


Thread Tools
Display Modes

Similar Threads
Thread Thread Starter Forum Replies Last Post
AVR off = BSOD... turtletrax HTPC Systems & Software 0 November 11, 2011 08:54 PM
BSOD kazman O/S's, Drivers & General Software 0 April 16, 2011 01:53 PM
BSOD Dar_ell Troubleshooting 2 August 12, 2010 12:51 PM
Help with BSOD plz Rocco_360 Troubleshooting 9 June 21, 2009 08:34 AM
bsod destroyerht Troubleshooting 4 June 19, 2009 02:02 PM