Question Locked

Looking for BSOD solution

0 helpful
17 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

When I power up my PC, I get the BSOD. Then I start in safe mode and restart...BSOD again. But I keep going to safe mode then restarting and after about ten times, PC starts normally. Now, I hibernate instead of shutting down, and 99% of the time it will awaken normally; 1% of the time the BSOD again.

When running normally, PC runs good. Using McAfee and scanned with Housecall; nothing found.

Running Vista Home Premium. The point at which the BSOD occurs is when the screen is black, except for "Microsoft Corporation" at the bottom and the status bar with the running green indicator right above it.

Using Vista repair utility found nothing to repair. This problem also causes some updates to fail if the system must be restarted.

I reinstalled Vista without reformatting, did not fix problem.

I needed more drive space anyway, so installed new HD, removed old one, installed Vista from original CD. Same problem.

Where should I look next? Vista memory test found no problem with memory.

MB is Gigabyte GA-EP35-DS3P

Thank you for your input!

17 replies

by older mycroft

It's for TELLING you what is wrong.

It's also so that you can tell us what is wrong. You see all the words written on the Blue Screen of Death?

Try typing some of them here. Especially the ERROR and the CODES below it.

They're not written there for fun. ;)

by raihan.nur

Stop : 0*0000007E(0C0000006,0*806A2760,0*F7BC06E8,0*F7BC03E4)
what should i do ? plz help

by ic-it

You may need to turn off automatic reboot on error to read the BSOD details. Please do so and post the actual error code and any modules that it points to i.e. the driver win32k.sys etc.

It could very well be a corrupt or poorly written driver.

by dshardy2004

Here's what the BSOD says:

BAD POOL CALLER
stop: 0x000000c2, (0x00000007, 0x00000113D, 0x00090211, 0x8EE1A090)

by dshardy2004

For what it's worth, I was going to add that the machine worked good for 8 months before this started.

by ic-it

installed a new driver? That error commonly is caused by a driver issue.

It may simply need the Motherboard's chipset drivers installed.

by peconet tietokoneet

The following procedure describes how to debug a OxC2 stop.

First, check the stop documentation. For example:

BAD_POOL_CALLER (0xC2)

The current thread is making a bad pool request. Typically this is at a bad IRQL level or double freeing the same allocation, etc.

1 - type of pool violation the caller is guilty of.
6 - the pool address being freed is already free.
7 - the pool address being freed is already free.
8 - parameter 2 is the IRQL allocating at, parameter 3 is the pool type
9 - parameter 2 is the IRQL freeing at, parameter 3 is the pool type

Parameter 1 = 0x1, 0x2, or 0x4 : Pool header has been corrupted
Parameter 2 = Pointer to pool header
Parameter 3 = First part of pool header contents
Parameter 4 = 0

Parameter 1 = 0x6 : Attempt to free pool which was already freed
Parameter 2 = Reserved (__LINE__)
Parameter 3 = Pointer to pool header
Parameter 4 = Pool header contents

Parameter 1 = 0x7 : Attempt to free pool which was already freed
Parameter 2 = Reserved (__LINE__)
Parameter 3 = Pointer to pool header
Parameter 4 = 0

Parameter 1 = 0x8 : Attempt to allocate pool at invalid IRQL
Parameter 2 = Current IRQL
Parameter 3 = Pool type
Parameter 4 = Size of allocation

Parameter 1 = 0x9 : Attempt to free pool at invalid IRQL
Parameter 2 = Current IRQL
Parameter 3 = Pool type
Parameter 4 = Address of pool

Parameter 1 = 0x40 : Attempt to free usermode address to kernel pool
Parameter 2 = Starting address
Parameter 3 = Start of system address space
Parameter 4 = 0

Parameter 1 = 0x41 : Attempt to free a non-allocated nonpaged pool
address
Parameter 2 = Starting address
Parameter 3 = physical page frame
Parameter 4 = highest physical page frame

Parameter 1 = 0x50 : Attempt to free a non-allocated paged pool address
Parameter 2 = Starting address
Parameter 3 = Start offset in pages from beginning of paged pool
Parameter 4 = Size in bytes of paged pool

Parameter 1 = 0x99 : Attempt to free pool with invalid address (or
corruption in pool header)
Parameter 2 = Address being freed
Parameter 3 = 0
Parameter 4 = 0

