BSoDs with no identifiable cause.

Aha! After a (depressing :p ) look back through my browser history I Googled the following code:

bcp1 000000000007FD2C

to no information.

I have the latest crash minidump but it makes no sense in notepad :p

I should add that I've run Memtest86+ and it came up with nothing. That and being able to run BOINC overnight makes me think it could be an issue with something random like heat on a southbridge.
 
Last edited:
http://msdn.microsoft.com/en-us/windows/hardware/gg463009

Download 'em, it's only WinDbg you need though. In WinDbg, click file, symbol path, and type

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

Then Ctrl+D to bring up the crashdump folder. Analyse the ones of your choice, should give you a proper code and faulting module when you click !analyze -v.

Another folder which'll give you your most recent crash dump in more detail is the root windows folder, name MEMORY.DMP. That's also worth a shot :)

It's a faff, but useful as hell. You can also use Whocrashed 3.01 but it's not as detailed.

EDIT: Also, turns out I had 4 different problems:
-Onchip Sata didn't like being disabled (Mine has two controllers, the Onchip one and a seperate Marvell one. For some reason disabling Onchip causes my IDE bus to malfunction.)
-My RAM doesn't like stock timings all of a sudden, has to be run 9-9-9-20 @1333mhz instead of 8-8-8-24 @1600mhz for some reason, both sticks :confused:
-Whatever it was that was fixed when I rebuilt
-Asus Anti-Surge causing ****e

Also, my memtest would come back with nothing too. :p
 
Last edited:
Code: 
---------

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

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED (7e)
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: fffff880041d739c, The address that the exception occurred at
Arg3: fffff88003cb6738, Exception Record Address
Arg4: fffff88003cb5f90, Context Record Address

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


EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

FAULTING_IP: 
dxgmms1!VIDMM_SEGMENT::InvalidateAllVirtualAddress+68
fffff880`041d739c 488b18          mov     rbx,qword ptr [rax]

EXCEPTION_RECORD:  fffff88003cb6738 -- (.exr 0xfffff88003cb6738)
ExceptionAddress: fffff880041d739c (dxgmms1!VIDMM_SEGMENT::InvalidateAllVirtualAddress+0x0000000000000068)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000000
   Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff

CONTEXT:  fffff88003cb5f90 -- (.cxr 0xfffff88003cb5f90)
rax=ee65764502080008 rbx=fffff8a0098bd010 rcx=fffffa8005579a10
rdx=fffff8a0098bd010 rsi=fffff8a00a0a6f70 rdi=fffffa80055976e8
rip=fffff880041d739c rsp=fffff88003cb6970 rbp=fffffa8005597670
 r8=0000000000000001  r9=0000000000000000 r10=fffffa80039739e0
r11=fffff88003cb6940 r12=fffffa80057cd500 r13=fffff8a00a0a6f70
r14=fffffa8003c603c0 r15=fffff8a00a0d5780
iopl=0         nv up ei pl nz na po nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010206
dxgmms1!VIDMM_SEGMENT::InvalidateAllVirtualAddress+0x68:
fffff880`041d739c 488b18          mov     rbx,qword ptr [rax] ds:002b:ee657645`02080008=????????????????
Resetting default scope

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  0

ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

EXCEPTION_PARAMETER1:  0000000000000000

EXCEPTION_PARAMETER2:  ffffffffffffffff

READ_ADDRESS:  ffffffffffffffff 

FOLLOWUP_IP: 
dxgmms1!VIDMM_SEGMENT::InvalidateAllVirtualAddress+68
fffff880`041d739c 488b18          mov     rbx,qword ptr [rax]

BUGCHECK_STR:  0x7E

LAST_CONTROL_TRANSFER:  from fffff880041a5749 to fffff880041d739c

