P55-GD65 BSOD With onboard audio enabled

Hello all,
I bought a new computer with a P55-GD65 motherboard 2 weeks ago and Im getting a random blue screen when the onboard audio is enabled in the BIOS.
Im using the latest BIOS version mainboard drivers. Im running a legal version of Windows 7 home premium and installed all updates.
The blue screen appears in all situations, browsing the internet, playing a game, even when the machine is just turned on and im not working on it.
Here parts of the latest dump files:
1. string:SYSTEM_SERVICE_EXCEPTION
bug check code: 0x0000003b
caused by driver: win32k.sys
2. string: KMODE_EXCEPTION_NOT_HANDLED
bug check code: 0x0000001e
caused by driver: ntoskrnl.exe
II did search a lot for this errors and found no relationship with onboard audio, the weird thing is the BSOD are only happening when onboard audio is enabled on my system.
Any idea how to fix this, it would be great because the onboard audiocard is working alright with games and teamspeak. I have tried a X-FI Titanium card of Creative that was not working.
Hope someione can help.
Kind regards,
Lex

Sorry, here is a full list of my hardware and software configuration.
BIOS version: version 1.5 091102
OS: Windows 7 Home Premium x64 (updated)
Software installed:
MCAfee VS 8.7 patch 2
Call of Duty Modern Warfare
Eve Online client
Teamspeak client RC2
Hardware:
Case: Loan Li PC-P80
PSU: be quiet dark power pro 750w
Motherboard: MSI P55-GD65
CPU: Intel Core i7-860 2899 1156
CPU Coller: Scythe Mugen 2 SCMG-2000
RAM: 4GB (2 modules of 2GB): OCZ Platinum Low Voltage OCZ3P1333LV4GK
HD: Intel SSD 80GB 70/250 X25M
DVD r/w: Sony NEC Optiarc AD-5240S
Video: Gigabyte GTX 280 with 195.62 Win7 x64 whql driver
Installed all latest x64 MSI drivers for the motherboard.
I am not overclocking the system, the BIOS has default values with onboard audio disabled at the moment.
Now once again the problem:
If I enable the onboard audio controller the systems crashed with a blue screen. Somethimes it takes an hour, somethimes it crashed within 2 minutes after booting.
It doesnt matter what Im doing, even when I just startup the machine and aint using it because Im making some cofee its stuck at a blue screen when I come back.
If I disable the onboard audio controller It does not crash, I can leave the system on all day without a problem.
Hope someone can help.

Similar Messages

P55-GD65 BSOD Issues, Help very much appreciated!

Hi Guys,
I recently bought a new PC with a P55-GD65 motherboard and Im getting a lot of blue screens.
I started a topic on SevenForums and attached all dump files but it seems the problem is hard to pin down.
The topic and dump files can be found here: http://www.sevenforums.com/crashes-debugging/48197-please-help-bsod-new-windows-7-x64-pc.html
Im using the latest BIOS (1.5), Im running Windows 7 x64 Home Premium with latest updates and Im using the latest MSI drivers for the Motherboard.
The only software installed is:
- Eve Online client
- Steam and Modern Warfare 2
- Teamspeak RC2
- MS Security Essentials
- PC Angel (revovery software)
On SevenForums I was advised to check my harddrives, I runned HD Tune and my drives showed no errors.
I was also advised to run memtest, Im running it for over 4.5 hours now without any errors.
I realy dont know what I can do anymore. Do you guys have any advise what else I can try?
I have changed nothing in the BIOS itself and Im not overclocking the system.
Should I manually adjust some settings maybe?
Below is my hardware configuration:
CPU: Intel Core i7-860 2899 1156
Motherboard: MSI P55-GD65 (BIOS 1.5)
Memory: 4GB (2 modules of 2GB): OCZ Platinum Low Voltage OCZ3P1333LV4GK
Graphics Card Gigabyte GTX 280 (latest nvidea driver)
PSU: Be Quiet dark power pro 750w
Monitor(s) Displays Samsung 226BW
Case Lian Li PC-p80
Cooling CPU: Scythe Mugen 2 SCMG-2000, VGA: Stock case: Stock
Hard Drives System drive: Intel SSD 80GB 70/250 X25M data: 160GB 10k raptor
I hope someone can help.
Thanks in advance

Quote from: Wonkanoby on 17-February-10, 22:46:31
http://www.ocztechnology.com/products/memory/ocz_ddr3_pc3_10666_platinum_low_voltage_dual_channel
try 1.65 or 1.7v

