Windows 7 Forums
Welcome to Windows 7 Forums. Our forum is dedicated to helping you find support and solutions for any problems regarding your Windows 7 PC be it Dell, HP, Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.


Windows 7: BSOD playin WoW, error 0x0000003b


06 Jul 2012   #1

Windows 7 Ultimate x64
 
 
BSOD playin WoW, error 0x0000003b

Hi People, first let me thank you for the time dedicated in helping people.

I started with bsod some days ago, the system panic while playing games, WoW, GTA IV, FIFA 12

I checked event viewer and I do see a bunch of errors ... Im pasting the last ones (Sorry for the spanish but thats my locale)

Code:
Nombre de registro:System
Origen:        Microsoft-Windows-WER-SystemErrorReporting
Fecha:         06/07/2012 10:24:32 a.m.
Id. del evento:1001
Categoría de la tarea:Ninguno
Nivel:         Error
Palabras clave:Clásico
Usuario:       No disponible
Equipo:        SPUTNIK
Descripción:
El equipo se reinició después de una comprobación de errores. La  comprobación de errores fue: 0x0000003b (0x00000000c0000005,  0xfffff88001054cf6, 0xfffff8800815ec10, 0x0000000000000000). Se guardó  un volcado en: C:\Windows\MEMORY.DMP. Id. de informe: 070612-17784-01.
XML de evento:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Microsoft-Windows-WER-SystemErrorReporting"  Guid="{ABCE23E7-DE45-4366-8631-84FA6C525952}" EventSourceName="BugCheck"  />
    <EventID Qualifiers="16384">1001</EventID>
    <Version>0</Version>
    <Level>2</Level>
    <Task>0</Task>
    <Opcode>0</Opcode>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2012-07-06T13:24:32.000000000Z" />
    <EventRecordID>245062</EventRecordID>
    <Correlation />
    <Execution ProcessID="0" ThreadID="0" />
    <Channel>System</Channel>
    <Computer>SPUTNIK</Computer>
    <Security />
  </System>
  <EventData>
    <Data Name="param1">0x0000003b (0x00000000c0000005,  0xfffff88001054cf6, 0xfffff8800815ec10, 0x0000000000000000)</Data>
    <Data Name="param2">C:\Windows\MEMORY.DMP</Data>
    <Data Name="param3">070612-17784-01</Data>
  </EventData>
</Event>

Nombre de registro:System
Origen:        Microsoft-Windows-WER-SystemErrorReporting
Fecha:         06/07/2012 12:16:14 a.m.
Id. del evento:1001
Categoría de la tarea:Ninguno
Nivel:         Error
Palabras clave:Clásico
Usuario:       No disponible
Equipo:        SPUTNIK
Descripción:
El equipo se reinició después de una comprobación de errores. La  comprobación de errores fue: 0x000000f7 (0x000002008218cb70,  0x000024f2a321d588, 0xffffdb0d5cde2a77, 0x0000000000000000). Se guardó  un volcado en: C:\Windows\MEMORY.DMP. Id. de informe: .
XML de evento:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Microsoft-Windows-WER-SystemErrorReporting"  Guid="{ABCE23E7-DE45-4366-8631-84FA6C525952}" EventSourceName="BugCheck"  />
    <EventID Qualifiers="16384">1001</EventID>
    <Version>0</Version>
    <Level>2</Level>
    <Task>0</Task>
    <Opcode>0</Opcode>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2012-07-06T03:16:14.000000000Z" />
    <EventRecordID>244518</EventRecordID>
    <Correlation />
    <Execution ProcessID="0" ThreadID="0" />
    <Channel>System</Channel>
    <Computer>SPUTNIK</Computer>
    <Security />
  </System>
  <EventData>
    <Data Name="param1">0x000000f7 (0x000002008218cb70,  0x000024f2a321d588, 0xffffdb0d5cde2a77, 0x0000000000000000)</Data>
    <Data Name="param2">C:\Windows\MEMORY.DMP</Data>
    <Data Name="param3">
    </Data>
  </EventData>
</Event>

Nombre de registro:System
Origen:        Microsoft-Windows-WER-SystemErrorReporting
Fecha:         05/07/2012 02:49:59 p.m.
Id. del evento:1001
Categoría de la tarea:Ninguno
Nivel:         Error
Palabras clave:Clásico
Usuario:       No disponible
Equipo:        SPUTNIK
Descripción:
El equipo se reinició después de una comprobación de errores. La  comprobación de errores fue: 0x0000003b (0x00000000c0000005,  0xfffff80003398111, 0xfffff880077a8fa0, 0x0000000000000000). Se guardó  un volcado en: C:\Windows\MEMORY.DMP. Id. de informe: .
XML de evento:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Microsoft-Windows-WER-SystemErrorReporting"  Guid="{ABCE23E7-DE45-4366-8631-84FA6C525952}" EventSourceName="BugCheck"  />
    <EventID Qualifiers="16384">1001</EventID>
    <Version>0</Version>
    <Level>2</Level>
    <Task>0</Task>
    <Opcode>0</Opcode>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2012-07-05T17:49:59.000000000Z" />
    <EventRecordID>244207</EventRecordID>
    <Correlation />
    <Execution ProcessID="0" ThreadID="0" />
    <Channel>System</Channel>
    <Computer>SPUTNIK</Computer>
    <Security />
  </System>
  <EventData>
    <Data Name="param1">0x0000003b (0x00000000c0000005,  0xfffff80003398111, 0xfffff880077a8fa0, 0x0000000000000000)</Data>
    <Data Name="param2">C:\Windows\MEMORY.DMP</Data>
    <Data Name="param3">
    </Data>
  </EventData>
</Event>

