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: Please help.

10 Sep 2010   #21
HelpMehPlz

MS Windows 7 Home Premium 64-bit
 
 

Ok, sorry I wasn't understanding this earlier.

I updated My System Specs for you.

The drivers which I updated from the HP website include:
1 - Original AMD USB Filter Driver
2 - Original Realtek Networking Controller Driver
3 - Original AMD RAID Controller Driver
4 - Original ATI Graphics Driver
5 - Original Ralink Wireless Networking Controller Driver
6 - Original Realtek High Definition Audio Driver

I am not sure if there are any updates for my BIOS. I tried looking on the HP website for an update and it stated that if there is no update within the search for Support&Drivers, that the one I have is current. However, I checked the FOXCONN website just in case. I was unable to find my motherboard, unless I was searching for it incorrectly.

I went into my BIOS and the revision date of that at the moment said : 6.03 04/12/10

Today I've had three more BSoDs. Attached are those files.


My System SpecsSystem Spec
.
10 Sep 2010   #22
CarlTR6

Windows 7 Ultimate 32 bit
 
 

These dumps all point to hardware issues and memory corruption; but they don't tell us anything specific.

Error code D1, DRIVER_IRQL_NOT_LESS_OR_EQUAL - usually caused by a device driver.

Error code A, IRQL_NOT_LESS_OR_EQUAL - usual causes are Kernel mode driver, System Service, BIOS, Windows, Virus scanner, Backup tool, compatibility.

Error code 4E, PFN_LIST_CORRUPT - usual causes are Device driver, ?memory.

Code:
Kernel base = 0xfffff800`02a60000 PsLoadedModuleList = 0xfffff800`02c9de50
Debug session time: Fri Sep 10 10:36:12.646 2010 (GMT-4)
System Uptime: 0 days 0:00:58.098
Loading Kernel Symbols
...............................................................
................................................................
..................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck D1, {100004, 2, 0, fffff880052a7505}

Probably caused by : USBPORT.SYS ( USBPORT!USBPORT_DereferenceDeviceHandle+ad )

Followup: MachineOwner
---------

3: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high.  This is usually
caused by drivers using improper addresses.
If kernel debugger is available get stack backtrace.
Arguments:
Arg1: 0000000000100004, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
Arg4: fffff880052a7505, address which referenced memory

Debugging Details:
------------------


READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002d080e0
 0000000000100004 

CURRENT_IRQL:  2

FAULTING_IP: 
USBPORT!USBPORT_DereferenceDeviceHandle+ad
fffff880`052a7505 488b4320        mov     rax,qword ptr [rbx+20h]

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xD1

PROCESS_NAME:  System

TRAP_FRAME:  fffff88002ffb930 -- (.trap 0xfffff88002ffb930)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000100004 rbx=0000000000000000 rcx=fffffa8005e2dcb0
rdx=0000000048766544 rsi=0000000000000000 rdi=0000000000000000
rip=fffff880052a7505 rsp=fffff88002ffbac0 rbp=0000000000000000
 r8=0000000048766544  r9=0000000000000000 r10=fffffa80036d3680
r11=0000000000000002 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz ac pe cy
USBPORT!USBPORT_DereferenceDeviceHandle+0xad:
fffff880`052a7505 488b4320        mov     rax,qword ptr [rbx+20h] ds:07ff:00000000`00000020=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002acfca9 to fffff80002ad0740

STACK_TEXT:  
fffff880`02ffb7e8 fffff800`02acfca9 : 00000000`0000000a 00000000`00100004 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff880`02ffb7f0 fffff800`02ace920 : fffffa80`069bcdb3 00000000`000fffe4 fffffa80`00000000 fffffa80`00000000 : nt!KiBugCheckDispatch+0x69
fffff880`02ffb930 fffff880`052a7505 : fffffa80`05260050 00000000`00000220 fffffa80`05e2dcb0 fffffa80`052601a0 : nt!KiPageFault+0x260
fffff880`02ffbac0 fffff880`052925bc : fffffa80`05260050 fffffa80`06beb402 00000000`00000000 fffffa80`052601a0 : USBPORT!USBPORT_DereferenceDeviceHandle+0xad
fffff880`02ffbb20 fffff880`05292ab7 : fffffa80`06ad8602 fffffa80`05151010 00000000`ffffffff fffffa80`05260ea8 : USBPORT!USBPORT_Core_iCompleteDoneTransfer+0x9f8
fffff880`02ffbc00 fffff880`0529064f : fffffa80`05260ea8 fffffa80`052601a0 fffffa80`05261040 00000000`00000000 : USBPORT!USBPORT_Core_iIrpCsqCompleteDoneTransfer+0x3a7
fffff880`02ffbc60 fffff880`05281f89 : fffffa80`05260050 00000000`00000000 fffffa80`05260e02 fffffa80`05260ea8 : USBPORT!USBPORT_Core_UsbIocDpc_Worker+0xf3
fffff880`02ffbca0 fffff800`02adbbfc : fffff880`02fd3180 fffffa80`05260ea8 fffffa80`05260ec0 00000000`00000000 : USBPORT!USBPORT_Xdpc_Worker+0x1d9
fffff880`02ffbcd0 fffff800`02ad8eea : fffff880`02fd3180 fffff880`02fddfc0 00000000`00000000 fffff880`05281db0 : nt!KiRetireDpcList+0x1bc
fffff880`02ffbd80 00000000`00000000 : fffff880`02ffc000 fffff880`02ff6000 fffff880`02ffbd40 00000000`00000000 : nt!KiIdleLoop+0x5a


STACK_COMMAND:  kb

FOLLOWUP_IP: 
USBPORT!USBPORT_DereferenceDeviceHandle+ad
fffff880`052a7505 488b4320        mov     rax,qword ptr [rbx+20h]

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  USBPORT!USBPORT_DereferenceDeviceHandle+ad

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: USBPORT