After you have collected detailed information about the 0xC2 stop, use the debugger:

E:\bin>i386kd -z K:\DOWNLOAD\memory.dmp
Loading Dump File [K:\DOWNLOAD\memory.dmp]
Full Kernel Dump File
...
0: kd> !reload GOOD HOUSEKEEPING DONE HERE

0: kd> dd kibugcheckdata l8 DUMPING THE ERROR

8047fba0 000000c2 00000007 00000b68 815bade0
8047fbb0 815bade8 e1007000 00000000 818988c0

0: kd> kv DUMPING STACK

ChildEBP RetAddr Args to Child
bdce0348 be11dc84 e1fff000 a08d0008 000007f8 banshee!vH3ImageTransferMm32
bdce037c be116f18 be85fd78 00000001 bdce03dc banshee!vMmXferNative
bdce03ac be113eec e1fff000 e25e2a38 bdce03dc banshee!vPutBits
bdce03e8 a008e47f e1ff86f8 e25e2a38 e1fef908 banshee!DrvCopyBits
bdce0430 a008e899 be113d40 bdce04d8 e1ff86f8 win32k!OffCopyBits
bdce04e4 a008e4d1 e1ff86f8 e25e2a38 00000000 win32k!SpBitBlt

The stop documentation indicates that memory is being freed. This information is indicated by the following line:
Parameter 1 = 0x7: Attempt to free pool which was already freed.
But the stack shows that the video card is in the process of a write, so you must continue to investigate. First, you must determine if this computer is a multiprocessor.

0: kd> ~1 SWITCH PROC

1: kd> kv DUMPING STACK

ChildEBP RetAddr Args to Child
bde81b7c 8046894d 815bade8 00000000 be03bb2b ntkrnlmp!ExFreePoolWithTag
bde81b88 be03bb2b 815bade8 be03ca94 815bade8 ntkrnlmp!ExFreePool
00000128 00000000 00000000 00000000 00000000 BADDRIVER

The preceding text indicates that memory is freed through the driver drivername. This could be the possible root cause.

Next, define the driver:

1: kd> !drivers
Loaded System Driver Summary

Base Code Size Data Size Driver Name Creation Time
80400000 139f40 (1255 kb) 4f3c0 (316 kb) ntoskrnl.exe Tue Dec 07 14:05:26 1999
80062000 ffe0 ( 63 kb) 3d60 ( 15 kb) hal.dll Tue Nov 02 20:14:22 1999
ed410000 1760 ( 5 kb) 1000 ( 4 kb) BOOTVID.dll Wed Nov 03 20:24:33 1999
ed49c000 1b00 ( 6 kb) 680 ( 1 kb) gameenum.sys Sat Sep 25 14:35:57 1999
ed080000 a000 ( 40 kb) 20c0 ( 8 kb) VIDEOPRT.SYS Sat Nov 06 16:55:20 1999
bfdcf000 1d480 ( 117 kb) 7520 ( 29 kb) mga64m.sys Mon Nov 29 20:47:46 1999
bfdbc000 11600 ( 69 kb) 1600 ( 5 kb) el90xnd5.sys Fri Oct 29 17:54:34 1999
ed090000 3a60 ( 14 kb) 5980 ( 22 kb) banshee.sys Fri Oct 29 19:00:56 1999
ed5df000 2e0 ( 0 kb) 4a0 ( 1 kb) audstub.sys Sat Sep 25 14:35:33 1999
ed370000 33e0 ( 12 kb) a40 ( 2 kb) raspti.sys Fri Oct 08 16:45:10 1999
ed0c0000 c5e0 ( 49 kb) 20e0 ( 8 kb) parallel.sys Fri Oct 22 18:00:54 1999
ed5e0000 580 ( 1 kb) 540 ( 1 kb) swenum.sys Sat Sep 25 14:36:31 1999
be552000 72a60 ( 458 kb) 13c40 ( 79 kb) mga64d.dll Tue Nov 30 04:33:19 1999
be113000 36f00 ( 219 kb) 7a20 ( 30 kb) banshee.dll Tue Nov 30 04:31:18 1999
be031000 FFFF ( FF kb) FFFF ( F kb) BADDRIVER.sys Mon Feb 30 23:22:43 2000

