Multiple BSOD's

kindgreens

New member
Local time
12:17 AM
Messages
4
Hi guys, I've been having multiple BSOD's. All my drivers are up to date. Here is my system hardware:
-MOBO: Foxconn 2AB1
-CPU: AMD Phenom ii x4 925
-RAM: 8 GB Dual channel Micron Technology
-Sound card: Realtek High Definition Audio
-PSU: Thermaltake tr2 650w
-BIOS: American Megatrends Inc. Version 6.02
Win7 home premium 64bit OEM. Service pack 1 installed

I uninstalled the GPU for the time being, using onboard graphics(ATI Radeon HD 4200), to see if that was causing any problems as that is the only recently added hardware, but still getting the BSOD's running the onboard graphics. Win7 home premium 64bit.

I ran verifier, did all test types except for low resource management and selected all non Microsoft drivers. Restarted and got a BSOD right away on start up. It is the dump file with DRIVER_PAGE_FAULT_IN_FREED_SPECIAL_POOL as the bug check string. Hopefully this can narrow the possibilities.

Attached are my recent dump files and screenshots of CPUID for system info.
Any help would be greatly appreciated. Let me know if you need any other info.
Thanks in advance!
 

My Computer

OS
windows 7 Home Premium 64bit
Sorry didn't get the attachments on the last post, here they are.
 

My Computer

OS
windows 7 Home Premium 64bit
My computer is now intermittently losing all output, VGA, all USB ports audio etc, but the power light is still on the computer and the only way I can restart is by holding the power button down and starting back up. There is no dump files being created for this error. Any ideas?
 

My Computer

OS
windows 7 Home Premium 64bit
Your Razer DeathAdder Mouse driver is the cause, please update it
Razer Support
Code:
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

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

Unable to load image \SystemRoot\system32\drivers\danew.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for danew.sys
*** ERROR: Module load completed but symbols could not be loaded for danew.sys
Probably caused by : danew.sys ( danew+6da )


KMODE_EXCEPTION_NOT_HANDLED (1e)
This is a very common bugcheck.  Usually the exception address pinpoints
the driver/function that caused the problem.  Always note this address
as well as the link date of the driver/image that contains this address.
Arguments:
Arg1: 0000000000000000, The exception code that was not handled
Arg2: 0000000000000000, The address that the exception occurred at
Arg3: 0000000000000000, Parameter 0 of the exception
Arg4: 0000000000000000, Parameter 1 of the exception

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


EXCEPTION_CODE: (Win32) 0 (0) - The operation completed successfully.

