 | |
| |
| 26 Jun 2010 | #1 |
| | BSOD, Dump Provided This is a bit of a mystery to me. Initially, I thought it was the Intel HD video card drivers...but now I'm not sure. Ran Memtest, RAM is o.k. after 27 passes. Did a few other things...still can't track it down. Any help is appreciated! |
My System Specs | |
| 26 Jun 2010 | #2 |
| | Welcome to the forum. The dmp indicates memory issues. Quote: Code: Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Mini Kernel Dump File: Only registers and stack trace are available
Executable search path is:
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Machine Name:
Kernel base = 0xfffff800`01852000 PsLoadedModuleList = 0xfffff800`01a8fe50
Debug session time: Sat Jun 26 21:34:51.946 2010 (GMT-4)
System Uptime: 0 days 0:17:31.618
Loading Kernel Symbols
...............................................................
................................................................
..........
Loading unloaded module list
.....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 4E, {99, 7180, 2, 49e81}
Probably caused by : memory_corruption ( nt!MiBadShareCount+4c )
Followup: MachineOwner
---------
2: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
PFN_LIST_CORRUPT (4e)
Typically caused by drivers passing bad memory descriptor lists (ie: calling
MmUnlockPages twice with the same list, etc). If a kernel debugger is
available get the stack trace.
Arguments:
Arg1: 0000000000000099, A PTE or PFN is corrupt
Arg2: 0000000000007180, page frame number
Arg3: 0000000000000002, current page state
Arg4: 0000000000049e81, 0
Debugging Details:
------------------
BUGCHECK_STR: 0x4E_99
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
PROCESS_NAME: svchost.exe
CURRENT_IRQL: 2
LAST_CONTROL_TRANSFER: from fffff800019522bc to fffff800018c2600
STACK_TEXT:
fffff880`0251d988 fffff800`019522bc : 00000000`0000004e 00000000`00000099 00000000`00007180 00000000`00000002 : nt!KeBugCheckEx
fffff880`0251d990 fffff800`0192571a : af100000`07180025 fffffa80`004e4d70 00000000`00000002 00000000`00000000 : nt!MiBadShareCount+0x4c
fffff880`0251d9d0 fffff800`019943cd : 00000000`00000001 fffff700`01080488 00000000`00001af1 fffffa80`03e18ec8 : nt! ?? ::FNODOBFM::`string'+0x17bf4
fffff880`0251daf0 fffff800`019d9337 : ffffffff`ffffffff fffff880`0251dca0 fffffa80`03079b60 00000000`00000001 : nt!MiFreeWsle+0xcd
fffff880`0251db30 fffff800`018c1853 : fffffa80`03079b60 00000000`076feaa0 00000000`076feaa8 00000000`0039a2f0 : nt!NtUnlockVirtualMemory+0x227
fffff880`0251dc20 00000000`7778161a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`076fea68 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7778161a
STACK_COMMAND: kb
FOLLOWUP_IP:
nt!MiBadShareCount+4c
fffff800`019522bc cc int 3
SYMBOL_STACK_INDEX: 1
SYMBOL_NAME: nt!MiBadShareCount+4c
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
DEBUG_FLR_IMAGE_TIMESTAMP: 4b88cfeb
IMAGE_NAME: memory_corruption
FAILURE_BUCKET_ID: X64_0x4E_99_nt!MiBadShareCount+4c
BUCKET_ID: X64_0x4E_99_nt!MiBadShareCount+4c
Followup: MachineOwner
--------- dadder.sys Thu Aug 02 05:33:03 2007 This a mouse driver - Razer Habu USB Optical Mouse Driver - Razer Habu USB Optical Mouse - Razer (Asia-Pacific) Pte Ltd. I recommend that you update this driver or upgrade your mouse. If you upgrade your mouse, uninstall this driver or navigate to c:\windows\system32\drivers and rename the driver from dadder.sys to dadder.bak. Reboot. I recommend that you run memtest86.Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder. Boot from the CD, and leave it running for at least 5 passes. Post back with the results of the test. If you have any questions, please ask. Last edited by CarlTR6; 26 Jun 2010 at 10:02 PM.. |
| My System Specs |
| 26 Jun 2010 | #3 |
| | Much appreciated. -Core i3 -2 Gigs of DDR3 1333 Gold Series OCZ RAM -Biostar TH55XE Mobo |
| My System Specs |
| . |
| |
| 26 Jun 2010 | #4 |
| | I have edited the original post. You may have to refresh the page. Please fill out your system information. Go to your User CP at the top of the page, look in the left column and click on Edit system specs. Filling in your specs will help us help you. You can make this easier by downloading Speccy. |
| My System Specs |
| 26 Jun 2010 | #5 |
| | Again, appreciated. I have updated the specs in the CP accordingly. Memtest86+ ran for 27 passes with no errors detected (as somewhat indicated in the OP -- I mentioned memtest -- but it was, in fact, 86+ -- run straight from boot). When you say memory, does this indicate a problem with the ram? |
| My System Specs |
| 26 Jun 2010 | #6 |
| | 
Quote: Originally Posted by telarium  Again, appreciated. I have updated the specs in the CP accordingly. Memtest86+ ran for 27 passes with no errors detected (as somewhat indicated in the OP -- I mentioned memtest -- but it was, in fact, 86+ -- run straight from boot). When you say memory, does this indicate a problem with the ram?  By the way, a bad or failing power supply can cause BSOD's.That says that your RAM is OK. A problem indicating memory includes bad or defective RAM, a faulty RAM slot, or something interfering with memory such as drivers, incompatible software or other hardware problems. I wanted to start with making sure your RAM is OK. It is possible that the old mouse driver is the source of the problem. We need to eliminate that as a cause. By the way, both of the dmp files were virtually identical. I am going to bed now; I will check this thread tomorrow. Others of the BOSD team may well drop by and pick it up. I wish you the best in getting your system running smoothly. |
| My System Specs |
| 26 Jun 2010 | #7 |
| | Many, many thanks. I will throw on a different mouse - to try and narrow down the issue. That may very well be the cause of the issue. I have re-seated the RAM into a different slot (no effect) -- so I don't believe, unless all the slots are bad, that it is a slot issue. The 'other hardware issues' worries me quite a bit -- but I'll keep troubleshooting! |
| My System Specs |
| 26 Jun 2010 | #8 |
| | You are very welcome. If the slot were bad, it would have showed up in memtest86 as bad RAM. After you upgrade your mouse, see how your system runs. Post back and let us know and post back ASAP if you get another BSOD. Good night. |
| My System Specs |
| 26 Jun 2010 | #9 |
| |
Quote: Originally Posted by telarium Many, many thanks. I will throw on a different mouse - to try and narrow down the issue. That may very well be the cause of the issue. I have re-seated the RAM into a different slot (no effect) -- so I don't believe, unless all the slots are bad, that it is a slot issue. The 'other hardware issues' worries me quite a bit -- but I'll keep troubleshooting! Ken |
| My System Specs |
| 27 Jun 2010 | #10 |
| | Primarily that it may be something on the mobo that I might never be able to pin down...or eliminate by trial and error. |
| My System Specs |
 |
BSOD, Dump Provided problems?
| Thread Tools | |
| Similar help and support threads for: BSOD, Dump Provided | ||||
| Thread | Forum | |||
| BSOD -Full Info Provided. irql_not_less_or_equal | BSOD Help and Support | |||
| Windows 7 64 bit spontaneous restart, Memory dump file provided, ty | BSOD Help and Support | |||
| BSOD on Windows7 Home Premium 64 bit, dump file url provided,Thanks | BSOD Help and Support | |||
| Random BSOD, full details provided, please help | BSOD Help and Support | |||
| BSOD, Dump Provided | BSOD Help and Support | |||
All times are GMT -5. The time now is 05:09 AM.