STACK_TEXT:  
fffff880`03cb6970 fffff880`041a5749 : fffffa80`05597670 00000040`00000020 fffffa80`055976e8 00000000`00000001 : dxgmms1!VIDMM_SEGMENT::InvalidateAllVirtualAddress+0x68
fffff880`03cb6a30 fffff880`040e04b9 : fffffa80`05574000 fffffa80`05561010 00000000`00000000 fffffa80`05561928 : dxgmms1!VidMmInvalidateAllVirtualAddresses+0x39
fffff880`03cb6a60 fffff880`0410cdad : fffffa80`04e9c4e0 fffffa80`04e9c4e0 fffffa80`04e9c4e0 fffffa80`05561010 : dxgkrnl!DXGADAPTER::PrepareToReset+0x59
fffff880`03cb6aa0 fffff880`041b3f07 : fffffa80`04e9c4e0 00000000`00000000 fffffa80`045fa850 fffffa80`05561010 : dxgkrnl!TdrIsRecoveryRequired+0x245
fffff880`03cb6ad0 fffff880`041e1d5a : fffffa80`ffffffff 00000000`000c2444 fffff880`03cb6c30 00000000`00000002 : dxgmms1!VidSchiReportHwHang+0x40b
fffff880`03cb6bb0 fffff880`041af29e : fffffa80`05561010 ffffffff`feced300 fffffa80`045fa850 00000000`00000000 : dxgmms1!VidSchWaitForCompletionEvent+0x196
fffff880`03cb6bf0 fffff880`041dbe7a : 00000000`00000000 fffffa80`045fa850 00000000`00000080 fffffa80`05561010 : dxgmms1!VidSchiScheduleCommandToRun+0x1b2
fffff880`03cb6d00 fffff800`02d80cce : 00000000`0ad2a661 fffffa80`05579a10 fffffa80`039739e0 fffffa80`05579a10 : dxgmms1!VidSchiWorkerThread+0xba
fffff880`03cb6d40 fffff800`02ad4fe6 : fffff880`02f63180 fffffa80`05579a10 fffff880`02f6dfc0 fffff880`0106bcb0 : nt!PspSystemThreadStartup+0x5a
fffff880`03cb6d80 00000000`00000000 : fffff880`03cb7000 fffff880`03cb1000 fffff880`06fa9b70 00000000`00000000 : nt!KxStartSystemThread+0x16


SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  dxgmms1!VIDMM_SEGMENT::InvalidateAllVirtualAddress+68

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: dxgmms1

IMAGE_NAME:  dxgmms1.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4ce799c1

STACK_COMMAND:  .cxr 0xfffff88003cb5f90 ; kb

FAILURE_BUCKET_ID:  X64_0x7E_dxgmms1!VIDMM_SEGMENT::InvalidateAllVirtualAddress+68

BUCKET_ID:  X64_0x7E_dxgmms1!VIDMM_SEGMENT::InvalidateAllVirtualAddress+68

Followup: MachineOwner
---------
 
I had the same BSoD once or twice, it's something related to DirectX but in my case it was solved by reseating memory and cleaning the slots out. Try an sfc /scannow too.

Are the others similar? If it's a repeating error it indicates something wrong softwareside or possibly graphics-related.
 
RAM slot voodoo done :p

Nothing on sfc /scannow

The other dumps aren't there - I think I cleaned them out with CCleaner :(

Will just wait and see now. Thing is the other 3 times happened outside of a game but I guess that could've been due to Aero.
 
Well \I hope you lot have finaly got rid of your bsods. been haveing mine for over a year.
each time it would be some different numbers or it would say page fault etc, or anything or nothing. but each time i would be able to get to desktop after restart. would go great for days or a week or weeks or an hour before next bsod.

today it bsoded in morning and still can't get to desktop. took ram out, put in one stick, swaped. pulled out the sata cables from everything except OS hd. No go. Swapped graphics card, no go. Changed from 5-5-5-18-2T to the rams 4-4-4-12-2T then back to everything Auto & defaults. Still the same.

Last couple of goes has given me this
0x0000007E (0xc0000006, 0x80696C12, 0xB84C36E4, 0xB84C33E0

Don't think there be any point in Re-Formating and starting again as I've done that 4 times over last few months with no change. I am at a loss.

Mobo--Asus M2N-SLI DELUXE.
 
Defaults - 1.30V for CPU I think.

Core unlocking doesn't need any more Volts, just doubles the amps.
Click to expand...

Damn, ah well it was worth a shot. Only other thing I can think of is stripping the system and rebuilding, and setting everything in the BIOS manually.

@above - you able to upload any minidumps if you can get into windows mate? Tried Memtest? I'd also take everything non-essential out for testing purposes, i.e down to HDD, one stick of RAM (in a different slot than usual preferably), CPU, and GFX.
 
hI, spleenharvester
done all that m8, that's why i'm at a loss, stumped. i can't seem to get my cpu out, gawd knows what i doing wrong. it's solidly in place. swapped graphics card, put each ram in different slot and vice versa. did memtest other day for dozenth time, no errors.
can't back to desktop to try anything else. just tried hirens boot cd and did the things i understood, still no getting into desktop. it's a brand new hdd and nothing wrong with the old one. second asus mobo to go up creek on me from oc over the years. might stick my old K8N-E Deluxe back up now that I've fixed it. New mobo and CPU on that un.
really stumpped on this. only other thing i can think of is PSU or mobo. Though If PSU surely i'd not get into bios.
 
Then you're in my/our boat again mate :(

Mine's started off again after nearly a week of perfectly working. Started off the same day I OC'ed my graphics. Coincidence? :S

Eitherway, I can't help but wonder if something is coming unseated, if I reseat it all it works for a while then goes again. :(
 
Have you tried doing a fresh install and installing drivers/software one at a time and running for a couple days each time?

Thats what I ended up having to do with my laptop.. Turned out it was Daemon Tools causing my BSoDs!
 
Street said:
Have you tried doing a fresh install and installing drivers/software one at a time and running for a couple days each time?

Thats what I ended up having to do with my laptop.. Turned out it was Daemon Tools causing my BSoDs!
Click to expand...

Hmmmm, I might uninstall daemon for me then. Haven't bothered to swap my motherboard which I was going to do this weekend.

Anybody know any other decent virtual drive apps?
 
me227 said:
Anybody know any other decent virtual drive apps?
Click to expand...

http://www.slysoft.com/en/virtual-clonedrive.html

:)