TOTAL: 7f8dc0 (8163 kb) 172140 (1480 kb) ( 0 kb 0 kb)

The preceding text indicates that the driver is used by a third-party software package. This driver is most likely the cause of the error. To further investigate this issue, search the Microsoft Knowledge Base for more information. Also, check the file properties with Windows Explorer or by using a Hex editor on the file itself. You can also check the vendor's Web site for any updates or known issues.

by dshardy2004

Well,I've been living with this problem for several months. I know I did not update any MB drivers since the unit was new and I'm not sure if any other drivers were updated at that time. I'll see if Gigabyte has some updated ones.

by oh smeg

As this M'Board has 2 PCI-E you have a separate Video Card or cards depending on what is fitted here and what it was built to do.

Col

by rob miners

Minidump Files can be found here. C:\WINDOWS\Minidump\Mini122707-02.dmp

How to read the small memory dump files that Windows creates for debugging

http://support.microsoft.com/kb/315263

To download and install the Windows debugging tools, visit the following Microsoft Web site:

http://www.microsoft.com/whdc/devtools/debugging/default.mspx

Instructions on using Windbg.

Open Windbg and select file, Symbol file path and browse to the Symbol folder that you have downloaded and installed Symbols to, select OK.
Close the workpage and save the Workspace information. This should lock in the Symbol path.
Open Windbg and select file and select Open Crash Dump then navigate to the minidump, highlight it and select Open.
There are two ways to use !analyze -v the easiest is to click on !analyze -v under Bugcheck Analysis.
When you have ran the initial dump if you look to the bottom of the screen you will see kd> to the right of that type in !analyze -v and press the Enter key.
Ctrl + a will let you copy the information and paste it into notepad.

Look to the bottom of the page for information like this. This was fixed by updating the Graphics Drivers.
FAULTING_THREAD: 864f6a98

DEFAULT_BUCKET_ID: GRAPHICS_DRIVER_FAULT

CUSTOMER_CRASH_COUNT: 1

BUGCHECK_STR: 0xEA

PROCESS_NAME: logon.scr

LAST_CONTROL_TRANSFER: from 00000000 to bfef0fea

STACK_TEXT:
f6434e6c 00000000 00000000 00000000 00000000 sgiul50!DrvBitBlt+0x585

STACK_COMMAND: .thread 0xffffffff864f6a98 ; kb

FOLLOWUP_IP:
sgiul50!DrvBitBlt+585
bfef0fea 75f9 jne sgiul50!DrvBitBlt+0x580 (bfef0fe5)

SYMBOL_STACK_INDEX: 0

SYMBOL_NAME: sgiul50!DrvBitBlt+585

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: sgiul50

IMAGE_NAME: sgiul50.dll

DEBUG_FLR_IMAGE_TIMESTAMP: 3b7dfec7

FAILURE_BUCKET_ID: 0xEA_IMAGE_sgiul50.dll_DATE_2001_08_18

BUCKET_ID: 0xEA_IMAGE_sgiul50.dll_DATE_2001_08_18

by oh smeg

This sounds like either a Hardware or Configuration issue and is not related to the OS at all other than the fact that it's not running on that hardware correctly.

Also a P35 M'Board is a bit old for a Vista Install while it may work it's just at the minimum level for a Vista Install and a newer M'Board like a P43 or 45 Chipset would be better.

Also how much RAM is fitted here?

Col

by dshardy2004

Thank you for all the help. Problem solved. Special thanks to those who suggested the windows debugging tools. I found a reference to a .sys file and when I googled it, I found a lot of references to modem drivers. It was at that point that I remembered I had installed a dial up modem from my old system close to a year ago to use with a fax program that never worked right. I yanked it out lightning fast and no more BSOD! Thank you again.

by rob miners

Keep us informed as to your progress if you require further assistance. ;) :D


If you think that any of the posts that have been made by all TechRepublic Members, have solved or contributed to solving the problem, please Mark them as Helpful so that others may benefit from the outcome. ;) :D :-bd


How do I rate the answers to my posted Question?
Click on the answer. Click the Mark "Helpful" button displayed below the post. You may mark more than one answer as "Helpful."

This discussion is closed to new replies.