BSOD (Blue Screen)

laumiulun

Distinguished
Dec 5, 2010
17
0
18,510
I got blue screen from my computer, which I did run some problem to try to figure out. I did find what PROBABLY cause by, but i don't know what to do from up that point.
I know you guy might call me dumb... but still want to go with it :p


Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\Minidump\122210-23259-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 (6 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0xfffff800`02c5f000 PsLoadedModuleList = 0xfffff800`02e9ce50
Debug session time: Wed Dec 22 19:13:24.936 2010 (UTC - 7:00)
System Uptime: 0 days 2:10:47.356
Loading Kernel Symbols
...............................................................
................................................................
........................................
Loading User Symbols
Loading unloaded module list
........
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1A, {41790, fffffa8000a7dd50, ffff, 0}

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

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

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

MEMORY_MANAGEMENT (1a)
# Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 0000000000041790, The subtype of the bugcheck.
Arg2: fffffa8000a7dd50
Arg3: 000000000000ffff
Arg4: 0000000000000000

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


BUGCHECK_STR: 0x1a_41790

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

PROCESS_NAME: java.exe

CURRENT_IRQL: 0

LAST_CONTROL_TRANSFER: from fffff80002d42f9e to fffff80002ccf740

STACK_TEXT:
fffff880`0bc25968 fffff800`02d42f9e : 00000000`0000001a 00000000`00041790 fffffa80`00a7dd50 00000000`0000ffff : nt!KeBugCheckEx
fffff880`0bc25970 fffff800`02d110da : 00000000`00000000 00000000`42af3fff fffffa80`00000000 fffffa80`07d97b30 : nt! ?? ::FNODOBFM::`string'+0x33906
fffff880`0bc25b30 fffff800`02cce993 : ffffffff`ffffffff 00000000`3e20e810 00000000`3e20e808 00000000`00008000 : nt!NtFreeVirtualMemory+0x5ca
fffff880`0bc25c20 00000000`77bfff3a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`3e20e7d8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x77bfff3a


STACK_COMMAND: kb

FOLLOWUP_IP:
nt! ?? ::FNODOBFM::`string'+33906
fffff800`02d42f9e cc int 3

SYMBOL_STACK_INDEX: 1

SYMBOL_NAME: nt! ?? ::FNODOBFM::`string'+33906

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 4c1c44a9

FAILURE_BUCKET_ID: X64_0x1a_41790_nt!_??_::FNODOBFM::_string_+33906

BUCKET_ID: X64_0x1a_41790_nt!_??_::FNODOBFM::_string_+33906

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

Can any one tell me how to fix it? :sol: I would be thankful

Anyway my system is:

Mobo:MSI 890FXA-GD70 AM3 AMD 890FX SATA 6Gb/s USB 3.0 ATX AMD Motherboard
Cpu: amd Phemon II x6 1075T 3 Ghz
Ram:G.SKILL Ripjaws Series 8GB (2 x 4GB) 240-Pin DDR3 SDRAM DDR3 1333 (PC3 10666) Desktop Memory Model F3-10666CL9D-8GBRL
GPU: Zotac 9800 GT 1gb
:pfff:
 

laumiulun

Distinguished
Dec 5, 2010
17
0
18,510


mostly memory, or Driver. It said that it Vista Driver Problem..
I think what i would do is first check Memory(but i did run a 6 hour test on it.. ) and than if it didn't fix, i would reinstall whole system(my last thing).

I don't know which driver is fault ..