Nombre de registro:System
Origen:        Microsoft-Windows-WER-SystemErrorReporting
Fecha:         05/07/2012 02:20:54 p.m.
Id. del evento:1001
Categoría de la tarea:Ninguno
Nivel:         Error
Palabras clave:Clásico
Usuario:       No disponible
Equipo:        SPUTNIK
Descripción:
El equipo se reinició después de una comprobación de errores. La  comprobación de errores fue: 0x0000003b (0x00000000c0000005,  0xfffff800033cc11c, 0xfffff88008683c30, 0x0000000000000000). Se guardó  un volcado en: C:\Windows\MEMORY.DMP. Id. de informe: 070512-18579-01.
XML de evento:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Microsoft-Windows-WER-SystemErrorReporting"  Guid="{ABCE23E7-DE45-4366-8631-84FA6C525952}" EventSourceName="BugCheck"  />
    <EventID Qualifiers="16384">1001</EventID>
    <Version>0</Version>
    <Level>2</Level>
    <Task>0</Task>
    <Opcode>0</Opcode>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2012-07-05T17:20:54.000000000Z" />
    <EventRecordID>244120</EventRecordID>
    <Correlation />
    <Execution ProcessID="0" ThreadID="0" />
    <Channel>System</Channel>
    <Computer>SPUTNIK</Computer>
    <Security />
  </System>
  <EventData>
    <Data Name="param1">0x0000003b (0x00000000c0000005,  0xfffff800033cc11c, 0xfffff88008683c30, 0x0000000000000000)</Data>
    <Data Name="param2">C:\Windows\MEMORY.DMP</Data>
    <Data Name="param3">070512-18579-01</Data>
  </EventData>
</Event>

Nombre de registro:System
Origen:        Microsoft-Windows-WER-SystemErrorReporting
Fecha:         04/07/2012 01:39:55 p.m.
Id. del evento:1001
Categoría de la tarea:Ninguno
Nivel:         Error
Palabras clave:Clásico
Usuario:       No disponible
Equipo:        sputnik
Descripción:
El equipo se reinició después de una comprobación de errores. La  comprobación de errores fue: 0x00000019 (0x0000000000000021,  0xfffffa8005b11000, 0x00000000000024a0, 0x74682f3c3e79646f). Se guardó  un volcado en: C:\Windows\MEMORY.DMP. Id. de informe: 070412-38111-01.
XML de evento:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Microsoft-Windows-WER-SystemErrorReporting"  Guid="{ABCE23E7-DE45-4366-8631-84FA6C525952}" EventSourceName="BugCheck"  />
    <EventID Qualifiers="16384">1001</EventID>
    <Version>0</Version>
    <Level>2</Level>
    <Task>0</Task>
    <Opcode>0</Opcode>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2012-07-04T16:39:55.000000000Z" />
    <EventRecordID>243316</EventRecordID>
    <Correlation />
    <Execution ProcessID="0" ThreadID="0" />
    <Channel>System</Channel>
    <Computer>sputnik</Computer>
    <Security />
  </System>
  <EventData>
    <Data Name="param1">0x00000019 (0x0000000000000021,  0xfffffa8005b11000, 0x00000000000024a0, 0x74682f3c3e79646f)</Data>
    <Data Name="param2">C:\Windows\MEMORY.DMP</Data>
    <Data Name="param3">070412-38111-01</Data>
  </EventData>
</Event>

Nombre de registro:System
Origen:        Microsoft-Windows-WER-SystemErrorReporting
Fecha:         04/07/2012 12:07:18 a.m.
Id. del evento:1001
Categoría de la tarea:Ninguno
Nivel:         Error
Palabras clave:Clásico
Usuario:       No disponible
Equipo:        SPUTNIK
Descripción:
El equipo se reinició después de una comprobación de errores. La  comprobación de errores fue: 0x0000001e (0x0000000000000000,  0x0000000000000000, 0x0000000000000000, 0x0000000000000000). Se guardó  un volcado en: C:\Windows\MEMORY.DMP. Id. de informe: 070412-17191-01.
XML de evento:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Microsoft-Windows-WER-SystemErrorReporting"  Guid="{ABCE23E7-DE45-4366-8631-84FA6C525952}" EventSourceName="BugCheck"  />
    <EventID Qualifiers="16384">1001</EventID>
    <Version>0</Version>
    <Level>2</Level>
    <Task>0</Task>
    <Opcode>0</Opcode>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2012-07-04T03:07:18.000000000Z" />
    <EventRecordID>242898</EventRecordID>
    <Correlation />
    <Execution ProcessID="0" ThreadID="0" />
    <Channel>System</Channel>
    <Computer>SPUTNIK</Computer>
    <Security />
  </System>
  <EventData>
    <Data Name="param1">0x0000001e (0x0000000000000000,  0x0000000000000000, 0x0000000000000000, 0x0000000000000000)</Data>
    <Data Name="param2">C:\Windows\MEMORY.DMP</Data>
    <Data Name="param3">070412-17191-01</Data>
  </EventData>
</Event>

Nombre de registro:System
Origen:        Microsoft-Windows-WER-SystemErrorReporting
Fecha:         03/07/2012 11:52:05 p.m.
Id. del evento:1001
Categoría de la tarea:Ninguno
Nivel:         Error
Palabras clave:Clásico
Usuario:       No disponible
Equipo:        sputnik
Descripción:
El equipo se reinició después de una comprobación de errores. La  comprobación de errores fue: 0x0000004e (0x0000000000000007,  0x00000000000c71fa, 0xff00000000000000, 0x0000000000000000). Se guardó  un volcado en: C:\Windows\MEMORY.DMP. Id. de informe: .
XML de evento:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Microsoft-Windows-WER-SystemErrorReporting"  Guid="{ABCE23E7-DE45-4366-8631-84FA6C525952}" EventSourceName="BugCheck"  />
    <EventID Qualifiers="16384">1001</EventID>
    <Version>0</Version>
    <Level>2</Level>
    <Task>0</Task>
    <Opcode>0</Opcode>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2012-07-04T02:52:05.000000000Z" />
    <EventRecordID>242811</EventRecordID>
    <Correlation />
    <Execution ProcessID="0" ThreadID="0" />
    <Channel>System</Channel>
    <Computer>sputnik</Computer>
    <Security />
  </System>
  <EventData>
    <Data Name="param1">0x0000004e (0x0000000000000007,  0x00000000000c71fa, 0xff00000000000000, 0x0000000000000000)</Data>
    <Data Name="param2">C:\Windows\MEMORY.DMP</Data>
    <Data Name="param3">
    </Data>
  </EventData>
</Event>

