BSOD on fresh x64 Windows 7 Install

[nomis42]

Hey,

Just wondering if anyone can help. Installed
I'm getting BSOD within a minute of startup of a fresh Windows 7 x64 Install.

I've tried changing RAM and a couple of other things.
I have as of yet not installed any programs, just updated my graphics card driver

I can boot into safe mode without a problem.
I can't see any hardware conflicts.

I am getting a IRQL_NOT_LESS_OR_EQUAL error on the BSOD.
I was also getting a Win32.sys error.

Any help would be greatly appreciated.

Attached are the 4 latest dump files.

Simon.


http://www.google.ie/url?sa=t&sourc...vIjnBg&usg=AFQjCNEHChAezJVNQpmO_1bxlpG3JQjZdA

 

[zigzag3143]

Hey,

Just wondering if anyone can help. Installed
I'm getting BSOD within a minute of startup of a fresh Windows 7 x64 Install.

I've tried changing RAM and a couple of other things.
I have as of yet not installed any programs, just updated my graphics card driver

I can boot into safe mode without a problem.
I can't see any hardware conflicts.

I am getting a IRQL_NOT_LESS_OR_EQUAL error on the BSOD.
I was also getting a Win32.sys error.

Any help would be greatly appreciated.

Attached are the 4 latest dump files.

Simon.

Simon

Hi and welcome

You have 3 distinct causes for these BSODs. First the directx portion of your video driver. The second is memory corruptoion, and the third are win 7 files

For the first I would completely remove the current driver and download a fresh copy. Install only the driver and not the rest of the things that usually get installed with them.

For memory corruption I would download memtestx86 burn it to a cd and run it for at least 5 passes.

For the win 7 files I would run a system file check
(type cmd in search>right click>sfc /scannow)

Let us know if you need more help

Ken

BugCheck D1, {fffff80001f02f50, 2, 8, fffff80001f02f50}
Probably caused by : dxgmms1.sys ( dxgmms1!VidSchiWaitForSchedulerEvents+1bc )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
BugCheck A, {a4400000000, 2, 0, fffff80002893317}
Probably caused by : win32k.sys ( win32k!SURFACE::Map+a1 )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
BugCheck A, {0, f, 0, fffff80002df6fde}
Probably caused by : pci.sys ( pci!PciReadSlotConfig+84 )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
BugCheck 4E, {99, 73a02, 0, 74282}
Probably caused by : memory_corruption ( nt!MiBadShareCount+4c )

 

[nomis42]

Hey Ken,

Thanks for the info and suggestions.

I ran the memtestx86: passed with more than 8 passes.
The System File check was fine: Windows Resource Protection did not find any integrity violations.

I removed all graphics drivers etc., but the display drivers seem to be the problem.
It stills gives me a BSOD with a minute of so even just sitting on the desktop.
I think it may be a atikmdag.sys problem....

any ideas what else you think it may be.
I have attached the 2 latest dump files.

Simon.

 

[zigzag3143]

Hey Ken,

Thanks for the info and suggestions.

I ran the memtestx86: passed with more than 8 passes.
The System File check was fine: Windows Resource Protection did not find any integrity violations.

I removed all graphics drivers etc., but the display drivers seem to be the problem.
It stills gives me a BSOD with a minute of so even just sitting on the desktop.
I think it may be a atikmdag.sys problem....

any ideas what else you think it may be.
I have attached the 2 latest dump files.

Simon.

Checking Now

 

[zigzag3143]

Hey Ken,

Thanks for the info and suggestions.

I ran the memtestx86: passed with more than 8 passes.
The System File check was fine: Windows Resource Protection did not find any integrity violations.

I removed all graphics drivers etc., but the display drivers seem to be the problem.
It stills gives me a BSOD with a minute of so even just sitting on the desktop.
I think it may be a atikmdag.sys problem....

any ideas what else you think it may be.
I have attached the 2 latest dump files.

Simon.

Correct. One was caused by it and the other was probably caused by it. The only way to really fix this is to completely remove the current software (they may have a removal tool), everything.

Then download and install a fresh copy of the driver only.

Also of note is an old FET6 driver listed below.

Let us know if you need help with any of that


Ken

BugCheck 116, {fffffa800199f4e0, fffff88002cdb40c, 0, 2}
Probably caused by : atikmpag.sys( atikmpag+640c )

Old driver

fffff880`04811000 fffff880`0481cb00   fet6x64  fet6x64.sys  Thu Jun 19 07:40:18 2008 (485A45A2)