BSOD

yeah its been updated and updated it with the same update again. Theres no latest update for the motherboard

 

i wouldn't mind throwing in some assistance, but your file host for the .dmp files is bad. The server is down, wont download the .dmp files. can you pick another file host.

 

here u go.http://www.sendspace.com/file/uxrspn

 

updating ur bios wont get u anywhere, this is a pointless action which might actually screw ur system in your situation. You have a problem with a device driver, which is running to make ur hardware work. to me it seems legit that if ur hardware does not work, the device driver will cause an error.

Windows will not give u any decent information. This operating system is too closed and simplified to be able to do this. Get urself a version of Backtrack or ubuntu and install it on a seperate partition on ur disk. Run memory tests with the linux kernel and try to run several benchmarks on linux. If a device driver crashes on this OS you will have more detailed information about the device error. If a device does not work, it will not work on windows neither it will on linux.

An example of a miracle is this: i do a cleaning of my pc once in some time. when i had an nvidia video card and i cleaned, after the cleaning my system was instable. after reinstalling the driver a couple of times the issue was over. very strange thing, dont ask me why, but in this case there is just something very unpredictable going on.

 

what OS are you running/

Win7 64 or 32
home premium?
service pack 1?

 

I haven't used a debug program outside of a class environment and it has been a while. Here is a dump debugged:

Code:

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