Nombre de registro:System
Origen:        Microsoft-Windows-WER-SystemErrorReporting
Fecha:         03/07/2012 11:33:04 p.m.
Id. del evento:1001
Categoría de la tarea:Ninguno
Nivel:         Error
Palabras clave:Clásico
Usuario:       No disponible
Equipo:        SPUTNIK
Descripción:
El equipo se reinició después de una comprobación de errores. La  comprobación de errores fue: 0x00000124 (0x0000000000000000,  0xfffffa8004fd6038, 0x0000000000000000, 0x0000000000000000). Se guardó  un volcado en: C:\Windows\Minidump\070312-16738-01.dmp. Id. de informe:  070312-16738-01.
XML de evento:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Microsoft-Windows-WER-SystemErrorReporting"  Guid="{ABCE23E7-DE45-4366-8631-84FA6C525952}" EventSourceName="BugCheck"  />
    <EventID Qualifiers="16384">1001</EventID>
    <Version>0</Version>
    <Level>2</Level>
    <Task>0</Task>
    <Opcode>0</Opcode>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2012-07-04T02:33:04.000000000Z" />
    <EventRecordID>242666</EventRecordID>
    <Correlation />
    <Execution ProcessID="0" ThreadID="0" />
    <Channel>System</Channel>
    <Computer>SPUTNIK</Computer>
    <Security />
  </System>
  <EventData>
    <Data Name="param1">0x00000124 (0x0000000000000000,  0xfffffa8004fd6038, 0x0000000000000000, 0x0000000000000000)</Data>
    <Data Name="param2">C:\Windows\Minidump\070312-16738-01.dmp</Data>
    <Data Name="param3">070312-16738-01</Data>
  </EventData>
</Event>

Nombre de registro:System
Origen:        Microsoft-Windows-WER-SystemErrorReporting
Fecha:         03/07/2012 04:22:43 p.m.
Id. del evento:1001
Categoría de la tarea:Ninguno
Nivel:         Error
Palabras clave:Clásico
Usuario:       No disponible
Equipo:        sputnik
Descripción:
El equipo se reinició después de una comprobación de errores. La  comprobación de errores fue: 0x0000001e (0xffffffffc0000005,  0xfffff80002eb302c, 0x0000000000000000, 0xffffffffffffffff). Se guardó  un volcado en: C:\Windows\MEMORY.DMP. Id. de informe: 070312-16863-01.
XML de evento:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Microsoft-Windows-WER-SystemErrorReporting"  Guid="{ABCE23E7-DE45-4366-8631-84FA6C525952}" EventSourceName="BugCheck"  />
    <EventID Qualifiers="16384">1001</EventID>
    <Version>0</Version>
    <Level>2</Level>
    <Task>0</Task>
    <Opcode>0</Opcode>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2012-07-03T19:22:43.000000000Z" />
    <EventRecordID>242340</EventRecordID>
    <Correlation />
    <Execution ProcessID="0" ThreadID="0" />
    <Channel>System</Channel>
    <Computer>sputnik</Computer>
    <Security />
  </System>
  <EventData>
    <Data Name="param1">0x0000001e (0xffffffffc0000005,  0xfffff80002eb302c, 0x0000000000000000, 0xffffffffffffffff)</Data>
    <Data Name="param2">C:\Windows\MEMORY.DMP</Data>
    <Data Name="param3">070312-16863-01</Data>
  </EventData>
</Event>
I've attached required dump files and a hardware report with my system specs.

Thanks again for the help&time!

JBZ

My System SpecsSystem Spec
.

06 Jul 2012   #2

Windows 7 Home Premium 64 Bit
 
 

Device Concerns:
Code:
AGN Virtual Network Adapter ROOT \ NET \ 0000 This device is disabled.
Was the above intentional? If so, please explain your troubleshooting steps.

Analysis:
AT&T Global Network Firewall Driver
Your most recent crash was caused by your AT&T Global Network Firewall driver.
sptd.sys:
Previous crashes point to sptd.sys:
Please remove any CD/DVD virtualization software, such as Daemon Tools/Alcohol 120%, as they use a driver called sptd.sys that is known to cause BSODs. Use add/remove programs to remove the software. After removing the software, use the sptd.sys uninstaller to remove sptd.sys from the system.

Many use MagicISO - Convert BIN to ISO, Create, Edit, Burn, Extract ISO file, ISO/BIN converter/extractor/editor as well, which is free.
Graphics/DirectX:
You also had a number of crashes that were DirectX/graphics card related. DirectX comes installed with Windows, so this may indicate Windows corruption. It may also be that you have corrupted drivers or a graphics card hardware problem.
  • If you are overclocking any hardware, please stop.

  • Check Windows for corruption. Run SFC /SCANNOW Command - System File Checker up to three times to fix all errors with a restart in between each. Post back if it continues to show errors after a fourth run or if the first run comes back with no integrity violations. Use OPTION THREE of SFC /SCANNOW Command - System File Checker to provide us with the sfcdetails.txt file if errors occur.


Follow the steps for Diagnosing basic problems with DirectX. To re-install your display card drivers as outlined in the DirectX link, use the following steps.
  1. Download the drivers you want for your display card(s)
  2. Click Start Menu
  3. Click Control Panel
  4. Click Uninstall a program
  5. For NVIDIA:
    • Uninstall the NVIDIA Graphics Driver (this should uninstall all NVIDIA software and drivers)
    • Restart your computer
    • Make sure NVIDIA 3D Vision Driver, NVIDIA 3D Vision Video Player, NVIDIA HD Audio Driver, and NVIDIA PhysX System Software are not still listed under Uninstall a program through Control Panel
    • If any remain of the above, uninstall one at a time
    • If asked to restart after uninstalling any of the above, do so, and continue uninstalling any remaining NVIDIA items until all are removed
  6. For AMD:
    • Uninstall AMD Catalyst Install Manager if it is listed (this should remove all AMD graphics software and drivers)
    • If AMD Catalyst Install Manager is not listed, use the following method to uninstall the graphics drivers (this applies to onboard graphics, as well):
      1. Click Start Menu
      2. Right Click My Computer/Computer
      3. Click Manage
      4. Click Device Manager from the list on the left
      5. Expand Display adapters
      6. Do the following for each adapter (in case you have multiple display cards)
        • Right click the adapter
        • Click Uninstall (do not click OK in the dialog box that pops up after hitting Uninstall)
        • Put a tick in Delete driver software for this device (if this option is available, otherwise just hit OK) and hit OK
      Alternatively:
      1. Login as an adminstrative user
      2. Click Start Menu
      3. Click Control Panel
      4. Click Hardware and Sound
      5. Click Device Manager (the last link under Devices and Printers)
      6. Expand Display adapters
      7. Do the following for each adapter (in case you have multiple display cards)
        • Right click the adapter
        • Click Uninstall (do not click OK in the dialog box that pops up after hitting Uninstall)
        • Put a tick in Delete driver software for this device (if this option is available, otherwise just hit OK) and hit OK
  7. Restart your computer after uninstalling drivers for all display cards
  8. Install the driver you selected for the display cards once Windows starts