MSI P55 GD65 - BSOD - MEMORY_MANAGEMENT

I'm facing a weird issue with my pc:
If I turn on the PC, the system starts up fine, but within 30 secs up to 5 minutes I get a BSOD (usually MEMORY_MANAGEMENT).
If I then restart the system it will run fine..
CPU intensive gaming, memory checks, benchmarks, standby and wakeup, all runs fine... after a first BSOD.
I've tried all kinds of memory settings, but nothing seems to help. Also hard to test if it runs fine after a crash.
It's almost like the system needs to warm-up a bit and then it will run fine
The BSOD message indicates a memory issue, but then I would expect random BSOD, not only right after cold start.
Any suggestions?
MSI P55 GD65 - latest 1.9 bios
i875k
Windows 7 64bit
Geil DDR3-1600 2x2GB Black Dragon GB34GB1600C8DC
This Geil ram is not in the MSI memory list but Geil shows the MSI P55 GD65 in their compatibility list for this memory:
"All motherboards listed on the GeIL Qualified Motherboard List – GQML have been tested with the specified GeIL memory kits for compatibility, stability and
performance by GeILs’ FAE to ensure best quality."
http://www.geil.com.tw/uploads/download_files/c8c397a9533d1896e708e3c106a99cb3.pdf

Status update:
I've reset the bios to safe defaults.
Started up memtest86+ and screen turned red rather then blue, so lots of mem-errors.
Restarted and then memtest ran fine for more then 10 hours.
Passed 20 times all tests no errors with both Dimms inserted.
Then I tested cold start with 1 dimm only:
- with 1 DIMM in slot 3 only system cold-starts fine and memtest runs fine with no errors.
- with 1 DIMM in slot 1 only system cold-starts fine and memtest starts up but then doesn't even start a test. So it seems to be hanging already.
Swapping both dimms showed the same result.
Preliminary conclusion now is a faulty slot 1
Does it indeed sound like a slot 1 issue?
MB is the worst part to RMA, so hopefully I can find a solution.... slot 1 seems not to be completely broken after all.
PS: increasing to 1.6V I had already tried before without success.

P55-GD65 BSODs

The last two weeks I've experiencing fairly frequent (1 or 2 a day) BSODs. They are 4 or 5 different ones that happen.
I'm running the following equipment:
MSI P55-GD65
Win 7 64 bit
i7-860
Two sets of G.SKILL Ripjaws Series 4GB (2 x 2GB) 240-Pin DDR3 SDRAM DDR3 1600 (PC3 12800) Desktop Memory Model F3-12800CL7D-4GBRM
SAPPHIRE Vapor-X 100281VX-2SR Radeon HD 5870 1GB 256-bit GDDR5
APC BR1500LCD 1500VA 865 Watts 8 Outlets BACK-UPS RS
SAMSUNG Spinpoint F3 HD103SJ 1TB 7200 RPM 32MB Cache SATA 3.0Gb/s 3.5" (raid 5)
CORSAIR HX Series CMPSU-850HX 850W
LG Black 8X BD-ROM 16X DVD-ROM 40X CD-ROM SATA
Thermaltake Armor water cooled box.
This system has been running this configuration for about 3 months. Temps are around 19 at idle and high 40s under 100% load. When the BSODs started I first ran memtest86 and found no problems. I have a second rig and swapped out the following
Replaced CPU with second i7-860.
Replaced memory with two sets of CORSAIR XMS3 4GB (2 x 2GB) 240-Pin DDR3 SDRAM DDR3 1333 (PC3 10666)
Replaced Video card with SAPPHIRE 100215L Radeon HD 3870 512MB 256-bit GDDR4
Made sure that all the drivers were up to date and tried various versions of bios.
I'm still getting BSODs. Only thing the same are Motherboard, disks, OS and PSU. Since most BSODs are related to drivers or Memory problems I believe that it may be the mother board which is bad. Time to RMA the board?
Dan

