[SOLVED] Vista Ultimate x64 SP1 random BSOD's

prop_dynamic · 10-12-2008, 01:45 PM

Hi, I'm new to this forum

and would like your help with a problem I've been having:

Recently I got a brandnew PC and installed Vista Ultimate x64 SP1 on it. Started with Windows Update (which also installed the latest Nvidia Drivers) and then I installed the Chipset Drivers and drivers supplied with the mobo. No BSOD's right then. So I continued installing programs and when I was quite far suddenly I got a BSOD. This has continued very randomly in 2-3 hour intervals (I haven't been able to find a pattern). In between the system acted fine. I could run games like Crysis Warhead on max settings and the performance would be fine. One time when I shut down this game THEN I got a BSOD. I also installed Rainbow Six Vegas 2 which ran fine while the updater program running prior to launch caused a BSOD. Since it is a new pc I almost immediately checked the RAM with the windows checker and memtest which didn't result in any errors. The HDD seemed fine and the PSU too. I also ran checkdisk which didn't find any problems. Since these BSOD's occur in 2-3 hour intervals it is almost impossible to find out the culprit.

Now the minidump logs all point to: DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT which doesn't help me find the exact cause.

Could someone help me out with what is the issue here?

I've included a hijackthis log, 5 analyzed minidumps so far and a 64 bit dxdiag lag. If you want any more information please say so.

prop_dynamic · 10-13-2008, 03:51 AM

I got a new BSOD yesterday on shutdown referring to eamon.sys. Therefore I uninstalled NOD32. Also I noticed my default account, the only one, having not full administrator rights (although it showed as an administrator account), which is still a mystery to me. I ran Net user administrator /active:yes in cmd which enabled the true administrator account. I switched to that one and removed the first one. The system has been stable this entire morning. Also Internet Explorer 7 used to crash because of the latest flashplayer. This was installed in the first account which wasn't fully admin. I uninstalled the flash player and installed it on the true admin account. This solved that problem.

Now I'm hoping not to get any BSOD's today

.

andressergio · 10-13-2008, 05:26 AM

Quote:

Originally Posted by prop_dynamic

I got a new BSOD yesterday on shutdown referring to eamon.sys. Therefore I uninstalled NOD32. Also I noticed my default account, the only one, having not full administrator rights (although it showed as an administrator account), which is still a mystery to me. I ran Net user administrator /active:yes in cmd which enabled the true administrator account. I switched to that one and removed the first one. The system has been stable this entire morning. Also Internet Explorer 7 used to crash because of the latest flashplayer. This was installed in the first account which wasn't fully admin. I uninstalled the flash player and installed it on the true admin account. This solved that problem.

Now I'm hoping not to get any BSOD's today

.

Mate why so much BSOD's

as you can see in my sig i have a heavy Overclocked system and never had a BSOD on Vista Ultimate 64 SP1...Used to have on Vista 32 before SP1 when installing windows updates...but yours sounds different like virus...specially if you say that nod service was the cause, Are you using a 64bits version of NOD32 ? I have 3.0629 for Vista 64 bits...

Cheers mate
Sergio

prop_dynamic · 10-13-2008, 06:28 AM

Yes I was using the 64 bit version of NOD32 and I'm not too sure about having a virus on a recently reformatted machine. And if it were spyware I would have nuked the HDD. On another note had another crash right now. So NOD32 seemed to cause an entirely seperate problem. This problem occurred while installing from an iso mounted from an external HDD (Maxtor 3200 USB device). In the eventviewer I see windows defender blabbing about an error in daemon tools and soon the BSOD followed. I'm gonna unplug the external HDD and disable windows defender. See how that is gonna work out. When I rebooted from the BSOD updateusb.exe was still running. Does something prevent my USB drivers from updating?

Anyways here is the crashlog:

*******************************************************************************
* *
* 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: fffff8900bc7e1a8, memory referenced.
Arg2: 0000000000000001, value 0 = read operation, 1 = write operation.
Arg3: fffff80001cd6d91, 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 fffff80001c38080
fffff8900bc7e1a8