Remember to try multiple versions of the graphics drivers, download them fresh, and install the freshly downloaded drivers.
BugCheck 0x124
You have a 0x124 hardware bugcheck. If the system is still under warranty, I would recommend sending it in to have diagnostic tests done and any bad hardware replaced.

warning   Warning
Before you proceed with the following, answer these two questions: Are you still under warranty? Does your warranty allow you to open up the machine to check hardware? If you are unsure of the answers to these questions, contact your system manufacturer. WARNING: The steps that follow can void your warranty!!!

For your hardware stop 0x124 crash, read through Stop 0x124 - what it means and what to try and use the following hardware checks to supplement that link.
  • If you are overclocking any hardware, please stop.

  • If you have an SSD, make sure the following are up to date:
    • SSD firmware
    • BIOS Version
    • Chipset Drivers
    • Hard disk controller drivers/SATA drivers
    • If you have a Marvell IDE ATA/ATAPI device, make sure the drivers are up to date from the Intel site or Marvell site and not from your motherboard/vendor support site.

  • Run all but the advanced tests with SeaTools for HDDs.
    SeaTools for Windows

    SeaTools for DOS
  • Monitor temperatures during the following tests.
    Use the following programs to monitor the temperatures.
  • Run the boot version of Memtest86+ paying close attention to Parts 2 and 3 of the tutorial. Also, in case Memtest86+ misses anything and comes up with no errors, run the extended version of the Windows Memory Diagnostics Tool for at least five passes. These you may want to run overnight since they take a long time to complete (run them an hour before bed each of the next two nights and check before going to sleep that they are still running).

    For Part 3: If You Have Errors: If you swap any memory components, follow these steps for ESD safety:
    1. Shut down and turn off your computer.
    2. Unplug all power supplies to the computer (AC Power then battery for laptops, AC power for desktops)
    3. Hold down the power button for 30 seconds to close the circuit and ensure all power drains from components.
    4. Make sure you are grounded by using proper grounding techniques, i.e. work on an anti-static workbench, anti-static desk, or an anti-static pad. Hold something metallic while touching it to the anti-static surface, or use an anti-static wristband to attach to the anti-static material while working. If you do not have an anti-static workbench, desk, or pad, you can use your computer tower/case by finding a metal hold in it, such as a drive bay.
    Once these steps have been followed, it is safe to remove and replace components within your computer.

Remember to read closely through Stop 0x124 - what it means and what to try for the crash.
My System SpecsSystem Spec
17 Jul 2012   #3

Windows 7 Ultimate x64
 
 

Hi writh, thanks for your detail information ... i went through everything and finally i decided to reinstall Windows 7. its now up2date, i installed ati driver from original cd and mobo drivers from cd as well. I kept my installation as clean as possible but today it crashed again.
I fear the worse, something related to hardware, but i dont know where to start off ... and i dont have spare to test so I think im at a dead end.

I would like to know if you would do a last check to this last dump to see where i can start of troubleshooting hardware.

Thanks again for your time.
My System SpecsSystem Spec
.


20 Jul 2012   #4

Windows 7 Home Premium 64 Bit
 
 

Software Concerns:
Security Software:
Security Software: ??? Make sure to install security software. I recommend either of these:
After installing your security software, update it, and then run full scans today with each program. Report back the results of the scans.
ASUS Utilities:
Recommend removing your ASUS utilities through Start Menu -> Control Panel -> Uninstall a program. They can provide software interfaces with the hardware for overclocking, and even when the overclock is not enabled, that interface can cause instability. They are also not needed for the system to function properly and may reduce system resources.

Analysis:
The following is for information purposes only.
Code:
--------------------------------------------
--------------------1-------------------
--------------------------------------------
Loading Dump File [C:\Users\Mike\Downloads\junglebz\070812-16348-01.dmp]

Windows 7 Kernel Version 7600 MP (4 procs) Free x64

System Uptime: 0 days 16:43:16.611

Use !analyze -v to get detailed debugging information.

BugCheck 1A, {5002, fffff780c0000000, 37f5, ff00380bfffffffe}

*** WARNING: Unable to verify timestamp for win32k.sys

*** ERROR: Module load completed but symbols could not be loaded for win32k.sys

Probably caused by : srv2.sys ( srv2!Smb2ExecuteLargeMdlWrite+164 )

MEMORY_MANAGEMENT (1a)

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  System

STACK_TEXT:  
fffff880`084593c8 fffff800`02b35c89 : 00000000`0000001a 00000000`00005002 fffff780`c0000000 00000000`000037f5 : nt!KeBugCheckEx