IMAGE_NAME:  USBPORT.SYS

DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bcc07

FAILURE_BUCKET_ID:  X64_0xD1_USBPORT!USBPORT_DereferenceDeviceHandle+ad

BUCKET_ID:  X64_0xD1_USBPORT!USBPORT_DereferenceDeviceHandle+ad

Followup: MachineOwner
---------

Kernel base = 0xfffff800`02a1d000 PsLoadedModuleList = 0xfffff800`02c5ae50
Debug session time: Fri Sep 10 10:34:42.462 2010 (GMT-4)
System Uptime: 0 days 1:45:18.914
Loading Kernel Symbols
...............................................................
................................................................
...................
Loading User Symbols
Loading unloaded module list
........
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck A, {0, 2, 1, fffff80002a6a087}

Probably caused by : ntkrnlmp.exe ( nt!KiDeliverApc+197 )

Followup: MachineOwner
---------

1: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

IRQL_NOT_LESS_OR_EQUAL (a)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high.  This is usually
caused by drivers using improper addresses.
If a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: 0000000000000000, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000001, bitfield :
    bit 0 : value 0 = read operation, 1 = write operation
    bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: fffff80002a6a087, address which referenced memory

Debugging Details:
------------------


WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff80002cc50e0
 0000000000000000 

CURRENT_IRQL:  2

