Recently i have been getting lots of BSODs, but that was about ever 2-3 hours, now they are occurring every 6-9 minutes, and they also aren't dumping memory to disk because it just shuts down to fast for me to even be able to see what it says. I have all the latest drivers, BIOS, updates, run anti virus, malware bytes and spybot with no results for any of them. I am starting to think that this is a hardware issue because since I've had this computer, about a year and a half, it has always had sporadic BSODs and other issues. My specs, Vista Ultimate x64, Core 2 quad 9650, Intel DX48BT2 Mobo, OCZ platinum 12800 2x2 GB and a GTX 260. if you need any other information please PM or post here, I really need help this is driving me crazy!!!
It is not dumping memory to disk just because you cant see what it says? Sorry but that is false. Im going to need to see your minidump files from there I can bug check it and tell you the PROBABLE cause of these BSOD's and go from there. To do this simply go to start - > computer - > windows - > minidump inside youll see a ton of .dmp files since you said your computer is BSODing every 6-9 minutes. zip all those files up and upload them to speedyshare located here [url]http://www.speedyshare.com/[/url] hope this helps.
[QUOTE=Java Llama;21578823]Recently i have been getting lots of BSODs, but that was about ever 2-3 hours, now they are occurring every 6-9 minutes, and they also aren't dumping memory to disk because it just shuts down to fast for me to even be able to see what it says. I have all the latest drivers, BIOS, updates, run anti virus, malware bytes and spybot with no results for any of them. I am starting to think that this is a hardware issue because since I've had this computer, about a year and a half, it has always had sporadic BSODs and other issues. My specs, Vista Ultimate x64, Core 2 quad 9650, Intel DX48BT2 Mobo, OCZ platinum 12800 2x2 GB and a GTX 260. if you need any other information please PM or post here, I really need help this is driving me crazy!!![/QUOTE]
Press F8 after your PC restart from a BSOD, and toggle the BSOD auto-restart thingy so you can tell us what error code the BSOD has.
I suspect bad RAM if you're getting a BSOD that frequently. Try running Memtest and see if you have memory errors.
[url]http://www.memtest.org[/url]
[QUOTE=Mandalore777;21584654]It is not dumping memory to disk just because you cant see what it says? Sorry but that is false. Im going to need to see your minidump files from there I can bug check it and tell you the PROBABLE cause of these BSOD's and go from there. To do this simply go to start - > computer - > windows - > minidump inside youll see a ton of .dmp files since you said your computer is BSODing every 6-9 minutes. zip all those files up and upload them to speedyshare located here [url]http://www.speedyshare.com/[/url] hope this helps.[/QUOTE]
There are only 5 dump files in the folder, I know it was 6-9 minutes because of my Steam game timers would advance that much every time. Heres the upload [url]http://www.speedyshare.com/files/22162565/Dump_Files.zip[/url]
[code]*******************************************************************************
* *
* 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: fffffa7f93f66504, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000001, value 0 = read operation, 1 = write operation
Arg4: fffff9800445ab1d, address which referenced memory
Debugging Details:
------------------
WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff800025fa0b0
fffffa7f93f66504
CURRENT_IRQL: 2
FAULTING_IP:
USBPORT!USBPORT_Core_QueueTransferUrb+d5
fffff980`0445ab1d 418b1424 mov edx,dword ptr [r12]
CUSTOMER_CRASH_COUNT: 2
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0xD1
PROCESS_NAME: Idle
TRAP_FRAME: fffff8000349d5c0 -- (.trap 0xfffff8000349d5c0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000052547571 rbx=0000000000000000 rcx=fffffa8006978a60
rdx=000000004f444648 rsi=0000000000000000 rdi=0000000000000000
rip=fffff9800445ab1d rsp=fffff8000349d750 rbp=fffffa8007276310
r8=000000004f444648 r9=0000000000000000 r10=fffffa800390f000
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei ng nz na po nc
USBPORT!USBPORT_Core_QueueTransferUrb+0xd5:
fffff980`0445ab1d 418b1424 mov edx,dword ptr [r12] ds:5045:00000000`00000000=????????
Resetting default scope
LAST_CONTROL_TRANSFER: from fffff8000244d8f3 to fffff8000244db50
STACK_TEXT:
fffff800`0349d478 fffff800`0244d8f3 : 00000000`0000000a fffffa7f`93f66504 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
fffff800`0349d480 fffff800`0244c7cb : 00000000`00000001 fffffa80`06950050 70627375`00800000 00000000`01000111 : nt!KiBugCheckDispatch+0x73
fffff800`0349d5c0 fffff980`0445ab1d : fffffa80`000003e8 fffff980`0444b3e1 fffffa80`07276310 fffffa80`069501a0 : nt!KiPageFault+0x20b
fffff800`0349d750 fffff980`0446faab : fffffa80`07276310 fffffa80`52547571 fffffa80`07276310 00000000`80000300 : USBPORT!USBPORT_Core_QueueTransferUrb+0xd5
fffff800`0349d790 fffff980`0446f485 : fffffa80`069501a0 00000000`52546c61 fffffa80`06fd4830 fffffa80`07230500 : USBPORT!USBPORT_AsyncTransfer+0x8f
fffff800`0349d7c0 fffff980`044770ce : fffffa80`06a37050 fffffa80`06950050 fffffa80`07230500 fffffa80`06a30009 : USBPORT!USBPORT_ProcessURB+0x9d1
fffff800`0349d8a0 fffff980`04448562 : fffffa80`07230500 fffffa80`072306f0 fffffa80`04b3c670 00000000`00000000 : USBPORT!USBPORT_PdoInternalDeviceControlIrp+0x1ea
fffff800`0349d8f0 fffff980`0589c13c : fffffa80`06a39050 fffffa80`07123060 fffffa80`07230500 fffffa80`071231b0 : USBPORT!USBPORT_Dispatch+0x396
fffff800`0349d960 fffff980`058c754d : 00000000`00000000 00000000`00000000 fffffa80`07123060 fffff980`070837d5 : usbhub!UsbhFdoUrbPdoFilter+0xe0
fffff800`0349d990 fffff980`0589ab83 : fffffa80`07230c60 00000000`00000000 00000000`00000000 fffffa80`07230e53 : usbhub!UsbhPdoInternalDeviceControl+0x375
fffff800`0349d9e0 fffff980`07086180 : fffffa80`07385000 fffffa80`07423b10 00000000`0000000e fffffa80`04b3c6b0 : usbhub!UsbhGenDispatch+0x57
fffff800`0349da20 fffffa80`07385000 : fffffa80`07423b10 00000000`0000000e fffffa80`04b3c6b0 fffff800`029052a0 : WUSB54GCv3+0x71180
fffff800`0349da28 fffffa80`07423b10 : 00000000`0000000e fffffa80`04b3c6b0 fffff800`029052a0 fffffa80`07423b10 : 0xfffffa80`07385000
fffff800`0349da30 00000000`0000000e : fffffa80`04b3c6b0 fffff800`029052a0 fffffa80`07423b10 fffffa80`06b43a00 : 0xfffffa80`07423b10
fffff800`0349da38 fffffa80`04b3c6b0 : fffff800`029052a0 fffffa80`07423b10 fffffa80`06b43a00 fffff980`07086485 : 0xe
fffff800`0349da40 fffff800`029052a0 : fffffa80`07423b10 fffffa80`06b43a00 fffff980`07086485 fffffa80`07385000 : 0xfffffa80`04b3c6b0
fffff800`0349da48 fffffa80`07423b10 : fffffa80`06b43a00 fffff980`07086485 fffffa80`07385000 00000000`00000000 : hal!MasterAdapter32
fffff800`0349da50 fffffa80`06b43a00 : fffff980`07086485 fffffa80`07385000 00000000`00000000 fffffa80`07233470 : 0xfffffa80`07423b10
fffff800`0349da58 fffff980`07086485 : fffffa80`07385000 00000000`00000000 fffffa80`07233470 fffffa80`06951340 : 0xfffffa80`06b43a00
fffff800`0349da60 fffffa80`07385000 : 00000000`00000000 fffffa80`07233470 fffffa80`06951340 fffffa80`07385000 : WUSB54GCv3+0x71485
fffff800`0349da68 00000000`00000000 : fffffa80`07233470 fffffa80`06951340 fffffa80`07385000 00000000`06fd4830 : 0xfffffa80`07385000
STACK_COMMAND: kb
FOLLOWUP_IP:
WUSB54GCv3+71180
fffff980`07086180 ?? ???
SYMBOL_STACK_INDEX: b
SYMBOL_NAME: WUSB54GCv3+71180
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: WUSB54GCv3
IMAGE_NAME: WUSB54GCv3.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 48ace7ab
FAILURE_BUCKET_ID: X64_0xD1_WUSB54GCv3+71180
BUCKET_ID: X64_0xD1_WUSB54GCv3+71180
Followup: MachineOwner
---------
[/code]
All of your bsods pointed to a driver problem but this one specifically pointed to your WUSB54GCv3 if I was to guess this is a wireless access point is it not? by linskys maybe? Linskys drivers have been known to cause tons of problems resulting in blue screens such as my self I got blue screens due to these bad drivers all the time while gaming just as you did while you were playing Just Cause.
To fix this go to [url]http://www.bilal.ca/linksys-wusb54g-v4-x64-windows-7/[/url] and follow all the instructions this should work even though u have vista it worked for me and i hope this works for you too.
thanks, ill try and report back. where are the directions?
alright i thought the site had detailed instructions on how to do this. but apparently not. here is what you do.
1.Extract everything u see in the folder that u downloaded to your desktop.
2.open device manager
3. go to network adapters you should see your linskys card there.
4. right click and click update driver software
5. Select browse
6. Select let me pick
7. click have disk
8. Browse to your desktop and select the rt2500.inf file
9. It should install the driver after this if u do not see the file try putting all the files from the RAR file into a new folder and name it something like Ralink and try again.
Hope this helps.
hmm, dosent work, is this only for the v4? cause i have the v3
im not quite sure what kind of error messages are you getting?
well first i get this: [url=http://j.imagehost.org/view/0593/first][img]http://j.imagehost.org/t/0593/first.jpg[/img][/url] ill post pic of later error. but after that it takes like 45 mins to roll back the drivers
Ok, this is what it shows when its "done" updating. [url=http://j.imagehost.org/view/0065/second][img]http://j.imagehost.org/t/0065/second.jpg[/img][/url]
It's funny. Lately, I've been having the same issues, and I came to FP to see if anyone else is having the same issue. Turns out this guy and the other guy who has the same issue [i]also has a GTX 260[/i]. Is it just me, or is it random?
What brand is your 260?
I have a BFG one.
To pinpoint that it is actually the USB network adapter thats causing the problem try playing a game where you BSOD in with the USB network adapter unplugged. If you bsod again post up the minidump file and we'll look at it, this will also show that your network adapter is not causing the issue.
ok, ill test in a little while
ok, i played without the wifi card in and it still crashed, and again and again. [url]http://www.speedyshare.com/files/22197537/BSOD_minidump_v2.zip[/url] there are 4 from today.
[code]*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced. This cannot be protected by try-except,
it must be protected by a Probe. Typically the address is just plain bad or it
is pointing at freed memory.
Arguments:
Arg1: ffffffffe198ea16, memory referenced.
Arg2: 0000000000000001, value 0 = read operation, 1 = write operation.
Arg3: fffff960001e670f, If non-zero, the instruction address which referenced the bad memory
address.
Arg4: 0000000000000002, (reserved)
Debugging Details:
------------------
Could not read faulting driver name
WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff800025fa0b0
ffffffffe198ea16
FAULTING_IP:
win32k!bPEBCacheHandle+9f
fffff960`001e670f 488d15ea98e1ff lea rdx,[win32k!DereferenceW32Process <PERF> (win32k+0x0) (fffff960`00000000)]
MM_INTERNAL_CODE: 2
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0x50
PROCESS_NAME: explorer.exe
CURRENT_IRQL: 0
TRAP_FRAME: fffff980173c5fa0 -- (.trap 0xfffff980173c5fa0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000001 rbx=0000000000000000 rcx=000000000000a204
rdx=0000000000000002 rsi=0000000000000000 rdi=0000000000000000
rip=fffff960001e670f rsp=fffff980173c6130 rbp=0000000000000001
r8=0000000000000001 r9=fffff900c020ce58 r10=fffff900c1e6b2b0
r11=fffffa800877bbb0 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl nz na pe nc
win32k!bPEBCacheHandle+0x9f:
fffff960`001e670f 488d15ea98e1ff lea rdx,[win32k!DereferenceW32Process <PERF> (win32k+0x0) (fffff960`00000000)]
Resetting default scope
LAST_CONTROL_TRANSFER: from fffff800024538a9 to fffff8000244db50
STACK_TEXT:
fffff980`173c5e98 fffff800`024538a9 : 00000000`00000050 ffffffff`e198ea16 00000000`00000001 fffff980`173c5fa0 : nt!KeBugCheckEx
fffff980`173c5ea0 fffff800`0244c6d9 : 00000000`00000001 ffffffff`a2040899 fffff900`c1e05000 fffff900`c1eabc30 : nt!MmAccessFault+0x509
fffff980`173c5fa0 fffff960`001e670f : fffff900`c2a4f710 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x119
fffff980`173c6130 fffff960`0005b687 : ffffffff`a2040899 fffff980`173c6220 00000000`0000a204 fffff900`c020ce58 : win32k!bPEBCacheHandle+0x9f
fffff980`173c61a0 fffff960`0005b594 : fffff900`c1e6b2b0 fffff980`173c6530 fffff960`001c0f60 00000000`00000000 : win32k!RGNOBJAPI::bDeleteRGNOBJAPI+0xa7
fffff980`173c6200 fffff960`00086d0e : ffffffff`a2040899 fffff960`0001ef00 00000000`00000000 00000000`00000000 : win32k!bDeleteRegion+0x34
fffff980`173c6250 fffff960`0007dfe1 : 00000000`00000000 fffff960`0001ef97 00000000`00000000 00000000`00000000 : win32k!NtGdiDeleteObjectApp+0x9e
fffff980`173c6280 fffff800`0244d4fc : fffffa80`0877bbb0 fffff980`173c6530 ffffffff`00000001 00000000`02322920 : win32k!NtGdiFlushUserBatch+0xca1
fffff980`173c64b0 000007fe`fe525d5a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceGdiTebAccess+0x25
00000000`03c4e228 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7fe`fe525d5a
STACK_COMMAND: kb
FOLLOWUP_IP:
win32k!bPEBCacheHandle+9f
fffff960`001e670f 488d15ea98e1ff lea rdx,[win32k!DereferenceW32Process <PERF> (win32k+0x0) (fffff960`00000000)]
SYMBOL_STACK_INDEX: 3
SYMBOL_NAME: win32k!bPEBCacheHandle+9f
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: win32k
IMAGE_NAME: win32k.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4a857206
FAILURE_BUCKET_ID: X64_0x50_win32k!bPEBCacheHandle+9f
BUCKET_ID: X64_0x50_win32k!bPEBCacheHandle+9f
Followup: MachineOwner
---------
[/code] all these crash dumps seem to point to system files/drivers/and processes. My first guess is you need to reformat but lets check some other possible issues before we go and do that.
1. Have you tried running memtest? The issue could be with your RAM not handling information properly.
To check your memory follow these steps [code]1. Go to http://www.memtest.org/#downiso and download the zip file.
2. Go to http://www.imgburn.com/ and download it this will mount the ISO onto the disk and also analyze it for you and even clear up disks if u dont have a blank one.
3. Reboot PC with the CD inside.
4. Your pc will now boot into memtest please allow it to run for 5 passes at minimum it may take a few hours to get done.
5. Be sure to take out a stick of RAM and do one at a time and alternate slots if you do receive errors this will help pinpoint which RAM stick is causing it.
NOTE: When you are handling PC parts be sure you are GROUNDED the smallest static discharge can damage these parts touch something metal or be on a wood floor do not do this on a carpet if you do though just be sure your touching something metal like a heater. [/code]
2. Your hard drive might be dieing or it could be riddled with errors to check your hard drive go to start type "chkdsk" (without the quotes) right click run as admin let it run through its thing and tell us if you get any errors.
3. A driver could be causing this issue to check them follow this guide [url]http://www.techsupportforum.com/microsoft-support/windows-vista-windows-7-support/473665-driver-verifier-windows-7-vista.html[/url] and follow it exactly if you dont your pretty much going to be forced to reformat.
4. Update your drivers for all hardware.
5. You could just reformat and cross your fingers that it fixes itself.
I'll try all that stuff, and thanks for all this help. One thing that may help is that I reformatted about 3 weeks ago, and right after the format i was still getting BSODs.
alright let us know the results.
So Verifier has been running for 5 hours and my computer hasn't crashed! I'm waiting for that to finish before doing the memory check.
have u been doing your normal activities such as playing games etc where bsods usually happen?
yeah, I don't know what happened, its weird not crashing.
damn it, not 10 minutes after this it crashed, it flashed a blue screen and i had to hard restart it, i snapped a pic before i did and will see if there's any new dump files. here is the pic, and no new dumps (lol) [url=http://j.imagehost.org/view/0356/0430002208][img]http://j.imagehost.org/t/0356/0430002208.jpg[/img][/url]
did driver verifier say it caught a violation? I think this issue could be with your video card because what driver verifier does is it puts stress on all the drivers you selected and it seems your display driver crashed while running the verifier and it failed to recover. Have you updated your video card drivers to the latest ones?
The verifier didnt say it had caught anything, and yes the drivers are the latest and always have been
Try using [url]http://www.guru3d.com/category/driversweeper/[/url] and try and do a quick registry clean up using [url]http://www.pctools.com/registry-mechanic/download/[/url]
I'm considering selling all my parts and starting fresh
Sorry, you need to Log In to post a reply to this thread.