fffff880`084593c8 fffff800`02b35c89 : 00000000`0000001a 00000000`00005002 fffff780`c0000000 00000000`000037f5 : nt!KeBugCheckEx
fffff880`084593d0 fffff800`02ae3ea6 : fffff6fc`c000db88 00000000`00000001 fffff880`0000000e ffffffff`ffff0001 : nt! ?? ::FNODOBFM::`string'+0x29d47
fffff880`08459540 fffff800`02aead54 : fffff980`01b71000 00000000`0000000f fffffa80`00000001 00000000`00000002 : nt!MmCheckCachedPageStates+0x4d6
fffff880`084596f0 fffff800`02a96e42 : fffffa80`059f2700 00000000`00000007 fffff880`08459701 fffff880`08459784 : nt!CcMapAndRead+0xc4
fffff880`08459750 fffff880`012aeb58 : fffff880`08459890 fffff880`08459870 fffff880`00010000 fffffa80`04e15d68 : nt!CcPrepareMdlWrite+0x1c2
fffff880`08459830 fffff880`010b030c : fffffa80`059f2780 fffff880`010b3732 fffff8a0`00010000 fffff780`00000000 : Ntfs!NtfsPrepareMdlWriteA+0x1f8
fffff880`08459a20 fffff880`010b3c2a : fffff880`08459af0 fffffa80`03f42978 00000000`00000000 00000000`00010000 : fltmgr!FltpPerformFastIoCall+0x2cc
fffff880`08459a80 fffff880`010da1d3 : 00000000`00010000 00000000`00000000 fffffa80`059f2780 fffffa80`04ca8890 : fltmgr!FltpPassThroughFastIo+0xda
fffff880`08459ac0 fffff880`06847b14 : fffffa80`04910d00 fffffa80`03f42978 fffffa80`04e15a30 00000000`00000000 : fltmgr! ?? ::NNGAKEGL::`string'+0x21d0
fffff880`08459b70 fffff880`0682ba3b : fffffa80`04e15a30 fffffa80`04e15eb8 fffffa80`04e15ce0 fffff880`06826af4 : srv2!Smb2ExecuteLargeMdlWrite+0x164
fffff880`08459bf0 fffff880`068265d0 : fffffa80`04e15a30 fffffa80`04e15a30 fffff880`06820110 fffff880`06820110 : srv2!Smb2ExecuteWrite+0x1bb
fffff880`08459c80 fffff880`0682616a : 00000000`0000000f 00000000`00000007 fffffa80`05f29620 fffffa80`04e15a40 : srv2!SrvProcessPacket+0xa0
fffff880`08459cc0 fffff800`02d666e6 : 00000000`00000000 fffffa80`04943910 00000000`00000080 fffffa80`0396e890 : srv2!SrvProcWorkerThread+0x15a
fffff880`08459d40 fffff800`02aa5566 : fffff800`02c40e80 fffffa80`04943910 fffff800`02c4ec40 fffff880`01240534 : nt!PspSystemThreadStartup+0x5a
fffff880`08459d80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16


FAILURE_BUCKET_ID:  X64_0x1a_5002_srv2!Smb2ExecuteLargeMdlWrite+164

--------------------------------------------
---------------------END--------------------
--------------------------------------------
--------------------------------------------
--------------------2-------------------
--------------------------------------------
Loading Dump File [C:\Users\Mike\Downloads\junglebz\070912-19000-01.dmp]

Windows 7 Kernel Version 7600 MP (4 procs) Free x64

System Uptime: 0 days 1:23:10.980

Use !analyze -v to get detailed debugging information.

BugCheck 3B, {c0000005, fffff960001ce4b1, fffff8800889dfa0, 0}

Probably caused by : win32k.sys ( win32k!StoreQMessageExtended+15 )

SYSTEM_SERVICE_EXCEPTION (3b)

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  chrome.exe

STACK_TEXT:  
fffff880`0889e970 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : win32k!StoreQMessageExtended+0x15


FAILURE_BUCKET_ID:  X64_0x3B_win32k!StoreQMessageExtended+15

--------------------------------------------
---------------------END--------------------
--------------------------------------------
--------------------------------------------
--------------------3-------------------
--------------------------------------------
Loading Dump File [C:\Users\Mike\Downloads\junglebz\070912-23696-01.dmp]

Windows 7 Kernel Version 7600 MP (4 procs) Free x64

System Uptime: 0 days 0:05:14.647

Use !analyze -v to get detailed debugging information.

BugCheck 3B, {c0000005, fffff80002bb1f8c, fffff88003bcffd0, 0}

Probably caused by : Pool_Corruption ( nt!ExDeferredFreePool+100 )

SYSTEM_SERVICE_EXCEPTION (3b)

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  lsass.exe