Loading Dump File [C:\Users\Documents\garbage\081712-26098-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: srv*
Executable search path is: srv*
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17803.amd64fre.win7sp1_gdr.120330-1504
Machine Name:
Kernel base = 0xfffff800`02a4e000 PsLoadedModuleList = 0xfffff800`02c92670
Debug session time: Fri Aug 17 11:54:17.215 2012 (UTC - 7:00)
System Uptime: 0 days 0:03:45.401
Loading Kernel Symbols
...............................................................
................................................................
.........................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 50, {fffff88075399d20, 1, fffffa8007dcf2e6, 5}

Could not read faulting driver name
Probably caused by : partmgr.sys ( partmgr!PmGlobalDispatch+9f )
Followup: MachineOwner
---------
2: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced.  This cannot be protected by try-except,
it must be protected by a Probe.  Typically the address is just plain bad or it
is pointing at freed memory.
Arguments:
Arg1: fffff88075399d20, memory referenced.
Arg2: 0000000000000001, value 0 = read operation, 1 = write operation.
Arg3: fffffa8007dcf2e6, If non-zero, the instruction address which referenced the bad memory
 address.
Arg4: 0000000000000005, (reserved)
Debugging Details:
------------------

Could not read faulting driver name
WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff80002cfc100
GetUlongFromAddress: unable to read from fffff80002cfc1c0
 fffff88075399d20 Nonpaged pool
FAULTING_IP: 
+0
fffffa80`07dcf2e6 f3aa            rep stos byte ptr [rdi]
MM_INTERNAL_CODE:  5
CUSTOMER_CRASH_COUNT:  1
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
BUGCHECK_STR:  0x50
PROCESS_NAME:  Adobelmsvc.exe
CURRENT_IRQL:  0
TRAP_FRAME:  fffff880072b54c0 -- (.trap 0xfffff880072b54c0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=000000008f430200
rdx=000000000000000d rsi=0000000000000000 rdi=0000000000000000
rip=fffffa8007dcf2e6 rsp=fffff880072b5658 rbp=fffffa8007f97a70
 r8=000000008f430200  r9=0000000000000001 r10=fffff880047c9d20
r11=0000fffffffff000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl zr na po nc
fffffa80`07dcf2e6 f3aa            rep stos byte ptr [rdi]
Resetting default scope
LAST_CONTROL_TRANSFER:  from fffff80002a73f1f to fffff80002acd1c0
STACK_TEXT:  
fffff880`072b5658 fffffa80`07dcf7e4 : 00000000`0000000d fffffa80`07f97910 fffffa80`00000001 fffffa80`07f97a70 : 0xfffffa80`07dcf2e6
fffff880`072b5660 00000000`0000000d : fffffa80`07f97910 fffffa80`00000001 fffffa80`07f97a70 fffffa80`00000001 : 0xfffffa80`07dcf7e4
fffff880`072b5668 fffffa80`07f97910 : fffffa80`00000001 fffffa80`07f97a70 fffffa80`00000001 fffffa80`00000000 : 0xd
fffff880`072b5670 fffffa80`00000001 : fffffa80`07f97a70 fffffa80`00000001 fffffa80`00000000 00000000`00000200 : 0xfffffa80`07f97910
fffff880`072b5678 fffffa80`07f97a70 : fffffa80`00000001 fffffa80`00000000 00000000`00000200 00000000`00000200 : 0xfffffa80`00000001
fffff880`072b5680 fffffa80`00000001 : fffffa80`00000000 00000000`00000200 00000000`00000200 fffffa80`07f97a70 : 0xfffffa80`07f97a70
fffff880`072b5688 fffffa80`00000000 : 00000000`00000200 00000000`00000200 fffffa80`07f97a70 fffffa80`07f97910 : 0xfffffa80`00000001
fffff880`072b5690 00000000`00000200 : 00000000`00000200 fffffa80`07f97a70 fffffa80`07f97910 fffffa80`07f97910 : 0xfffffa80`00000000
fffff880`072b5698 00000000`00000200 : fffffa80`07f97a70 fffffa80`07f97910 fffffa80`07f97910 fffff880`00eb67a7 : 0x200
fffff880`072b56a0 fffffa80`07f97a70 : fffffa80`07f97910 fffffa80`07f97910 fffff880`00eb67a7 fffffa80`07f97910 : 0x200
fffff880`072b56a8 fffffa80`07f97910 : fffffa80`07f97910 fffff880`00eb67a7 fffffa80`07f97910 fffffa80`07f97910 : 0xfffffa80`07f97a70
fffff880`072b56b0 fffffa80`07f97910 : fffff880`00eb67a7 fffffa80`07f97910 fffffa80`07f97910 fffffa80`077b7580 : 0xfffffa80`07f97910
fffff880`072b56b8 fffff880`00eb67a7 : fffffa80`07f97910 fffffa80`07f97910 fffffa80`077b7580 fffff8a0`03e0bca8 : 0xfffffa80`07f97910
fffff880`072b56c0 fffff880`00ebe789 : fffff880`00edcb50 fffff880`072b5878 00000000`00000200 fffffa80`07f97a70 : ACPI!ACPIDispatchForwardIrp+0x37
fffff880`072b56f0 fffff880`00eb6a3f : fffff880`00edcb50 fffffa80`069dd2d0 fffffa80`07f97910 00000000`00000000 : ACPI!ACPIIrpDispatchDeviceControl+0x75
fffff880`072b5720 fffff880`01651445 : 00000000`00000000 00000000`00000001 00000000`00000000 00000000`00000001 : ACPI!ACPIDispatchIrp+0x12b
fffff880`072b57a0 fffff880`01651975 : fffffa80`07a93010 fffffa80`077b7580 00000000`00020000 fffff880`00000000 : CLASSPNP!ServiceTransferRequest+0x355
fffff880`072b5840 fffff880`00f560af : fffffa80`06c08500 fffffa80`06c08500 fffffa80`06c086f0 fffffa80`06f1e010 : CLASSPNP!ClassReadWrite+0xd5
fffff880`072b5890 fffff800`02d341b0 : fffffa80`06c08738 fffffa80`06ea51b0 fffffa80`06b51ac0 00000000`00000000 : partmgr!PmGlobalDispatch+0x9f
fffff880`072b58c0 fffff800`02d33e4d : 00000000`00000000 fffff880`072b59a0 fffffa80`06c08500 fffff800`02ac2e1d : nt!RawReadWriteDeviceControl+0xa8
fffff880`072b5900 fffff880`00e5abcf : fffffa80`06c08738 fffffa80`07ee1bb0 00000000`00000000 fffffa80`06c08500 : nt!RawDispatch+0x7d
fffff880`072b5960 fffff880`00e596df : fffffa80`06ebf8d0 00000000`00000001 fffffa80`06ebf800 fffffa80`06c08500 : fltmgr!FltpLegacyProcessingAfterPreCallbacksCompleted+0x24f
fffff880`072b59f0 fffff800`02dd0eab : 00000000`00000000 fffffa80`06b51ac0 00000000`00000001 fffffa80`06c08500 : fltmgr!FltpDispatch+0xcf
fffff880`072b5a50 fffff800`02db2753 : fffffa80`06b51ac0 fffffa80`06c08501 fffffa80`06b51ac0 00000000`00000002 : nt!IopSynchronousServiceTail+0xfb
fffff880`072b5ac0 fffff800`02acc453 : 00000000`0000011c 00000000`00000000 00000000`00000000 00000000`00000000 : nt!NtReadFile+0x631
fffff880`072b5bb0 00000000`73db2e09 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`0094f0f8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x73db2e09

STACK_COMMAND:  .trap 0xfffff880072b54c0 ; kb
FOLLOWUP_IP: 
partmgr!PmGlobalDispatch+9f
fffff880`00f560af 8bf0            mov     esi,eax
SYMBOL_STACK_INDEX:  12
SYMBOL_NAME:  partmgr!PmGlobalDispatch+9f
FOLLOWUP_NAME:  MachineOwner
MODULE_NAME: partmgr
IMAGE_NAME:  partmgr.sys
DEBUG_FLR_IMAGE_TIMESTAMP:  4f641bc1
FAILURE_BUCKET_ID:  X64_0x50_partmgr!PmGlobalDispatch+9f
BUCKET_ID:  X64_0x50_partmgr!PmGlobalDispatch+9f
Followup: MachineOwner
---------
2: kd> lmvm partmgr
start             end                 module name
fffff880`00f55000 fffff880`00f6a000   partmgr    (pdb symbols)          C:\ProgramData\dbg\sym\partmgr.pdb\7E391DC4AAAC45C4A8D0FA49903564362\partmgr.pdb
    Loaded symbol image file: partmgr.sys
    Mapped memory image file: C:\ProgramData\dbg\sym\partmgr.sys\4F641BC115000\partmgr.sys
    Image path: \SystemRoot\System32\drivers\partmgr.sys
    Image name: partmgr.sys
    Timestamp:        Fri Mar 16 22:06:09 2012 (4F641BC1)
    CheckSum:         0001DFC8
    ImageSize:        00015000
    File version:     6.1.7601.17796
    Product version:  6.1.7601.17796
    File flags:       0 (Mask 3F)
    File OS:          40004 NT Win32
    File type:        3.7 Driver
    File date:        00000000.00000000
    Translations:     0000.04b0
    CompanyName:      Microsoft Corporation
    ProductName:      Microsoft

 

I'm not sure this is the correct one but it might be the same problem as yours - http://www.sevenforums.com/crashes-debugging/134952-bsod-couple-times-week-win7-ultimate-x64.html

 

Here's a different outcome of the debug:

Code:

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

Loading Dump File [C:\Users\Documents\garbage\081612-72961-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: srv*
Executable search path is: srv*
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17803.amd64fre.win7sp1_gdr.120330-1504
Machine Name:
Kernel base = 0xfffff800`02a1f000 PsLoadedModuleList = 0xfffff800`02c63670
Debug session time: Thu Aug 16 16:53:24.836 2012 (UTC - 7:00)
System Uptime: 0 days 0:12:55.413
Loading Kernel Symbols
...............................................................
................................................................
.................
Loading User Symbols
Loading unloaded module list
......
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1E, {ffffffffc0000005, fffff80002a7e82f, 0, 7efa0000}
Probably caused by : ntkrnlmp.exe ( nt!RtlImageNtHeaderEx+3f )
Followup: MachineOwner
---------
2: 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: fffff80002a7e82f, The address that the exception occurred at
Arg3: 0000000000000000, Parameter 0 of the exception
Arg4: 000000007efa0000, Parameter 1 of the exception
Debugging Details:
------------------

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002ccd100
GetUlongFromAddress: unable to read from fffff80002ccd1c0
 0000000000000000 Nonpaged pool
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
FAULTING_IP: 
nt!RtlImageNtHeaderEx+3f
fffff800`02a7e82f 66390a          cmp     word ptr [rdx],cx
BUGCHECK_STR:  0x1E_c0000005_R
CUSTOMER_CRASH_COUNT:  1
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
PROCESS_NAME:  iexplore.exe
CURRENT_IRQL:  0
TRAP_FRAME:  fffff880031bd8f0 -- (.trap 0xfffff880031bd8f0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=0000000000005a4d
rdx=000000007efa0000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002a7e82f rsp=fffff880031bda88 rbp=fffff880031bdbc0
 r8=0000000000000000  r9=fffff880031bdac8 r10=0000000000000000
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz na pe nc
nt!RtlImageNtHeaderEx+0x3f:
fffff800`02a7e82f 66390a          cmp     word ptr [rdx],cx ds:00000000`7efa0000=????
Resetting default scope
LAST_CONTROL_TRANSFER:  from fffff80002ae8db8 to fffff80002a9e1c0
STACK_TEXT:  
fffff880`031bd068 fffff800`02ae8db8 : 00000000`0000001e ffffffff`c0000005 fffff800`02a7e82f 00000000`00000000 : nt!KeBugCheckEx
fffff880`031bd070 fffff800`02a9d842 : fffff880`031bd848 fffffa80`07157660 fffff880`031bd8f0 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x48d3d
fffff880`031bd710 fffff800`02a9c3ba : 00000000`00000000 00000000`7efa0000 00000000`00860000 fffffa80`07157660 : nt!KiExceptionDispatch+0xc2
fffff880`031bd8f0 fffff800`02a7e82f : fffff800`02a7e9be 00000000`00000010 00000000`00000082 fffff880`031bdab8 : nt!KiPageFault+0x23a
fffff880`031bda88 fffff800`02a7e9be : 00000000`00000010 00000000`00000082 fffff880`031bdab8 ffffffff`80000a08 : nt!RtlImageNtHeaderEx+0x3f
fffff880`031bda90 fffffa80`07db5b07 : fffff880`031bdbc0 00000000`00000000 fffffa80`07db9250 fffffa80`07dbc750 : nt!RtlImageNtHeader+0x1e
fffff880`031bdac0 fffff880`031bdbc0 : 00000000`00000000 fffffa80`07db9250 fffffa80`07dbc750 00000000`00000000 : 0xfffffa80`07db5b07
fffff880`031bdac8 00000000`00000000 : fffffa80`07db9250 fffffa80`07dbc750 00000000`00000000 00000000`00000000 : 0xfffff880`031bdbc0

STACK_COMMAND:  kb
FOLLOWUP_IP: 
nt!RtlImageNtHeaderEx+3f
fffff800`02a7e82f 66390a          cmp     word ptr [rdx],cx
SYMBOL_STACK_INDEX:  4
SYMBOL_NAME:  nt!RtlImageNtHeaderEx+3f
FOLLOWUP_NAME:  MachineOwner
MODULE_NAME: nt
IMAGE_NAME:  ntkrnlmp.exe
DEBUG_FLR_IMAGE_TIMESTAMP:  4f76721c
FAILURE_BUCKET_ID:  X64_0x1E_c0000005_R_nt!RtlImageNtHeaderEx+3f
BUCKET_ID:  X64_0x1E_c0000005_R_nt!RtlImageNtHeaderEx+3f
Followup: MachineOwner
---------
2: kd> lmvm nt
start             end                 module name
fffff800`02a1f000 fffff800`03007000   nt         (pdb symbols)          C:\ProgramData\dbg\sym\ntkrnlmp.pdb\C686F808831A41929FA627FEC3AA7D1B2\ntkrnlmp.pdb
    Loaded symbol image file: ntkrnlmp.exe
    Mapped memory image file: C:\ProgramData\dbg\sym\ntoskrnl.exe\4F76721C5e8000\ntoskrnl.exe
    Image path: ntkrnlmp.exe
    Image name: ntkrnlmp.exe
    Timestamp:        Fri Mar 30 19:55:24 2012 (4F76721C)
    CheckSum:         0055A167
    ImageSize:        005E8000
    File version:     6.1.7601.17803
    Product version:  6.1.7601.17803
    File flags:       0 (Mask 3F)
    File OS:          40004 NT Win32
    File type:        1.0 App
    File date:        00000000.00000000
    Translations:     0409.04b0
    CompanyName:      Microsoft Corporation
    ProductName:      Microsoft

 

Im on windows 7 ultimate sp1. My hd is partition to if that helps in anyway

 

Your debug information only shows the memory stack of the computer at that time. If you want to know exactly what happened, you need to have quite extended Assembly knowledge, to be more precise: MASM32.

Besides that, while reading your debug information, i read the following line.

Probably caused by : ntkrnlmp.exe ( nt!RtlImageNtHeaderEx+3f )

The second debug information stated the same sort of line:

Probably caused by : partmgr.sys ( partmgr!PmGlobalDispatch+9f )

At first these lines indicate that Windows assumes that the following driver caused the error, because the function call, in these cases RtlImageNtHeaderEx and PmGlobalDispatch would have caused the errors. The +3f and +9f indicate the offset in memory where the function error value was stored at that time. In a function call, many operations can be done, including calls to a whole different driver. This means that the debug information could only suggest guesses from Windows Debug, and no reliable information.

Besides, the symbol information you loaded is general kernel information. Only built-in Windows kernel mode drivers are included in this information. Since we have no idea what kind of drivers he is using this is not accurate as far as i m concerned.

Your best guess is reinstall ur system. Why? Because you probably dont know what we are all talking about and u dont give a shit to it, u just want ur system fixed.

 

I reinstalled it 3 times. It still bsod

 

IF it is a driver problem try windows Driver Verifier. Type verifier in the start menu, you will see it.

err.. perhaps read about it first to see what it does, how it works.

I don't see how it could be a driver issue if you've reinstalled 3 times. but strange that it works fine in safe mode. I am putting my bet on hardware..
do you have any spare hardware, HDD, RAM, onboard graphics? or can trade with a friend?

Also: when you reinstall are you doing a format inbetween installs?

Does the Event Viewer have any info from the point that is BSODs?

how about giving the complete loadout of the hardware in your PC.. It might be helpful...?

 

I strongly recommend you guys to have this bookmarked on another computer - Demystifying the 'Blue Screen of Death'

It shows all the info about the error messages that appears on the BSOD (or some that might not be in the article) and ways to create the DUMPEXAM.EXE file.

This is the least I can do for you guys at this moment.

Also, I hope I don't get this kind of BSOD on my Windows 8 Preview XD

 

ok atreyu, the bsod information wont get u anywhere so this is what u gotta do, since ur hardware is broken at a hard to identify spot.

- ubuntu live cd, memory test. dont run a windows memory test;
- make note of the moments where the blue screen occurs. Take note of what u were doing at that time, and which programs u have had opened. a computer is a logical device. If you tell it to start l4d, it will not start the calculator. there is a specific operation that causes your computer to crash, let that be clear. information that ur blue error screen shows will not be nessecary;
- burn ur system with benchmarking tools. i suggest u use 3dmark 06 or vantage to burn the shit out of ur graphics card and processor. run it multiple times if it doesnt crash. this is the only way to find out if one of those main components have problems;
- run superpi on the highest setting for multiple times. also try prime95 and any other cpu load generators available;

some of my other experienced problems:

- you got poweriso, or deamon tools or any program that simulates a optical drive? get rid of it, these programs cause these problems too. i wont say that it would for certain in ur case, but i have seen enough cases in which they did. you cannot exclude anything suspicious without having proven it innocent.

and one last thing. run ur computer in safe mode for some hours, maybe days. if ur system doesnt crash, it is clearly a driver that windows does not load in safe mode, like display, sound, network, etc. You are able to enable each driver one by one for safe mode. This makes it easier to identify faulty drivers.

good luck

 

I am seeing alots of posts about people having more than one antivirus program of firewall. Even if only one is active it could cause driver conflicts. I have seen a few solved threads after removong on of the antivirus or firewall programs.

 

Download something like Ultimate Boot CD or Hiren's Boot Disk and perform a hardware diagnostic check by booting off the live cd.

 

tested my HDD, it failed how would i fix this

[TABLE]
[TR]
[TD]Test Option:[/TD]
[TD]EXTENDED TEST[/TD]
[/TR]
[TR]
[TD]Model Number:[/TD]
[TD]WDC WD5000AAVS-00N7B0[/TD]
[/TR]
[TR]
[TD]Unit Serial Number:[/TD]
[TD]WD-WCAV91633383[/TD]
[/TR]
[TR]
[TD]Firmware Number:[/TD]
[TD]01.00A01[/TD]
[/TR]
[TR]
[TD]Capacity:[/TD]
[TD]500.11 GB[/TD]
[/TR]
[TR]
[TD]SMART Status:[/TD]
[TD]PASS[/TD]
[/TR]
[TR]
[TD]Test Result:[/TD]
[TD]FAIL[/TD]
[/TR]
[TR]
[TD]Test Error Code:[/TD]
[TD]08-Too many bad sectors detected.[/TD]
[/TR]
[TR]
[TD]Test Time:[/TD]
[TD]13:58:52, August 21, 2012[/TD]
[/TR]
[/TABLE]

 

Looks like you need a new harddrive.

Trust me, my Western Digital at my old workplace had the same error as you.

Bad sectors = damaged hard drive, which means you need a hard drive.

 

Here is a good reason to upgrade to a SSD!

hmm, but you will probably still need a new HDD for extra secondary storage.

 

i need about 500gb but i dont want to get 2 HD's SSD is a little to expensive and as good as it is its offers are like 64GB for $100 =[. To little space dont wanna spend another $80 for HD lol. currently looking at this

http://www.newegg.com/Product/Product.aspx?Item=N82E16822136769