Here are all the errors. The system was totally clean before 22 May.
22 May
The computer has rebooted from a bugcheck. The bugcheck was: 0x0000000a (0x0000000000000028, 0x0000000000000002, 0x0000000000000000, 0xfffff80003305410). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 052210-25334-01.
The computer has rebooted from a bugcheck. The bugcheck was: 0x00000019 (0x0000000000000020, 0xfffffa80069d6bd0, 0xfffffa80069d6c30, 0x0000000004060017). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 052210-24460-01.
The computer has rebooted from a bugcheck. The bugcheck was: 0x00000019 (0x0000000000000020, 0xfffffa80069d6bd0, 0xfffffa80069d6c30, 0x0000000004060017). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 052210-24460-01.
27 May
The computer has rebooted from a bugcheck. The bugcheck was: 0x00000019 (0x0000000000000020, 0xfffffa80069d59e0, 0xfffffa80069d5ab0, 0x00000000040d0007). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 052710-29078-01.
The computer has rebooted from a bugcheck. The bugcheck was: 0x00000034 (0x000000000000077a, 0xffffffffc0000420, 0x0000000000000000, 0x0000000000000000). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 052710-30841-01.
The computer has rebooted from a bugcheck. The bugcheck was: 0x000000d1 (0x0000000000000020, 0x0000000000000009, 0x0000000000000000, 0xfffff88004e0b7d7). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 052710-26582-01.
28 May
The computer has rebooted from a bugcheck. The bugcheck was: 0x0000001a (0x0000000000000411, 0xfffff680000d9f10, 0xf5500001bdf32886, 0xfffff8a0108b57b9). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 052810-26379-01.
29 May
The computer has rebooted from a bugcheck. The bugcheck was: 0x000000d1 (0x000000010000006f, 0x0000000000000002, 0x0000000000000000, 0xfffff88001a368f9). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 052910-32479-01.
The computer has rebooted from a bugcheck. The bugcheck was: 0x00000024 (0x00000000001904fb, 0xfffff8800374d5c8, 0xfffff8800374ce30, 0xfffff8000322f9e9). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 052910-36270-01.
30 May
The computer has rebooted from a bugcheck. The bugcheck was: 0x0000004e (0x0000000000000099, 0x00000000000bf20e, 0x0000000000000003, 0x0000000000209de5). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 053010-26083-01.
31 May
The computer has rebooted from a bugcheck. The bugcheck was: 0x00000024 (0x00000000001904fb, 0xfffff8800b67a8d8, 0xfffff8800b67a140, 0xfffff880016c172f). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 053110-28158-01.
The computer has rebooted from a bugcheck. The bugcheck was: 0x00000019 (0x0000000000000020, 0xfffffa800ca6c270, 0xfffffa800ca6c740, 0x00000000044d0005). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 053110-27924-01.
The computer has rebooted from a bugcheck. The bugcheck was: 0x0000001a (0x0000000000000403, 0xfffff68000103670, 0xa12000022385c867, 0xfffff6800002b840). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 053110-29920-01.
1 June
The computer has rebooted from a bugcheck. The bugcheck was: 0x0000001a (0x0000000000041201, 0xfffff680000243d8, 0x97b0000066e89867, 0xfffffa800c772810). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 060110-29811-01.
2 June
The computer has rebooted from a bugcheck. The bugcheck was: 0x0000004e (0x0000000000000099, 0x000000000020ad1d, 0x0000000000000003, 0x0000000000016a25). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 060210-22682-01.
The computer has rebooted from a bugcheck. The bugcheck was: 0x0000001a (0x0000000000000031, 0xfffffa800d81fa50, 0xfffff8800820c000, 0xfffff8a00e4be67d). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 060210-23899-01.
The computer has rebooted from a bugcheck. The bugcheck was: 0x0000003b (0x00000000c0000005, 0xfffff800035b8f1a, 0xfffff8800c0dde00, 0x0000000000000000). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 060210-33805-01.
The computer has rebooted from a bugcheck. The bugcheck was: 0x0000004e (0x0000000000000099, 0x00000000001f6fe9, 0x0000000000000003, 0xffffffffffffffff). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 060210-24835-01.
The computer has rebooted from a bugcheck. The bugcheck was: 0x0000003b (0x00000000c0000005, 0xfffff8000352f90d, 0xfffff8800ad85080, 0x0000000000000000). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 060210-30279-01.
The computer has rebooted from a bugcheck. The bugcheck was: 0x0000003b (0x00000000c0000096, 0xfffff800032da873, 0xfffff8800be47600, 0x0000000000000000). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 060210-31574-01.
3 June
The computer has rebooted from a bugcheck. The bugcheck was: 0x00000050 (0xfffffbbc0209541b, 0x0000000000000000, 0xfffff800032d543b, 0x0000000000000007). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 060310-23337-01.
The computer has rebooted from a bugcheck. The bugcheck was: 0x0000001a (0x0000000000000411, 0xfffff680000203d8, 0xb310000169bc8886, 0xfffff6800004fca1). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 060310-22838-01.
The computer has rebooted from a bugcheck. The bugcheck was: 0x0000004e (0x0000000000000099, 0x0000000000124b4a, 0x0000000000000002, 0x0000000000123bb4). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 060310-25272-01.
The computer has rebooted from a bugcheck. The bugcheck was: 0x0000004e (0x0000000000000099, 0x0000000000172aeb, 0x0000000000000002, 0x00000000001721ea). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 060310-31995-01.
4 June
The computer has rebooted from a bugcheck. The bugcheck was: 0x00000050 (0xfffff88004bfb000, 0x0000000000000000, 0xfffff88004eb56a0, 0x0000000000000000). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 060410-33665-01.
5 June
The computer has rebooted from a bugcheck. The bugcheck was: 0x0000007e (0xffffffffc0000005, 0xfffff88001274efa, 0xfffff88003b398b8, 0xfffff88003b39120). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 060510-25989-01.
The computer has rebooted from a bugcheck. The bugcheck was: 0x0000007e (0xffffffffc0000005, 0xfffff80003309371, 0xfffff8800375b0e8, 0xfffff8800375a950). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 060510-25677-01.
The computer has rebooted from a bugcheck. The bugcheck was: 0x00000034 (0x0000000000000c72, 0xffffffffc0000420, 0x0000000000000000, 0x0000000000000000). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 060510-27315-01.
The computer has rebooted from a bugcheck. The bugcheck was: 0x000000f4 (0x0000000000000003, 0xfffffa800c6d3b30, 0xfffffa800c6d3e10, 0xfffff8000358c540). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 060510-26176-01.
The computer has rebooted from a bugcheck. The bugcheck was: 0x0000001a (0x0000000000000411, 0xfffff6800001a270, 0xa2f0000223f1c886, 0xfffff8a00aec7c29). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 060510-29343-01.
The computer has rebooted from a bugcheck. The bugcheck was: 0x0000004e (0x0000000000000099, 0x00000000005422f1, 0x0000000000000003, 0xccccccccccc35f20). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 060510-33228-01.
The computer has rebooted from a bugcheck. The bugcheck was: 0x000000f4 (0x0000000000000003, 0xfffffa800c0f9940, 0xfffffa800c0f9c20, 0xfffff8000358c540). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 060510-34055-01.

