BSOD in RTM build 7600.16385.090713-1255 x64

[Typhos]

Hi !

I´ve gotten a BSOD twice after i installed this build (2 days ago)

In the reliability monitor it states the following
The computer has rebooted from a bugcheck. The bugcheck was: 0x0000001e (0xffffffffc0000005, 0xfffff800026f235f, 0x0000000000000000, 0xffffffffffffffff). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 071909-20389-0

does anyone know what this means ?

 

[Pepc619]

Maybe it is connected to ram? I'm just guessing because it's saying memory.dmp.

 

[Typhos]

i might add i´ve never had this issue while running x86 rc

problem came after i installed the 64 bit rtm

 

[keypox]

i might add i´ve never had this issue while running x86 rc

problem came after i installed the rumored 64 bit rtm

Fixed that for ya :sarc:

 

[xendrome]

i might add i´ve never had this issue while running x86 rc

problem came after i installed the 64 bit rtm

This is probably due to a device driver..

 

[Typhos]

thought crossed my mine aswell

anyway to narrow it down to what driver ?

 

[niea]

This might help.

0xFFFFFFFFC0000005 = Access Violation (AV error)
A system thread (i.e a thread running in kernel mode) attempted to access some memory that it doesn't have permission to, or is an invalid memory address. Get the minidump file and we may be able to pinpoint the faulting module/driver

STOP 0x0000001E = Kernel Mode Exception Not Handled. Same type of error (Access Violation = 0xC0000005). Probably caused by the same thing that caused the previous BugCheck, as these two errors are similar.

 

[Avien]

Memory error.

 

[Frostbite]

Try running the memory test tool in Windows 7 and see if that comes up with anything
http://www.sevenforums.com/tutorials/715-memory-diagnostics-tool.html

 

[usasma]

The memory dump file contains information that may help to figure out what caused it.
Upload it to a free filehosting service (I like Box.net | Simple Online Collaboration: Online File Storage, FTP Replacement, Team Workspaces ~ Free Version), share it, and post the link here so we can run an analysis on it.

 

[Dorfdad]

ive been having problem lately with my Video Card causing it (Hyper transport Synch Flood) was the bios error i was getting. Playing game it would be fine for a while than stutter up and lock up.

I found it was the video card heating up! Funny as my 4890 never did this before on old builds. Im playing Bionic Commando and if I adjust the fan speed manually in the the ATI settings it works. Weird that RTM would cause this!

 

[Colby89]

Windows 7 RC x64 worked flawlessly on my Inspiron 1520. Upgrading to RTM x64, both through a hacked upgrade, then through a clean install has been nothing but frustrating. Minidump crash analysis has shown multiple problems. First, the bluetooth causes almost daily crashes. I had AnyComm drivers installed, but even with deleting the device, and all associated drivers, then reinstalling with standard drivers did not fix the problem.

Intel Turbo Memory initially would not install, but with lots of tweaks, finally did, only to give hourly WHEA crashes! The newest release of intel drivers (link is provided in another thread) cured that problem.

As for antivirus, Norton IS 2009, which works without a problem on my desktop, in Win 7 64-bit, caused nearly hourly crashes. NIS2010 beta was no better. Computer Associates IS 2009 would not install, regardless of Troubleshooting Compatability. CA IS 2010, installed, but I hate their new interface! McAfee 2010 beta seems to work fine.

With all these frustrations, I am restoring to my RC image that luckily I created before starting this one week descent into RTM hell. I will use RC until I am forced to change. Maybe by then, the bluetooth and antivirus software will be compatible. I don't know why these problems are unique to RTM and not RC, and are unique to my laptop, not my desktop (Asus P5KE Deluxe Wifi-AP motherboard)???