FAULTING_IP:
nt!CmpDelayDerefKCBWorker+6d
fffff800`01cd6d91 4c896808 mov qword ptr [rax+8],r13

MM_INTERNAL_CODE: 5

CUSTOMER_CRASH_COUNT: 2

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

BUGCHECK_STR: 0x50

PROCESS_NAME: System

CURRENT_IRQL: 0

TRAP_FRAME: fffffa6001bd4b30 -- (.trap 0xfffffa6001bd4b30)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffff8900bc7e1a0 rbx=fffff80001c0c680 rcx=00000000000000aa
rdx=fffff88000017070 rsi=fffff88006c0b808 rdi=fffffa80039b2bb0
rip=fffff80001cd6d91 rsp=fffffa6001bd4cc0 rbp=0000000000000001
r8=0000000000000001 r9=fffffa80039b2bb0 r10=0000000000000000
r11=fffff80001c38640 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl nz na pe nc
nt!CmpDelayDerefKCBWorker+0x6d:
fffff800`01cd6d91 4c896808 mov qword ptr [rax+8],r13 ds:fffff890`0bc7e1a8=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER: from fffff80001a724e2 to fffff80001a64390

STACK_TEXT:
fffffa60`01bd4a38 fffff800`01a724e2 : 00000000`00000050 fffff890`0bc7e1a8 00000000`00000001 fffffa60`01bd4b30 : nt!KeBugCheckEx
fffffa60`01bd4a40 fffff800`01a62f19 : 00000000`00000001 00000000`00000023 00000000`00000000 fffffa80`039b2bb0 : nt!MmAccessFault+0x4f2
fffffa60`01bd4b30 fffff800`01cd6d91 : 00000000`00000000 fffff880`00d1c010 fffff880`0828dbf0 fffffa80`039b2bb0 : nt!KiPageFault+0x119
fffffa60`01bd4cc0 fffff800`01a7105a : fffff800`01cd6d24 fffff800`01ba18f8 fffffa80`039b2bb0 00000000`00000000 : nt!CmpDelayDerefKCBWorker+0x6d
fffffa60`01bd4cf0 fffff800`01c87f73 : fffff800`01c0c680 01c92b9e`488161cc fffffa80`039b2bb0 00000000`00000080 : nt!ExpWorkerThread+0x11a
fffffa60`01bd4d50 fffff800`01a9e526 : fffffa60`019d2180 fffffa80`039b2bb0 fffffa60`019dbd40 00000000`00000001 : nt!PspSystemThreadStartup+0x57
fffffa60`01bd4d80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16

STACK_COMMAND: kb

FOLLOWUP_IP:
nt!CmpDelayDerefKCBWorker+6d
fffff800`01cd6d91 4c896808 mov qword ptr [rax+8],r13

SYMBOL_STACK_INDEX: 3

SYMBOL_NAME: nt!CmpDelayDerefKCBWorker+6d

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 4812c3f7

FAILURE_BUCKET_ID: X64_0x50_W_nt!CmpDelayDerefKCBWorker+6d

BUCKET_ID: X64_0x50_W_nt!CmpDelayDerefKCBWorker+6d

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

It is consistant with the other crashdumps so the problem is'n't solved yet.

prop_dynamic · 10-13-2008, 07:51 AM

Maybe this hotfix will solve the problem: http://support.microsoft.com/kb/953186
It seems when I run a graphic application: flashplayer, a game or even adobe graphics manager the application or my computer crashes. The corruption described matches my problem and I am running a quad core processor.

Edit:

It doesn't apply to my system so it appears it has already been patched?

prop_dynamic · 10-13-2008, 12:26 PM

Wercon has detected a problem with my harddisk. Some processes can't access files on my HDD suddenly. This wouldn't surprise me as it's a Samsung HD103UJ. Also the sata might not be plugged in entirely? Gonna check.

prop_dynamic · 10-14-2008, 11:37 AM

Ok so I solved another BSOD because my NVidia drivers were corrupted or something, really strange. Reinstalled them. I thought I was done with the BSODs now but:

*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

MEMORY_MANAGEMENT (1a)
# Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 0000000000005003, The subtype of the bugcheck.
Arg2: fffff70001080000
Arg3: 00000000000031c9
Arg4: 0000000005bfa201

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

BUGCHECK_STR: 0x1a_5003

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

PROCESS_NAME: dwm.exe

CURRENT_IRQL: 0

LAST_CONTROL_TRANSFER: from fffff80001ccdac7 to fffff80001c72390

STACK_TEXT:
fffffa60`0b606ad8 fffff800`01ccdac7 : 00000000`0000001a 00000000`00005003 fffff700`01080000 00000000`000031c9 : nt!KeBugCheckEx
fffffa60`0b606ae0 fffff800`01c826b7 : 00000000`00077b43 fffffa80`08e7da00 fffffa80`01671c90 fffffa80`0522dbb0 : nt! ?? ::FNODOBFM::`string'+0x14ab7
fffffa60`0b606b30 fffff800`01c70f19 : 00000000`00000001 fffffa60`0b606ca0 fffffa60`0b606a01 00000000`00000040 : nt!MmAccessFault+0x26c7
fffffa60`0b606c20 00000001`8052f289 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x119
00000000`032cca60 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x1`8052f289

STACK_COMMAND: kb

FOLLOWUP_IP:
nt! ?? ::FNODOBFM::`string'+14ab7
fffff800`01ccdac7 cc int 3

