Jump to content

Welcome to Geeks to Go - Register now for FREE

Geeks To Go is a helpful hub, where thousands of volunteer geeks quickly serve friendly answers and support. Check out the forums and get free advice from the experts. Register now to gain access to all of our features, it's FREE and only takes one minute. Once registered and logged in, you will be able to create topics, post replies to existing threads, give reputation to your fellow members, get your own private messenger, post status updates, manage your profile and so much more.

Create Account How it Works
Photo

bsod help me please


  • Please log in to reply

#61
rshaffer61

rshaffer61

    Moderator

  • Moderator
  • 34,114 posts
Grrr after trying a game let me know.
We may have to do a repair installation to get it corrected.
There is a feedback forum if you want to leave feedback be it good or bad for everyone to see.
  • 0

Advertisements


#62
John Lauhoff

John Lauhoff

    Member

  • Topic Starter
  • Member
  • PipPipPip
  • 104 posts
On Sat 5/5/2012 3:52:00 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\050412-33727-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)
Bugcheck code: 0x1 (0x74962E09, 0x0, 0xFFFF0000, 0xFFFFF88008703CA0)
Error: APC_INDEX_MISMATCH
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 there has been a mismatch in the APC state index.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.

  • 0

#63
John Lauhoff

John Lauhoff

    Member

  • Topic Starter
  • Member
  • PipPipPip
  • 104 posts
On Sat 5/5/2012 4:07:43 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\050412-32526-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC10)
Bugcheck code: 0x1E (0x0, 0x0, 0x0, 0x0)
Error: KMODE_EXCEPTION_NOT_HANDLED
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 a kernel-mode program generated an exception which the error handler did not catch.
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.

  • 0

#64
rshaffer61

rshaffer61

    Moderator

  • Moderator
  • 34,114 posts
OK the error suggest a possible driver, updates from Microsoft or the Service pack is not up to date and finally a possible infection.
  • 0

#65
John Lauhoff

John Lauhoff

    Member

  • Topic Starter
  • Member
  • PipPipPip
  • 104 posts
so whats my next move
  • 0

#66
rshaffer61

rshaffer61

    Moderator

  • Moderator
  • 34,114 posts
First is to make sure you have all critical updates from Microsoft's Window Update site. If you are using IE for your browser go up to Tools and then click on Windows update.
Get all Critical updates and lets see what it finds.
  • 0

#67
John Lauhoff

John Lauhoff

    Member

  • Topic Starter
  • Member
  • PipPipPip
  • 104 posts
i nstalled bout 23 optional and 3 important restarting now
  • 0

#68
John Lauhoff

John Lauhoff

    Member

  • Topic Starter
  • Member
  • PipPipPip
  • 104 posts
On Sat 5/5/2012 4:33:11 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\050412-54896-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC80)
Bugcheck code: 0xF4 (0x3, 0xFFFFFA80096A0B30, 0xFFFFFA80096A0E10, 0xFFFFF80003184660)
Error: CRITICAL_OBJECT_TERMINATION
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 a process or thread crucial to system operation has unexpectedly exited or been terminated.
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 5/5/2012 4:33:11 AM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0xF4 (0x3, 0xFFFFFA80096A0B30, 0xFFFFFA80096A0E10, 0xFFFFF80003184660)
Error: CRITICAL_OBJECT_TERMINATION
Bug check description: This indicates that a process or thread crucial to system operation has unexpectedly exited or been terminated.
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.

  • 0

#69
John Lauhoff

John Lauhoff

    Member

  • Topic Starter
  • Member
  • PipPipPip
  • 104 posts
crash dump file: C:\Windows\Minidump\050512-33633-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC80)
Bugcheck code: 0x1A (0x41287, 0x295F, 0x0, 0x0)
Error: MEMORY_MANAGEMENT
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 a severe memory management error occurred.
This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.

  • 0

#70
rshaffer61

rshaffer61

    Moderator

  • Moderator
  • 34,114 posts
OK the issue seems to be the Win 7 OS itself that is causing your problem so lets do a Repair Installation by following the steps HERE.
Please read and follow all instructions carefully.
  • 0

Advertisements


#71
John Lauhoff

John Lauhoff

    Member

  • Topic Starter
  • Member
  • PipPipPip
  • 104 posts
ran repair then launched a game and

On Sat 5/5/2012 7:50:18 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\050512-36114-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x71ED0)
Bugcheck code: 0x1E (0x0, 0x0, 0x0, 0x0)
Error: KMODE_EXCEPTION_NOT_HANDLED
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 a kernel-mode program generated an exception which the error handler did not catch.
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 5/5/2012 7:50:18 PM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: usbehci.sys (usbehci+0x2A72)
Bugcheck code: 0x1E (0x0, 0x0, 0x0, 0x0)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32\drivers\usbehci.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: EHCI eUSB Miniport Driver
Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
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.

  • 0

#72
John Lauhoff

John Lauhoff

    Member

  • Topic Starter
  • Member
  • PipPipPip
  • 104 posts
well got updates for windows to install lol
  • 0

#73
rshaffer61

rshaffer61

    Moderator

  • Moderator
  • 34,114 posts

well got updates for windows to install lol


Was that after the previous bsods?
  • 0

#74
John Lauhoff

John Lauhoff

    Member

  • Topic Starter
  • Member
  • PipPipPip
  • 104 posts
yes i went straight from launch to game without doing windows update stupid lol
  • 0

#75
rshaffer61

rshaffer61

    Moderator

  • Moderator
  • 34,114 posts
OK no problem...now that you have all the windows updates try the game and see if it works now.
  • 0






Similar Topics

0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users

As Featured On:

Microsoft Yahoo BBC MSN PC Magazine Washington Post HP