Having huge problems with my R3

Hello Pro´s!

Have no clue what to do any more.
Dell repair service has been out 5 times in the matter of blue screens and alot of other problems. They swapped RAM 3 times , MB 4 times GPU 4 times and the blue screens still appears and i can not play for example BF3 on more then medium or its lagging ALOT! 3D mark Vantage gives me 3-4K . Im on a i7-2820QM 2,3GHz , 32GB RAM Corsair 1333MHz , GTX 580M , Windows Ultimate. Something is really wrong with this one...
Here´s a list of the last ones who a few cant be read...

On Sat 2011-11-19 18:10:42 GMT your computer crashed
crash dump file: C:\Windows\Minidump\111911-11044-01.dmp
This was probably caused by the following module: sdbus.sys (Unloaded_sdbus.sys+0x100B8)
Bugcheck code: 0xD1 (0xFFFFF8800451C0B8, 0x2, 0x8, 0xFFFFF8800451C0B8)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\sdbus.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: SecureDigital Bus Driver
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system which cannot be identified at this time.
Google query: sdbus.sys Microsoft Corporation DRIVER_IRQL_NOT_LESS_OR_EQUAL




On Sat 2011-11-19 18:10:42 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: sdbus.sys (Unloaded_sdbus.sys+0x100B8)
Bugcheck code: 0xD1 (0xFFFFF8800451C0B8, 0x2, 0x8, 0xFFFFF8800451C0B8)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\sdbus.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: SecureDigital Bus Driver
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system which cannot be identified at this time.
Google query: sdbus.sys Microsoft Corporation DRIVER_IRQL_NOT_LESS_OR_EQUAL




On Sat 2011-11-19 17:59:05 GMT your computer crashed
crash dump file: C:\Windows\Minidump\111911-10483-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x71F00)
Bugcheck code: 0xA (0x0, 0x2, 0x1, 0xFFFFF80002ED2DAF)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


On Sat 2011-11-19 17:06:53 GMT your computer crashed
crash dump file: C:\Windows\Minidump\111911-10639-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x71F00)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80002ECC8D6, 0xFFFFF88005410560, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


The following dump files were found but could not be read. These files may be corrupt:
C:\Windows\Minidump\111811-11934-01.dmp
C:\Windows\Minidump\111811-11980-01.dmp
C:\Windows\Minidump\111811-13010-01.dmp


thanks for any help at all.

Kindest // Emvees =)

 

oh man this is just screwed... just get a replacement unit, complain that you are having the nightmare of your life! (just try to disable optimus first)

 

yea asking for a replacement is prob what you wanna do. sucks that you have all those parts replaced and it still doesn't work. Makes me not feel as bad about my dead video card

 

Yeah will try to get the service guy on monday to push for a new unit then...... Blows thou. Cheers for the quick respond =)

 

5 times! Yeah, man if you've cleaned and scrubbed your drivers and looked in device manager to find the offending hardware/drive combo then it was be something that requires a full RMA clean/full replacement. Sucks man, good luck. Now I'm getting worried...getting yellow artifacts in BF3... thought it was just driver and poor programming...now I'm getting skittish...

 

You OC'd at all? that could lead to the artifacts you are seeing

 

No I haven't yet... I asked the other day which software people have been using but I forgot which post that was in and haven't been able to find a reply. But no it's still running stock. It only happens in BF3. I'll try the beta drivers later today and see what happens

 

yea i'd try the BF3 beta drivers and see if that fixes the issues