Can't load Mandrake 9 with onBoard sound enabled.

Any ideas as to why?
I can not boot into Mandrake 9 when I have onBoard sound enabled, it always freezes when it tries to load the i810 sound interface system. Yet when I disable it in the bios it loads perfectly.
I've already installed the nForce system drivers and that didn't help at all. Likely because it didn't know the sound card was there to install for.

I know your problem.Your not editing the modules.conf and adding these lines.Use vi command to edit.You may have one or more of these lines in your modules.conf and will only need to add the ones you don't have.I only had to add the audio line.
#vi /etc/modules.conf,press INSERT key, add the following lines,
alias eth0 mcpeth
alias sound-slot-1 i810_audio
alias usb-interface usb-ohci
press ESC, (Shift) colon, wq and Enter.
This will save the changes you made.

New P55-GD65 System with old already installeWindows 7 doesn't boot, Blue screen

I just built my new system with these specs
1. Core i5
2. P55-GD65
3. Kingston 2x2gb 1333Mhz DDR3
4. MSI N275GTX Twin FROZR
5. 650watt PSU
6. Sony DVD/CD RW+
7. BIOS Ver 1.2
I had a 500gb SATA WD HDD which i used with my old system, with windows 7 ultimate 32bit and windows xp 64bit installed. It was working pretty fine with that system. When i built this new rig, i installed the same HDD with it but wt i now face is that my win7 doesn't boot. Soon after windows 7's logo appears, the system reboots after a short blue screen. On reboot win7 asks for a startup repair . . . when i go for it, it fails to repair. I get the following thing in error;
Problem event name: StartupRepairOffline
Problem Signature 01: (win 7's version is listed here - the same goes for Prob Signature 02)
Problem Signature 03: Unknown
Problem Signature 04: 21201167
Problem Signature 05: AutoFailover
Problem Signature 06: 6
Problem Signature 07: CorruptAcl
Locale ID: 1033
I even tried to go for Repair through Windows 7 CD but in vain.
Can anybody help me here. I really don't want to go for a fresh installation.
Regards,
Bkee
P.S
My XP 64bit works pretty fine wid it although some drivers for "SM BUS Controller" and "Base System Cannot" can't be found.. The problem is only wid win7.

Quote
will give a try to install msi drivers using my old system and then connecting the HDD back to this new rig.... Hope it will work...!!!!
That activity is pointless. You cannot install drivers for stuff that is not there on your old system.
Please do yourself a favour and stop dancing around this whole problem (which seems like a pseudo-problem to me). Putting on a fresh installation of the operating system is the first thing that should be done on a new system configuration. Even if you manage to get stuff working without reinstalling, you are working with a potential driver mess and a confused Windows Registry that may throw problems at you that you may currently not be an issue.

P55-GD65 sound with HT Omega Striker 7.1

mobo = MSI P55-GD65
audio = PCI-e HT Omega Striker 7.1
Win 7 64
Should 9-pin HDAudio/EAR_MIC cable plug into FP Audio connector on Omega Striker sound card, or into JAUD1 connector on mobo?

There is an Intel 9-pin (one no pin) High Def Audio connector linked to the front panel of the case (Antec P183). Case manual says to connect that to the internal audio connector "on motherboard or sound card."
Now that I think about it, connecting to sound card makes most sense; only connect to mobo if no sound card. Guess this is one of those duh... moments - just had to think it through.
If someone can verify my thinking is correct, I'll just swallow my pride and move on to the next conundrum.
Thanks!

P55-GD65 bsod(es)

just built the following:
P55-GD65
intel i5
OCZ3G10664GK (1066 cl7 2x2gb) @ 1.6v
2x 4870
ABT-730MM 730W RT (certified 730w psu)
that's all of the important stuff.
After a week of trying to figure these problems out and giving up. I've deiced to come to you guys.
memtest fails. vista's memory test fails. occt's cpu/memory test fails. hyper pi fails. the system blue screens about every 30m.
This is in vista home x64 and in 7 business x64. Data get corupted. If i copy a file or download a file, it will not run.
the only way to fix this is to turn off turbo boost AND run my memory at 800 instead of 1066.
i have access to another system using the "GIGABYTE GA-P55-UD6" and both the chip and the ram work with turbo and at rated speeds without issue.
browsing the forums on tomshardware and on anandtech several others are having these same issues. everyone says the 1.4 bios will fix it.
My options until that is released?

Please post screenshots of the CPU-Z "SPD" and "Memory" views.

Xpower Bigbang//BSOD with OC GENIE enabled???

So recently I upgraded from a Corsair H70 to a Corsair H100 and after all thing were completed I restarted and re-enabled OC Genie and now it is causeing BSOD's...I have also tried doing a small OC manually and I get the same results..No other hardware has been changed...QUestion is what could cause this??
Xpower Bigbang X58 mobo
i7 950
Corsair XMS3 1066 6gigs.
Note prior to the install of this new cooler I never had an issue with OC GENIE***

Fredrik, the OC Genie I believe is the onboard hardware switch he is referring to. You activate it before system start and it applies a pre-set factory OC to the BIOS.
If the only thing that was changed is the cooler, then I would recheck the seating of the CPU. With the removal and install of the waterpump/heatsink it may have caused a slight move of the CPU itself. Also recheck all your cable connections

915G Neo2 won't boot win XP with onboard LAN enabled

Just wondering if anyone can solve my problem. Have got a 915G Neo2 board running with Windows XP. On enabling the onboard LAN in the BIOS it won't boot Windows....the following error is displayed on a windows blue screen
"0x0000007E pci.sys - Address F75DE0BF base at F75D7000"
Anyone got any idea how i can get this to work?
Thanks.

Moan Guide

MSI P55-GD65 - Problem with automatic fan control.

Hello.
I wish to share story of my fan speed controller.
Lately I've upgraded my machine to modern specs (look at signature) and I was quite happy about that.
It worked flawlessly for about week.
My H/W Bios settings was - CPU Smart Fan Target = 60°C and minimal fan speed 50%.
I was amazed how nicely GD65 maintained between heat and speed.
Yesterday, I've noticed that my fan is really quiet all the time, even when gaming (before it accelerate speed while hardcore gaming settings). I was quite content about that, until my computer crashed due to overheating while playing Battleforge match.
After reboot I've ran Intel BurnTest and HWmonitor. OH my, what was my surprise when I saw that fan speed is always 50% and do not speeds up when cores are heating up!
I started to checking things out. What I've discovered:
-(CPU Smart Fan ON) Fan is always at minimal speed given in BIOS. It doesn't accelerate even if CPU is burning.
-(CPU Smart Fan ON) Fan speed cannot be controlled by any program (like SpeedFan).
-(CPU Smart Fan OFF = 100% fan speed) Fan speed CAN be controlled by program like SpeedFan, which saves me from fan buzzing.
I've try to fix that by:
-Checking cables.
-Clearing CMOS.
-Updating BIOS to 1.6.
-Praying.
And still nothing.
My conclusion:
Fan speed cannot be change when Smart Fan is on, it locks fan speed at minimal speed given in bios.
Now I just hoping that this is somehow stock fan fault, new Zalman CNPS 10X QUIET is in delivery.

No problem here with Target 55° and Speed 37.5%.
Fan runs at 1330 below 58° and 2050 above which is max.
The CPU is running at 3050 MHz because of XMP 'overclocking'
Have reverted to BIOS version 1.3, due to XMP problems with other versions.

MOVED: Xpower Bigbang//BSOD with OC GENIE enabled???

This topic has been moved to Intel Core-iX boards.
https://forum-en.msi.com/index.php?topic=155073.0

Fredrik, the OC Genie I believe is the onboard hardware switch he is referring to. You activate it before system start and it applies a pre-set factory OC to the BIOS.
If the only thing that was changed is the cooler, then I would recheck the seating of the CPU. With the removal and install of the waterpump/heatsink it may have caused a slight move of the CPU itself. Also recheck all your cable connections

BSOD with graphics card enabled

Hey guys. Just wanted to stop in to help fix my problem at the moment I have a z77a-g45 board. I took old parts from my old build and put them into the board. all the parts were in completely functional in the old build no bsod.
I ran the msi on integrated graphics and I wouldn't get any bsod. But once I install my 560 gtx. It would be bsod randomly. And this is while it idles I don't use the pc and it bsod. I tried stress testing everything in an attempt to recreate it. But it wouldn't go. It will only do it randomly. I have narrowed it to my CPU or mobo. Also my mobo pci 2.0 slots seem to be missing metal contacts. I don't think that's meant to be. Meaning the pci slots might not be built properly and I might just RMA it.
Any help would be great on this matter. Thanks in advance
Sorry if this seems rushed. This is like the 7th time on different help site ive been on

Quote
PSU: Apevia AQ700W (14a 12v rail)
That's not going to cut it. Recommend a +12V single rail Corsair PSU of at least 500W and 31 +12V amps.
What was the old build? OS migrated or fresh install?

KT3 Ultra2 onboard audio not recognized by win 98SE

I have a KT3 Ultra2 MB with the onboard audio enabled in BIOS and running Win98SE. I installed the drivers from the driver disk and followed all the prompts from windows. The device is listed under system and multimedia devices. But windows itself does not recognize that the device exists for playing sounds, recording et al. Multimedia properties says there is no playback device. Sound recorder sees no device. Volume control does not come up at all. The MSI sound manager will not open at all. I downloaded the latest drivers from the website, but there are no instructions as to how to install them, they just expand into a collection of files with no readme.
Silent in Texas

Reintalling Win98se certainly didn't do the trick for me. I've spent two days installing, trying a few changes, re-installing, trying something else, reinstalling. I even tried removing all my cards except the video but the problem was identical every try.
Can you think of anything special you did during or after the re-install that did the trick? Do you remember versions that you were using and where you got them? This may be a case of the latest drivers being worse than some earlier ones, or some combination of older chipset, newer audio or something crazy.
Speaking of the failed POST, I had a thing with a different MSI board a while ago, where it wouldn't hold the BIOS settings. Every so often (if it was unplugged for a few hours) it would reset (as if the RTC Reset had been jumpered and the checksum was off). If your video card was AGP, and the BIOS reset itself to "primary video = PCI" it might look like nothing was happening on boot up.
I admit that I am about ready to pitch this board too, (or try to return it at least).

P55-GD65 Bios Can't Detect Hard Drives

I can't get my motherboard bios to detect my hard drives (An OCZ Agility SSD and WD Black). My SATA DVD drive is detected properly. I have a Corsair HX850 power supply. My P55-GD65 came with 1.4 Bios.
I had tried default optimised settings and also having AHCI enabled. I tried different SATA cables as well as SATA power cables. I tried plugging the hard drives in different SATA slots including the one that worked with the dvd drive. I cleared CMOS. I'm stumped. Should I look into flashing a new bios?

He hasn't come back for a year--highly unlikely he'll see this. Also, don't respond to long dead threads. Create your own thread.
Please read the >>Posting Guide<< and make a new thread.

P55-GD65 BSOD With onboard audio enabled

Similar Messages

Maybe you are looking for