STACK_TEXT:  
fffff880`03bd09a0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!ExDeferredFreePool+0x100


FAILURE_BUCKET_ID:  X64_0x3B_nt!ExDeferredFreePool+100

--------------------------------------------
---------------------END--------------------
--------------------------------------------
--------------------------------------------
--------------------4-------------------
--------------------------------------------
Loading Dump File [C:\Users\Mike\Downloads\junglebz\071112-18283-01.dmp]

Windows 7 Kernel Version 7600 MP (4 procs) Free x64

System Uptime: 0 days 5:52:26.750

Use !analyze -v to get detailed debugging information.

BugCheck 1A, {5002, fffff780c0000000, da09, ff00dcf8fffffffe}

Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+29d47 )

MEMORY_MANAGEMENT (1a)

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  Wow.exe

STACK_TEXT:  
fffff880`083b1368 fffff800`02af5c89 : 00000000`0000001a 00000000`00005002 fffff780`c0000000 00000000`0000da09 : nt!KeBugCheckEx

fffff880`083b1368 fffff800`02af5c89 : 00000000`0000001a 00000000`00005002 fffff780`c0000000 00000000`0000da09 : nt!KeBugCheckEx
fffff880`083b1370 fffff800`02aa3ea6 : fffff6fc`c007bfe8 00000000`00000001 fffffa80`00000003 ffffffff`ffff0001 : nt! ?? ::FNODOBFM::`string'+0x29d47
fffff880`083b14e0 fffff800`02acb0ae : fffff980`0f7fc000 00000000`00005000 fffffa80`00000000 fffffa80`05818580 : nt!MmCheckCachedPageStates+0x4d6
fffff880`083b1690 fffff800`02d9e55b : 00000000`00980000 00000000`009bc0d0 fffffa80`043c96d0 00000000`1a1a0d10 : nt!CcFetchDataForRead+0x10e
fffff880`083b16f0 fffff880`012f2c48 : fffff880`00000000 00000000`00000005 fffffa80`00003f30 fffffa80`00004001 : nt!CcCopyRead+0x16b
fffff880`083b17b0 fffff880`00fac0c8 : fffffa80`043c96d0 fffffa80`05818518 00000000`00000000 fffffa80`043c9701 : Ntfs!NtfsCopyReadA+0x1a8
fffff880`083b1980 fffff880`00fafc2a : fffff880`083b1a50 00000000`1a1a0d03 00000000`1a1a0d00 fffffa80`043c9600 : fltmgr!FltpPerformFastIoCall+0x88
fffff880`083b19e0 fffff880`00fcd5f0 : fffffa80`043c96d0 00000000`00000000 fffff880`083b1b40 00000000`00004000 : fltmgr!FltpPassThroughFastIo+0xda
fffff880`083b1a20 fffff800`02d9ee89 : fffffa80`043c96d0 fffffa80`00000001 fffffa80`039dff30 fffffa80`043c96d0 : fltmgr!FltpFastIoRead+0x1d0
fffff880`083b1ac0 fffff800`02a86293 : fffff880`083b1ca0 00000000`00000000 00000000`00000000 00000000`0e70e118 : nt!NtReadFile+0x417
fffff880`083b1bb0 00000000`73682dd9 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`0dc9ee08 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x73682dd9


FAILURE_BUCKET_ID:  X64_0x1a_5002_nt!_??_::FNODOBFM::_string_+29d47

--------------------------------------------
---------------------END--------------------
--------------------------------------------
--------------------------------------------
--------------------5-------------------
--------------------------------------------
Loading Dump File [C:\Users\Mike\Downloads\junglebz\071312-15444-01.dmp]

Windows 7 Kernel Version 7601 (Service Pack 1) MP (3 procs) Free x64

System Uptime: 0 days 0:04:05.002

Use !analyze -v to get detailed debugging information.

BugCheck 24, {1904fb, fffff88003138598, fffff88003137df0, fffff80002ae72b4}

*** WARNING: Unable to verify timestamp for win32k.sys

*** ERROR: Module load completed but symbols could not be loaded for win32k.sys

Probably caused by : Ntfs.sys ( Ntfs!NtfsAcquireExclusiveFcb+73 )

NTFS_FILE_SYSTEM (24)

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  System

STACK_TEXT:  
fffff880`031387d0 fffff880`012412c3 : 00000000`c00000d8 fffff8a0`02d87010 fffffa80`060aac50 fffff880`03138978 : nt!ExAcquireResourceExclusiveLite+0x54
fffff880`03138840 fffff880`012cd711 : 00000000`00000000 fffff880`03138a40 00000000`00000014 fffff8a0`02d87140 : Ntfs!NtfsAcquireExclusiveFcb+0x73
fffff880`03138890 fffff880`0123f574 : fffffa80`060aac50 fffffa80`03bd3ae0 fffff880`03138a00 fffff880`03138901 : Ntfs!NtfsCommonSetInformation+0x401
fffff880`03138970 fffff880`010aebcf : fffff880`03138aa0 fffffa80`03bd3ae0 fffffa80`060aac50 fffff880`03138998 : Ntfs!NtfsFsdSetInformation+0x11c
fffff880`031389f0 fffff880`010ad6df : fffffa80`049dd760 fffff800`02b268c1 fffffa80`049dd700 fffffa80`03bd3ae0 : fltmgr!FltpLegacyProcessingAfterPreCallbacksCompleted+0x24f
fffff880`03138a80 fffff800`02ac7713 : fffffa80`049dd760 fffffa80`049dd760 00000000`00000011 fffff880`03138c58 : fltmgr!FltpDispatch+0xcf
fffff880`03138ae0 fffff800`02b268c1 : fffffa80`03b680d0 00000000`00006ccc fffffa80`03b681e0 fffffa80`03a0ab50 : nt!CcSetValidData+0x11b
fffff880`03138b50 fffff800`02b27158 : fffff880`00000000 fffff880`03138c58 fffffa80`05cec150 fffff800`02ce08b8 : nt!CcWriteBehind+0x2f1
fffff880`03138c00 fffff800`02aeb841 : fffffa80`03a663b0 fffff800`02dd4601 fffff800`02ce08c0 00000000`00000000 : nt!CcWorkerThread+0x1c8
fffff880`03138cb0 fffff800`02d78e6a : 00000000`00000000 fffffa80`03a0ab50 00000000`00000080 fffffa80`039e1040 : nt!ExpWorkerThread+0x111
fffff880`03138d40 fffff800`02ad2ec6 : fffff880`02f63180 fffffa80`03a0ab50 fffff880`02f6df80 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`03138d80 00000000`00000000 : fffff880`03139000 fffff880`03133000 fffff880`03137d40 00000000`00000000 : nt!KxStartSystemThread+0x16


FAILURE_BUCKET_ID:  X64_0x24_Ntfs!NtfsAcquireExclusiveFcb+73

--------------------------------------------
---------------------END--------------------
--------------------------------------------
--------------------------------------------
--------------------6-------------------
--------------------------------------------
Loading Dump File [C:\Users\Mike\Downloads\junglebz\071412-15600-01.dmp]

Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64

System Uptime: 0 days 22:30:05.629

Use !analyze -v to get detailed debugging information.

BugCheck 3B, {c0000005, fffff880016cd26b, fffff88008198a90, 0}

Probably caused by : tcpip.sys ( tcpip!IppFillPathRodUnderLock+2b )

SYSTEM_SERVICE_EXCEPTION (3b)

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  svchost.exe

STACK_TEXT:  
fffff880`08199470 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : tcpip!IppFillPathRodUnderLock+0x2b


FAILURE_BUCKET_ID:  X64_0x3B_tcpip!IppFillPathRodUnderLock+2b

--------------------------------------------
---------------------END--------------------
--------------------------------------------
--------------------------------------------
--------------------7-------------------
--------------------------------------------
Loading Dump File [C:\Users\Mike\Downloads\junglebz\071412-14586-01.dmp]

Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64

System Uptime: 0 days 0:00:07.020

Use !analyze -v to get detailed debugging information.

BugCheck 124, {0, fffffa80049638f8, 0, 0}

Probably caused by : hardware

WHEA_UNCORRECTABLE_ERROR (124)

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  System

STACK_TEXT:  
fffff880`031b66f0 fffff800`02cdaca9 : fffffa80`049638d0 fffffa80`039f1040 00000000`0000000a 00000000`00000000 : nt!WheapCreateLiveTriageDump+0x6c
fffff880`031b6c10 fffff800`02bbb547 : fffffa80`049638d0 fffff800`02c352d8 fffffa80`039f1040 00000000`00000000 : nt!WheapCreateTriageDumpFromPreviousSession+0x49
fffff880`031b6c40 fffff800`02b22945 : fffff800`02c96ae0 fffff800`02aa1822 00000000`00000010 00000000`00000292 : nt!WheapProcessWorkQueueItem+0x57
fffff880`031b6c80 fffff800`02aa1841 : fffff880`01078e00 fffff800`02b22920 fffffa80`039f1000 00000000`00000000 : nt!WheapWorkQueueWorkerRoutine+0x25
fffff880`031b6cb0 fffff800`02d2ee6a : 00000000`00000000 fffffa80`039f1040 00000000`00000080 fffffa80`039ec040 : nt!ExpWorkerThread+0x111
fffff880`031b6d40 fffff800`02a88ec6 : fffff880`02f63180 fffffa80`039f1040 fffff880`02f6dfc0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`031b6d80 00000000`00000000 : fffff880`031b7000 fffff880`031b1000 fffff880`03d1b740 00000000`00000000 : nt!KxStartSystemThread+0x16