FAULTING_IP: 
+0
00000000`00000000 ??              ???

EXCEPTION_PARAMETER1:  0000000000000000

EXCEPTION_PARAMETER2:  0000000000000000

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x1E

PROCESS_NAME:  System

CURRENT_IRQL:  2

LAST_CONTROL_TRANSFER:  from fffff80002ad76be to fffff80002adfcd0

STACK_TEXT:  
fffff880`02ffcc98 fffff800`02ad76be : fffffa80`098ac130 00000000`00000000 fffff880`02ffd4a0 fffff800`02b0b890 : nt!KeBugCheck
fffff880`02ffcca0 fffff800`02b0b55d : fffff800`02ce6968 fffff800`02c23cbc fffff800`02a60000 fffff880`02ffd400 : nt!KiKernelCalloutExceptionHandler+0xe
fffff880`02ffccd0 fffff800`02b0a335 : fffff800`02c270fc fffff880`02ffcd48 fffff880`02ffd400 fffff800`02a60000 : nt!RtlpExecuteHandlerForException+0xd
fffff880`02ffcd00 fffff800`02b0d632 : fffff880`02ffd400 fffff880`02ffd4a0 00000000`00000001 00000000`00000000 : nt!RtlDispatchException+0x415
fffff880`02ffd3e0 fffff800`02a9a6ea : fffffa80`082c7000 00000000`00000000 00000000`00000000 fffff800`02a1a6e5 : nt!RtlRaiseStatus+0x4e
fffff880`02ffd980 fffff880`069ce6da : fffffa80`07fc9680 fffff800`00000000 00000000`00000008 fffff800`02a19300 : nt! ?? ::FNODOBFM::`string'+0xf5a9
fffff880`02ffda00 fffffa80`07fc9680 : fffff800`00000000 00000000`00000008 fffff800`02a19300 00000000`00000008 : danew+0x6da
fffff880`02ffda08 fffff800`00000000 : 00000000`00000008 fffff800`02a19300 00000000`00000008 fffff800`02a1969a : 0xfffffa80`07fc9680
fffff880`02ffda10 00000000`00000008 : fffff800`02a19300 00000000`00000008 fffff800`02a1969a fffffa80`080afc60 : 0xfffff800`00000000
fffff880`02ffda18 fffff800`02a19300 : 00000000`00000008 fffff800`02a1969a fffffa80`080afc60 fffff800`02ae3091 : 0x8
fffff880`02ffda20 fffffa80`07fc9690 : fffffa80`07fc9602 fffff880`04f6e6d6 00000000`54627255 00000000`00000220 : hal!HalpDmaAllocateMapRegisters+0x3b8
fffff880`02ffdab0 fffffa80`07fc9602 : fffff880`04f6e6d6 00000000`54627255 00000000`00000220 fffffa80`70627375 : 0xfffffa80`07fc9690
fffff880`02ffdab8 fffff880`04f6e6d6 : 00000000`54627255 00000000`00000220 fffffa80`70627375 00000000`00000000 : 0xfffffa80`07fc9602
fffff880`02ffdac0 fffff880`04f59631 : fffffa80`0820b050 fffffa80`06aa8300 00000000`00000000 00000000`00000000 : USBPORT!USBPORT_DereferenceDeviceHandle+0x14e
fffff880`02ffdb20 fffff880`04f59b0f : fffffa80`078c8002 fffffa80`080afc60 00000000`ffffffff fffffa80`0820beb0 : USBPORT!USBPORT_Core_iCompleteDoneTransfer+0xa15
fffff880`02ffdc00 fffff880`04f5766f : fffffa80`0820beb0 fffffa80`0820b1a0 fffffa80`0820c050 00000000`00000000 : USBPORT!USBPORT_Core_iIrpCsqCompleteDoneTransfer+0x3a7
fffff880`02ffdc60 fffff880`04f48f89 : fffffa80`0820b050 00000000`00000000 fffffa80`0820be02 fffffa80`0820beb0 : USBPORT!USBPORT_Core_UsbIocDpc_Worker+0xf3
fffff880`02ffdca0 fffff800`02aeb10c : fffff880`02fd5180 fffffa80`0820beb0 fffffa80`0820bec8 00000000`00000000 : USBPORT!USBPORT_Xdpc_Worker+0x1d9
fffff880`02ffdcd0 fffff800`02ad7a2a : fffff880`02fd5180 fffff880`02fdffc0 00000000`00000000 fffff880`04f48db0 : nt!KiRetireDpcList+0x1bc
fffff880`02ffdd80 00000000`00000000 : fffff880`02ffe000 fffff880`02ff8000 fffff880`02ffdd40 00000000`00000000 : nt!KiIdleLoop+0x5a


STACK_COMMAND:  kb

FOLLOWUP_IP: 
danew+6da
fffff880`069ce6da ??              ???

SYMBOL_STACK_INDEX:  6

SYMBOL_NAME:  danew+6da

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: danew

IMAGE_NAME:  danew.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4ba87dcd

FAILURE_BUCKET_ID:  X64_0x1E_danew+6da

BUCKET_ID:  X64_0x1E_danew+6da

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

My Computer

Computer type
PC/Desktop
Computer Manufacturer/Model Number
Custom Build
OS
Windows 10 Pro x64, Arch Linux
CPU
Intel Core 2 Quad Q8200 OC'd 3.08GHz
Motherboard
Asus Rampage formula LGA775
Memory
8GB DDR2 900Mhz
Graphics Card(s)
MSI GT730 2GB GDDR5 (Kepler)
Sound Card
Supreme FX2
Monitor(s) Displays
Samsung LS22F350 LED
Screen Resolution
1080P
Hard Drives
Kingston SSDNow UV400 120GB, 500GB Hitachi, 2TB Samsung, 500GB Seagate FreeAgent, 640GB Samsung, 160GB Toshiba (Arch)
PSU
AeroCool 500W Bronze
Cooling
Cooler Master V6 + 3X fans
Keyboard
Prolink keyboard
Mouse
Logitech M705
Internet Speed
1MiB/s
Browser
Chrome Beta
Thanks for the reply. I did just update yesterday and the website said the driver was last modified June 2011 but my computer said that driver was last modified in 2010, thought that was a little odd. I did upgrade the firmware maybe that caused the driver to rollback, idk, I'll try updating the driver again.
 

My Computer

OS
windows 7 Home Premium 64bit
Back
Top