FAULTING_IP: 
nt!KiDeliverApc+197
fffff800`02a6a087 488910          mov     qword ptr [rax],rdx

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xA

PROCESS_NAME:  Wow.exe

TRAP_FRAME:  fffff88007f6a8b0 -- (.trap 0xfffff88007f6a8b0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=0000000000000000
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002a6a087 rsp=fffff88007f6aa40 rbp=0000000000000000
 r8=fffffa8006446bb0  r9=0000000000000000 r10=fffffa8006446ba0
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl zr na po nc
nt!KiDeliverApc+0x197:
fffff800`02a6a087 488910          mov     qword ptr [rax],rdx ds:10bd:00000000`00000000=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002a8cca9 to fffff80002a8d740

STACK_TEXT:  
fffff880`07f6a768 fffff800`02a8cca9 : 00000000`0000000a 00000000`00000000 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
fffff880`07f6a770 fffff800`02a8b920 : 00000000`00000000 fffffa80`06456b60 00000000`00000000 fffffa80`046d0cc0 : nt!KiBugCheckDispatch+0x69
fffff880`07f6a8b0 fffff800`02a6a087 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x260
fffff880`07f6aa40 fffff800`02a40bb5 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDeliverApc+0x197
fffff880`07f6aac0 fffff800`02d82016 : fffffa80`06456b60 fffffa80`06456b60 00000000`00000000 00000000`00000003 : nt!KiCheckForKernelApcDelivery+0x25
fffff880`07f6aaf0 fffff800`02daa139 : 0000000c`56835300 00000000`00000002 fffffa80`03711200 00000000`0b8aff01 : nt!ObReferenceObjectByHandleWithTag+0x3b6
fffff880`07f6abc0 fffff800`02a8c993 : fffffa80`06456b60 fffff880`07f6ac01 00000000`00da7a64 fffffa80`06dc44a0 : nt!NtSetEvent+0x75
fffff880`07f6ac20 00000000`72b02dd9 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`0969f0f8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x72b02dd9


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!KiDeliverApc+197
fffff800`02a6a087 488910          mov     qword ptr [rax],rdx

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  nt!KiDeliverApc+197

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4c1c44a9

FAILURE_BUCKET_ID:  X64_0xA_nt!KiDeliverApc+197

BUCKET_ID:  X64_0xA_nt!KiDeliverApc+197

Followup: MachineOwner
---------

Kernel base = 0xfffff800`02a14000 PsLoadedModuleList = 0xfffff800`02c51e50
Debug session time: Fri Sep 10 21:19:42.572 2010 (GMT-4)
System Uptime: 0 days 0:01:29.023
Loading Kernel Symbols
...............................................................
................................................................
...................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 4E, {99, 5415b, 2, 8e641}

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: 000000000005415b, page frame number
Arg3: 0000000000000002, current page state
Arg4: 000000000008e641, 0

Debugging Details:
------------------


BUGCHECK_STR:  0x4E_99

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  2

LAST_CONTROL_TRANSFER:  from fffff80002b1438c to fffff80002a84740

STACK_TEXT:  
fffff880`031936e8 fffff800`02b1438c : 00000000`0000004e 00000000`00000099 00000000`0005415b 00000000`00000002 : nt!KeBugCheckEx
fffff880`031936f0 fffff800`02a28407 : fffff980`0cf00005 fffff780`c0000000 fffff880`031937c0 fffff880`031937c0 : nt!MiBadShareCount+0x4c
fffff880`03193730 fffff800`02d9b1b5 : fffff980`0cf40000 fffff8a0`02783480 00000000`00000000 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x2c15b
fffff880`03193a10 fffff800`02a9d567 : 00000000`00000000 fffffa80`036ac200 00000000`00000000 00000000`00040000 : nt!CcUnmapVacb+0x5d
fffff880`03193a50 fffff800`02a74274 : 00000000`00000001 fffffa80`06753660 fffffa80`0380f000 00000000`00000000 : nt!CcUnmapVacbArray+0x1b7
fffff880`03193ae0 fffff800`02a77d1c : fffffa80`0380f010 00000000`00000011 fffffa80`0380f010 fffffa80`00000000 : nt!CcDeleteSharedCacheMap+0x140
fffff880`03193b50 fffff800`02a78520 : fffff800`02c8b100 fffff880`03193c58 00000000`00000000 fffff800`00000000 : nt!CcWriteBehind+0x5bc
fffff880`03193c00 fffff800`02a91961 : fffffa80`036d93d0 fffff800`02a78358 fffff800`02c8b140 fffffa80`00000000 : nt!CcWorkerThread+0x1c8
fffff880`03193cb0 fffff800`02d28c06 : 2c4a8b30`74010442 fffffa80`036f1680 00000000`00000080 fffffa80`03669b30 : nt!ExpWorkerThread+0x111
fffff880`03193d40 fffff800`02a62c26 : fffff880`02f63180 fffffa80`036f1680 fffff880`02f6dfc0 4cd88b49`00000004 : nt!PspSystemThreadStartup+0x5a
fffff880`03193d80 00000000`00000000 : fffff880`03194000 fffff880`0318e000 fffff880`03192d20 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!MiBadShareCount+4c
fffff800`02b1438c cc              int     3

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt!MiBadShareCount+4c

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP:  4c1c44a9

IMAGE_NAME:  memory_corruption

FAILURE_BUCKET_ID:  X64_0x4E_99_nt!MiBadShareCount+4c

BUCKET_ID:  X64_0x4E_99_nt!MiBadShareCount+4c

Followup: MachineOwner
---------
I notice two of these crashes occurred during or shortly after boot. That is a sign of a hardware or driver problem. My advice is to have your computer checked by a technician while it is still under warranty. That said, if your still want to try, you can run some hardware tests.

Test your RAM following this excellent tutorial. This will take some time. RAM - Test with Memtest86+. Post back with your results.

This driver is slightly out of date and was implicated in one of the dumps:

ahcix64s.sys Tue Mar 17 02:38:19 2009 - This is an AMD chipset driver apparently. Read the following threads:

AMD Game Forums - Need a signed ahcix64s.sys

AMD Game Forums - W7 startup stops at loading ahcix64s.sys for a minute or so...

I also find this outdated driver.

amdsbs.sys Fri Mar 20 14:36:03 2009 -
AMD Technology AHCI Compatible Controller Driver for Windows family is a driver file from company AMD Technologies Inc. belonging to product AMD Technology AHCI Compatible Controller.