FAILURE_BUCKET_ID:  X64_0x124_AuthenticAMD_PROCESSOR_BUS_PRV

--------------------------------------------
---------------------END--------------------
--------------------------------------------
--------------------------------------------
--------------------8-------------------
--------------------------------------------
Loading Dump File [C:\Users\Mike\Downloads\junglebz\071612-15178-01.dmp]

Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64

System Uptime: 0 days 11:46:59.384

Use !analyze -v to get detailed debugging information.

BugCheck 1E, {0, 0, 0, 0}

Probably caused by : usbohci.sys ( usbohci!OHCI_ProcessDoneAsyncTd+24 )

KMODE_EXCEPTION_NOT_HANDLED (1e)

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  pes2012.exe

STACK_TEXT:  
fffff880`009afba8 fffff800`02a89bbe : fffffa80`3725d744 00000003`05e8b0f0 fffff880`009b0320 fffff800`02abd160 : nt!KeBugCheck

fffff880`009afba8 fffff800`02a89bbe : fffffa80`3725d744 00000003`05e8b0f0 fffff880`009b0320 fffff800`02abd160 : nt!KeBugCheck
fffff880`009afbb0 fffff800`02abce2d : fffff800`02c98770 fffff800`02bd52f0 fffff800`02a13000 fffff880`009b0ac8 : nt!KiKernelCalloutExceptionHandler+0xe
fffff880`009afbe0 fffff800`02abbc05 : fffff800`02bd8ed8 fffff880`009afc58 fffff880`009b0ac8 fffff800`02a13000 : nt!RtlpExecuteHandlerForException+0xd
fffff880`009afc10 fffff800`02accb81 : fffff880`009b0ac8 fffff880`009b0320 fffff880`00000000 fffffa80`039d9000 : nt!RtlDispatchException+0x415
fffff880`009b02f0 fffff800`02a91842 : fffff880`009b0ac8 fffffa80`05886c30 fffff880`009b0b70 00fffa80`041553a8 : nt!KiDispatchException+0x135
fffff880`009b0990 fffff800`02a9014a : 00000000`00000000 00000000`00000000 fffffa80`00000004 fffffa80`05927000 : nt!KiExceptionDispatch+0xc2
fffff880`009b0b70 fffff880`04864ec8 : 00000000`00000000 fffff880`02cb2ea0 00000000`00000000 fffff880`02cb2208 : nt!KiGeneralProtectionFault+0x10a
fffff880`009b0d00 fffff880`04864d98 : fffffa80`05886c30 fffffa80`039d9180 00000000`00000000 fffffa80`039d9000 : usbohci!OHCI_ProcessDoneAsyncTd+0x24
fffff880`009b0d50 fffff880`04866737 : fffffa80`05886ba8 fffffa80`05886960 00000000`00000000 fffffa80`050e91a0 : usbohci!OHCI_PollAsyncEndpoint+0x3ec
fffff880`009b0db0 fffff880`02c86e8b : 00000000`00000002 fffffa80`05886960 fffffa80`050e91a0 00000000`00000000 : usbohci!OHCI_PollEndpoint+0x3f
fffff880`009b0de0 fffff880`02c8b9d1 : 00000000`00000040 00000000`00000004 fffffa80`05886960 fffffa80`050e9050 : USBPORT!MPf_PollEndpoint+0x9b
fffff880`009b0e10 fffff880`02c97077 : fffffa80`050e91a0 00000000`00000040 fffffa80`0000000e 00000000`00000000 : USBPORT!USBPORT_iSetGlobalEndpointStateTx+0x7c1
fffff880`009b0e70 fffff880`02c87f89 : fffffa80`050e9050 00000000`00000000 fffffa80`050e9a02 fffffa80`050e9a18 : USBPORT!USBPORT_Core_UsbHcIntDpc_Worker+0x1c3
fffff880`009b0ed0 fffff800`02a9c8ec : fffff880`02fd3180 fffffa80`050e9a18 fffffa80`050e9a30 00000000`ffff0000 : USBPORT!USBPORT_Xdpc_Worker+0x1d9
fffff880`009b0f00 fffff800`02a95305 : 01000001`00000100 fffffa80`0674f370 00000000`00000000 fffff880`02c87db0 : nt!KiRetireDpcList+0x1bc
fffff880`009b0fb0 fffff800`02a9511c : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxRetireDpcList+0x5
fffff880`081e4380 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDispatchInterruptContinue


FAILURE_BUCKET_ID:  X64_0x1E_0_usbohci!OHCI_ProcessDoneAsyncTd+24

--------------------------------------------
---------------------END--------------------
--------------------------------------------
--------------------------------------------
--------------------9-------------------
--------------------------------------------
Loading Dump File [C:\Users\Mike\Downloads\junglebz\071712-22822-01.dmp]

Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64

System Uptime: 0 days 0:00:09.938

Use !analyze -v to get detailed debugging information.

BugCheck 124, {0, fffffa80049538f8, 0, 0}

Probably caused by : hardware

WHEA_UNCORRECTABLE_ERROR (124)

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  System

STACK_TEXT:  
fffff880`031af6f0 fffff800`02cdaca9 : fffffa80`049538d0 fffffa80`03a7f040 00000000`0000000f 00000000`00000000 : nt!WheapCreateLiveTriageDump+0x6c
fffff880`031afc10 fffff800`02bbb547 : fffffa80`049538d0 fffff800`02c352d8 fffffa80`03a7f040 00000000`00000000 : nt!WheapCreateTriageDumpFromPreviousSession+0x49
fffff880`031afc40 fffff800`02b22945 : fffff800`02c96ae0 00000000`00000001 fffffa80`04957820 fffffa80`03a7f040 : nt!WheapProcessWorkQueueItem+0x57
fffff880`031afc80 fffff800`02aa1841 : fffff880`01111e00 fffff800`02b22920 fffffa80`03a7f000 00000000`00000000 : nt!WheapWorkQueueWorkerRoutine+0x25
fffff880`031afcb0 fffff800`02d2ee6a : 00000000`00000000 fffffa80`03a7f040 00000000`00000080 fffffa80`039ec040 : nt!ExpWorkerThread+0x111
fffff880`031afd40 fffff800`02a88ec6 : fffff880`02f63180 fffffa80`03a7f040 fffff880`02f6dfc0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`031afd80 00000000`00000000 : fffff880`031b0000 fffff880`031aa000 fffff880`037eb5b0 00000000`00000000 : nt!KxStartSystemThread+0x16