SYMBOL_STACK_INDEX: 1

SYMBOL_NAME: nt! ?? ::FNODOBFM::`string'+14ab7

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 4812c3f7

FAILURE_BUCKET_ID: X64_0x1a_5003_nt!_??_::FNODOBFM::_string_+14ab7

BUCKET_ID: X64_0x1a_5003_nt!_??_::FNODOBFM::_string_+14ab7

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

*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

MEMORY_MANAGEMENT (1a)
# Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 0000000000005100, The subtype of the bugcheck.
Arg2: fffff6fd30053ee8
Arg3: 0000000000000001
Arg4: 800000007fd0e963

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

BUGCHECK_STR: 0x1a_5100

CUSTOMER_CRASH_COUNT: 2

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

PROCESS_NAME: svchost.exe

CURRENT_IRQL: 0

LAST_CONTROL_TRANSFER: from fffff80001c6ab47 to fffff80001ca9390

STACK_TEXT:
fffffa60`0af294e8 fffff800`01c6ab47 : 00000000`0000001a 00000000`00005100 fffff6fd`30053ee8 00000000`00000001 : nt!KeBugCheckEx
fffffa60`0af294f0 fffff800`01c779c8 : fffff6fd`30053ee8 fffffa80`035b2c30 00000000`00000000 0000a7d9`00029ce6 : nt! ?? ::FNODOBFM::`string'+0x50c7
fffffa60`0af29600 fffff800`01c9b0ea : fffffa80`00000000 00000000`00000001 fffffa80`0000001d fffffa80`00000000 : nt!MiZeroPhysicalPage+0x200
fffffa60`0af29670 fffff800`01c68cb4 : fffffa80`09118570 00000000`00000000 00000000`00000000 00000000`00003000 : nt!MiWaitForInPageComplete+0x3da
fffffa60`0af29740 fffff800`01ea4d3d : fffffa80`08650f60 00000000`00000001 fffffa80`08650f60 00000000`0000003f : nt!MiPfCompletePrefetchIos+0x28
fffffa60`0af29770 fffff800`02058ea1 : 00000000`00000000 fffff880`082ea618 fffff880`082de000 fffffa60`0af29908 : nt!MmPrefetchPages+0x141
fffffa60`0af297c0 fffff800`02082799 : fffff880`00000000 00000000`00000000 00000000`0000041d 00000000`00000000 : nt!PfpPrefetchFilesTrickle+0x211
fffffa60`0af298c0 fffff800`02082a52 : 00000000`00000000 fffffa60`0af29ca0 fffffa60`0af29a08 fffff880`082de001 : nt!PfpPrefetchRequestPerform+0x2f9
fffffa60`0af29960 fffff800`02082cb6 : fffffa60`0af29a08 fffffa80`086f7901 fffffa80`08fc00b0 00000000`00000000 : nt!PfpPrefetchRequest+0x171
fffffa60`0af299d0 fffff800`020953e8 : 00000000`00000000 00000000`00000004 00000000`00000000 00000000`0220f301 : nt!PfSetSuperfetchInformation+0x1a5
fffffa60`0af29ab0 fffff800`01ca8e33 : fffffa80`08b09060 00000000`00000000 00000000`00000001 00000000`0002dbe2 : nt!NtSetSystemInformation+0x8fb
fffffa60`0af29c20 00000000`773970ea : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`0220fb68 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x773970ea

STACK_COMMAND: kb

FOLLOWUP_IP:
nt! ?? ::FNODOBFM::`string'+50c7
fffff800`01c6ab47 cc int 3

SYMBOL_STACK_INDEX: 1

SYMBOL_NAME: nt! ?? ::FNODOBFM::`string'+50c7

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 4812c3f7

FAILURE_BUCKET_ID: X64_0x1a_5100_nt!_??_::FNODOBFM::_string_+50c7

BUCKET_ID: X64_0x1a_5100_nt!_??_::FNODOBFM::_string_+50c7

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

At least they are consistent. Last time I ran verifier.exe I got a BSOD. Should I run the repair function?

rockstat · 10-14-2008, 12:24 PM

A similar thing happened to my friends computer. He got random BSOD's and the boot up would take 10 mins.

I made him reformat and reinstall the whole O/S. It seemed like it was a problem with him installing several programs and the updates together and not rebooting when required to finish the installation.

What I would suggest is, reformat and install the whole OS. First thing to do when you install it.

1) Install all of the drivers available on the mobo CD. Get all of the drivers from the CD's for all of your system, unless you don't have the driver for vista 64 bit.

2) After you're done installing all that, then run windows update and let it update and don't install anything while its running. Reboot as required and then you should have a pretty stable system. It worked for my friend.
Windows update will replace any old driver you have.

