Solution
Code:
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1A, {41790, fffffa80047f3fd0, ffff, 0}
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+35084 )
Followup: MachineOwner
Code:
PROCESS_NAME: Jingling.exe
Hi,
your pc blue screened whilst using the above process. jingling.exe. This app is apparently for...
kemical
Essential Member
- Joined
- Aug 28, 2007
- Messages
- 36,176
You have this version?:VirtDiskBus64.sys: I have the last one
3TB+ unlock
B12.1102.01:
6.21 MB:
2012/11/02
http://www.gigabyte.com/products/product-page.aspx?pid=3863#utility
Yours is dated 2011 so I'm not sure that you do.
Also for gdrv.sys do a search and if you find it, break the driver by renaming to something like gdrv.old.
kemical
Essential Member
- Joined
- Aug 28, 2007
- Messages
- 36,176
Code:
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1A, {5003, fffff70001080000, 191e, 191c0800323c}
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+2984f )
Followup: MachineOwner
---------
0: kd> !analyze -v;r;kv;lmtsmn;.bugcheck;!peb;!sysinfo cpuinfo;!sysinfo machineid; !sysinfo cpuspeed; !sysinfo smbios
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
MEMORY_MANAGEMENT (1a)
# Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 0000000000005003, The subtype of the bugcheck.
Arg2: fffff70001080000
Arg3: 000000000000191e
Arg4: 0000191c0800323c
ref:0x5003 : The working set free list is corrupt. This is probably a hardware error.
https://msdn.microsoft.com/en-us/library/windows/hardware/ff557391(v=vs.85).aspx
Hi,
You possibly have some bad RAM. Even Memtest86 doesn't catch everything and personally I would try running your machine on one stick of RAM. See if it run's ok and then swap over to try the next. Do this until a bad stick is found (which blue screens).
You need to update the Intel chipset drivers. Please run the update utility:
Link Removed
gdrv.sys Fri Mar 13 03:22:29 2009: Gigabyte Easy Saver - mobo power utility driver please either remove or update.
If your having trouble removing it try using this app:
http://www.revouninstaller.com/
(trial version)
kemical
Essential Member
- Joined
- Aug 28, 2007
- Messages
- 36,176
Judging by the above dump file it didn't update them all and i would try updating your Intel drivers as advised. Using third party apps to find your drivers is ok but not perfect. Your far better sourcing drivers yourself. Your system will thank you for it by running better and you'll also understand your system better.
kemical
Essential Member
- Joined
- Aug 28, 2007
- Messages
- 36,176
Sounds like you might have either some corruption within the os or possible malware infection?
Try running an sfc scan. Run command prompt as administrator, type:
sfc /scannow
press enter and await results.
Download a copy of malwarebytes:
https://www.malwarebytes.org/mwb-download/
Try running an sfc scan. Run command prompt as administrator, type:
sfc /scannow
press enter and await results.
Download a copy of malwarebytes:
https://www.malwarebytes.org/mwb-download/
Similar threads
- Featured
- Article
- Replies
- 0
- Views
- 2K
- Replies
- 1
- Views
- 646
- Solved
- Replies
- 3
- Views
- 1K
- Featured
- Article
- Replies
- 0
- Views
- 17