FAILURE_BUCKET_ID:  X64_0x124_AuthenticAMD_PROCESSOR_BUS_PRV

--------------------------------------------
---------------------END--------------------
--------------------------------------------

3rd Party Drivers:
The following is for information purposes only. Any drivers in red should be updated.
Code:
mcdbus.sys Tue Feb 24 03:34:07 2009 (49A3CD1F)
AsUpIO.sys Sun Jul 5 20:21:38 2009 (4A515FB2)
ASACPI.sys Wed Jul 15 21:31:29 2009 (4A5E9F11)
AsIO.sys Mon Aug 3 01:03:16 2009 (4A768BB4)
xusb21.sys Thu Aug 13 16:10:17 2009 (4A848F49)
AtiHdmi.sys Sun Aug 23 06:35:11 2009 (4A91377F)
atikmdag.sys Fri Sep 18 20:44:52 2009 (4AB445A4)
viahduaa.sys Mon Jan 11 03:05:18 2010 (4B4AF7DE)
amdxata.sys Fri Mar 19 10:18:18 2010 (4BA3A3CA)
point64.sys Wed May 18 02:07:20 2011 (4DD37E38)
Rt64win7.sys Fri Jun 10 00:33:15 2011 (4DF1BAAB)
mcdbus.sys
AsUpIO.sys
ASACPI.sys
AsIO.sys
xusb21.sys
AtiHdmi.sys
atikmdag.sys
viahduaa.sys
amdxata.sys
point64.sys
Rt64win7.sys

Recommendations:
  1. Uninstall all XBOX related software and drivers. Remove your XBOX device from the system.
    1. Click Start Menu
    2. Right Click My Computer/Computer
    3. Click Manage
    4. Click Device Manager from the list on the left
    5. Find the device you are trying to uninstall by expanding the appropriate set of devices
    6. Right click the device
    7. Click Uninstall (do not click OK in the dialog box that pops up after hitting Uninstall)
    8. Put a tick in Delete driver software for this device (if this option is available, otherwise just hit OK) and hit OK
    9. Remove the device from the computer.
    10. Restart your computer only if Windows asks you to.

    Alternatively:
    1. Login as an adminstrative user.
    2. Click Start Menu
    3. Click Control Panel
    4. Click Hardware and Sound
    5. Click Device Manager (the last link under Devices and Printers)
    6. Find the device you are trying to uninstall by expanding the appropriate set of devices
    7. Right click the device
    8. Click Uninstall (do not click OK in the dialog box that pops up after hitting Uninstall)
    9. Put a tick in Delete driver software for this device (if this option is available, otherwise just hit OK) and hit OK
    10. Remove the device from the computer.
    11. Restart your computer only if Windows asks you to.

  2. Your crashes primarily indicate memory problems and/or hard disk problems. When doing the tests below, start with those for the hard disk and memory first.

    BugCheck 0x124
    You have a 0x124 hardware bugcheck. If the system is still under warranty, I would recommend sending it in to have diagnostic tests done and any bad hardware replaced.

    warning   Warning
    Before you proceed with the following, answer these two questions: Are you still under warranty? Does your warranty allow you to open up the machine to check hardware? If you are unsure of the answers to these questions, contact your system manufacturer. WARNING: The steps that follow can void your warranty!!!

    For your hardware stop 0x124 crash, read through Stop 0x124 - what it means and what to try and use the following hardware checks to supplement that link.
    • If you are overclocking any hardware, please stop.

    • If you have an SSD, make sure the following are up to date:
      • SSD firmware
      • BIOS Version
      • Chipset Drivers
      • Hard disk controller drivers/SATA drivers
      • If you have a Marvell IDE ATA/ATAPI device, make sure the drivers are up to date from the Intel site or Marvell site and not from your motherboard/vendor support site.

    • Run all but the advanced tests with SeaTools for HDDs.
      SeaTools for Windows

      SeaTools for DOS
    • Monitor temperatures during the following tests.
      Use the following programs to monitor the temperatures.
    • Run the boot version of Memtest86+ paying close attention to Parts 2 and 3 of the tutorial. Also, in case Memtest86+ misses anything and comes up with no errors, run the extended version of the Windows Memory Diagnostics Tool for at least five passes. These you may want to run overnight since they take a long time to complete (run them an hour before bed each of the next two nights and check before going to sleep that they are still running).

      For Part 3: If You Have Errors: If you swap any memory components, follow these steps for ESD safety:
      1. Shut down and turn off your computer.
      2. Unplug all power supplies to the computer (AC Power then battery for laptops, AC power for desktops)
      3. Hold down the power button for 30 seconds to close the circuit and ensure all power drains from components.
      4. Make sure you are grounded by using proper grounding techniques, i.e. work on an anti-static workbench, anti-static desk, or an anti-static pad. Hold something metallic while touching it to the anti-static surface, or use an anti-static wristband to attach to the anti-static material while working. If you do not have an anti-static workbench, desk, or pad, you can use your computer tower/case by finding a metal hold in it, such as a drive bay.
      Once these steps have been followed, it is safe to remove and replace components within your computer.

    Remember to read closely through Stop 0x124 - what it means and what to try for the crash.
My System SpecsSystem Spec
Reply

 BSOD playin WoW, error 0x0000003b




Thread Tools



Similar help and support threads for2: BSOD playin WoW, error 0x0000003b
Thread Forum
BSOD playin WOW, error 0x00000101 notskrnl.exe BSOD Help and Support
Solved Random BSOD - Error 0x0000003b BSOD Help and Support
BSOD randomly, error 0x0000003B BSOD Help and Support
BSOD While using ftp error 0x0000003b BSOD Help and Support
BSOD, Error 0X0000003b with dxgmm1.sys BSOD Help and Support
Help ks.sys BSOD error 0x0000003B BSOD Help and Support
BSOD Error 0x0000003B BSOD Help and Support

Our Sites

Site Links

About Us

Find Us

Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd

All times are GMT -5. The time now is 09:00 AM.
Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App
  

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33