prop_dynamic · 10-14-2008, 02:09 PM

Thank you for your reply, I will do that soon. Windows update did run first and it made some errors yeah. But I don't have a lot of time to be doing reformats as I have exams next week. I'll keep this in consideration and keep you posted on any progress

Nagrad · 10-14-2008, 02:16 PM

I had a similar issue after reformatting my PC. I have an Asus Crosshair MB, the problem was caused when windows update decided to update the NVIDIA SATA drivers. I rolled back the drivers and bingo no more problem.

prop_dynamic · 10-16-2008, 12:17 PM

No reformat needed as I found the problem:

My motherboard: An Asus P5Q3 Deluxe WiFi-AP@n seems to be incompatible with Corsair TW3X4G1333C9DHX DDRIII SDRAM. Even though it's on the QVL (http://asus.com/999/download/products/2273/2273_10.pdf) almost everyone has these problems: http://vip.asus.com/forum/view.aspx?...age=1&count=17

Corsair thread:
http://www.asktheramguy.com/v3/showthread.php?t=73070

This is also true for OCZ DDRIII memory: http://www.ocztechnologyforum.com/fo...ad.php?t=39418

I'm one of the "lucky" few as most people couldn't even get an OS installed in the first place. Updating the BIOS doesn't seem to solve the problem completely/partially or will make it even worse.