Also, in other news, my rig has just started with these random BSOD as well.

It's been solid for months, spent all last week playing Crysis2 on it no fuss.

Then all of a sudden over the last couple of days i've had it BSOD while sat at desktop, or while browsing etc.

Yet all tests pass no problem, Linx, OCCT, Prime, Memtest, all clean.



Yesterday I BSOD watching a youtube vid, then rebooted and locked up logging in, but then it was fine for the rest of the day.


Makes no sense :confused:
 
I've been having problems like this for about 4 months

Memtest 86 runs faultlessly overnight with all 3 RAM sticks in, or one at a time and swapping slots around. Prime95 can run endlessly with no issues too.

Swapped out the PSU, GFX, bought a new HDD and DVD-RW, done 2 clean installs despite the old HDD not showing errors. Driver verifier reports nothing
I'm currently running with nothing but the basics to see if it'll be stable for any longer than a week, that's my current record. Despite the fact you guys seem to be on MSI & Asus boards, Im on a Gigabyte with a Core i7. Are you all running Win7 x64 ? My latest install is only 2 days old, applied security and reliability updates, but not SP1. Only installed drivers that came on the Win7DVD apart from Catalyst 10.11 (briefly tried 11.3 but that bluescreened yesterday so I uninstalled and reverted to a version I trust).

I've tried so many different BIOS settings I can't count.

If I get anything even close to improved reliability I'll post what might have worked
 
I had a new error message last night.

"A clock interrupt was not received on a secondary processor"

It happened 3 times last night after being fine for days. I still haven't bothered to change my m/board with the new one sitting on my floor yet. :p

I had a quick look online with that message and it seemed to be more people with Asus boards and they suggested it could be a possible incompatibility. I read about underclocking the processor by about 2%. I gave it a go and its been fine so far.

This was the first time I'd seen that BSOD before, normally it was similar to the ones people were having in this thread.
 
I'm still getting mine if that's any consolation. :p

Mine will either hard lock or BSoD (usually on attempting to shut down) with 0x50/"Faulting module memory_corruption".

I'll take a look round, could be interesting. Odd how mine'll work for a few days then die again. Though through that, I've determined it's not a BIOS/setting issue.

One theory is I have a weak CPU socket or similar and the heatsink is making the CPU work its way out slowly, hence working perfectly after reseating.

Cheers
 
I'm 100% sure it's the board now, everything seems to work in the other PC. Filed an RMA request but I doubt it'll go through - it says "14 day warranty" on the page but apparently all the B-grades are meant to have 60 day warranty? :S

EDIT: RMA accepted :D

EDIT2: From an auction site listing and another forum -

I am selling this as faulty because sometimes it just will not start up. When it is running it will run stable, until it blue screens or freezes and then you know it will not start up. I dont know what is wrong with it, I dont have a spare CPU to try it with or any DDR3 RAM but I have tried another graphics card and it made no difference, so I havent really gone into any troubleshooting. I think it has the latest BIOS but its been a while since I did anything with it to be honest.
Click to expand...

M4a79xtd evo & OCZ DDR3 PC3-12800 blue screen

At the moment I have the timings as 9-9-9-24, 2TD, voltage at 1.5 (I cant seem to input the reccomended 1.35? any lower than 1.5 and it changes it to automatic), freq 1600...

It works for about 2 days, then it will start to blue screen on me. Then if I change the voltage or frequency to something different, restart, and then change them back to the above again, it works for another couple of days then starts to blue screen again (i'm new at this)

Also with these settings, if i try to do the core unlocker that the motherboard has, it just says failed to boot on overclocking settings etc. So am i even getting the best out of the chips i have bought?? Any help appreciated as this is becoming very annoying and am considering getting a different motherboard as it has other issues too. I have installed latest chipset and bios etc....
Click to expand...

Both the same issues as me. Anyone else with this board, have you had similar problems?

I will keep y'all updated.
 
Last edited:
You must log in or register to reply here.
Back
Top Bottom