See if you can find updates for these two drivers.

Enable Driver Verifier using this tutorial; read it carefully: Driver Verifier - Enable and Disable
. Upload any Driver Verifier enabled dumps you get.

My recommendation still is to take your computer to the shop while it is still under warranty. I realize that is a PITA; but your computer should be able to run Windows 7 out of the box.
My System SpecsSystem Spec
11 Sep 2010   #23
HelpMehPlz

MS Windows 7 Home Premium 64-bit
 
 

Well, HP online technicians were no help whatsoever. They did a Hardware Diagnostics test with their own program, and everything passed. I feel that I doubt this. The technician I spoke with said to do a complete system recovery as they assume it is a software issue. Before I do this, however, I will give your methods a try of course. I also received a couple of more BSoDs this evening. For the record. Haha.

Am I able to take my computer anywhere for repair under warranty...maybe I should go read what my warranty says first...
My System SpecsSystem Spec
.

11 Sep 2010   #24
Dave76

Microsoft Community Contributor Award Recipient

Windows 7 Ult x64 - SP1/ Windows 8 Pro x64
 
 

That is a good idea, this is starting to sound like the AMD integrated memory controller issue.

First run the tests that Carl recommended, this might be the evidence you need to get HP the fix it.


Try to find new or even the same chipset drivers and update or re-install them.

A new BIOS version is the next thing to confirm.

If these don't solve the issues, try to get HP to replace the RAM.

Let us know the results of the tests.
My System SpecsSystem Spec
12 Sep 2010   #25
HelpMehPlz

MS Windows 7 Home Premium 64-bit
 
 

Well, I did the Memtest. I let it run overnight, it did 9 passes and found no errors.

Yesterday, my computer ran fine. This is rather perplexing.

As far as those driver updates go, I can't seem to find any. The forums about the ahcix64s.sys are beyond my knowledge. I'm not sure if I feel comfortable handling any of that.

And how would I go about finding a new BIOS version, if that is the case.

Oh I also enabled the driver verifier.
My System SpecsSystem Spec
12 Sep 2010   #26
Dave76

Microsoft Community Contributor Award Recipient

Windows 7 Ult x64 - SP1/ Windows 8 Pro x64
 
 

Looks like your moving in the right direction.

You need to knock off the possibilities one at a time.

That's a good sign that the RAM passed.

Checked your HP site and there's no BIOS listed, probably means there is no update yet.

The Driver Verifier will BSoD if it finds a faulty driver.
My System SpecsSystem Spec
12 Sep 2010   #27
HelpMehPlz

MS Windows 7 Home Premium 64-bit
 
 

Ok good to know, thanks for all the help, I will keep you updated!
My System SpecsSystem Spec
12 Sep 2010   #28
CarlTR6

Windows 7 Ultimate 32 bit
 
 

Quote   Quote: Originally Posted by HelpMehPlz View Post
Well, I did the Memtest. I let it run overnight, it did 9 passes and found no errors.

Yesterday, my computer ran fine. This is rather perplexing.

As far as those driver updates go, I can't seem to find any. The forums about the ahcix64s.sys are beyond my knowledge. I'm not sure if I feel comfortable handling any of that.

And how would I go about finding a new BIOS version, if that is the case.

Oh I also enabled the driver verifier.
Quote   Quote: Originally Posted by Dave76 View Post
Look like your moving in the right direction.

You need to knock off the possibilities one at a time.

That's a good sign that the RAM passed.

Checked your the HP site and there's no BIOS listed, probably means there is no update yet.

The Driver Verifier will BSoD if it finds a faulty driver.
Glad to hear that your RAM passed. We can mark that one off. As Dave advised, go ahead with Driver Verifier. We will worry about ahcix64s.sys later. It is one of your chipset drivers.
My System SpecsSystem Spec
13 Sep 2010   #29
HelpMehPlz

MS Windows 7 Home Premium 64-bit
 
 

You got it. So far so good. Trying not to get my hopes up though. Just in case.
My System SpecsSystem Spec
16 Sep 2010   #30
HelpMehPlz

MS Windows 7 Home Premium 64-bit
 
 

Well, running smoothly. Thought maybe I'd post an update. I honestly think that the program SUPER Anti-Spyware was causing all of my crashes. I recall removing it before things started looking better. This may be good for future reference. And, a bit embarrassing on my part, I should have removed all software sooner.
My System SpecsSystem Spec
Reply

 Please help.




Thread Tools



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 14:32.
Twitter Facebook Google+ Seven Forums iOS App Seven Forums Android App