Now I will have to look for a new set of DDRIII memory that hopefully works (where are the good old days when ram would just work :() and contact my vendor.

At least I'm happy I found the problem :D.

prop_dynamic · 10-17-2008, 03:37 AM

My hardware vendor suggested the following solution:

This problem occurs quite a lot and would be relatively easy to solve:

-Remove one of the 2x2GB memory banks so you have effectively 2GB installed.

-Install Windows Vista.

-Update Windows Vista. (As I haven't tested this solution yet it would be wise to update your mobo drivers first (chipset, ethernet etc.etc.))

-Place the removed memory bank back. Everything should work without any problems now.

I'm not gonna test this solution right now. It would explain the BSOD's I got while updating Windows Vista and that might have resulted in the corrupted nt module. I do think it will work as my hardware vendor has ALOT of experience and they wouldn't suggest this if it wouldn't work.

**jcgriff2** · 10-17-2008, 03:57 AM

Hi. . .

Sorry that I missed all of this.

For info, you may have had a problem with the ESET driver eamon.sys if you did not have the most recent version of ESET. I run ESET NOD32 on x86 and x64 systems here and did suffer a crash that named eamon.sys - and it turned out to ne that I had an older version of ESET installed that for some reason never got updated (virus defs were OK).

Good Luck to you.

Regards. . .

jcgriff2

.

prop_dynamic · 10-17-2008, 04:24 AM

Ok I'll keep that in mind the next time I try to install NOD32.

prop_dynamic · 10-18-2008, 11:56 AM

Quote:

Originally Posted by prop_dynamic

My hardware vendor suggested the following solution:

This problem occurs quite a lot and would be relatively easy to solve:

-Remove one of the 2x2GB memory banks so you have effectively 2GB installed.

-Install Windows Vista.

-Update Windows Vista. (As I haven't tested this solution yet it would be wise to update your mobo drivers first (chipset, ethernet etc.etc.))

-Place the removed memory bank back. Everything should work without any problems now.

I'm not gonna test this solution right now. It would explain the BSOD's I got while updating Windows Vista and that might have resulted in the corrupted nt module. I do think it will work as my hardware vendor has ALOT of experience and they wouldn't suggest this if it wouldn't work.

I tried this solution but when I was done installing the mobo drivers and went to Windows update first my computer just froze and on reboot and retry it gave me a 0x50 BSOD. The freeze pointed me in the powermanagement direction. When I hit ctrl+alt+del I saw Asus ACPI (Advanced Configuration and Power Interface) Center running (aaCenter.exe). I think this is the culprit (did some googling http://www.techspot.com/vb/all/windo...-of-ideas.html). Now I can't uninstall it as it doesnt show in the list, but it has a program files folder.

Does anyone have any suggestions as to uninstalling it? I am reformatting right now. This also throws the 2x2GB vs. 1x2GB theory out of the window.

prop_dynamic · 10-18-2008, 02:24 PM

Problem solved, Not installing any Asus related mobo drivers/utilities fixed the Asus ACPI not being installed and therefore not creating any 0x50 BSOD's XD. Quite sad though you can't install any Asus related software on an Asus mobo. Gonna plug the other 2GB DDR3 RAM in tomorrow so I can use my pc finally.

10-13-2008, 03:51 AM	#2 (permalink)
prop_dynamic Registered User Join Date: Oct 2008 Posts: 12 OS: Vista Ultimate x64 SP1	Re: Vista Ultimate x64 SP1 random BSOD's I got a new BSOD yesterday on shutdown referring to eamon.sys. Therefore I uninstalled NOD32. Also I noticed my default account, the only one, having not full administrator rights (although it showed as an administrator account), which is still a mystery to me. I ran Net user administrator /active:yes in cmd which enabled the true administrator account. I switched to that one and removed the first one. The system has been stable this entire morning. Also Internet Explorer 7 used to crash because of the latest flashplayer. This was installed in the first account which wasn't fully admin. I uninstalled the flash player and installed it on the true admin account. This solved that problem. Now I'm hoping not to get any BSOD's today .

10-13-2008, 06:28 AM	#4 (permalink)
prop_dynamic Registered User Join Date: Oct 2008 Posts: 12 OS: Vista Ultimate x64 SP1	Re: Vista Ultimate x64 SP1 random BSOD's Yes I was using the 64 bit version of NOD32 and I'm not too sure about having a virus on a recently reformatted machine. And if it were spyware I would have nuked the HDD. On another note had another crash right now. So NOD32 seemed to cause an entirely seperate problem. This problem occurred while installing from an iso mounted from an external HDD (Maxtor 3200 USB device). In the eventviewer I see windows defender blabbing about an error in daemon tools and soon the BSOD followed. I'm gonna unplug the external HDD and disable windows defender. See how that is gonna work out. When I rebooted from the BSOD updateusb.exe was still running. Does something prevent my USB drivers from updating? Anyways here is the crashlog: ******************************************************************************* * * * 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: fffff8900bc7e1a8, memory referenced. Arg2: 0000000000000001, value 0 = read operation, 1 = write operation. Arg3: fffff80001cd6d91, 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 fffff80001c38080 fffff8900bc7e1a8 FAULTING_IP: nt!CmpDelayDerefKCBWorker+6d fffff800`01cd6d91 4c896808 mov qword ptr [rax+8],r13 MM_INTERNAL_CODE: 5 CUSTOMER_CRASH_COUNT: 2 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0x50 PROCESS_NAME: System CURRENT_IRQL: 0 TRAP_FRAME: fffffa6001bd4b30 -- (.trap 0xfffffa6001bd4b30) NOTE: The trap frame does not contain all registers. Some register values may be zeroed or incorrect. rax=fffff8900bc7e1a0 rbx=fffff80001c0c680 rcx=00000000000000aa rdx=fffff88000017070 rsi=fffff88006c0b808 rdi=fffffa80039b2bb0 rip=fffff80001cd6d91 rsp=fffffa6001bd4cc0 rbp=0000000000000001 r8=0000000000000001 r9=fffffa80039b2bb0 r10=0000000000000000 r11=fffff80001c38640 r12=0000000000000000 r13=0000000000000000 r14=0000000000000000 r15=0000000000000000 iopl=0 nv up ei pl nz na pe nc nt!CmpDelayDerefKCBWorker+0x6d: fffff800`01cd6d91 4c896808 mov qword ptr [rax+8],r13 ds:fffff890`0bc7e1a8=???????????????? Resetting default scope LAST_CONTROL_TRANSFER: from fffff80001a724e2 to fffff80001a64390 STACK_TEXT: fffffa60`01bd4a38 fffff800`01a724e2 : 00000000`00000050 fffff890`0bc7e1a8 00000000`00000001 fffffa60`01bd4b30 : nt!KeBugCheckEx fffffa60`01bd4a40 fffff800`01a62f19 : 00000000`00000001 00000000`00000023 00000000`00000000 fffffa80`039b2bb0 : nt!MmAccessFault+0x4f2 fffffa60`01bd4b30 fffff800`01cd6d91 : 00000000`00000000 fffff880`00d1c010 fffff880`0828dbf0 fffffa80`039b2bb0 : nt!KiPageFault+0x119 fffffa60`01bd4cc0 fffff800`01a7105a : fffff800`01cd6d24 fffff800`01ba18f8 fffffa80`039b2bb0 00000000`00000000 : nt!CmpDelayDerefKCBWorker+0x6d fffffa60`01bd4cf0 fffff800`01c87f73 : fffff800`01c0c680 01c92b9e`488161cc fffffa80`039b2bb0 00000000`00000080 : nt!ExpWorkerThread+0x11a fffffa60`01bd4d50 fffff800`01a9e526 : fffffa60`019d2180 fffffa80`039b2bb0 fffffa60`019dbd40 00000000`00000001 : nt!PspSystemThreadStartup+0x57 fffffa60`01bd4d80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16 STACK_COMMAND: kb FOLLOWUP_IP: nt!CmpDelayDerefKCBWorker+6d fffff800`01cd6d91 4c896808 mov qword ptr [rax+8],r13 SYMBOL_STACK_INDEX: 3 SYMBOL_NAME: nt!CmpDelayDerefKCBWorker+6d FOLLOWUP_NAME: MachineOwner MODULE_NAME: nt IMAGE_NAME: ntkrnlmp.exe DEBUG_FLR_IMAGE_TIMESTAMP: 4812c3f7 FAILURE_BUCKET_ID: X64_0x50_W_nt!CmpDelayDerefKCBWorker+6d BUCKET_ID: X64_0x50_W_nt!CmpDelayDerefKCBWorker+6d Followup: MachineOwner --------- It is consistant with the other crashdumps so the problem is'n't solved yet.

10-13-2008, 07:51 AM	#5 (permalink)
prop_dynamic Registered User Join Date: Oct 2008 Posts: 12 OS: Vista Ultimate x64 SP1	Re: Vista Ultimate x64 SP1 random BSOD's Maybe this hotfix will solve the problem: http://support.microsoft.com/kb/953186 It seems when I run a graphic application: flashplayer, a game or even adobe graphics manager the application or my computer crashes. The corruption described matches my problem and I am running a quad core processor. Edit: It doesn't apply to my system so it appears it has already been patched? Last edited by prop_dynamic; 10-13-2008 at 08:05 AM.

10-13-2008, 12:26 PM	#6 (permalink)
prop_dynamic Registered User Join Date: Oct 2008 Posts: 12 OS: Vista Ultimate x64 SP1	Re: Vista Ultimate x64 SP1 random BSOD's Wercon has detected a problem with my harddisk. Some processes can't access files on my HDD suddenly. This wouldn't surprise me as it's a Samsung HD103UJ. Also the sata might not be plugged in entirely? Gonna check.

10-14-2008, 11:37 AM	#7 (permalink)
prop_dynamic Registered User Join Date: Oct 2008 Posts: 12 OS: Vista Ultimate x64 SP1	Re: Vista Ultimate x64 SP1 random BSOD's Ok so I solved another BSOD because my NVidia drivers were corrupted or something, really strange. Reinstalled them. I thought I was done with the BSODs now but: ******************************************************************************* * * * Bugcheck Analysis * * * ***************************************************************************** MEMORY_MANAGEMENT (1a) # Any other values for parameter 1 must be individually examined. Arguments: Arg1: 0000000000005003, The subtype of the bugcheck. Arg2: fffff70001080000 Arg3: 00000000000031c9 Arg4: 0000000005bfa201 Debugging Details: ------------------ BUGCHECK_STR: 0x1a_5003 CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT PROCESS_NAME: dwm.exe CURRENT_IRQL: 0 LAST_CONTROL_TRANSFER: from fffff80001ccdac7 to fffff80001c72390 STACK_TEXT: fffffa60`0b606ad8 fffff800`01ccdac7 : 00000000`0000001a 00000000`00005003 fffff700`01080000 00000000`000031c9 : nt!KeBugCheckEx fffffa60`0b606ae0 fffff800`01c826b7 : 00000000`00077b43 fffffa80`08e7da00 fffffa80`01671c90 fffffa80`0522dbb0 : nt! ?? ::FNODOBFM::`string'+0x14ab7 fffffa60`0b606b30 fffff800`01c70f19 : 00000000`00000001 fffffa60`0b606ca0 fffffa60`0b606a01 00000000`00000040 : nt!MmAccessFault+0x26c7 fffffa60`0b606c20 00000001`8052f289 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x119 00000000`032cca60 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x1`8052f289 STACK_COMMAND: kb FOLLOWUP_IP: nt! ?? ::FNODOBFM::`string'+14ab7 fffff800`01ccdac7 cc int 3 SYMBOL_STACK_INDEX: 1 SYMBOL_NAME: nt! ?? ::FNODOBFM::`string'+14ab7 FOLLOWUP_NAME: MachineOwner MODULE_NAME: nt IMAGE_NAME: ntkrnlmp.exe DEBUG_FLR_IMAGE_TIMESTAMP: 4812c3f7 FAILURE_BUCKET_ID: X64_0x1a_5003_nt!_??_::FNODOBFM::_string_+14ab7 BUCKET_ID: X64_0x1a_5003_nt!_??_::FNODOBFM::_string_+14ab7 Followup: MachineOwner --------- ***************************************************************************** * * * Bugcheck Analysis * * * ******************************************************************************* MEMORY_MANAGEMENT (1a) # Any other values for parameter 1 must be individually examined. Arguments: Arg1: 0000000000005100, The subtype of the bugcheck. Arg2: fffff6fd30053ee8 Arg3: 0000000000000001 Arg4: 800000007fd0e963 Debugging Details: ------------------ BUGCHECK_STR: 0x1a_5100 CUSTOMER_CRASH_COUNT: 2 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT PROCESS_NAME: svchost.exe CURRENT_IRQL: 0 LAST_CONTROL_TRANSFER: from fffff80001c6ab47 to fffff80001ca9390 STACK_TEXT: fffffa60`0af294e8 fffff800`01c6ab47 : 00000000`0000001a 00000000`00005100 fffff6fd`30053ee8 00000000`00000001 : nt!KeBugCheckEx fffffa60`0af294f0 fffff800`01c779c8 : fffff6fd`30053ee8 fffffa80`035b2c30 00000000`00000000 0000a7d9`00029ce6 : nt! ?? ::FNODOBFM::`string'+0x50c7 fffffa60`0af29600 fffff800`01c9b0ea : fffffa80`00000000 00000000`00000001 fffffa80`0000001d fffffa80`00000000 : nt!MiZeroPhysicalPage+0x200 fffffa60`0af29670 fffff800`01c68cb4 : fffffa80`09118570 00000000`00000000 00000000`00000000 00000000`00003000 : nt!MiWaitForInPageComplete+0x3da fffffa60`0af29740 fffff800`01ea4d3d : fffffa80`08650f60 00000000`00000001 fffffa80`08650f60 00000000`0000003f : nt!MiPfCompletePrefetchIos+0x28 fffffa60`0af29770 fffff800`02058ea1 : 00000000`00000000 fffff880`082ea618 fffff880`082de000 fffffa60`0af29908 : nt!MmPrefetchPages+0x141 fffffa60`0af297c0 fffff800`02082799 : fffff880`00000000 00000000`00000000 00000000`0000041d 00000000`00000000 : nt!PfpPrefetchFilesTrickle+0x211 fffffa60`0af298c0 fffff800`02082a52 : 00000000`00000000 fffffa60`0af29ca0 fffffa60`0af29a08 fffff880`082de001 : nt!PfpPrefetchRequestPerform+0x2f9 fffffa60`0af29960 fffff800`02082cb6 : fffffa60`0af29a08 fffffa80`086f7901 fffffa80`08fc00b0 00000000`00000000 : nt!PfpPrefetchRequest+0x171 fffffa60`0af299d0 fffff800`020953e8 : 00000000`00000000 00000000`00000004 00000000`00000000 00000000`0220f301 : nt!PfSetSuperfetchInformation+0x1a5 fffffa60`0af29ab0 fffff800`01ca8e33 : fffffa80`08b09060 00000000`00000000 00000000`00000001 00000000`0002dbe2 : nt!NtSetSystemInformation+0x8fb fffffa60`0af29c20 00000000`773970ea : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13 00000000`0220fb68 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x773970ea STACK_COMMAND: kb FOLLOWUP_IP: nt! ?? ::FNODOBFM::`string'+50c7 fffff800`01c6ab47 cc int 3 SYMBOL_STACK_INDEX: 1 SYMBOL_NAME: nt! ?? ::FNODOBFM::`string'+50c7 FOLLOWUP_NAME: MachineOwner MODULE_NAME: nt IMAGE_NAME: ntkrnlmp.exe DEBUG_FLR_IMAGE_TIMESTAMP: 4812c3f7 FAILURE_BUCKET_ID: X64_0x1a_5100_nt!_??_::FNODOBFM::_string_+50c7 BUCKET_ID: X64_0x1a_5100_nt!_??_::FNODOBFM::_string_+50c7 Followup: MachineOwner --------- At least they are consistent. Last time I ran verifier.exe I got a BSOD. Should I run the repair function?

10-14-2008, 12:24 PM	#8 (permalink)
rockstat Registered User Join Date: Mar 2008 Location: Where ever I live Posts: 114 OS: XP_Pro-SP3/Vista_x64_SP2/Linux	Re: Vista Ultimate x64 SP1 random BSOD's A similar thing happened to my friends computer. He got random BSOD's and the boot up would take 10 mins. I made him reformat and reinstall the whole O/S. It seemed like it was a problem with him installing several programs and the updates together and not rebooting when required to finish the installation. What I would suggest is, reformat and install the whole OS. First thing to do when you install it. 1) Install all of the drivers available on the mobo CD. Get all of the drivers from the CD's for all of your system, unless you don't have the driver for vista 64 bit. 2) After you're done installing all that, then run windows update and let it update and don't install anything while its running. Reboot as required and then you should have a pretty stable system. It worked for my friend. Windows update will replace any old driver you have. __________________ _____________________________________________ Whatever problem you have...I didn't do it...It's not my fault Okay. But I'll help you..

10-14-2008, 02:09 PM	#9 (permalink)
prop_dynamic Registered User Join Date: Oct 2008 Posts: 12 OS: Vista Ultimate x64 SP1	Re: Vista Ultimate x64 SP1 random BSOD's Thank you for your reply, I will do that soon. Windows update did run first and it made some errors yeah. But I don't have a lot of time to be doing reformats as I have exams next week. I'll keep this in consideration and keep you posted on any progress

10-14-2008, 02:16 PM	#10 (permalink)
Nagrad Registered User Join Date: Oct 2008 Posts: 4 OS: Vista x86	Re: Vista Ultimate x64 SP1 random BSOD's I had a similar issue after reformatting my PC. I have an Asus Crosshair MB, the problem was caused when windows update decided to update the NVIDIA SATA drivers. I rolled back the drivers and bingo no more problem.

10-16-2008, 12:17 PM	#11 (permalink)
prop_dynamic Registered User Join Date: Oct 2008 Posts: 12 OS: Vista Ultimate x64 SP1	Re: Vista Ultimate x64 SP1 random BSOD's No reformat needed as I found the problem: My motherboard: An Asus P5Q3 Deluxe WiFi-AP@n seems to be incompatible with Corsair TW3X4G1333C9DHX DDRIII SDRAM. Even though it's on the QVL (http://asus.com/999/download/products/2273/2273_10.pdf) almost everyone has these problems: http://vip.asus.com/forum/view.aspx?...age=1&count=17 Corsair thread: http://www.asktheramguy.com/v3/showthread.php?t=73070 This is also true for OCZ DDRIII memory: http://www.ocztechnologyforum.com/fo...ad.php?t=39418 I'm one of the "lucky" few as most people couldn't even get an OS installed in the first place. Updating the BIOS doesn't seem to solve the problem completely/partially or will make it even worse. Now I will have to look for a new set of DDRIII memory that hopefully works (where are the good old days when ram would just work :() and contact my vendor. At least I'm happy I found the problem :D.

10-17-2008, 03:37 AM	#12 (permalink)
prop_dynamic Registered User Join Date: Oct 2008 Posts: 12 OS: Vista Ultimate x64 SP1	Re: [SOLVED] Vista Ultimate x64 SP1 random BSOD's My hardware vendor suggested the following solution: This problem occurs quite a lot and would be relatively easy to solve: -Remove one of the 2x2GB memory banks so you have effectively 2GB installed. -Install Windows Vista. -Update Windows Vista. (As I haven't tested this solution yet it would be wise to update your mobo drivers first (chipset, ethernet etc.etc.)) -Place the removed memory bank back. Everything should work without any problems now. I'm not gonna test this solution right now. It would explain the BSOD's I got while updating Windows Vista and that might have resulted in the corrupted nt module. I do think it will work as my hardware vendor has ALOT of experience and they wouldn't suggest this if it wouldn't work.

10-17-2008, 03:57 AM	#13 (permalink)
jcgriff2 Moderator, Microsoft Supp Join Date: Sep 2007 Location: The Great State of New Jersey - away from the gross corruption of the Riverside County, CA, SO office. SHAMEFUL ! Posts: 10,125 OS: Windows 7, Vista Ultimate My System	Re: [SOLVED] Vista Ultimate x64 SP1 random BSOD's Hi. . . Sorry that I missed all of this. For info, you may have had a problem with the ESET driver eamon.sys if you did not have the most recent version of ESET. I run ESET NOD32 on x86 and x64 systems here and did suffer a crash that named eamon.sys - and it turned out to ne that I had an older version of ESET installed that for some reason never got updated (virus defs were OK). Good Luck to you. Regards. . . jcgriff2 . __________________ . . . . . . . . BSOD Posting Instructions B Expecting a reply and waiting > 36 hours ? Send a PM to me containing a link to your thread Glad to be home in the Great State of New Jersey ! !

10-17-2008, 04:24 AM	#14 (permalink)
prop_dynamic Registered User Join Date: Oct 2008 Posts: 12 OS: Vista Ultimate x64 SP1	Re: [SOLVED] Vista Ultimate x64 SP1 random BSOD's Ok I'll keep that in mind the next time I try to install NOD32.

10-18-2008, 02:24 PM	#16 (permalink)
prop_dynamic Registered User Join Date: Oct 2008 Posts: 12 OS: Vista Ultimate x64 SP1	Re: [SOLVED] Vista Ultimate x64 SP1 random BSOD's Problem solved, Not installing any Asus related mobo drivers/utilities fixed the Asus ACPI not being installed and therefore not creating any 0x50 BSOD's XD. Quite sad though you can't install any Asus related software on an Asus mobo. Gonna plug the other 2GB DDR3 RAM in tomorrow so I can use my pc finally.